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 successfully run an aptitude full-upgrade.
Regards, Leszek niedz., 31.05.2015 o 17:24 użytkownik Niko Tyni <nt...@debian.org> napisał: > On Sun, May 31, 2015 at 11:04:38AM +0000, 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 there are severe bugs I could tolerate the instability. > > Unfortunately the 5.22 packages alone aren't really fit for anything else > than a chroot for experimenting. All binary Perl modules need a rebuild > between Perl versions, and there isn't a way to provide such an overlay > currently. So much of your system would suddenly become uninstallable, > unless you rebuild those packages yourself. > > > I was simply updating from an older version of testing. It's been several > > weeks since the last update, though, probably more than a month. > > That's weird. I just tried an upgrade from stable on amd64 with a few > i386 packages installed, which should be pretty close to that, with no > problems, so I suppose it's some specific combination of packages that > breaks it. > > I expect there's a way out of your current situation, but I'm not really > an expert on that part. I'd expect it to work with apt-get (rather than > aptitude) and removing a few packages, but it sounded like you've already > tried that. > > You might want to try the debian-user list for help. > -- > Niko Tyni nt...@debian.org >
