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

Bug#925576: marked as done (unblock: python-trustme/0.4.0-2)

Your message dated Wed, 27 Mar 2019 06:34:00 +0000
with message-id <f4f76ae5-a8d7-55bb-9f83-007372a73dc8@thykier.net>
and subject line Re: Bug#925576: unblock: python-trustme/0.4.0-2
has caused the Debian Bug report #925576,
regarding unblock: python-trustme/0.4.0-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.)


-- 
925576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925576
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 package python-trustme

This fixes an FTBFS. The package previously built fine, pulling in
python3-idna implicitly via python3-cryptography via python3-openssl.
Since then, python3-cryptography stopped depending on python3-idna,
exposing the bug that python-trustme's build does actually depend on
python3-idna but this wasn't explicitly declared. This change declares
explicitly what was being pulled in previously, so shouldn't in itself
cause any functional change; only the FTBFS will be fixed (along with
the usual regression risk associated with a rebuild).

diff -Nru python-trustme-0.4.0/debian/changelog python-trustme-0.4.0/debian/changelog
--- python-trustme-0.4.0/debian/changelog	2018-10-13 22:48:59.000000000 +0100
+++ python-trustme-0.4.0/debian/changelog	2019-03-26 23:23:50.000000000 +0000
@@ -1,3 +1,10 @@
+python-trustme (0.4.0-2) unstable; urgency=medium
+
+  * Explicitly build-depend on python3-idna to fix FTBFS.
+    Closes: #925566.
+
+ -- Robie Basak <robie@justgohome.co.uk>  Tue, 26 Mar 2019 23:22:42 +0000
+
 python-trustme (0.4.0-1) unstable; urgency=low
 
   * Initial release. Closes: #910951.
diff -Nru python-trustme-0.4.0/debian/control python-trustme-0.4.0/debian/control
--- python-trustme-0.4.0/debian/control	2018-10-13 22:48:59.000000000 +0100
+++ python-trustme-0.4.0/debian/control	2019-03-26 23:21:57.000000000 +0000
@@ -6,6 +6,7 @@
 Build-Depends: debhelper (>= 9~),
                dh-python,
                python3,
+               python3-idna,
                python3-openssl,
                python3-pytest,
                python3-service-identity,

unblock python-trustme/0.4.0-2

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Robie Basak:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> Please unblock package python-trustme
> 
> This fixes an FTBFS. The package previously built fine, pulling in
> python3-idna implicitly via python3-cryptography via python3-openssl.
> Since then, python3-cryptography stopped depending on python3-idna,
> exposing the bug that python-trustme's build does actually depend on
> python3-idna but this wasn't explicitly declared. This change declares
> explicitly what was being pulled in previously, so shouldn't in itself
> cause any functional change; only the FTBFS will be fixed (along with
> the usual regression risk associated with a rebuild).
> 
> [...]
> 
> unblock python-trustme/0.4.0-2
> 

Unblocked, thanks.
~Niels

--- End Message ---
Reply to: