> I'm beginning to think I need to make some automated
> tests for an elaborate series of multi-arch edge cases.
Hi Scott
Seems that wine is bringing a lot of these m-a issues to your desk :-)
Hopefully this:
> winetricks is actually arch: all now
will be sufficient to avoid immediately having to m-a: foreign the winetricks dependencies. In Debian unstable, cabextract (d) and xdg-utils (r) are the only *declared* dependencies not already marked. These should still be done in due course and I see you are tracking this as bug #905055; great.
I suspect there may be still some cases where it would help for winetricks to also be m-a: foreign (e.g. the user in debian bug #696591 has installed a foreign-arch wine package).
> I'm beginning to think I need to make some automated
> tests for an elaborate series of multi-arch edge cases.
Hi Scott
Seems that wine is bringing a lot of these m-a issues to your desk :-)
Hopefully this:
> winetricks is actually arch: all now
will be sufficient to avoid immediately having to m-a: foreign the winetricks dependencies. In Debian unstable, cabextract (d) and xdg-utils (r) are the only *declared* dependencies not already marked. These should still be done in due course and I see you are tracking this as bug #905055; great.
I suspect there may be still some cases where it would help for winetricks to also be m-a: foreign (e.g. the user in debian bug #696591 has installed a foreign-arch wine package).