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


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

Bug#1072821: wireshark: binNMUs revert t64 transition

Started byAdrian Bunk <bunk@debian.org>
First post2024-06-08 14:50 +0200
Last post2024-06-12 17:10 +0200
Articles 3 — 2 participants

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


Contents

  Bug#1072821: wireshark: binNMUs revert t64 transition Adrian Bunk <bunk@debian.org> - 2024-06-08 14:50 +0200
    Bug#1072821: wireshark: binNMUs revert t64 transition Jeremy Bícha <jeremy.bicha@canonical.com> - 2024-06-09 15:00 +0200
    Bug#1072821: wireshark: binNMUs revert t64 transition Jeremy Bícha <jeremy.bicha@canonical.com> - 2024-06-12 17:10 +0200

#1200215 — Bug#1072821: wireshark: binNMUs revert t64 transition

FromAdrian Bunk <bunk@debian.org>
Date2024-06-08 14:50 +0200
SubjectBug#1072821: wireshark: binNMUs revert t64 transition
Message-ID<IN3Ga-1tIq-7@gated-at.bofh.it>
Source: wireshark
Version: 4.2.4-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=wireshark&arch=amd64&ver=4.2.5-1%2Bb1&stamp=1717834351&raw=0

...
Description:
 libwireshark-dev - network packet dissection library -- development files
 libwireshark17 - network packet dissection library -- shared library
 libwiretap-dev - network packet capture library -- development files
 libwiretap14 - network packet capture library -- shared library
 libwsutil-dev - network packet dissection utilities library -- development files
 libwsutil15 - network packet dissection utilities library -- shared library
 tshark     - network traffic analyzer - console version
 wireshark  - network traffic analyzer - graphical interface
 wireshark-common - network traffic analyzer - common files
 wireshark-dev - network traffic analyzer - development tools
Changes:
 wireshark (4.2.5-1+b1) sid; urgency=low, binary-only=yes
 .
   * Binary-only non-maintainer upload for amd64; no source changes.
   * Rebuild against Qt 6.6.2.
...



debian/rules:
...
ifneq ($(filter noble unstable testing trixie UNRELEASED,$(DEB_DISTRIBUTION)),)
        sed "$(CONTROL_IN_SED_CMD)" debian/control.t64.in > debian/control
else
        sed "$(CONTROL_IN_SED_CMD)" debian/control.in > debian/control
...



sid != unstable

[toc] | [next] | [standalone]


#1200283

FromJeremy Bícha <jeremy.bicha@canonical.com>
Date2024-06-09 15:00 +0200
Message-ID<INqjn-1Hv9-1@gated-at.bofh.it>
In reply to#1200215
That debian/rules code seems fragile. Beyond sid, it also doesn't
recognize several other valid upload targets: experimental, oracular
(for Ubuntu), devel (for Ubuntu), forky (not valid yet but it will be
the release after trixie).

Thank you,
Jeremy Bícha

[toc] | [prev] | [next] | [standalone]


#1200664

FromJeremy Bícha <jeremy.bicha@canonical.com>
Date2024-06-12 17:10 +0200
Message-ID<IOxLP-2pjJ-3@gated-at.bofh.it>
In reply to#1200215
On Sun, Jun 9, 2024 at 9:21 AM Bálint Réczey <balint@balintreczey.hu> wrote:
> I've just added sid and oracular. I can't recall any upload targeting
> devel in Ubuntu, but it may work, thus I can add that as well.
> I expect the next upstream SO version bump to take place this
> summer/autumn, thus the code is expected to be short-lived.
> Is there any better example of generating a t64 transitioned control
> file for one set of releases and a not transitioned one for backports?

I have seen 'devel' used for the upload series a few times in Ubuntu,
but it's unusual.

The simplest way to handle backporting is to ensure your package is
not built on affected 32-bit architectures (armel & armhf for Debian
release architectures).

I'm not aware of anyone attempting debian/rules tweaks like you did
for Debian Backports, but I've never worked with Debian Backports
either.

Thank you,
Jeremy Bícha

[toc] | [prev] | [standalone]


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


csiph-web