It’s more than just libcapi that is the problem though. There is a libav* package that was an issue as well, and I only found out libcapi was an issue after manually satisfying the dependency of the libav package.
So there is the potential of more missing dependencies after libcapi. I didn’t try satisfying that dependency to find out though. Regards, William Varona Sent from Gmail for iOS On Tue, Jan 20, 2026 at 9:28 PM Colin Watson <[email protected]> wrote: > Control: block -1 by 1121773 > > On Sun, Jan 18, 2026 at 01:09:19AM +0100, Antoine Le Gonidec wrote: > >Le Sat, Jan 17, 2026 at 01:41:25PM -0500, William Varona a écrit : > >> 1. libcapi20-3t64:i386=1:3.27-3.2+b1 is not selected for install > because: > >> 1. libwine:amd64=10.0~repack-12+b1 is selected for install > >> 2. libwine:amd64 Depends libcapi20-3t64 > >> 3. libcapi20-3t64:amd64 Breaks libcapi20-3t64:i386 (!= > 1:3.27-3.2+b2) > >> 2. libcapi20-3t64:i386=1:3.27-3.2+b1 is selected for install because: > >> 1. libwine:i386=10.0~repack-12+b1 is selected for install > >> 2. libwine:i386 Depends libcapi20-3t64:i386 > >> 3. libcapi20-3t64:i386 is available in version 1:3.27-3.2+b1 > > This particular issue shouldn't be a problem since unstable now has > libcapi20-3t64 1:3.27-3.2+b2 on both amd64 and i386. > > I think the main problem here can probably only be resolved once wine's > current problems migrating to testing are resolved, as seen in > https://tracker.debian.org/pkg/wine. That means this bug is likely > blocked on at least #1121773, although there may be other problems too. > > -- > Colin Watson (he/him) [[email protected]] >
