X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/c9b0c3e980efbd9035fb5feff4f7cf09a64215a4..63b23978754917fd0482bf5b939236af5e06a59d:/blog/Circular_package_dependencies_harms_apt_recovery.html diff --git a/blog/Circular_package_dependencies_harms_apt_recovery.html b/blog/Circular_package_dependencies_harms_apt_recovery.html index f729c40ee7..fe1ab589bb 100644 --- a/blog/Circular_package_dependencies_harms_apt_recovery.html +++ b/blog/Circular_package_dependencies_harms_apt_recovery.html @@ -4,15 +4,15 @@
I discovered this while doing -automated +automated testing of upgrades from Debian Lenny to Squeeze. A few packages in Debian still got circular dependencies, and it is often claimed that apt and aptitude should be able to handle this just fine, but some times these dependency loops causes apt to fail.
An example is from todays -upgrade +upgrade of KDE using aptitude. In it, a bug in kdebase-workspace-data causes perl-modules to fail to upgrade. The cause is simple. If a package fail to unpack, then only part of packages with the circular @@ -72,7 +72,7 @@ dependency. Reported both to BTS to try to get someone to look at it.