Bug#238214: marked as done (apt-get: warn the user when it is known that an upgrade may break the package system)
Your message dated Tue, 16 Mar 2004 15:27:46 -0800
with message-id <20040316232746.GU4918@alcor.net>
and subject line Bug#238214: apt-get: warn the user when it is known that an upgrade may break the package system
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 15 Mar 2004 23:58:06 +0000
>From vincent@vinc17.org Mon Mar 15 15:58:06 2004
Return-path: <vincent@vinc17.org>
Received: from vinc17.net1.nerim.net (ay.vinc17.org) [62.4.18.82]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B31y9-0006Zy-00; Mon, 15 Mar 2004 15:58:06 -0800
Received: from lefevre by ay.vinc17.org with local (Exim 4.30)
id 1B31xc-0007MB-VA; Tue, 16 Mar 2004 00:57:32 +0100
Date: Tue, 16 Mar 2004 00:57:32 +0100
From: Vincent Lefevre <vincent@vinc17.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: apt-get: warn the user when it is known that an upgrade may break the package system
Message-ID: <[🔎] 20040315235732.GA28110@ay.vinc17.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 2.48
X-Mailer-Info: http://www.vinc17.org/mutt/
User-Agent: Mutt/1.5.6i
Sender: Vincent Lefevre <vincent@vinc17.org>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_12
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_12
X-Spam-Level:
Package: apt
Version: 0.5.23
Severity: wishlist
There should be a way to warn the user when some other user already
reported that an upgrade may break the package system, without having
a *clean* way to go back to a previous working state (for instance,
"apt-get install -f" doesn't work). This would behave a bit like what
apt-listbugs does, but would be specific to the package system. This
would probably require a new tag.
-- Package-specific info:
-- (/etc/apt/preferences present, but not submitted) --
-- (/etc/apt/sources.list present, but not submitted) --
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (900, 'testing'), (200, 'unstable')
Architecture: powerpc (ppc)
Kernel: Linux 2.4.18-newpmac
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1
Versions of packages apt depends on:
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libgcc1 1:3.3.3-1 GCC support library
ii libstdc++5 1:3.3.3-1 The GNU Standard C++ Library v3
-- no debconf information
---------------------------------------
Received: (at 238214-done) by bugs.debian.org; 17 Mar 2004 00:00:10 +0000
>From mdz@alcor.net Tue Mar 16 16:00:10 2004
Return-path: <mdz@alcor.net>
Received: from mta9.adelphia.net [68.168.78.199]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B3OTi-0007C4-00; Tue, 16 Mar 2004 16:00:10 -0800
Received: from mizar.alcor.net ([68.64.159.24]) by mta9.adelphia.net
(InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP
id <20040316235939.YSHF1423.mta9.adelphia.net@mizar.alcor.net>;
Tue, 16 Mar 2004 18:59:39 -0500
Received: from mdz by mizar.alcor.net with local (Exim 4.30)
id 1B3NyM-0000yf-Ql; Tue, 16 Mar 2004 15:27:46 -0800
Date: Tue, 16 Mar 2004 15:27:46 -0800
From: Matt Zimmerman <mdz@debian.org>
To: Vincent Lefevre <vincent@vinc17.org>
Cc: 238214-done@bugs.debian.org
Subject: Re: Bug#238214: apt-get: warn the user when it is known that an upgrade may break the package system
Message-ID: <20040316232746.GU4918@alcor.net>
References: <[🔎] 20040315235732.GA28110@ay.vinc17.org> <[🔎] Pine.LNX.4.58.0403161149570.13832@gradall.private.brainfood.com> <[🔎] 20040316191424.GJ4918@alcor.net> <20040316233317.GC16556@ay.vinc17.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040316233317.GC16556@ay.vinc17.org>
User-Agent: Mutt/1.5.5.1+cvs20040105i
Sender: Matt Zimmerman <mdz@alcor.net>
Delivered-To: 238214-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_12
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_12
X-Spam-Level:
On Wed, Mar 17, 2004 at 12:33:17AM +0100, Vincent Lefevre wrote:
> On 2004-03-16 11:14:24 -0800, Matt Zimmerman wrote:
> > What do you want exactly?
>
> Sometimes packages have bugs that have the effect that they can't be
> installed completely; as a consequence, it is impossible to install
> or upgrade anything else because dpkg would return an error as long
> as the broken package hasn't been fixed or removed.
>
> There should be a way so that users can report such a problem (e.g.
> via the BTS); in this way, packages would be marked as potentially
> dangerous, and this would be detected by apt, which would warn the
> user when trying to upgrade such a package.
>
> Note that apt-listbugs won't necessarily show *all* these bugs unless
> the "important" severity is tracked too, but too many bugs would be
> shown in this case. That's why apt-listbugs isn't sufficient.
This is exactly what apt-listbugs does. If a bug makes a package
uninstallable, then it is Severity: grave (unusable). Users report these
bugs, and apt-listbugs displays them.
--
- mdz
Reply to: