Re: Status of circular dependencies in Sid
Ian Jackson dixit:
>There is still nothing per se wrong with circular dependencies
Actually, I’m hitting an APT bug during dist-upgrades right now
for packages with circular dependencies, usually two (perl with
perl-modules, and g++-$version with its library), when they are
indirectly depended on by a package with Important: yes set, as
was recommended for metapackages which should not be considered
by APT for automatic removal.
My upgrade documentation for our company wiki has sections like:
In case of problems, solve iteratively:
* E: Could not perform immediate configuration on 'perl'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
* E: Could not perform immediate configuration on 'perl-modules'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
apt-get --purge install perl -o APT::Immediate-Configure=no
apt-get --purge dist-upgrade
* E: Could not perform immediate configuration on 'g++-4.4'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
apt-get --purge install build-essential -o APT::Immediate-Configure=no
apt-get --purge dist-upgrade
And Policy says:
[…]
breaking point is arbitrary. Packages should therefore avoid circular
dependencies where possible, particularly if they have ostinst'
scripts.
[…]
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-314
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Boris Esser, Sebastian Mancke
Reply to: