Hi! On Mon, 2014-10-27 at 04:11:33 +0100, Vincent Lefevre wrote: > On 2014-10-27 02:44:38 +0100, Guillem Jover wrote: > > Let's lower this for now, as this is certainly not critical in any > > way, and I don't think it's serious for now, too many unknowns, but > > I'll bump it again if it happens to be so. > > IMHO, it would be bad if it affected stable.
It would be an undesirable regression sure, I want to understand what's going on first. It could be an issue in how apt invokes dpkg, that only showed up now that triggers are only processed when they have their dependencies satisfied. In any case, I want to see 1.17.21 migrate first, and then if this is a regression in dpkg I'll be immediately uploading .22 with a fix for it, and requesting an unblock for just .22 to the release team. I don't want to have to deal with a request to unblock 1.17.13..1.17.22 at all, TBH. > > On Mon, 2014-10-27 at 02:14:32 +0100, Vincent Lefevre wrote: > > > I've just upgraded another machine, and: > [...] > > > So, this is similar to the other one. > > > > Ok, I know you set the version affecting the other system to 1.17.21, > > but is this one too that version? was it upgraded to that on the same > > upgrade run? > > 1.17.21 too, because I had upgraded dpkg first, then upgraded > everything else later. Yes, I've got now a reliable reproducer on my kfreebsd-amd64 system. It's not processing the man-db triggers because libpipeline1 is not configured yet, but I don't know yet why it's not marked as being configured in that run. I'll be checking how apt is calling dpkg tomorrow, so see where this fails. > > Just installing and reinstalling ekiga here does not reproduce that. > > Could you backup that dpkg status file anyway, and check if > > «dpkg --configure -a» fixes it for you? > > # dpkg --configure -a > Setting up gconf2 (3.2.6-3) ... > Setting up man-db (2.7.0.2-2) ... > Building database of manual pages ... > Setting up ekiga (4.0.1-5) ... > Processing triggers for menu (2.1.47) ... > > which fixes the problem. Yeah, so while quite annoying, this is actually just self-healing, which is good. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
