Bug#722217: legacy304 also

2014-01-28 Thread Mika
I have Nvidia's newest driver 331.20-2 so its not only on Legacy drivers. Dpkg is 1.17.6 now. I don't know did I already try an upgrade with this dpkg version. I have the libc packages now pinned so I can use my system. Kernel and kbuild packages are version 3.12.6. I tried an upgrade a few week

Bug#722217: legacy304 also

2013-12-20 Thread Wendy J. Elmer
> > What version of dpkg are you using? Could it be this problem? > > dpkg (1.17.5) unstable; urgency=low > > [ Guillem Jover ] > [...] > * Fix segfault in update-alternatives when adding or renaming slaves for > an existing alternative. Regression introduced in dpkg 1.17.2. > Clo

Bug#722217: legacy304 also

2013-12-19 Thread Russ Allbery
Andreas Beckmann writes: > On 2013-12-19 14:50, Brent S. Elmer Ph.D. wrote: >> I am running legacy304, so it is not just legacy173. > I cannot reproduce any of these bugs in chroots ... > Did anyone investigate what is failing in the preinst? > Inserting 'set -x' instead of 'exit 0' into the pr

Bug#722217: legacy304 also

2013-12-19 Thread Andreas Beckmann
On 2013-12-19 14:50, Brent S. Elmer Ph.D. wrote: > I am running legacy304, so it is not just legacy173. I cannot reproduce any of these bugs in chroots ... Did anyone investigate what is failing in the preinst? Inserting 'set -x' instead of 'exit 0' into the preinst would be more helpful to debug

Bug#722217: legacy304 also

2013-12-19 Thread Brent S. Elmer Ph.D.
I am running legacy304, so it is not just legacy173. Brent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org