Your message dated Sun, 22 Apr 2001 14:36:49 +0100
with message-id <[EMAIL PROTECTED]>
and subject line dpkg-mountable removed from Debian unstable
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.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 9 May 1998 10:36:28 +0000
Received: (qmail 25957 invoked from network); 9 May 1998 10:36:27 -0000
Received: from irwell.zetnet.co.uk ([EMAIL PROTECTED])
by debian.novare.net with SMTP; 9 May 1998 10:36:27 -0000
Received: from beaker.zetnet.co.uk ([EMAIL PROTECTED] [194.247.41.78])
by irwell.zetnet.co.uk (8.8.7/8.8.5) with SMTP id LAA00800;
Sat, 9 May 1998 11:36:20 +0100
Received: from asm21 by beaker.zetnet.co.uk with local (Exim 1.82 #1)
id 0yY5r8-0001KB-00 (Debian); Sat, 9 May 1998 10:23:46 +0100
To: debian-devel-changes@lists.debian.org
CC: [EMAIL PROTECTED]
Subject: Re: Uploaded dpkg-mountable 0.7 (source i386) to erlangen
References: <[EMAIL PROTECTED]>
From: Andy Mortimer <[EMAIL PROTECTED]>
Date: 09 May 1998 10:23:45 +0100
In-Reply-To: Craig Sanders's message of Sat, 9 May 1998 14:27:29 +1000 (EST)
Message-ID: <[EMAIL PROTECTED]>
Lines: 73
X-Mailer: Gnus v5.4.37/XEmacs 19.16
Sender: Andy Mortimer <[EMAIL PROTECTED]>
Package: dpkg-mountable
Version: 0.7
[ CC'd to bug system; don't forget to remove it again! ]
Craig Sanders <[EMAIL PROTECTED]> writes:
> On Sat, 9 May 1998 [EMAIL PROTECTED] wrote:
>
> > Changes:
> > dpkg-mountable (0.7) unstable frozen; urgency=low
>
> > * Fix the location of the autoup.sh script.
>
> curious. does it use autoup or just mention it?
If a predependency fails, it says "If you're upgrading from bo to hamm, use
the autoup script here".
> did you include my patch to fix the "allow overwrite" option?
No, I've never seen it before.
> it's a simple one line addition....i've just made the change manually on
> every system i have installed it on. it is needed on systems running recent
> versions of dpkg (since 1.4.0.19 i believe) which have --refuse-overwrite by
> default. The previous behaviour was to have --force-overwrite as the
> default. My patch makes it work correctly regardless of what dpkg's default
> behaviour is.
OK, good point; I hadn't twigged this. I'll fix it in the next version.
> i didn't post it directly to you, but to debian-devel back in Feb.
I probably missed it.
Thanks,
Andy
--
Andy Mortimer, [EMAIL PROTECTED]
http://www.poboxes.com/andy.mortimer
PGP public key available on key servers
--
The people are fading away, as I slip into colours then ten shades of grey;
If I don't last this one tell them when I've gone,
That playing with you was incredible fun.
[ Remainder left in for bug system ]
> here's what i wrote back then:
>
> I had to modify /usr/lib/dpkg/methods/install after dpkg got upgraded to
> 1.4.0.20 so that the "allowoverwrite=1" option still worked.
>
>
>
> --- /usr/lib/dpkg/methods/mountable/install.orig Thu Feb 26 09:09:55 1998
> +++ /usr/lib/dpkg/methods/mountable/install Thu Feb 26 09:10:11 1998
> @@ -329,6 +329,7 @@
>
> my $dpkgargs="--admindir=$vardir --refuse-downgrade --skip-same-version
> --auto-deconfigure --unpack";
> $dpkgargs = "--refuse-overwrite ".$dpkgargs unless $::allowoverwrite;
> + $dpkgargs = "--force-overwrite ".$dpkgargs if $::allowoverwrite;
> if (!syscmd("$bindir/logcmd -aq -f $::logfile -- dpkg $dpkgargs
> $flist")) {
> # parse the list of problematical files, and remove them from our list,
> # then carry on.
>
>
> craig
>
> --
> craig sanders
---------------------------------------
Received: (at 22279-done) by bugs.debian.org; 22 Apr 2001 13:36:39 +0000
>From [EMAIL PROTECTED] Sun Apr 22 08:36:39 2001
Return-path: <[EMAIL PROTECTED]>
Received: from web1.lanscape.net [64.240.156.194]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14rK2Y-0002v2-00; Sun, 22 Apr 2001 08:36:38 -0500
Received: from fisch.cyrius.com (web1.lanscape.net [64.240.156.194])
by web1.lanscape.net (8.9.3/8.9.3) with ESMTP id IAA21428;
Sun, 22 Apr 2001 08:36:23 -0500
Received: by fisch.cyrius.com (Postfix, from userid 1000)
id 38987229CF; Sun, 22 Apr 2001 14:36:49 +0100 (BST)
Date: Sun, 22 Apr 2001 14:36:49 +0100
From: Martin Michlmayr <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: dpkg-mountable removed from Debian unstable
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Delivered-To: [EMAIL PROTECTED]
dpkg-mountable has been removed from Debian unstable and won't be
released with the next official release of Debian, codenamed "woody".
The original maintainer writes:
| * I can no longer test new versions of this package, as I'm using
| apt-zip rather than my not-free dialup access. I wrote it when I
| was accessing the University's NFS archive mirror!
|
| * It's slightly buggy, and badly out-of-date policy-wise.
|
| * Apt now provides (AFAIK) all the features provided by
| dpkg-mountable, and some (such as package ordering) that it never
| got around to getting.
Please switch to apt.
If you have questions about this, please contact me.
--
Martin Michlmayr
[EMAIL PROTECTED]
