Processed: Bug#749797: papi: FTBFS as non-root: ldconfig not in PATH
Processing commands for cont...@bugs.debian.org: # setting severity back to normal : Debian builders are not impacted severity 749797 normal Bug #749797 [papi] papi: FTBFS as non-root: ldconfig not in PATH Severity set to 'normal' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 749797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749797: papi: FTBFS as non-root: ldconfig not in PATH
severity #749797 whishbug thanks On 29/05/2014 23:06, Michael Tautschnig wrote: Package: papi Version: 5.3.0-3 Severity: serious Are you kidding ? If you build a package in a non-standard environment, there is no certitude that it will build correctly. There is way too much building environments to support all of them. You might ask for support for another one with a whishbug but do to try to remove the software from Debian if it does not build in your non-standard environment! Note that using fakeroot should be a very quick workaround and I'm sure that *lots* of packages do not build without fakeroot. As non-root builds should not fail, Where does this should come from? Policy? And *non-root build does not fail* if you use fakeroot (I never build my packages as root myself!) and it should probably also work (not tested) if /sbin is added in your PATH. please use the full path here. I'm really not convinced with your argument. If I do this modification, it wont be possible to test another ldconfig implementation with just adjusting the PATH envvar. Regards, Vincent -- Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749797: papi: FTBFS as non-root: ldconfig not in PATH
Hello Vincent, [...] Are you kidding ? If you build a package in a non-standard environment, there is no certitude that it will build correctly. There is way too much building environments to support all of them. You might ask for support for another one with a whishbug but do to try to remove the software from Debian if it does not build in your non-standard environment! I'm well aware that there may be specifics to my build environment and certainly I wouldn't have filed an RC bug if it were to be attributed to such an aspect. Note that using fakeroot should be a very quick workaround and I'm sure that *lots* of packages do not build without fakeroot. As non-root builds should not fail, Where does this should come from? Policy? And *non-root build does not fail* if you use fakeroot (I never build my packages as root myself!) and it should probably also work (not tested) if /sbin is added in your PATH. please use the full path here. I'm really not convinced with your argument. If I do this modification, it wont be possible to test another ldconfig implementation with just adjusting the PATH envvar. Well, the change was just a proposal, you might want to go for an entirely different solution. (Indeed I'm not sure why ldconfig is being run at all.) So let's try to work out the (non-)standard build environment first. Here's what I now did: ssh m...@barriere.debian.org (pick any porterbox of your choice) schroot -c sid (install wget, build-deps of papi) dget http://ftp.de.debian.org/debian/pool/main/p/papi/papi_5.3.0-3.dsc dpkg-source -x *.dsc cd papi-5.3.0/ dpkg-buildpackage -rfakeroot (...) make[1]: Entering directory '/home/mt/papi-5.3.0' find debian/libpapi5.3/usr/lib/x86_64-linux-gnu -type l -name 'libpapi.so.*' | xargs -r rm -v removed 'debian/libpapi5.3/usr/lib/x86_64-linux-gnu/libpapi.so.5.3.0' removed 'debian/libpapi5.3/usr/lib/x86_64-linux-gnu/libpapi.so.5' ldconfig -n -v debian/libpapi5.3/usr/lib/x86_64-linux-gnu make[1]: ldconfig: Command not found debian/rules:46: recipe for target 'override_dh_shlibdeps' failed make[1]: *** [override_dh_shlibdeps] Error 127 make[1]: Leaving directory '/home/mt/papi-5.3.0' debian/rules:24: recipe for target 'binary' failed make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 (sid_amd64-dchroot)mt@barriere:~/papi-5.3.0$ In my opinion that should qualify as a standard build environment, but arguably it's not sbuild. Thanks a lot, Michael pgpCuTzuD5a9x.pgp Description: PGP signature
Bug#749797: papi: FTBFS as non-root: ldconfig not in PATH
Hi, On 30/05/2014 11:47, Michael Tautschnig wrote: Hello Vincent, [...] Are you kidding ? If you build a package in a non-standard environment, there is no certitude that it will build correctly. There is way too much building environments to support all of them. You might ask for support for another one with a whishbug but do to try to remove the software from Debian if it does not build in your non-standard environment! I'm well aware that there may be specifics to my build environment and certainly I wouldn't have filed an RC bug if it were to be attributed to such an aspect. The fact is that, to my knowledge, the package successfully builds on all Debian build machines. Note that I was not arguing against the fact that this is a bug, only about the severity. Seeing with your answer that the bug is still there with dpkg-buildpackage -rfakeroot I would give it the normal or important severity. But not more (ie not RC) as official Debian build machine correctly work. Well, the change was just a proposal, you might want to go for an entirely different solution. (Indeed I'm not sure why ldconfig is being run at all.) Look at the sources, I'm not sure myself. The call has been added by Andreas so I will wait for him to comment. Regards, Vincent So let's try to work out the (non-)standard build environment first. Here's what I now did: ssh m...@barriere.debian.org (pick any porterbox of your choice) schroot -c sid (install wget, build-deps of papi) dget http://ftp.de.debian.org/debian/pool/main/p/papi/papi_5.3.0-3.dsc dpkg-source -x *.dsc cd papi-5.3.0/ dpkg-buildpackage -rfakeroot (...) make[1]: Entering directory '/home/mt/papi-5.3.0' find debian/libpapi5.3/usr/lib/x86_64-linux-gnu -type l -name 'libpapi.so.*' | xargs -r rm -v removed 'debian/libpapi5.3/usr/lib/x86_64-linux-gnu/libpapi.so.5.3.0' removed 'debian/libpapi5.3/usr/lib/x86_64-linux-gnu/libpapi.so.5' ldconfig -n -v debian/libpapi5.3/usr/lib/x86_64-linux-gnu make[1]: ldconfig: Command not found debian/rules:46: recipe for target 'override_dh_shlibdeps' failed make[1]: *** [override_dh_shlibdeps] Error 127 make[1]: Leaving directory '/home/mt/papi-5.3.0' debian/rules:24: recipe for target 'binary' failed make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 (sid_amd64-dchroot)mt@barriere:~/papi-5.3.0$ In my opinion that should qualify as a standard build environment, but arguably it's not sbuild. Thanks a lot, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749797: papi: FTBFS as non-root: ldconfig not in PATH
Hi Vincent, Andreas, [...] The fact is that, to my knowledge, the package successfully builds on all Debian build machines. That's true (with the exception of s390x, but that's a completely different issue) - it seems the buildds, according to the logs, have /sbin in the PATH. Note that I was not arguing against the fact that this is a bug, only about the severity. Seeing with your answer that the bug is still there with dpkg-buildpackage -rfakeroot I would give it the normal or important severity. But not more (ie not RC) as official Debian build machine correctly work. I'm absolutely fine with this, I'm not going to argue with the maintainer about severity. I'd just use serious as my default severity for FTBFS as I cannot generally tell whether the official buildds work around that problem in some way. Well, the change was just a proposal, you might want to go for an entirely different solution. (Indeed I'm not sure why ldconfig is being run at all.) Look at the sources, I'm not sure myself. The call has been added by Andreas so I will wait for him to comment. [...] So, Andreas, why was that change http://anonscm.debian.org/gitweb/?p=collab-maint/papi.git;a=commit;h=a37ddbb5f2eb6cee322ff104d9f05c4fa6127ee8 necessary? I can see what it does, but I'm not sure why that would be necessary in the first place (after all, the links ought to be correct at the end of the build process anyway). Best, Michael pgpxx3ys2a8hd.pgp Description: PGP signature
Bug#749797: papi: FTBFS as non-root: ldconfig not in PATH
Package: papi Version: 5.3.0-3 Severity: serious Usertags: goto-cc During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder) the build failed with the following error. [...] make[1]: Entering directory '/srv/jenkins-slave/workspace/sid-goto-cc-papi/papi-5.3.0' find debian/libpapi5.3/usr/lib/x86_64-linux-gnu -type l -name 'libpapi.so.*' | xargs -r rm -v removed 'debian/libpapi5.3/usr/lib/x86_64-linux-gnu/libpapi.so.5.3.0' removed 'debian/libpapi5.3/usr/lib/x86_64-linux-gnu/libpapi.so.5' ldconfig -n -v debian/libpapi5.3/usr/lib/x86_64-linux-gnu make[1]: ldconfig: Command not found debian/rules:46: recipe for target 'override_dh_shlibdeps' failed In all likelihood this problem is caused by building as non-root user, who will not have /sbin/ldconfig in their path. As non-root builds should not fail, please use the full path here. Best, Michael pgpEFElVQviaK.pgp Description: PGP signature
