December 2014 - openSUSE Packaging - openSUSE Mailing Lists

[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 [ 224s] cp: cannot create regular file '/home/abuild/rpmbuild/BUILDROOT/openldap2-2.4.40-0.x86_64/usr/local/etc/openldap/schema': No such file or directory [ 224s] Makefile:67: recipe for target 'install' failed [ 224s] make: *** [install] Error 1 [ 224s] error: Bad exit status from /var/tmp/rpm-tmp.SgHWLT (%install) [ 224s] [ 224s] [ 224s] RPM build errors: [ 224s] Bad exit status from /var/tmp/rpm-tmp.SgHWLT (%install) ------------------- snip ------------------- Even if I *remove* (for testing) this line from openldap2.spec it fails like above: ------------------- snip ------------------- install -m 644 *.schema $RPM_BUILD_ROOT/%{_sysconfdir}/openldap/schema ------------------- snip ------------------- Any hint what's going on is appreciated. Ciao, Michael.

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/lib/systemd/system-preset/90-default-openSUSE.preset and the default to disable all other: /usr/lib/systemd/system-preset/99-default-disable.preset It makes a lot of sense for packages with optional services, that should be always on, like apache, network servers etc. But I think that makes less sense for packages that are optional to install, but it they are installed and not active, they are broken. Especially if they are socket activated, the standby state means no more than one socket opened by systemd. I have two examples from last weeks: uuidd: Optional socket activated util-linux daemon providing support for UUIDs. pcsc-lite pcscd: Smart Card daemon that is socket activated whenever application attempts to use Smart Card PC/SC API. If it is not enabled, Smart Card access does not work. Note that it has a security implication: Each package that installs default-on preset, should be audited by security team. Security team would need to watch the whole directory, not only a branding file. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +49 911 7405384547 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz/ PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

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 `/usr/bin/python': free(): invalid pointer: 0x0000000025c4b120 *** >>======= Backtrace: ========= >>/lib64/libc.so.6(+0x730bf)[0x7ffff74da0bf] >>/lib64/libc.so.6(+0x7892e)[0x7ffff74df92e] >>/usr/lib64/libtsk.so.10(hfs_file_read_special+0x615)[0x7ffff02c5045] >>/usr/lib64/python2.7/site-packages/pytsk3.so(+0x1a2b9)[0x7ffff05a62b9] >>/usr/lib64/python2.7/site-packages/pytsk3.so(+0xb4ec)[0x7ffff05974ec] >>/usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x1295)[0x7ffff7af43e5] >>/usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x221)[0x7ffff7afa061] >>I expected to get line numbers on those lines. What am I doing wrong? > > pdb? can't say. But were it gdb, you want python-tsk-debugsource too. I'm invoking gdb as gdb, no idea why it is prompting as Pdb. My real issue is that when the segfault happens a low information back trace is dumped on my konsole screen. I assumed gdb was creating that. Apparently not. When I issue the "bt" command I get the output I expected. Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

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 the stack trace it generates: =============== (Pdb) cont *** Error in `/usr/bin/python': free(): invalid pointer: 0x0000000025c4b120 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x730bf)[0x7ffff74da0bf] /lib64/libc.so.6(+0x7892e)[0x7ffff74df92e] /usr/lib64/libtsk.so.10(hfs_file_read_special+0x615)[0x7ffff02c5045] /usr/lib64/python2.7/site-packages/pytsk3.so(+0x1a2b9)[0x7ffff05a62b9] /usr/lib64/python2.7/site-packages/pytsk3.so(+0xb4ec)[0x7ffff05974ec] /usr/lib64/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x1295)[0x7ffff7af43e5] /usr/lib64/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x221)[0x7ffff7afa061] ... ================ I expected to get line numbers on those lines. What am I doing wrong? Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1