Re: apt-listchanges in standard (was Re: Release update: ...)
* Matt Zimmerman (email@example.com) [050223 21:05]:
> On Tue, Feb 22, 2005 at 08:15:04PM +0000, Martin Michlmayr wrote:
> > There has one been a plan once to promote apt-listchanges to standard
> > - the ability to send only "news" items was introduced and made the
> > default. Even though this was done, apt-listchanges is still
> > optional. I think apt-listchanges and its dependencies only need an
> > override change but maybe there's more I've overlooked. Could someone
> > look into this? Matt, do you know what happened to the plan of
> > apt-listchanges to standard?
> I adjusted the behaviour of apt-listchanges to make it suitable for
> Priority: standard, discussing the process on -devel along the way. I then
> pointed out (in private, I think) that python-apt, ucf and any relevant
> dependencies would also need to be promoted to standard, and it wasn't clear
> whether that was OK.
I can remember that having apt-listchanges installed at a buildd breaks
the buildd, as the installation of files in the chroot is stuck. Is this
still the case?
PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C