Your message dated Mon, 8 Jul 2002 16:19:22 -0500 (CDT)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#152299: dpkg: Should warn when 3rd-party file effects
(un)installation
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; 8 Jul 2002 19:08:58 +0000
>From [EMAIL PROTECTED] Mon Jul 08 14:08:58 2002
Return-path: <[EMAIL PROTECTED]>
Received: from front2.mail.megapathdsl.net [66.80.60.30]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 17RdsX-0007X3-00; Mon, 08 Jul 2002 14:08:57 -0500
Received: from [216.36.77.18] (HELO cheeseskin)
by front2.mail.megapathdsl.net (CommuniGate Pro SMTP 3.5.8)
with ESMTP id 37029637 for [EMAIL PROTECTED]; Mon, 08 Jul 2002 12:08:12 -0700
Received: from toomim by cheeseskin with local (Exim 3.35 #1 (Debian))
id 17Rdsd-0000GW-00; Mon, 08 Jul 2002 12:09:03 -0700
Subject: dpkg: Should warn when 3rd-party file effects (un)installation
From: "Michael Toomim" <[EMAIL PROTECTED]>
To: "Debian Bug Tracking System" <[EMAIL PROTECTED]>
X-Mailer: reportbug 1.99.47
Date: Mon, 08 Jul 2002 12:09:03 -0700
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Package: dpkg
Version: 1.10.2
Severity: wishlist
When dpkg encounters a package's installed file that has been modified
by the user, it doesn't by default replace it with a new version.
Instead, it just leaves the file there and skips the new version's
file.
This is a prime source of system-breakage. For instance, I've had X
become broken twice in the last year when dpkg didn't replace an old
.so driver file for my video card on upgrade, and have had it happen
in other cases as well.
While I think it's a good thing for dpkg to be conservative and keep
the 3rd-party file, I think that we could solve the system-breakage
problem by giving a warning during dpkg's install/uninstall process
when a 3rd-party file is not removed/replaced. If I had seen such a
warning during my last upgrades, I would have been saved from a lot of
ugly debugging.
-- System Information:
Debian Release: 3.0
Architecture: i386
Kernel: Linux cheeseskin 2.4.18-k7 #1 Sun Apr 14 13:19:11 EST 2002 i686
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages dpkg depends on:
ii dselect 1.10.2 a user tool to manage Debian packa
ii libc6 2.2.5-7 GNU C Library: Shared libraries an
-- no debconf information
---------------------------------------
Received: (at 152299-done) by bugs.debian.org; 8 Jul 2002 21:17:19 +0000
>From [EMAIL PROTECTED] Mon Jul 08 16:17:19 2002
Return-path: <[EMAIL PROTECTED]>
Received: from boof.brainfood.com (gradall.private.brainfood.com)
[65.125.64.189]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 17Rfsl-0006NR-00; Mon, 08 Jul 2002 16:17:19 -0500
Received: from localhost ([127.0.0.1] ident=adam)
by gradall.private.brainfood.com with esmtp (Exim 3.35 #1 (Debian))
id 17Rful-0006LV-00; Mon, 08 Jul 2002 16:19:23 -0500
Date: Mon, 8 Jul 2002 16:19:22 -0500 (CDT)
From: Adam Heath <[EMAIL PROTECTED]>
X-X-Sender: <[EMAIL PROTECTED]>
To: Michael Toomim <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>
Subject: Re: Bug#152299: dpkg: Should warn when 3rd-party file effects
(un)installation
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]
On Mon, 8 Jul 2002, Michael Toomim wrote:
> When dpkg encounters a package's installed file that has been modified
> by the user, it doesn't by default replace it with a new version.
> Instead, it just leaves the file there and skips the new version's
> file.
Er, only conffiles get such treatment.
> This is a prime source of system-breakage. For instance, I've had X
> become broken twice in the last year when dpkg didn't replace an old
> .so driver file for my video card on upgrade, and have had it happen
> in other cases as well.
A .so is a binary file. And .sos reside in /usr. This file is not a
conffile. So, the file will be overwritten.
> While I think it's a good thing for dpkg to be conservative and keep
> the 3rd-party file, I think that we could solve the system-breakage
> problem by giving a warning during dpkg's install/uninstall process
> when a 3rd-party file is not removed/replaced. If I had seen such a
> warning during my last upgrades, I would have been saved from a lot of
> ugly debugging.
There was no warning to give, so no warning was printed.
If you have something wrong, then say so. Hand waving will be dismissed as
such.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
