On 2020-04-29 at 10:04, Dale Harris wrote: > On Wed, Apr 29, 2020 at 9:35 AM Dale Harris <rodmur@gmail.com> wrote: > >> On Wed, Apr 29, 2020 at 8:54 AM The Wanderer <wanderer@fastmail.fm> wrote: >> >>> The basic procedure would be an iteration over adding the "will not be >>> installed" packages (or, in the case of a remove-the-wrong-things >>> explosion, the important packages that would otherwise be removed) >>> explicitly to the command line, and repeating with the ones from the >>> next failure, until it shows you the actual conflict. >>> >> >> Okay, did some of that, the one that really blows up is libicu63:i386, >> when I try to install that it was to remove most of the amd64 packages. >> >> # apt-cache policy libicu63:i386 >> libicu63:i386: >> Installed: (none) >> Candidate: 63.1-6 >> Version table: >> 63.1-6 500 >> 500 https://deb.debian.org/debian stable/main i386 Packages > > Okay, so this was the problem, there was several differences in versions > with some of the amd64 packages and the i386 version I wanted to install. > So I had to downgrade some of the amd64 packages and I was finally able to > install wine32. W00t! Yep, that's the usual expected problem here; the trick is figuring out which packages are the ones with the version mismatch. The reason this crops up with the symptom that it does is, as far as I can tell, that apt will basically never consider downgrading one package in order to install or upgrade another. (aptitude might, in the right circumstances, but whether that will ever be the first proposed dependency solution I don't know.) I'm glad I was able to point you in the right direction! -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature