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

Groups > linux.debian.bugs.rc > #388830 > unrolled thread

Bug#1102441: wireshark: build changes when rebuilt in trixie-security

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

Contents

  Bug#1102441: wireshark: build changes when rebuilt in trixie-security Helmut Grohne <helmut@subdivi.de> - 2025-04-09 09:00 +0200
    Bug#1102441: marked as done (wireshark: build changes when  rebuilt in trixie-security) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-04-17 10:40 +0200

#388830 — Bug#1102441: wireshark: build changes when rebuilt in trixie-security

Package: wireshark
Version: 4.4.5-1
Severity: serious
Justification: violates ftp-master reject faq

Hi,

via codesearching around, I ran into the following part of debian/rules

    ifneq ($(filter noble oracular unstable sid testing trixie UNRELEASED,$(DEB_DISTRIBUTION)),)
    CONTROL_IN_SED_CMD := $(CONTROL_IN_SED_CMD)s/@LIBSSH_DEV@/libssh-dev/;
    else
    CONTROL_IN_SED_CMD := $(CONTROL_IN_SED_CMD)s/@LIBSSH_DEV@/libssh-gcrypt-dev/;
    endif

Consider what happens when wireshark receives a security upload. At that
point, DEB_DISTRIBUTION will be trixie-security and we flip from the
first branch to the second branch. That's bad, but what does
CONTROL_IN_SED_CMD actually do? It's run during override_dh_clean and
rewrites debian/control. That practice is prohibited by the ftp-master
reject faq and incurs an rc bug.

Helmut

[toc] | [next] | [standalone]

#390000 — Bug#1102441: marked as done (wireshark: build changes when rebuilt in trixie-security)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Thu, 17 Apr 2025 08:37:11 +0000
with message-id <E1u5KkB-0007LO-Em@fasolo.debian.org>
and subject line Bug#1102441: fixed in wireshark 4.4.6-1
has caused the Debian Bug report #1102441,
regarding wireshark: build changes when rebuilt in trixie-security
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 owner@bugs.debian.org
immediately.)


-- 
1102441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102441
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

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

csiph-web