Bug#1077451: marked as done (golang-github-gopacket-gopacket: FTBFS: make: *** [debian/rules:10: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Wed, 11 Sep 2024 01:49:12 +0000
with message-id <E1soCTo-004Twr-***@fasolo.debian.org>
and subject line Bug#1077451: fixed in golang-github-gopacket-gopacket 1.3.0-1
has caused the Debian Bug report #1077451,
regarding golang-github-gopacket-gopacket: FTBFS: make: *** [debian/rules:10: binary] Error 25
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 ***@bugs.debian.org
immediately.)

[Debian Bug Tracking System]

unarchive -1
reopen -1

Bug #1077451 {Done: Stephen Gelman <***@debian.org>} [src:golang-github-gopacket-gopacket] golang-github-gopacket-gopacket: FTBFS: make: *** [debian/rules:10: binary] Error 25
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions golang-github-gopacket-gopacket/1.3.0-1.

notfixed -1 1.3.0-1

Bug #1077451 [src:golang-github-gopacket-gopacket] golang-github-gopacket-gopacket: FTBFS: make: *** [debian/rules:10: binary] Error 25
Ignoring request to alter fixed versions of bug #1077451 to the same values previously set

[Debian Bug Tracking System]

Your message dated Tue, 15 Oct 2024 05:42:38 +0000
with message-id <E1t0aKM-00783T-***@fasolo.debian.org>
and subject line Bug#1077451: fixed in golang-github-gopacket-gopacket 1.3.0-2
has caused the Debian Bug report #1077451,
regarding golang-github-gopacket-gopacket: FTBFS: make: *** [debian/rules:10: binary] Error 25
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 ***@bugs.debian.org
immediately.)