Cyril Brulebois wrote: > So, finally tracked it down, confirming my initial suspicion: the > triggers are doing that. > > Basically, we have debconf in target setting titles through the > frontend script, even when maintainer scripts are called with the > “triggered” action. > > I'm suggesting the attached patch, avoiding setting the title in that > specific case. That doesn't affect debconf-apt-progress feedback: one > still sees triggers being processed (and that's good since they can > take a while). > > > Confirmed by partial-cloning an archive, hacking hashsums and keyrings > in place, and installing with that… [*crazy evening*] > > Does that look fine enough? If so, a quick upload to get that fixed in > testing before publishing d-i wheezy rc1 would be nice. (I'll be > replying to the debconf 1.5.48 unblock request in the meanwhile.)
This seems acceptable for now. If a package used debconf for interaction in a trigger, it would then have the wrong title .. but until someone finds a reason for a package to need to do that, we can live with this patch. -- see shy jo
signature.asc
Description: Digital signature
