Bug#787310: perl-base: Dependency conflict on multiarch

2015-07-10 Thread OmegaPhil
Thankyou for this information - I escaped this upgrade hell by killing off just libsane:i386 (I didn't need to do any other purging etc) and then full-upgrading. I'm in control of my system again! On 07/07/15 16:03, Leszek Godlewski wrote: Hi Niko, Just letting you know I was able to resolve

Bug#787310: perl-base: Dependency conflict on multiarch

2015-07-07 Thread Leszek Godlewski
Hi Niko, Just letting you know I was able to resolve this by purging the perl i386 packages with dpkg and removing libsane:i386, which (indirectly) caused the dependency on i386 perl in the first place and which I don't need. My system remains functional after this change and I was able to

Bug#787310: perl-base: Dependency conflict on multiarch

2015-05-31 Thread Niko Tyni
On Sun, May 31, 2015 at 11:04:38AM +, Leszek Godlewski wrote: In that case I will try to live with this conflict for a while longer and hope for a resolution by 5.22. Or maybe I could grab the packages from experimental? It's a home workstation, not a production server, so I guess unless

Bug#787310: perl-base: Dependency conflict on multiarch

2015-05-31 Thread Leszek Godlewski
Package: perl-base Version: 5.20.2-6 Severity: important Dear Maintainer, I was trying to normally aptitude full-upgrade my system (Debian testing amd64 w/i386 multiarch), when I was met with a dependency conflict: The following packages have unmet dependencies: perl-base : Conflicts:

Bug#787310: perl-base: Dependency conflict on multiarch

2015-05-31 Thread Niko Tyni
On Sun, May 31, 2015 at 10:59:04AM +0200, Leszek Godlewski wrote: Package: perl-base Version: 5.20.2-6 Severity: important I was trying to normally aptitude full-upgrade my system (Debian testing amd64 w/i386 multiarch), when I was met with a dependency conflict: The following packages

Bug#787310: perl-base: Dependency conflict on multiarch

2015-05-31 Thread Leszek Godlewski
Hi Niko, In that case I will try to live with this conflict for a while longer and hope for a resolution by 5.22. Or maybe I could grab the packages from experimental? It's a home workstation, not a production server, so I guess unless there are severe bugs I could tolerate the instability. I