Advice needed: update-manager in wheezy considered dangerous

[Julian Andres Klode]

On Tue, Mar 12, 2013 at 06:59:01AM +0200, Martin-Éric Racine wrote:
> 2013/3/12 Julian Andres Klode <jak at debian.org>:
> > Dear release team, I report this problem as we have switched our package management
> > stack in wheezy from update-manager and other components to PackageKit. Those
> > old components are still in wheezy however, and especially update-manager can
> > be considered to be horribly dangerous: It might break systems or contain extreme
> > security issues as it has not seen someone really care about it since 2 years.
> >
> > We cannot simply remove update-manager however, as there are reverse
> > dependencies. The most important ones appear to be:
> >
> >   * upgrade-system
> >   * update-notifier
> >
> > We could simply drop upgrade-system from testing. For update-notifier, we cannot
> > do this, as update-notifier-kde depends on update-notifier-common, and there are
> > no other notifiers for KDE AFAIK. I could however upload an empty update-notifier
> > package (for GNOME) that switches the user to the PackageKit notifier, thus
> > removing that reverse dependency.
> >
> > Summary of the proposed solution:
> >         1. Remove upgrade-system from testing
> 
> I really don't see the point in removing upgrade-system from Testing,
> since the dependency relationship is merely a Suggests.

Yes, sorry, I somehow missed that; as apt-cache rdepends does not list
the dependency type and I overlooked that it was only Suggests when
reading `apt-cache show upgrade-system`.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.