[Debconf-devel] Bug#558262: "dpkg-reconfigure -a" fails to complete

[Kalle Michanek]

2009/11/27 Raphael Hertzog <hertzog at debian.org>

> reassign 558262 debconf
> thanks
>
> On Fri, 27 Nov 2009, Kalle Michanek wrote:
> > 2009/11/27 Raphael Hertzog <hertzog at debian.org>
> >
> > > On Fri, 27 Nov 2009, Kalle Michanek wrote:
> > > > When one runs "dpkg-reconfigure -a" the process stops when it comes
> to a
> > > package
> > > > that has changed from dpkg install-info to GNU install-info.
> > >
> > > Which package is that?
>
> >
> >
> > How can I check that? AFAIK dpkg-reconfigure doesn't display what package
> is
> > being configured, does it?
>
> You likely can check the list of process (ps auxf) and find out a package
> name in sub-process of dpkg-reconfigure.
>
> Please attach the output of "ps auxf" when dpkg-reconfigure is blocked.
>

Hey,

I've found 3 packages that behave like this when using dpkg-reconfigure.
These are:
autoconf/testing uptodate 2.64-4
coreutils/testing uptodate 7.4-2
cpio/testing uptodate 2.10-1
sml-mode/testing uptodate 4.0-7

However, they aren't listed with ps auxf, as dpkg-reconfigure terminates
after the error message is shown. I found them manually (when I was bored
and started to play with apt-show-versions).
dpkg-reconfigure -a comes to autoconf on my desktop and to coreutils on my
laptop (where autoconf apparently isn't installed).


>
> > > That package should be fixed, there's nothing dpkg can do. The problem
> is
> > > probably the unexpected output that debconf is receiving but the
> > > solution might be to fix the package to not call install-info any more.
> > >
> > > (Or it's something totally unrelated)
> >
> > I see. Then I suggest, if it's possible, that dpkg-reconfigure should
> > continue with the next packages that are reconfigurable instead of
> stopping.
> > Maybe that makes this bugreport a wishlist item instead, I don't know.
>
> dpkg-reconfigure is not part of dpkg but of "debconf". Thus reassigning.
> Its maitainers can reassign or clone the bug report to the problematic
> package once it's known.
>
>  Oh, I'm sorry. I thought it was part of dpkg because dpkg was in the
packages name. My bad.

/K
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debconf-devel/attachments/20091202/91909a76/attachment.htm>