Bug#341945: Investigation of the bug
On Sat, Dec 10, 2005 at 11:18:53AM +0100, Enrico Zini wrote: Sorry to have been lingering on this bug: on Igloo's buildd report I saw that some of the packages were still rebuilding and I thought it was just a matter of waiting. Today I investigated a bit more. The problem is indeed connected to the C++ allocator thing, and the recompile was incomplete because debtags links statically with some libraries, and it's nonobvious to find the dependencies. Luckily, thanks to a suggestion of Jonas Smedegaard at Debconf4, I use dh_buildinfo. It turned out that the libtagcoll-dev is still built with libstdc++6 4.0.2-3. It in turn gets statically linked into libapt-front-dev, which in turn gets statically linked into debtags. So, it seems that there are some recompiles to be triggered: Step 1: libtagcoll-dev Step 2: tagcoll, tagcolledit, libapt-front-dev (since they statically link libtagcoll-dev) Step 3: debtags, debtags-edit, packagesearch (since they statically link libapt-front-dev) Could you perform these steps locally on your system and confirm that it does correct the failure, before we commit buildd time on all archs to rebuilding these? Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#341945: Investigation of the bug
On Sat, Dec 10, 2005 at 11:18:53AM +0100, Enrico Zini wrote: Hello, Sorry to have been lingering on this bug: on Igloo's buildd report I saw that some of the packages were still rebuilding and I thought it was just a matter of waiting. Today I investigated a bit more. The problem is indeed connected to the C++ allocator thing, and the recompile was incomplete because debtags links statically with some libraries, and it's nonobvious to find the dependencies. Luckily, thanks to a suggestion of Jonas Smedegaard at Debconf4, I use dh_buildinfo. It turned out that the libtagcoll-dev is still built with libstdc++6 4.0.2-3. It in turn gets statically linked into libapt-front-dev, which in turn gets statically linked into debtags. So, it seems that there are some recompiles to be triggered: Step 1: libtagcoll-dev Step 2: tagcoll, tagcolledit, libapt-front-dev (since they statically link libtagcoll-dev) Step 3: debtags, debtags-edit, packagesearch (since they statically link libapt-front-dev) BTW, due to the way static linking works, this is only two steps. libapt-front-dev doesn't *contain* the code from libtagcoll-dev; rather, the reverse-build-deps of libapt-front-dev pull this code in directly from libtagcoll-dev at build-time. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#341945: Investigation of the bug
On Sun, Dec 11, 2005 at 12:41:57AM -0800, Steve Langasek wrote: On Sat, Dec 10, 2005 at 11:18:53AM +0100, Enrico Zini wrote: So, it seems that there are some recompiles to be triggered: Step 1: libtagcoll-dev Step 2: tagcoll, tagcolledit, libapt-front-dev (since they statically link libtagcoll-dev) Step 3: debtags, debtags-edit, packagesearch (since they statically link libapt-front-dev) Could you perform these steps locally on your system and confirm that it does correct the failure, before we commit buildd time on all archs to rebuilding these? Sure. Done. It works. Here's the list of things I did: there are small mismatches with the list I gave above, as I was thinking more in terms of upstream deps than actual debian deps. * tagcoll apt-get source tagcoll cd tagcoll-1.5.1/ debuild -us -uc -rfakeroot cd .. su -c dpkg -i libtagcoll-dev_1.5.1-1_i386.deb tagcoll_1.5.1-1_i386.deb * tagcolledit apt-get source tagcolledit cd tagcolledit-1.2/ debuild -us -uc -rfakeroot cd .. su -c dpkg -i tagcolledit_1.2-1_i386.deb * libapt-front-dev apt-get source libapt-front-dev cd libapt-front-0.3.4/ debuild -us -uc -rfakeroot cd .. su -c dpkg -i libapt-front-dev_0.3.4_i386.deb * debtags apt-get source debtags cd debtags-1.5.2/ debuild -us -uc -rfakeroot cd .. su -c dpkg -i debtags_1.5.2_i386.deb * It works! * * debtags-edit apt-get source debtags-edit cd debtags-edit-1.1.2/ debuild -us -uc -rfakeroot cd .. su -c dpkg -i debtags-edit_1.1.2_i386.deb Haven't done packagesearch, but I think we have the idea. Ciao, Enrico -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#341945: Investigation of the bug
Version: 1.5.2+b2 On Sun, Dec 11, 2005 at 12:34:42PM +0100, Enrico Zini wrote: On Sun, Dec 11, 2005 at 12:41:57AM -0800, Steve Langasek wrote: On Sat, Dec 10, 2005 at 11:18:53AM +0100, Enrico Zini wrote: So, it seems that there are some recompiles to be triggered: Step 1: libtagcoll-dev Step 2: tagcoll, tagcolledit, libapt-front-dev (since they statically link libtagcoll-dev) Step 3: debtags, debtags-edit, packagesearch (since they statically link libapt-front-dev) Could you perform these steps locally on your system and confirm that it does correct the failure, before we commit buildd time on all archs to rebuilding these? Sure. Done. It works. Spiff. Closing the bug as fixed in the next binNMU then, which is already scheduled (along with the binNMUs for tagcolledit, debtags-edit, libapt-front, and packagesearch). Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#341945: Investigation of the bug
Hello, Sorry to have been lingering on this bug: on Igloo's buildd report I saw that some of the packages were still rebuilding and I thought it was just a matter of waiting. Today I investigated a bit more. The problem is indeed connected to the C++ allocator thing, and the recompile was incomplete because debtags links statically with some libraries, and it's nonobvious to find the dependencies. Luckily, thanks to a suggestion of Jonas Smedegaard at Debconf4, I use dh_buildinfo. It turned out that the libtagcoll-dev is still built with libstdc++6 4.0.2-3. It in turn gets statically linked into libapt-front-dev, which in turn gets statically linked into debtags. So, it seems that there are some recompiles to be triggered: Step 1: libtagcoll-dev Step 2: tagcoll, tagcolledit, libapt-front-dev (since they statically link libtagcoll-dev) Step 3: debtags, debtags-edit, packagesearch (since they statically link libapt-front-dev) Thanks, Enrico Thanks also to azeem and peterS who helped me figuring some details of the course of action to follow. -- GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini [EMAIL PROTECTED] signature.asc Description: Digital signature
