Hi Andre,

On Tue, Aug 20, 2024 at 09:38:59PM +0200, Andre Noll wrote:
> answered my question. BTW: There's a typo in the text of the "Implicit
> and foreign dependencies of a package" item: s/thoug/though.

Thanks. You may also edit the wiki. I've updated it now.

> I tried that on two debian-12 systems. First I built lopsub with
> your patch applied on the i386 system, copied over the resulting
> -bin.deb to the amd64 system, and ran dpkg --add-architecture i386
> there. Attempting to install the -bin.deb package fails because
> liblopsub1t64:i386 is not installed, and trying to install that
> results in:
> 
>       # dpkg -i liblopsub1t64_1.0.5-1.1_i386.deb 
>       dpkg: regarding liblopsub1t64_1.0.5-1.1_i386.deb containing 
> liblopsub1t64:i386:
>        liblopsub1t64:i386 breaks liblopsub1 (<< 1.0.5-1.1)
>         liblopsub1 (version 1.0.3-2) is present and installed.
> 
>       dpkg: error processing archive liblopsub1t64_1.0.5-1.1_i386.deb 
> (--install):
>        installing liblopsub1t64:i386 would break liblopsub1, and
>        deconfiguration is not permitted (--auto-deconfigure might help)
>       Errors were encountered while processing:
>        liblopsub1t64_1.0.5-1.1_i386.deb
> 
> Any hints?

My patch has an important omission. Thanks for testing. liblopsub1t64
should be marked "Multi-Arch: same". That annotation tells the package
manager that this package can be installed multiple times for different
architectures concurrently. On tracker.d.o, you see a note from the
multiarch hinter about this. For that to work, the versions have to
match up exactly, so you'll also need an amd64 build for testing this.

> > You may also just upload to experimental. Then you can try your change
> > there and since upgrading from experimental to unstable is not generally
> > supported, you may just revert it (without Breaks+Replaces) in case it
> > does not work out. Once uploaded, you may try cross building tfortune
> > against the experimental liblopsub.
> 
> Good to know. But this is more complicated since I'd always need somebody
> to sponsor the upload.

Please keep in mind that NEW uploads must be binary (ftp master
requirement) and that in order for your upload to migrate to testing, it
must not be binary. Hence you usually need two uploads anyway. liblopsub
may get away with a binNMU request as it does not build any Arch:all
packages. Going through experimental for NEW uploads generally is
recommended practice still.

Helmut

Reply via email to