Re: The trigger in your Debian packages

On 2011-06-03 10:24, Raphael Hertzog wrote: > Please reply for the packages that you maintain to the question that > concerns you: > > 1/ If your package uses the "interest" directive in the triggers files, > is it important that the "triggering" packages that activate your triggers > be considere

Re: Bug#781649: ghc-doc: trigger problem during wheezy->jessie upgrade: haddock: error while loading shared libraries: libffi.so.6: cannot open shared object file: No such file or directory

On 2015-04-01 11:17, Joachim Breitner wrote: > eek. This is #769554 which I was hoping to have fixed by changing the > trigger to a trigger-noawait, but it seems that it has not helped. That is probably the correct solution, just we need to ensure that the new ghc-doc get installed early enough (o

Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

On 2018-01-18 21:45, Aurelien Jarno wrote: [...] Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ... /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /lib/i386-linux-gnu/libexpat.so.1) dpkg: warning: subprocess o

Re: Bug#887629: libc6: bad upgrade path: libexpat1 unpacked and python3 called before libc6 unpacked

On 2018-01-18 23:59, David Kalnischkies wrote: > Hi, > > On Thu, Jan 18, 2018 at 09:45:51PM +0100, Aurelien Jarno wrote: > [...] > Preparing to unpack .../3-libglib2.0-dev_2.54.3-1_i386.deb ... > /usr/bin/python3: /lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.25' > not found