Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1110605 > unrolled thread

Bug#1015839: dpkg: Back-port ARC support in stable version

Started byAlexey Brodkin <Alexey.Brodkin@synopsys.com>
First post2022-07-22 12:40 +0200
Last post2022-07-27 12:40 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.debian.bugs.dist


Contents

  Bug#1015839: dpkg: Back-port ARC support in stable version Alexey Brodkin <Alexey.Brodkin@synopsys.com> - 2022-07-22 12:40 +0200
    Bug#1015839: dpkg: Back-port ARC support in stable version Guillem Jover <guillem@debian.org> - 2022-07-27 12:40 +0200

#1110605 — Bug#1015839: dpkg: Back-port ARC support in stable version

FromAlexey Brodkin <Alexey.Brodkin@synopsys.com>
Date2022-07-22 12:40 +0200
SubjectBug#1015839: dpkg: Back-port ARC support in stable version
Message-ID<ELYeB-d2Yc-3@gated-at.bofh.it>
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

[toc] | [next] | [standalone]


#1111091

FromGuillem Jover <guillem@debian.org>
Date2022-07-27 12:40 +0200
Message-ID<ENMCl-e9Ae-1@gated-at.bofh.it>
In reply to#1110605
Hi!

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.

> 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.

Thanks,
Guillem

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web