Your message dated Wed, 14 Sep 2022 05:18:23 +0200
with message-id <YyFH/5onubgyo...@thunder.hadrons.org>
and subject line Re: Bug#1015839: dpkg: Back-port ARC support in stable version
has caused the Debian Bug report #1015839,
regarding dpkg: Back-port ARC support in stable version
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1015839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.20.11
Severity: normal
Dear Maintainer,
ARCv2 support was added a while back in dpkg (see [1], [2])
and was included in dpkg starting from 1.21.0.
The problem is even uploads of other packages in "unstable"
fail to build if they expect the build system system to know about ARC.
Apparently newly uploaded packages are being built in a "stable"
environment, and so we need dpkg of that "stable" system to be
aware of ARC as well.
In particular this is relevant to Binutils, GCC etc.
Thus I'm asking to back-port [2] to 1.20.x branch and add it to the
"stable" upload of dpkg sometime soon. That will really unblock
normal package building and uploading for ARC as well.
Note also, as per Aurelien, ARC was added to debian-ports so
we're pretty much all set for normal package building on ARC,
for ARC and upload built packages in the repo.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980963
[2]
https://salsa.debian.org/dpkg-team/dpkg/-/commit/0d134cdcb0dcc6b21fa7926964c1426a5821181d
-- Package-specific info:
System tainted due to merged-usr-via-symlinks.
-- System Information:
Debian Release: bullseye/sid
APT prefers focal-updates
APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500,
'focal-proposed'), (500, 'focal'), (100, 'focal-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.74.3-microsoft-standard-WSL2+ (SMP w/12 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
--- End Message ---
--- Begin Message ---
Version: 1.20.12
On Wed, 2022-07-27 at 15:29:37 +0000, Alexey Brodkin wrote:
> > On Fri, 2022-07-22 at 12:27:01 +0200, Alexey Brodkin wrote:
> > > Package: dpkg
> > > Version: 1.20.11
> > > Severity: normal
> >
> > > The problem is even uploads of other packages in "unstable"
> > > fail to build if they expect the build system system to know about ARC.
> > >
> > > Apparently newly uploaded packages are being built in a "stable"
> > > environment, and so we need dpkg of that "stable" system to be
> > > aware of ARC as well.
> >
> > I think this is more about the archive tools and surrounding tooling
> > than any build infrastructure. But in any case, yes, it's
> > inconvenient.
>
> Sorry, I'm not very familiar with these details.
> But you've got my idea ;)
>
> > > Thus I'm asking to back-port [2] to 1.20.x branch and add it to the
> > > "stable" upload of dpkg sometime soon. That will really unblock
> > > normal package building and uploading for ARC as well.
> >
> > Yes, I'll queue this for the next stable update. Note that even once
> > this gets uploaded and ACCEPTed by the SRMs it will still not be
> > available at least until the next stable point release is actually
> > released, and the servers running that tooling upgraded.
>
> I was told of that already. Thus I emailed FTP team asking for
> a manual work-around for a time being. I hope they also understand
> and there will be no need to wait before the next dot release happens,
> which otherwise could be quite a long time since 11.4 was just released.
This was included in the recent stable release with dpkg 1.20.12.
Closing now.
Thanks,
Guillem
--- End Message ---
