Bug#896019: libglib2.0-0: undefined symbol g_date_copy breaking many programs

Xilin Sun s.sn.giraffe at gmail.com
Tue Dec 4 04:10:02 GMT 2018


On Mon, 23 Apr 2018 17:47:56 +0100 Simon McVittie <smcv at debian.org> wrote:
> On Mon, 23 Apr 2018 at 17:11:11 +0200, Michael Biebl wrote:
> > @smcv: Do you think this is a failure of dpkg/apt cleaning up old
> > versions? My suspicion is rather, that there is some old copy of libglib
> > lying around in /lib/x86_64-linux which was copied there by some 3rd
> > party installer, possibly lying around for years there.
>
> That's entirely possible.

By comparing the file lists of package libglib2.0-0 in stretch and
sid, I think the old copy of libglib in /lib/x86_64-linux was
introduced by the package itself, not 3rd party installers.

stretch: https://packages.debian.org/stretch/amd64/libglib2.0-0/filelist

/lib/x86_64-linux-gnu/libglib-2.0.so.0
/lib/x86_64-linux-gnu/libglib-2.0.so.0.5000.3
...

sid: https://packages.debian.org/sid/amd64/libglib2.0-0/filelist

...
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5800.1
...



More information about the pkg-gnome-maintainers mailing list