Your message dated Mon, 21 Sep 2015 19:52:52 +0100
with message-id <[email protected]>
and subject line Re: aptitude marks package w/ circular dependency as broken
instead of upgrading
has caused the Debian Bug report #213263,
regarding aptitude marks package w/ circular dependency as broken instead of
upgrading
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 [email protected]
immediately.)
--
213263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=213263
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.2.11.1-3
Severity: normal
Currently I have console-common 0.7.28 and console-tools 0.2.3dbs-39
installed. Today's update shows 0.7.29 and 0.2.3dbs-43 as the latest
versions, respectively. Each of these packages depends on the other.
I'm not sure if circular dependencies are allowed, but I'm assuming
they're ok.
aptitude marks console-common as broken when trying to upgrade to
0.7.29. I have Apt:Default=testing.
Since console-tools is in testing and console-common is in sid,
shouldn't console-common be marked as hold instead of broken?
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux tiamat 2.4.21-5-686 #1 Sun Aug 24 15:25:33 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages aptitude depends on:
ii apt [libapt-pkg-libc6.2-3 0.5.4 Advanced front-end for dpkg
ii libc6 2.3.2-7 GNU C Library: Shared libraries an
ii libncurses5 5.3.20030719-1 Shared libraries for terminal hand
ii libsigc++0 1.0.4-3 Type-safe Signal Framework for C++
ii libstdc++2.10-glibc2.2 1:2.95.4-17 The GNU stdc++ library
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Jerry,
And just shy of 12 years later...
2003-09-29 16:52 Jerry Quinn:
Package: aptitude
Version: 0.2.11.1-3
Severity: normal
Currently I have console-common 0.7.28 and console-tools 0.2.3dbs-39
installed. Today's update shows 0.7.29 and 0.2.3dbs-43 as the latest
versions, respectively. Each of these packages depends on the other.
I'm not sure if circular dependencies are allowed, but I'm assuming
they're ok.
aptitude marks console-common as broken when trying to upgrade to
0.7.29. I have Apt:Default=testing.
Since console-tools is in testing and console-common is in sid,
shouldn't console-common be marked as hold instead of broken?
I am triaging this bug among the hundreds still remaining, sorry that
this was not handled in all these years.
Information about circular dependencies in policy:
http://www.debian.org/doc/debian-policy/ch-relationships.html
Basically, they are not a great idea.
There are several references about this in the changelog of this
package:
console-common (0.7.31) unstable; urgency=low
[...]
* No longer depend on console-tools for fgconsole. Cope with it being
[...]
-- Alastair McKinstry <[email protected]> Wed, 22 Oct 2003 20:21:40 +0000
console-common (0.7.59) unstable; urgency=low
[...]
* Depend on kbd | console-tools, instead of console-tools | kbd.
Prefer kbd for etch, and to help remove circular dependency
with console-tools.
[...]
-- Alastair McKinstry <[email protected]> Wed, 5 Jul 2006 08:07:12 +0100
Anyway, about aptitude, I tested with "winff" [1], which has circular
dependencies now between several packages, and installing them in
different fashions, removing one and adding another, and updating them
works fine.
dpkg is not very happy about them though:
dpkg: winff-gtk2: dependency problems, but removing anyway as you requested:
winff depends on winff-gtk2 | winff-qt; however:
Package winff-gtk2 is to be removed.
Package winff-qt is not configured yet.
Either aptitude was enhanced since then, or those packages at the time
had further problems than dependencies (some of the complications that
Policy or the mailing list threads talk about, perhaps).
Or perhaps it was a manifestation of the more general problem (not
restricted about circular dependencies) that sometimes prefers to remove
packages rather than upgrade two packages at the same time. But there
are lots of reports about this, with more recent examples, so I don't
think that it's useful to keep this bug around for this reason.
So I think that it is safe to close the bug report now, doing it. Sorry
again that it was not handled sooner.
[1] See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798191
winff :Depends: winff-gtk2 | winff-qt
winff-gtk2 :Depends: winff
winff-qt :Depends: winff
Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
