Bug#459810: marked as done (reorder uploading)
Your message dated Fri, 16 Jan 2009 16:34:36 +0100
with message-id <20090116153436.GA17460@jak-linux.org>
and subject line Re: Bug#459810: reorder uploading
has caused the Debian Bug report #459810,
regarding reorder uploading
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
459810: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=459810
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: python-apt
Every few weeks I wonder why I don't get those cheery
apt-listchanges messages any more.
It turns out every few weeks I must have hit RET when all along buried
within the question I was being asked was, e.g.,
The following packages will be REMOVED:
apt-file apt-listchanges libapt-pkg-perl python-apt
The following packages will be upgraded:
apt apt-utils
Yes, I know the correct procedure when greeted with such a message is
to just wait a couple of days before hitting RET.
But now I am starting to wonder, why do packages other than
apt-listchanges seem not so easy to get deleted so often?
Could it be the order in which the dependencies are sent to the
mirrors? Or something about the dependencies themselves.
-o Debug::PkgProblemResolver=True shows
Investigating python-apt
Package python-apt has broken dep on libapt-inst-libc6.6-6-1.1
Considering apt-utils 4 as a solution to python-apt 1
Removing python-apt rather than change libapt-inst-libc6.6-6-1.1
Investigating libapt-pkg-perl
Package libapt-pkg-perl has broken dep on libapt-pkg-libc6.6-6-4.6
Considering apt 10 as a solution to libapt-pkg-perl 1
Removing libapt-pkg-perl rather than change libapt-pkg-libc6.6-6-4.6
Investigating apt-file
Package apt-file has broken dep on libapt-pkg-perl
Considering libapt-pkg-perl 1 as a solution to apt-file 0
Removing apt-file rather than change libapt-pkg-perl
Investigating apt-listchanges
Package apt-listchanges has broken dep on python-apt
Considering python-apt 1 as a solution to apt-listchanges 0
Removing apt-listchanges rather than change python-apt
Anyways, all I know is the order in which you upstream guys push out
your new packages creates a window of a day or two where users are
faced with the above painful decisions.
--- End Message ---
--- Begin Message ---
On Wed, Jan 09, 2008 at 05:00:33AM +0800, jidanni@jidanni.org wrote:
> Anyways, all I know is the order in which you upstream guys push out
> your new packages creates a window of a day or two where users are
> faced with the above painful decisions.
This is no bug, therefore I'm closing it. It may be inconvenient when
uploads happen in such an order. But this is nothing that could be
fixed somewhere in the packages.
--
Julian Andres Klode - Free Software Developer
Debian Developer - Contributing Member of SPI
Ubuntu Member - Fellow of FSFE
Website: http://jak-linux.org/ XMPP: juliank@jabber.org
Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/
Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/
--- End Message ---
Reply to: