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

Bug#926426: marked as done (unblock: python-smoke-zephyr/1.4.1-1)

Your message dated Fri, 05 Apr 2019 14:34:12 +0000
with message-id <E1hCPv2-0003Vv-BT@respighi.debian.org>
and subject line unblock python-smoke-zephyr
has caused the Debian Bug report #926426,
regarding unblock: python-smoke-zephyr/1.4.1-1
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.)


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

Hello,

I'm asking for the unblock of python-smoke-zephyr
 because a critical bug was solved upstream.

This bug was detected in the past and me and upstream thought it was fixed already[0], then after it was reported again recently[1]  we found out that the problem still persisted.

This time I first tried to fix the problem by uploading 1.4.0-2, and while it was on Unstable I think somebody else filled an unblock request and it was granted, but before this version hit testing I uploaded the correct fix (1.4.1-1) to unstable, that's why you can see two changelog entries on the debdiff.

Thanks
--
Samuel Henrique <samueloph>

Attachment: python-smoke-zephyr.debdiff
Description: Binary data


--- End Message ---
--- Begin Message --- 
Unblocked python-smoke-zephyr.

--- End Message ---
Reply to: