Hello,
is there a simple way to force the GCC version used to build a package?
openSUSE Leap 42.2 for example
uses GCC 4.8 as default compiler, but also provides packages for GCC
5.3. Simply using BuildRequires gcc5
pulls gcc5 in but still uses gcc48 to build the package (especially in
Build Service).
So is there maybe some Buid Service or spec file switch (bcond) to
select the used GCC version?
Best greetings
Matthias Fehring
P.S. Not sure if it is a problem with my browser settings, but when I
try to search lists.opensuse.org, it is not possible
for me to limit the results to a specific list. Even if I set one, I get
results from all lists, what makes searching almost
impossible, because most results are commit messages.
--
Das Gesetz hat zum Schneckengang verdorben, was Adlerflug geworden wäre.
(Friedrich Schiller - Die Räuber)
www.buschmann23.de
GPG-Key: 0x614C3258
GPG Fingerprint: D786 DDF8 4CA9 00BC CDE0 9A5F CCC5 125D 6E87 D4FC
Hi all,
As per complains here that we should use URL rather than Url in the
preamble of the spec-files I've decided to create quick doodle poll.
From parser perspective there is 0 difference but since there is vocal
proposition for URL instead of Url that is now replaced by spec-
cleaner.
I decided to create a poll where the majority will become default set
value. [1]
I will keep the doodle running until 14.8. and announce the results
afterwards and tweak spec-cleaner if other value wins.
I still think Url is fine as it is not URL in the "Uniform Resource
Locator" but just variable name.
Thanks for voting
Tom
[1] https://beta.doodle.com/poll/9y6gfunm8bm8cz3b
Hi!
I am currently working on updating the Microsoft Azure SDK for Python for SLE12SP2.
All of these Python packages use setuptools upstream which causes some problems on
SLE12SP2 because they use a feature not present in the old version of setuptools in
SLE12P2, namely the "~=" operator which is used to denote compatible versions in
Python. To resolve this problem, I simply patched the setup.py to replace "~=" with
">" and made sure the proper version dependencies are noted in the spec file.
This worked all fine and without problems until I worked on a package (python-azure-sdk)
that I branched from the devel:languages:python project. Although the package uses the
aforementioned operator in setup.py, the package still builds fine in a SLE12SP2 environment
without the necessary patch.
After digging some time, I noticed that the chroot for the package branched from
devel:languages:python was using a current version of setuptools, namely version
36.2.2 while my other packages were using the setuptools version present in
SLE12SP2 which is 1.10.x.
So, I have obviously the problem that OBS is enabling the devel:languages:python
repository for the build which it shouldn't. Is there a way to tell OBS which
repositories it's allowed to use during build and which not?
Or do I have to branch the package into a specific project to avoid the inclusion
of these particular repositories?
Thanks,
Adrian
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
On Jul 28 2017, Martin Pluskal <mpluskal(a)suse.cz> wrote:
> Removal of "BuildRequires: perl-libintl-perl" was intentional, as with
> external perl-libintl-perl internal testsuite does not work.
Did you file a bug?
Andreas.
--
Andreas Schwab, SUSE Labs, schwab(a)suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
devel:languages:python currently has two version of Django, the
up-to-date python-Django package and the obsolete python-django
package. The latter (python-django) has not been updated in two years,
and the up-to-date python-Django provides python-django.
However, there are still a few projects that link to it. I would like
to remove it, but I want to give other projects that link to it a
chance to it break the link and/or link to python-Django instead.
If there are no objections, I will remove python-django in one week,
on Friday, August 4.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
I'm trying to update mongo-tools [1] to version 3.4.6, and encounter an error
on the Leap-builds:
[ 210s] # github.com/mongodb/mongo-tools/common/archive
[ 210s] .gopath/src/github.com/mongodb/mongo-tools/common/archive/
demultiplexer.go:47: internal compiler error: haspointers: unexpected type,
NamespaceStatus map[string]int
[ 210s] error: Bad exit status from /var/tmp/rpm-tmp.7Px93a (%build)
This breaks on go 1.6.2 (Leap) but works for go 1.8.x (TW)
Should I report this upstream, or any other idea?
Cheers
Axel
[1] https://build.opensuse.org/package/show/home:DocB/mongo-tools
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
I have problem with format_spec_file, it moves comments to different lines for no obvious reason.
For example in SUSE:SLE-12-SP1:Update/tigervnc:
Snipped from original spec file:
Url: http://tigervnc.org/
BuildRoot: %{_tmppath}/%{name}-%{version}-build
Summary: A high-performance, platform-neutral implementation of VNC
License: GPL-2.0 and MIT
Group: System/X11/Servers/XF86_4
# would need fixing to use fPIC in common/CMakeLists.txt
ExcludeArch: s390
Source1: https://github.com/TigerVNC/tigervnc/archive/v%version}.tar.gz
Source3: vnc.xinetd
After format_spec_file:
Url: http://tigervnc.org/
BuildRoot: %{_tmppath}/%{name}-%{version}-build
Summary: A high-performance, platform-neutral implementation of VNC
# would need fixing to use fPIC in common/CMakeLists.txt
License: GPL-2.0 and MIT
Group: System/X11/Servers/XF86_4
ExcludeArch: s390
Source1: https://github.com/TigerVNC/tigervnc/archive/v%{version}.tar.gz
Source3: vnc.xinetd
The comment moved to a different line where it doesn't make sense.
Is it a bug in obs-service-format_spec_file?
Michal Srb
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Does anyone happen to know why perl-Text-Unicode overrides
perl-libintl-perl (or perl(Locale::Textdomain))?
devel:languges:perl/perl-Event-ExecFlow fails because libintl-perl is
not installed, even if specified as BuildRequires.
So far I have not spotted a Substitute or Provides/Obsoletes in prjconf.
Olaf