Debian bug report logs - #584
dpkg change requests (was Re: Bug#581: Replacement & conflicting packages)
Reported by: iwj10@cus.cam.ac.uk (Ian Jackson); 104 days old.
Message received at debian-bugs:
From legislate.com!rdr Wed Mar 8 10:08:21 1995
Return-Path: <rdr@legislate.com>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0rmQ9h-0005o0C; Wed, 8 Mar 95 10:08 PST
Received: from [192.77.155.4] by pixar.com with SMTP id AA03531
(5.65c/IDA-1.4.4 for <debian-bugs@Pixar.com>); Wed, 8 Mar 1995 10:08:04 -0800
Received: by [192.77.155.4]
id m0rmQ3x-0004kZC
(Debian /\oo/\ Smail3.1.29.1 #29.27); Wed, 8 Mar 95 13:02 EST
Message-Id: <m0rmQ3x-0004kZC@[192.77.155.4]>
Date: Wed, 8 Mar 95 13:02 EST
From: rdr@legislate.com (Raul Miller)
To: iwj10@cus.cam.ac.uk, debian-bugs@Pixar.com
In-Reply-To: <m0rmKtc-0002gOZ.ijackson@nyx.cs.du.edu> (iwj10@cus.cam.ac.uk)
Subject: Re: Bug#584: dpkg change requests (was Re: Bug#581: Replacement & conflicting packages)
Raul Miller:
> I think that there should be a warning after dpkg -r that the package
> is on hold. More generally, I think there should be a warning any
> time a package is moved to a final state other than fully installed or
> fully removed.
Ian Jackson:
The only times a package gets put into such a state are:
* You asked for it, with --unpack.
* An error happened, in which case dpkg will print an error message
and give a non-zero exit status.
Is this not satisfactory ? We're going to have a login-time or
boot-time check that will moan about any incompletely-installed
packages and tell the user what to do about them.
I don't see the necessity for a specific message saying that a
package has been put `on hold'. Firstly, that only happens iff
there was an error, which will have been reported. Secondly, the
`hold' flag's only effect is to prevent the package from being
processed using dpkg --auto (you can override it with
--force-hold).
Hmm... this is a documentation problem, so it's really in my plate.
One of these days, I'm going to take another stab at comprehending
what dpkg is doing. [Last time I tried -- around .24 -- I was having
a hard time building a mental model of the major data structures of
dpkg.]
> Also, I think I'd want an option on dpkg which goes through all
> the motions except installation/removal, so I can get a better
> feel for what's going to be happening when I use dpkg.
> Basically, it should list the changes that would be introduced in
> package status as a result of my other command line. Ideally, it
> might also include the reasons for making these decisions.
I think this would be an excellent thing to have. I think, though,
that in practice dselect is more urgent. Is the C rewrite of dpkg
(which will come once the core functionality in dselect is done)
soon enough ?
That's fine with me.
Raul
Message sent:
From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: rdr@legislate.com (Raul Miller)
Subject: Bug#584: Info received (was Bug#584: dpkg change requests (was Re: Bug#581: Replacement & conflicting packages))
In-Reply-To: <m0rmQ3x-0004kZC@[192.77.155.4]>
References: <m0rmQ3x-0004kZC@[192.77.155.4]>
Thank you for the additional information you have supplied regarding
this problem report. It has been forwarded to the developers to
accompany the original report.
If you wish to continue to submit further information on your problem,
please do the same thing again: send it to debian-bugs@pixar.com, ensuring
that the Subject line starts with "Bug#584" or "Re: Bug#584" so that
we can identify it as relating to the same problem.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Ian Jackson
(maintainer, debian-bugs)
Message sent to debian-devel@pixar.com:
Subject: Bug#584: dpkg change requests (was Re: Bug#581: Replacement & conflicting packages)
Reply-To: rdr@legislate.com (Raul Miller), debian-bugs@pixar.com
Resent-To: debian-devel@pixar.com
Resent-From: rdr@legislate.com (Raul Miller)
Resent-Sender: iwj10@cus.cam.ac.uk
Resent-Date: Wed, 08 Mar 1995 18:18:02 GMT
Resent-Message-ID: <debian-bugs-handler.584.030818094616461@pixar.com>
X-Debian-PR-Package:
X-Debian-PR-Keywords:
Received: via spool for debian-bugs; Wed, 08 Mar 1995 18:18:02 GMT
Received: with rfc822 via encapsulated-mail id 030818094616461;
Wed, 08 Mar 1995 18:09:47 GMT
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0rmQ9h-0005o0C; Wed, 8 Mar 95 10:08 PST
Received: from [192.77.155.4] by pixar.com with SMTP id AA03531
(5.65c/IDA-1.4.4 for <debian-bugs@Pixar.com>); Wed, 8 Mar 1995 10:08:04 -0800
Received: by [192.77.155.4]
id m0rmQ3x-0004kZC
(Debian /\oo/\ Smail3.1.29.1 #29.27); Wed, 8 Mar 95 13:02 EST
Message-Id: <m0rmQ3x-0004kZC@[192.77.155.4]>
Date: Wed, 8 Mar 95 13:02 EST
From: rdr@legislate.com (Raul Miller)
To: iwj10@cus.cam.ac.uk, debian-bugs@Pixar.com
In-Reply-To: <m0rmKtc-0002gOZ.ijackson@nyx.cs.du.edu> (iwj10@cus.cam.ac.uk)
Raul Miller:
> I think that there should be a warning after dpkg -r that the package
> is on hold. More generally, I think there should be a warning any
> time a package is moved to a final state other than fully installed or
> fully removed.
Ian Jackson:
The only times a package gets put into such a state are:
* You asked for it, with --unpack.
* An error happened, in which case dpkg will print an error message
and give a non-zero exit status.
Is this not satisfactory ? We're going to have a login-time or
boot-time check that will moan about any incompletely-installed
packages and tell the user what to do about them.
I don't see the necessity for a specific message saying that a
package has been put `on hold'. Firstly, that only happens iff
there was an error, which will have been reported. Secondly, the
`hold' flag's only effect is to prevent the package from being
processed using dpkg --auto (you can override it with
--force-hold).
Hmm... this is a documentation problem, so it's really in my plate.
One of these days, I'm going to take another stab at comprehending
what dpkg is doing. [Last time I tried -- around .24 -- I was having
a hard time building a mental model of the major data structures of
dpkg.]
> Also, I think I'd want an option on dpkg which goes through all
> the motions except installation/removal, so I can get a better
> feel for what's going to be happening when I use dpkg.
> Basically, it should list the changes that would be introduced in
> package status as a result of my other command line. Ideally, it
> might also include the reasons for making these decisions.
I think this would be an excellent thing to have. I think, though,
that in practice dselect is more urgent. Is the C rewrite of dpkg
(which will come once the core functionality in dselect is done)
soon enough ?
That's fine with me.
Raul
Message received at debian-bugs:
From cus.cam.ac.uk!iwj10 Wed Mar 8 07:38:35 1995
Return-Path: <iwj10@cus.cam.ac.uk>
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0rmNoo-0005oGC; Wed, 8 Mar 95 07:38 PST
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA27699
(5.65c/IDA-1.4.4 for <debian-bugs@Pixar.com>); Wed, 8 Mar 1995 07:38:26 -0800
Received: by bootes.cus.cam.ac.uk
(Smail-3.1.29.0 #30) id m0rmNoN-000C06C; Wed, 8 Mar 95 15:38 GMT
Received: by chiark (Smail3.1.28.1 #3)
id m0rmKtc-0002gOZ; Wed, 8 Mar 95 12:31 GMT
Message-Id: <m0rmKtc-0002gOZ.ijackson@nyx.cs.du.edu>
Date: Wed, 8 Mar 95 12:31 GMT
From: iwj10@cus.cam.ac.uk (Ian Jackson)
To: debian-bugs@Pixar.com
Subject: dpkg change requests (was Re: Bug#581: Replacement & conflicting packages)
In-Reply-To: <m0rm4Q9-0004i6C@[192.77.155.4]>
References: <m0rlyA4-0002gOZ.ijackson@nyx.cs.du.edu>
<m0rm4Q9-0004i6C@[192.77.155.4]>
Raul Miller writes ("Re: Bug#581: Replacement & conflicting packages"):
> I think that there should be a warning after dpkg -r that the package
> is on hold. More generally, I think there should be a warning any
> time a package is moved to a final state other than fully installed or
> fully removed.
The only times a package gets put into such a state are:
* You asked for it, with --unpack.
* An error happened, in which case dpkg will print an error message
and give a non-zero exit status.
Is this not satisfactory ? We're going to have a login-time or
boot-time check that will moan about any incompletely-installed
packages and tell the user what to do about them.
I don't see the necessity for a specific message saying that a package
has been put `on hold'. Firstly, that only happens iff there was an
error, which will have been reported. Secondly, the `hold' flag's
only effect is to prevent the package from being processed using
dpkg --auto (you can override it with --force-hold).
> Also, I think I'd want an option on dpkg which goes through all the
> motions except installation/removal, so I can get a better feel for
> what's going to be happening when I use dpkg. Basically, it should
> list the changes that would be introduced in package status as a
> result of my other command line. Ideally, it might also include the
> reasons for making these decisions.
I think this would be an excellent thing to have. I think, though,
that in practice dselect is more urgent. Is the C rewrite of dpkg
(which will come once the core functionality in dselect is done) soon
enough ?
(I've submitted this as a new bug report, as the other one is more
urgent and will be fixed as soon as I'm happy that we have a proposed
solution that everyone is happy with.)
Ian.
Message sent:
From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: iwj10@cus.cam.ac.uk (Ian Jackson)
Subject: Bug#584: Acknowledgement (was: dpkg change requests (was Re: Bug#581: Replacement & conflicting packages))
In-Reply-To: <m0rmKtc-0002gOZ.ijackson@nyx.cs.du.edu>
References: <m0rmKtc-0002gOZ.ijackson@nyx.cs.du.edu>
Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received. It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.
If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#584" or "Re: Bug#584" so that
we can identify it as relating to the same problem.
Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.
Your message didn't have a Package: line at the start (in the
pseudo-header following the real mail header), or didn't have a
psuedo-header at all.
This makes it much harder for us to categorise and deal with your
problem report; please ensure that you say which package(s) and
version(s) the problem is with next time. Some time in the future the
problem reports system may start rejecting such messages.
Ian Jackson
(maintainer, debian-bugs)
Message sent to debian-devel@pixar.com:
Subject: Bug#584: dpkg change requests (was Re: Bug#581: Replacement & conflicting packages)
Reply-To: iwj10@cus.cam.ac.uk (Ian Jackson), debian-bugs@pixar.com
Resent-To: debian-devel@pixar.com
Resent-From: iwj10@cus.cam.ac.uk (Ian Jackson)
Resent-Sender: iwj10@cus.cam.ac.uk
Resent-Date: Wed, 08 Mar 1995 15:48:04 GMT
Resent-Message-ID: <debian-bugs-handler.584.03081540141133@pixar.com>
X-Debian-PR-Package:
X-Debian-PR-Keywords:
Received: via spool for debian-bugs; Wed, 08 Mar 1995 15:48:04 GMT
Received: with rfc822 via encapsulated-mail id 03081540141133;
Wed, 08 Mar 1995 15:40:14 GMT
Received: from pixar.com by mongo.pixar.com with smtp
(Smail3.1.28.1 #15) id m0rmNoo-0005oGC; Wed, 8 Mar 95 07:38 PST
Received: from bootes.cus.cam.ac.uk by pixar.com with SMTP id AA27699
(5.65c/IDA-1.4.4 for <debian-bugs@Pixar.com>); Wed, 8 Mar 1995 07:38:26 -0800
Received: by bootes.cus.cam.ac.uk
(Smail-3.1.29.0 #30) id m0rmNoN-000C06C; Wed, 8 Mar 95 15:38 GMT
Received: by chiark (Smail3.1.28.1 #3)
id m0rmKtc-0002gOZ; Wed, 8 Mar 95 12:31 GMT
Message-Id: <m0rmKtc-0002gOZ.ijackson@nyx.cs.du.edu>
Date: Wed, 8 Mar 95 12:31 GMT
From: iwj10@cus.cam.ac.uk (Ian Jackson)
To: debian-bugs@Pixar.com
In-Reply-To: <m0rm4Q9-0004i6C@[192.77.155.4]>
References: <m0rlyA4-0002gOZ.ijackson@nyx.cs.du.edu>
<m0rm4Q9-0004i6C@[192.77.155.4]>
Raul Miller writes ("Re: Bug#581: Replacement & conflicting packages"):
> I think that there should be a warning after dpkg -r that the package
> is on hold. More generally, I think there should be a warning any
> time a package is moved to a final state other than fully installed or
> fully removed.
The only times a package gets put into such a state are:
* You asked for it, with --unpack.
* An error happened, in which case dpkg will print an error message
and give a non-zero exit status.
Is this not satisfactory ? We're going to have a login-time or
boot-time check that will moan about any incompletely-installed
packages and tell the user what to do about them.
I don't see the necessity for a specific message saying that a package
has been put `on hold'. Firstly, that only happens iff there was an
error, which will have been reported. Secondly, the `hold' flag's
only effect is to prevent the package from being processed using
dpkg --auto (you can override it with --force-hold).
> Also, I think I'd want an option on dpkg which goes through all the
> motions except installation/removal, so I can get a better feel for
> what's going to be happening when I use dpkg. Basically, it should
> list the changes that would be introduced in package status as a
> result of my other command line. Ideally, it might also include the
> reasons for making these decisions.
I think this would be an excellent thing to have. I think, though,
that in practice dselect is more urgent. Is the C rewrite of dpkg
(which will come once the core functionality in dselect is done) soon
enough ?
(I've submitted this as a new bug report, as the other one is more
urgent and will be fixed as soon as I'm happy that we have a proposed
solution that everyone is happy with.)
Ian.
Ian Jackson /
iwj10@thor.cam.ac.uk,
with the debian-bugs tracking mechanism