Bug#401122: marked as done (broken dependencies must never occur, even for a moment)
Your message dated Fri, 1 Dec 2006 12:14:00 +0100
with message-id <20061201111400.GA28667@wavehammer.waldi.eu.org>
and subject line Bug#401122: broken dependencies must never occur, even for a moment
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)
--- Begin Message ---
Package: linux-image-2.6.18-2-686
Severity: normal
Package linux-image-2.6-686 has broken dep on linux-image-2.6.18-2-686
Package linux-image-2.6-k7 has broken dep on linux-image-2.6.18-2-k7
Package linux-headers-2.6-k7 has broken dep on linux-headers-2.6.18-2-k7
Package linux-headers-2.6-686 has broken dep on linux-headers-2.6.18-2-686
Package linux-image-686 has broken dep on linux-image-2.6-686
Considering linux-image-2.6-686 1 as a solution to linux-image-686 -1
Holding Back linux-image-686 rather than change linux-image-2.6-686
Keeping package linux-image-2.6-k7
Keeping package linux-headers-2.6-k7
Can you please figure out a way not to let this happen, even for one
minute.
Why? Because one of these months one day I will go to town to burn my
sid upgrades CDROM to take back to my rural location.
And if on that day I cannot get all my upgrades without any bloops and
blunders, then it will have to wait for next time months away.
Often it is not be burning the CDROM, so it all must work without any
such snags.
You might say that oh, just try back later, the problem will be gone
soon. But then I miss my chance for months. You might even not think
twice about what I'm saying and close this bug "momentary bug... fixed
by itself".
As I assume this momentary blunder is characteristic of the whole
Debian packaging system, then please copy this bug to where it belongs
too.
http://jidanni.org/comp/debian/apt-offline/index_en.html
Hope I can upgrade from 17 to 18 when the time comes for me to go to town!
--- End Message ---
--- Begin Message ---
On Fri, Dec 01, 2006 at 03:37:34AM +0800, Dan Jacobson wrote:
> Can you please figure out a way not to let this happen, even for one
> minute.
Impossible and no bug.
> Why? Because one of these months one day I will go to town to burn my
> sid upgrades CDROM to take back to my rural location.
And? Dependencies are not supposed to be always correct in unstable, use
testing if you need that.
Bastian
--
It would be illogical to kill without reason.
-- Spock, "Journey to Babel", stardate 3842.4
--- End Message ---
Reply to: