Re: automatically cross-grading lib32nss-mdns to libnss-mdns:i386?
On Fri, Nov 01, 2013 at 01:28:59PM +, Simon McVittie wrote:
> In nss-mdns/experimental, I tried this:
>
> Package: libnss-mdns
> Architecture: any
> Multi-Arch: same
>
> Package: lib32nss-mdns
> Architecture: i386
> Depends: libnss-mdns (= ${binary:Version})
> Description: ... transitional package ...
>
> hoping that apt would automatically cross-grade lib32nss-mdns:amd64 to
> lib32nss-mdns:i386, pulling in libnss-mdns:i386 as a dependency.
> However, when I installed those packages in a local apt repository and
> upgraded a VM that tracks that repository, it turns out that doesn't
> actually work.
Can you give more details on what did not work here? Maybe there is a
bug here, that can be fixed?
> I thought I remembered an announcement that cross-arch dependencies were
> OK for jessie, but I couldn't find it, so that might just be wishful
> thinking?
This was only considered for build dependencies and does not apply to
runtime dependencies.
Helmut
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131102080819.ga16...@alf.mars
Re: automatically cross-grading lib32nss-mdns to libnss-mdns:i386?
On Fri, Nov 1, 2013 at 9:28 PM, Simon McVittie wrote: > I thought I remembered an announcement that cross-arch dependencies were > OK for jessie, but I couldn't find it, so that might just be wishful > thinking? The cross-compilers built by [1] need them so I guess we need them before [2] can be implemented. 1. https://wiki.debian.org/MultiarchCrossToolchainBuild 2. https://wiki.debian.org/ReleaseGoals/CrossToolchains -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caktje6g-nizikj34p6gdq0f+brisdeox48c+uhmtb44c6ds...@mail.gmail.com
Re: automatically cross-grading lib32nss-mdns to libnss-mdns:i386?
On 1 November 2013 13:28, Simon McVittie wrote:
> If cross-architecture dependencies are allowed in the archive (and don't
> break dak or britney) these days, then it's easy:
>
> Package: libnss-mdns
> Architecture: any
> Multi-Arch: same
>
> Package: lib32nss-mdns
> Architecture: amd64
> Depends: libnss-mdns:i386 (= ${binary:Version})
> Description: ... transitional package ...
>
> I thought I remembered an announcement that cross-arch dependencies were
> OK for jessie, but I couldn't find it, so that might just be wishful
> thinking?
>
This one is allowed:
Depends: python:any
Actually spelling out the arch, is not.
> The only other option I can think of is to imitate Wine:
>
> Package: libnss-mdns
> Architecture: any
> Multi-Arch: same
>
> Package: lib32nss-mdns
> Architecture: amd64
> Depends: libnss-mdns-i386 (= ${binary:Version})
> Description: ... transitional package ...
>
> Package: libnss-mdns-i386
> Architecture: i386
> Depends: libnss-mdns (= ${binary:Version})
> Description: ... transitional package ...
>
> but that requires yet another content-free package, and a trip through
> the NEW queue. So, before I upload that: is there a better way?
>
That's the currently supported way of doing such migration.
Regards,
Dmitrijs.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CANBHLUiOMaGdfTEa0gNJrLmy1aAcw8w3Zc06P83acmbDmN2=n...@mail.gmail.com
automatically cross-grading lib32nss-mdns to libnss-mdns:i386?
nss-mdns/unstable is currently available in these flavours:
libnss-mdns:any (contains a native binary)
lib32nss-mdns:amd64 (contains an i386 binary)
My goal is that when amd64 users with both packages do a dist-upgrade to
jessie, if they have the i386 foreign architecture, they receive
libnss-mdns:amd64 and libnss-mdns:i386, plus whatever transitional
packages are needed to make that transition work. I expect that "most"
lib32nss-mdns users installed it for Wine's benefit (having libnss-mdns
but not lib32nss-mdns used to break DNS for 32-bit things, which appears
to be a long-since-fixed glibc bug), so they'll have the i386 foreign
architecture already.
In nss-mdns/experimental, I tried this:
Package: libnss-mdns
Architecture: any
Multi-Arch: same
Package: lib32nss-mdns
Architecture: i386
Depends: libnss-mdns (= ${binary:Version})
Description: ... transitional package ...
hoping that apt would automatically cross-grade lib32nss-mdns:amd64 to
lib32nss-mdns:i386, pulling in libnss-mdns:i386 as a dependency.
However, when I installed those packages in a local apt repository and
upgraded a VM that tracks that repository, it turns out that doesn't
actually work.
If cross-architecture dependencies are allowed in the archive (and don't
break dak or britney) these days, then it's easy:
Package: libnss-mdns
Architecture: any
Multi-Arch: same
Package: lib32nss-mdns
Architecture: amd64
Depends: libnss-mdns:i386 (= ${binary:Version})
Description: ... transitional package ...
I thought I remembered an announcement that cross-arch dependencies were
OK for jessie, but I couldn't find it, so that might just be wishful
thinking?
The only other option I can think of is to imitate Wine:
Package: libnss-mdns
Architecture: any
Multi-Arch: same
Package: lib32nss-mdns
Architecture: amd64
Depends: libnss-mdns-i386 (= ${binary:Version})
Description: ... transitional package ...
Package: libnss-mdns-i386
Architecture: i386
Depends: libnss-mdns (= ${binary:Version})
Description: ... transitional package ...
but that requires yet another content-free package, and a trip through
the NEW queue. So, before I upload that: is there a better way?
Thanks,
S
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5273ac9b.9090...@debian.org
