December 2014

[opensuse-packaging] Python 2 and 3 in single specfile
by Jan Matějek 22 Jul '15

22 Jul '15

Fellow packagers, after some discussions in our team, we figured that it would be neat if we could build python modules for Python 2 and 3 from a single spec file. Now that a great deal of python modules work with both pythons, this makes a lot of sense. A good deal of work can be done by RPM macros. Then we could even seamlessly start building modules for PyPy, Jython and other pythons. A sample specfile, and the corresponding set of RPM macros, is attached. As you can see, the appropriate … [View More]

3 5

[opensuse-packaging] Using autogen.sh in a spec file?
by Johannes Kastl 12 Jan '15

12 Jan '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, sorry if this is an old hat, but I just stumbled upon it. lxc changed the sources layout between 1.0.x and 1.1, and no longer directly includes a configure file. So it has to be generated via ./autogen.sh. What's the right way to do this in a spec file? Just call the autogen.sh script? Or is there a macro for it? I found an older mail from Ludwig (and others), where %_configure is being redefined to run autogen.sh http://lists.… [View More]

6 9

[opensuse-packaging] File-package-in-two-packages-error only on 13.1?
by Johannes Kastl 27 Dec '14

27 Dec '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Evening everybody, is there a reason why the following is an error only on 13.1, and not on 13.2? > ERROR: /usr/sbin/rclxc is packaged in both lxc-libs and lxc, and > the packages do not conflict The package is here, and as you can see, it builds fine for > https://build.opensuse.org/package/live_build_log/home:ojkastl_buildservice… Is > this intentional? Or what am I missing? (The solution is to exclude the link in the files … [View More]

2 3

[opensuse-packaging] have a choice
by Peter Czanik 20 Dec '14

20 Dec '14

Hi, I did not change anything other than updating the syslog-ng version (3.6.1 to 3.6.2), but yesterday my syslog-ng package compiled on SLES 12, and today not any more. I get the following error: Getting buildconfig from server and store to /root/home:czanik:syslog-ng36/syslog-ng/.osc/_buildconfig-SLE_12-x86_64 buildinfo is broken... it says: unresolvable: have choice for syslog needed by syslog-service: syslog-ng rsyslog Why do I get this error, and how can I resolve this? As you can … [View More]

2 1

[opensuse-packaging] Binary packages not being published?
by Erico Mendonca 19 Dec '14

19 Dec '14

Hello all, I have (one of many) weird problems with Build Service. Here's the first one. :-) I built this package: https://build.opensuse.org/package/show/home:emendonca:branches:devel:langu… Which has an _aggregate on another branched project and two packages: <aggregatelist> <aggregate project="home:emendonca:branches:devel:languages:perl"> <package>perl-Gnome2-Vte</package> <package>perl-macros</package> <repository target="SLE_11" … [View More]

4 4

[opensuse-packaging] How to force a forked package to stay?
by Stanislav Baiduzhyi 18 Dec '14

18 Dec '14

Let's say I have a fork of one of the packages that comes with system core. That fork is targeted for very special target audience or special use-cases, so please no flaming on the topic of how wrong is it to do something like that... But, that fork consists of libs and devel packages, and every time update for this package comes in main repository - it gets replaced with updated non- forked version. Or someone installs lib from official version and devel from forked version, which is … [View More]

4 9

[opensuse-packaging] How to use gcc49 at OBS
by Dmitriy Perlow 17 Dec '14

17 Dec '14

Hi to all! How gcc49 can be used for oS 13.2? If it is required to build unresolvable state will appear with message "conflict for provider of libgcc_s1 >= 4.9.0+r211729-2.1.7 needed by gcc49, (provider libgcc_s1-gcc49 is conflicted by installed libgcc_s1)". By the way gcc49 isn't my goal, I would like to make a clang build with gcc 4.9' environment so any tips are welcomed. -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-packaging+… [View More]

5 10

[opensuse-packaging] new rpmlint-Factory-strict failures in TW
by Olaf Hering 16 Dec '14

16 Dec '14

All Factory and TW packages in packman start to fail because for some reason rpmlint-Factory-strict-1.0-89.115 is now installed. This seems to include a license check, which is most likely needed just in OBS and IBS. I wonder if this was a change in OBS, and if so how can I can avoid to change a very large amount of spec files. If this was caused by the update of the buildservice version in PMBS, what is the knob to disable rpmlint-Factory-strict again? http://lists.links2linux.de/pipermail/… [View More]

2 5

[opensuse-packaging] Can Cacti package be updated to 0.8.8c from 0.8.8b
by doiggl＠velocitynet.com.au 14 Dec '14

14 Dec '14

Hello Can Cacti package be updated to 0.8.8c from 0.8.8b http://forums.cacti.net/viewtopic.php?f=8&t=53725 https://build.opensuse.org/package/show/server:monitoring/cacti Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 5

[opensuse-packaging] SuSE version macros
by Michael Ströder 13 Dec '14

13 Dec '14

HI! Is there a comprehensible list/table of SuSE version macros usable in .spec files and some hints how they should be used? I'm having a hard time to distinguish SLES 11SP3, SLES12 and openSUSE 13.1+ to set right dependencies. Ciao, Michael.

4 5

[opensuse-packaging] -rpath /usr/lib64/modules
by Michael Ströder 10 Dec '14

10 Dec '14

HI! I'm still trying to get this to build: https://build.opensuse.org/package/show/home:stroeder:branches:network:ldap… Although I set ./configure --libexecdir=/usr/lib64 for some reason the build log shows that the OpenLDAP standard backend and overlay modules get installed into ${RPM_BUILD_ROOT}/usr/lib64/modules instead of ${RPM_BUILD_ROOT}/usr/lib64/openldap. Is /usr/lib64/modules coming from some magic macro? Any hint is appreciated. Ciao, Michael.

5 13

[opensuse-packaging] $RPM_BUILD_ROOT/%{_sysconfdir}/openldap/schema
by Michael Ströder 09 Dec '14

09 Dec '14

Disclaimer: I'm not a packaging expert. I'm just trying to update packages here and there. In the current case I'm fighting with a strange problem here: https://build.opensuse.org/package/show/home:stroeder:branches:network:ldap… It seems %{_sysconfdir} expands to /usr/local/etc but only in some cases. Build always fails like this: ------------------- snip ------------------- [ 224s] cp ldapns.schema /home/abuild/rpmbuild/BUILDROOT/openldap2-2.4.40-0.x86_64/usr/local/etc/openldap/schema [ … [View More]

4 6

[opensuse-packaging] ifdef troubles
by Peter Czanik 05 Dec '14

05 Dec '14

Hi, Anybody still awake late Friday afternoon? If so, please take a look at the syslog-ng.spec file at https://build.opensuse.org/package/show/home:czanik:syslog-ng36/syslog-ng as I can't figure out, why riemann-c-client-devel is marked as unresolvable on SLES12. Yes, it's unavailable for SLES12, but it's also switched off in the spec file just as other unavailable dependencies. Bye, CzP -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] systemd service presets: branding files or packages?
by Stanislav Brabec 04 Dec '14

04 Dec '14

I would like to open a discussion about use of systemd presets while packaging. Systemd preset files are preferred way how packages set the default state of services. Preset files are located in /usr/lib/systemd/system-preset directory. %service_add_post is aware of presets, and if the package adds systemd service together with presets, %service_add_post performs one-time set to the preset default state. Current policy is simple: All presets belongs to: systemd-presets-branding-{product} /usr/… [View More]

12 46

[opensuse-packaging] kmp packages fail for 13.2 but nor errors in build log
by Vitaliy Tomin 04 Dec '14

04 Dec '14

Hello, I have some kmp packages in my home project https://build.opensuse.org/project/monitor/home:HighwayStar:hardware All of them builds fine for openSUSE 12.3 and 13.1 but fails for 13.2. Cant find any reason for that. Build logs show only minor warnings and no errors. Is it something wrong with buildservice or with my specfiles? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

Re: [opensuse-packaging] [RESOLVED] Need help with gdb, debuginfo, etc.
by Greg Freemyer 03 Dec '14

03 Dec '14

-- Greg Freemyer On Wed, Dec 3, 2014 at 11:45 AM, Jan Engelhardt <jengelh(a)inai.de> wrote: > > On Wednesday 2014-12-03 17:43, Greg Freemyer wrote: > >>I have the debuginfo rpms installed: >> >>-- >>$ rpm -qa | grep tsk >>python-tsk-debuginfo-0~20140506-5.1.x86_64 >>python-tsk-0~20140506-5.1.x86_64 >>libtsk10-debuginfo-4.1.3-4.1.x86_64 >>libtsk10-4.1.3-4.1.x86_64 >>=============== >>(Pdb) cont >>*** Error in `/… [View More]

1 0

[opensuse-packaging] Need help with gdb, debuginfo, etc.
by Greg Freemyer 03 Dec '14

03 Dec '14

All, note: I haven't used gdb much in a decade., so look for something obvious I'm doing wrong. I maintain libtsk and I've got a bug in libtsk I'm trying to troubleshoot with upstream. I have the debuginfo rpms installed: -- $ rpm -qa | grep tsk python-tsk-debuginfo-0~20140506-5.1.x86_64 python-tsk-0~20140506-5.1.x86_64 libtsk10-debuginfo-4.1.3-4.1.x86_64 libtsk10-4.1.3-4.1.x86_64 -- python-tsk is just a python binding for libtsk. I ran the higher level app in gdb and this is the top of … [View More]

2 1

Main

Development

Information

Community

Social Media

Other

openSUSE Packaging