AM It is a known temporary problem caused by the ... transition,
All I know is on the first days of such transitions, my usual
# apt-get -o Debug::pkgProblemResolver=true --purge dselect-upgrade
barfs up kilometers of broken dep messages, the next day it is fewer,
but still several broken
On Sun, 04 May 2008, [EMAIL PROTECTED] wrote:
Why can't all the dependency stuff be resolved first before it is sent
to sid?
Unstable is the place where dependencies are resolved before they are
sent on to testing. It's not like they're hard to deal with; you just
don't upgrade packages whose
Hi,
[EMAIL PROTECTED] wrote:
My question is why can't this drama be played out behind the scenes?
Why can't all the dependency stuff be resolved first before it is sent
to sid?
Or is that how dependency problems are detected and hunt down? If so,
then why can't this be played out offline
I am unable to upgrade my sid chroot. This is what I get
$pbuilder-sid update
Upgrading for distribution sid
Building the build Environment
- extracting base tarball [/home/rajulocal/pbuilder/sid-base.tgz]
- creating local configuration
- copying local configuration
- mounting /proc
Kamaraju S Kusumanchi [EMAIL PROTECTED] wrote:
I am unable to upgrade my sid chroot. This is what I get
[...]
The following packages have unmet dependencies:
e2fsprogs: PreDepends: libuuid1 (= 1.34-1) but it is not going to be
installed
mount: PreDepends: libuuid1 but it is not going to be
5 matches
Mail list logo
