Your message dated Fri, 29 Oct 2021 04:00:00 +0200
with message-id <[email protected]>
and subject line Re: Bug#998010: dpkg: Compression type not respected by, or
passed to .deb packing
has caused the Debian Bug report #998010,
regarding dpkg: Compression type not respected by, or passed to .deb packing
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 [email protected]
immediately.)
--
998010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998010
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.20.9
Severity: normal
Dear Maintainer,
We (Prosody.im) have a repo where we provide the latest version of
Prosody, as well as nightly builds. We use pbuilder and reprepro.
Due to Canonical having gone ahead with making Zstandard the default
Compression method for Ubuntu (see #892664), and thus packages built in
an Ubuntu environment having zstd control and data archives, which are
not supported (indirectly?) by reprepro on Debian, I've tried to pass -Z
to the package build procedure, but it appears to have no effect on the
resulting .deb files.
Running e.g. `dpkg-buildpackage -Zgzip` still produces .xz members of
the .deb on Debian, and .zstd on Ubuntu, so it seems that the -Z flag is
not passed all the way to whichever command (dpkg-deb ?) actually packs
the .deb file.
-- Package-specific info:
System tainted due to merged-usr-via-aliased-dirs.
-- System Information:
Debian Release: 11.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-9-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dpkg depends on:
ii libbz2-1.0 1.0.8-4
ii libc6 2.31-13+deb11u2
ii liblzma5 5.2.5-2
ii libselinux1 3.1-3
ii tar 1.34+dfsg-1
ii zlib1g 1:1.2.11.dfsg-2
dpkg recommends no packages.
Versions of packages dpkg suggests:
ii apt 2.2.4
pn debsig-verify <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
On Thu, 2021-10-28 at 15:28:39 +0200, Kim Alvefur (Zash) wrote:
> Package: dpkg
> Version: 1.20.9
> Severity: normal
> We (Prosody.im) have a repo where we provide the latest version of
> Prosody, as well as nightly builds. We use pbuilder and reprepro.
>
> Due to Canonical having gone ahead with making Zstandard the default
> Compression method for Ubuntu (see #892664), and thus packages built in
> an Ubuntu environment having zstd control and data archives, which are
> not supported (indirectly?) by reprepro on Debian, I've tried to pass -Z
> to the package build procedure, but it appears to have no effect on the
> resulting .deb files.
> Running e.g. `dpkg-buildpackage -Zgzip` still produces .xz members of
> the .deb on Debian, and .zstd on Ubuntu, so it seems that the -Z flag is
> not passed all the way to whichever command (dpkg-deb ?) actually packs
> the .deb file.
The -Z option in dpkg-buildpackage is for dpkg-source which it manages
directly. The dpkg-deb calls are managed by debian/rules (not
necessarily directly), so there's no way to control what those are doing.
If you want to build for Debian, then your build environment should be
a Debian system, otherwise there's no guarantee this will work
correctly (as Ubuntu rebuilds binaries and modifies sources), as shown
by the zstd divergence. Mixing and matching distributions is generally
frowned upon and considered unsupported, and I've been meaning to add
explicit and automatic vendor/origin tracking to built packages so
that this is more clear, which I'd just done that locally and will
include in dpkg 1.21.0 (will emit warnings and perhaps in the future
might get switched to require a --force-origin).
I'm thus closing this report.
Thanks,
Guillem
--- End Message ---
