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

Bug#875771: marked as done (nmu: libnettle6_3.3-1+b1 liblzma5_5.2.2-1.2+b1 libdb5.35.3.28-12+b1 libselinux1_5.2.2-1.2+b1)

Your message dated Sat, 07 Oct 2017 11:33:55 +0100
with message-id <1507372435.18586.64.camel@adam-barratt.org.uk>
and subject line Closing bugs for 9.2 point release
has caused the Debian Bug report #875771,
regarding nmu: libnettle6_3.3-1+b1 liblzma5_5.2.2-1.2+b1 libdb5.35.3.28-12+b1 libselinux1_5.2.2-1.2+b1
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.)


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

nmu libnettle6_3.3-1+b1 liblzma5_5.2.2-1.2+b1 libdb5.35.3.28-12+b1 libselinux1_5.2.2-1.2+b1 . ALL . -m "fix wrong build date"

sbuild in versions older than 0.73.0-1 didn't use the build date as
binnmu changelog date. The binNMUs of libdb5.3, liblzma5, libnettle6
+ libselinux1 as present in stretch are affected by this (wrong)
behavior. (Related see #843773 + #873489.)

Thanks to Guillem for debugging help and Holger for assistance at
properly reporting this.

regards,
-mika-

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Version: 9.2

Hi.

The updates referenced by each of these bugs was included in today's
point release of stretch.

Regards,

Adam

--- End Message ---
Reply to: