[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#861226: marked as done (unblock: gopacket/1.1.12-2)

Your message dated Wed, 26 Apr 2017 16:36:00 +0000
with message-id <0ca57921-fe24-09fa-e1be-5384c50db476@thykier.net>
and subject line Re: Bug#861226: unblock: gopacket/1.1.12-2
has caused the Debian Bug report #861226,
regarding unblock: gopacket/1.1.12-2
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.)


-- 
861226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861226
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock gopacket. The current version in unstable fixes RC bug
#860692 by simply adjusting a variable in d/rules to match the correct
path component on the i386 architecture. From my own test builds in an
i386 pbuilder chroot, I can confirm this resolves the FTBFS currently
observed in stretch.

IMHO the update is suitable for stretch as it only introduces the
minimum of change necessary to fix the bug; no patches to the source
are necessary.

If there are any more questions, please do not hesitate to ask.
I have attached a debdiff of the version in testing (1.1.12-1) against
the one in unstable (1.1.12-2).

unblock gopacket/1.1.12-2

Kind regards
Sascha

diff -Nru gopacket-1.1.12/debian/changelog gopacket-1.1.12/debian/changelog
--- gopacket-1.1.12/debian/changelog	2016-11-14 11:14:16.000000000 +0100
+++ gopacket-1.1.12/debian/changelog	2017-04-26 10:00:35.000000000 +0200
@@ -1,3 +1,11 @@
+gopacket (1.1.12-2) unstable; urgency=medium
+
+  * Team upload.
+  * Use DEB_HOST_GNU_TYPE to fix building on i386.
+    Closes: #860692
+
+ -- Sascha Steinbiss <satta@debian.org>  Wed, 26 Apr 2017 10:00:35 +0200
+
 gopacket (1.1.12-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru gopacket-1.1.12/debian/rules gopacket-1.1.12/debian/rules
--- gopacket-1.1.12/debian/rules	2016-11-14 11:14:16.000000000 +0100
+++ gopacket-1.1.12/debian/rules	2017-04-26 10:00:35.000000000 +0200
@@ -19,7 +19,7 @@
 	dh_auto_configure
 	rm -rf $(patsubst %,obj-*/src/$(DH_GOPKG)/%,$(NOBUILD))
 	# Copy test files to build dir
-	cp pcap/*.pcap obj-$(DEB_HOST_MULTIARCH)/src/$(DH_GOPKG)/pcap/
+	cp pcap/*.pcap obj-$(DEB_HOST_GNU_TYPE)/src/$(DH_GOPKG)/pcap/
 
 override_dh_install:
 	dh_install --fail-missing

--- End Message ---
--- Begin Message --- 
Sascha Steinbiss:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> Please unblock gopacket. The current version in unstable fixes RC bug
> #860692 by simply adjusting a variable in d/rules to match the correct
> path component on the i386 architecture. From my own test builds in an
> i386 pbuilder chroot, I can confirm this resolves the FTBFS currently
> observed in stretch.
> 
> IMHO the update is suitable for stretch as it only introduces the
> minimum of change necessary to fix the bug; no patches to the source
> are necessary.
> 
> If there are any more questions, please do not hesitate to ask.
> I have attached a debdiff of the version in testing (1.1.12-1) against
> the one in unstable (1.1.12-2).
> 
> unblock gopacket/1.1.12-2
> 
> Kind regards
> Sascha
> 

Unblocked, thanks.

~Niels

--- End Message ---
Reply to: