Your message dated Tue, 13 Feb 2018 06:03:31 +0000
with message-id <>
and subject line Bug#879053: Removed package(s) from unstable
has caused the Debian Bug report #558622,
regarding Missing autoreconf to fix 554821 or similar bugs in the future
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Source: pygoocanvas
Version: 0.10.0-2
Severity: minor
Usertags: missing-libtool-update

I did a rebuild of all packages which are affected by bug #554821. As it seems
your package doesnt do the needed autoreconf needed for libtool. When doing
autoreconf or the needed sequence of different autotools/libtool utilities the
package should be able to fix the problem automatically.
/usr/share/doc/autotools-dev/README.Debian.gz explains it in section "Basic
summary of packaging source that uses autotools".

The build was done in a cowbuild chroot with the patch from #554821 included in
/usr/share/aclocal/libtool.m4 and binutils-gold installed. All logs were then
greped for -export-symbols-regex and not including -version-script. This
should indicate that your package doesnt do the required autoreconf with
updating the libtools stuff.

A small extra test output "test-version-script" was added to libtool.m4 and
silent mode was disabled in global so it is easier for me to decide if
it was really updated in case libtool doesnt output the ld command to stdout.
So if the output and "test-version-script" is missing then your program doesnt
update the files. I am sorry if this is still a false positive.

udev 147-5 for example fails completely due to new (unknown) symbols appearing
inside the .so, but `autoreconf -fi -I m4` (with libtool.m4 installed on my
system with the mentioned patch) fixes the problem. I had to remove a patch
with touches, but the rest worked out of the box. Maybe it is
better to copy all clean files into a extra directory, run autoreconf inside
the directory, build and install everything from that directory and in clean
remove that directory. This way the diff.gz should be clean and you still do
the necessary autoreconf. A package which does that is g3dviewer. Many other
packages like libupnp4 and compizconfig-python just ignore the fact that these
changes are included in debian.tar.gz/diff.gz

The interesting output inside the log of your program is:

/bin/bash ./libtool --tag=CC --mode=link cc  -g -O2 -g -Wall -O2 -std=c9x 
-fno-strict-aliasing   -o -rpath 
/usr/lib/python2.5/site-packages -module -avoid-version -export-symbols-regex 
initgoocanvas goocanvasmodule_la-goocanvasmodule.lo 
goocanvasmodule_la-goocanvas.lo -lgoocanvas -lgtk-x11-2.0 -lgdk-x11-2.0 
-latk-1.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lgio-2.0 
-lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 
generating symbol list for `'
/usr/bin/nm -B  .libs/goocanvasmodule_la-goocanvasmodule.o 
.libs/goocanvasmodule_la-goocanvas.o  | sed -n -e 's/^.*[    
]\([ABCDGIRSTW][ABCDGIRSTW]*\)[         ][      
]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | /bin/sed 's/.* //' | sort | uniq > 
/bin/grep -E -e "initgoocanvas" ".libs/goocanvasmodule.exp" > 
mv -f ".libs/goocanvasmodule.expT" ".libs/goocanvasmodule.exp"
cc -shared  .libs/goocanvasmodule_la-goocanvasmodule.o 
.libs/goocanvasmodule_la-goocanvas.o  -lgoocanvas /usr/lib/ 
/usr/lib/ /usr/lib/ /usr/lib/ 
/usr/lib/ -lm /usr/lib/ 
/usr/lib/ /usr/lib/ /usr/lib/ 
-lfontconfig /usr/lib/ /usr/lib/ 
/usr/lib/ /usr/lib/  -Wl,-soname 
-Wl, -o .libs/
(cd .libs && rm -f && ln -s ../
make[3]: Leaving directory 

--- End Message ---
--- Begin Message ---
Version: 0.14.1-1.3+rm

Dear submitter,

as the package pygoocanvas has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see

The version of this package that was in Debian prior to this removal
can still be found using

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing

Debian distribution maintenance software
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to