Bug#560120: libcanberra: FTBFS: Mismatch in dpkg-gensymbols
Gone ahead and reverted the change. You may want to close this bug by passing -Xlibcanberra-alsa.so to dh_makeshlibs, both so it doesn't include that library in the shlibs file, and so it doesn't FTBFS again when you switch to debhelper v8 later. -- see shy jo signature.asc Description: Digital signature
Bug#560120: libcanberra: FTBFS: Mismatch in dpkg-gensymbols
Daniel Schepler wrote: > CC to debhelper maintainer to ask: It seems that until recently, debhelper > would ignore these plugins in subdirectories of /usr/lib. Was this change > in behavior intentional? If so, I don't see any entries in the debhelper > changelog about it, at least with a quick scan for dh_makeshlibs. (See also > bug #559657.) I think there was an inaverdent behavior change caused by #557603. dh_makeshlibs has always generated shlibs files for anything that looks like a legitimate shared library, no matter where it is located. However, before Peter's change, it ran dpkg-gensymbols and let it use its own search methods to find shared libraries -- which does only look in well known library directories. If this has the potential to break a lot of package's builds, I may need to revert that change and only enable it in the next compatability level. -- see shy jo signature.asc Description: Digital signature
Bug#560120: libcanberra: FTBFS: Mismatch in dpkg-gensymbols
Source: libcanberra Version: 0.22-1 Severity: serious X-Debbugs-CC: Joey Hess From my pbuilder build log: ... dh_fixperms -plibcanberra0 dh_makeshlibs -plibcanberra0 --exclude=usr/lib/gtk-2.0/modules --exclude=/usr/lib/libcanberra-0.20 -V "libcanberra0 (>= 0.20)" -- -c4 dpkg-gensymbols: warning: new libraries appeared in the symbols file: libcanberra-alsa.so dpkg-gensymbols: warning: debian/libcanberra0/DEBIAN/symbols doesn't match completely debian/libcanberra0.symbols --- debian/libcanberra0.symbols (libcanberra0 amd64) +++ dpkg-gensymbols_HNnPL 2009-12-08 13:00:48.0 + @@ -1,3 +1,12 @@ +libcanberra-alsa.so libcanberra0 #MINVER# + alsa_driver_ca...@base 0.22-1+pb1 + alsa_driver_can...@base 0.22-1+pb1 + alsa_driver_change_dev...@base 0.22-1+pb1 + alsa_driver_change_pr...@base 0.22-1+pb1 + alsa_driver_dest...@base 0.22-1+pb1 + alsa_driver_o...@base 0.22-1+pb1 + alsa_driver_p...@base 0.22-1+pb1 + driver_play...@base 0.22-1+pb1 libcanberra.so.0 libcanberra0 #MINVER# * Build-Depends-Package: libcanberra-dev canberr...@canberra_0 0.3 dh_makeshlibs: dpkg-gensymbols -plibcanberra0 -Idebian/libcanberra0.symbols -Pdebian/libcanberra0 -edebian/libcanberra0/usr/lib/libcanberra-0.22/libcanberra-alsa.so -edebian/libcanberra0/usr/lib/libcanberra.so.0.2.1 -c4 returned exit code 4 make: *** [binary-fixup/libcanberra0] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 CC to debhelper maintainer to ask: It seems that until recently, debhelper would ignore these plugins in subdirectories of /usr/lib. Was this change in behavior intentional? If so, I don't see any entries in the debhelper changelog about it, at least with a quick scan for dh_makeshlibs. (See also bug #559657.) -- Daniel Schepler -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
