Phillip Susi wrote:
> Sorry for the delayed response, but what?
Sorry for the nonsense. What I was fumbling to say was that it had
been many months since this last came up with nothing changed but
still you were asking "Is this a bug in apt?". It seemed more like a
time to act, for example by f
On 5/10/2011 10:17 PM, Jonathan Nieder wrote:
Yes, I suppose it is a bug in apt.
Wait a second: I feel like I've been in this conversation before. Did
anything change in light of previous replies?
http://thread.gmane.org/gmane.linux.debian.devel.dpkg.general/12500
Sorry for the delayed resp
Jonathan Nieder wrote:
> Phillip Susi wrote:
>> Is this a bug in apt? It shouldn't have installed the new version of
>> e2fslibs while the old version of e2fsprogs was still installed and
>> pre-depending on it should it?
>
> Yes, I suppose it is a bug in apt.
Wait a second: I feel like I've bee
Phillip Susi wrote:
> After it finished, I tried running apt-get dist-upgrade, and it
> complains that e2fsprogs has unmet deps because it pre-depends on the
> old version of e2fslibs, but the new version of e2fslibs is installed.
>
> Is this a bug in apt? It shouldn't have installed the new vers
.log to try and figure out why.
>
> Becaue apt has not been changed to tell dpkg to defer trigger processing,
> and to them run them all at the end. Or rather, it has, see
> http://bugs.debian.org/473461 -- but they do not have the options
> enabled by default.
>
> DPkg
&g
Phillip Susi wrote:
> I've noticed triggers being invoked repeatedly during upgrades rather
> than once at the end, as they are supposed to. I started looking at
> /var/log/dpkg.log to try and figure out why.
Becaue apt has not been changed to tell dpkg to defer trigger processin
(+bcc: a hypothetical debian-dpkg-frontends@ list)
Phillip Susi wrote:
> I've noticed triggers being invoked repeatedly during upgrades rather
> than once at the end, as they are supposed to.
[...]
> Is this a known bug or misconfiguration in apt?
Yes, known frontend bug (though it doesn't seem
On 10/29/2010 2:29 PM, Cyril Brulebois wrote:
> You could check that by calling your package manager with:
> strace -f -e execve $your_stuff_goes_here
I'll try that out.
> After a very quick search, I didn't see a matching bug in:
> http://bugs.debian.org/src:apt
I didn't either. Sounds lik
Phillip Susi (29/10/2010):
> Is this a known bug or misconfiguration in apt?
AFAICT, package managers do indeed call dpkg several times, meaning
the triggers effect isn't as much a big win as it could be. :(
You could check that by calling your package manager with:
strace -f -e execve $your_s
I've noticed triggers being invoked repeatedly during upgrades rather
than once at the end, as they are supposed to. I started looking at
/var/log/dpkg.log to try and figure out why. I was wondering, does a
record like this:
2010-10-29 10:50:17 startup archives unpack
Indicate that a new invoca
10 matches
Mail list logo
