Ok, I understand what's going on better now, and I'm sorry for the
combative tone. I was indeed running the kvm from unstable, because I
had to move to the that kernel to fix a bug, and I figured keeping kvm
in as close sync as possible made the most sense. That may not have
been necessary,
By adding your conflict with KVM, you're now breaking systems, if the
administrators aren't paying attention. People running KVM, if they
want to KEEP running KVM, can't update QEMU. There is no
non-conflicting version of KVM available anywhere in testing or unstable.
Since not even unstable
I didn't realize that you guys didn't do any anti-spam obfuscation of
email addresses. Would you please substitute this one
([EMAIL PROTECTED]) anywhere the other one showed up? (same domain.)
Thanks much!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trou
I got my boxes confused; this is a non-production Unstable machine, not
Testing. But it's still busted. :)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: python2.4-minimal
Version: 2.4.4-3
Python 2.4 minimal is horribly borked in Testing. At the bottom of the
message is a transcript of attempts to both install and uninstall,
neither of which work. I'm stuck, because I can't uninstall the old
package and fall back to the version that w
Package: linux-image-2.6.14-2.k7
Version: linux-image-2.6.14-2-k7 2.6.14-3
This version of the kernel appears to have switched to yaird to make
initrds. It does not correctly detect and include the 'gdth.ko' kernel
module on one of my servers. gdth.ko is the ICP Vortex family of SCSI
control
6 matches
Mail list logo
