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

Bug#784963: marked as done (jessie-pu: preapproval for gdnsd/2.1.2-1~deb8u1)

Your message dated Sat, 06 Jun 2015 13:11:11 +0100
with message-id <1433592671.2987.12.camel@adam-barratt.org.uk>
and subject line Fix released with 8.1 point release
has caused the Debian Bug report #784963,
regarding jessie-pu: preapproval for gdnsd/2.1.2-1~deb8u1
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.)


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

Hi,

I'd like to upload new version of gdnsd to spu. This would be a new upstream
release, 2.1.2, but this is from the 2.1.x stable maintenance branch which
contains only critical fixes. Upstream is using SemVer and has moved major
releases to the 2.2.x versioning scheme (2.2.0 was released a few months ago).

There are no Debian-related changes between 2.1.0-1 and 2.1.2-1[1].
Upstream-wise, the 2.1.0 - 2.1.2 work is 8 commits[2] which can be documented
with the following changelog:

2.1.2 - 2015-05-06
    * Cherrypicked manpage title bugfix from v2.2.0 - (was f7672493 there)
      (Because newer perl pod2man commands fail completely without
      a valid title)

2.1.1 - 2014-12-30
  *** Bugfixes backported from master branch:
    * Fixed incorrect error-handling code for the sendmmsg() syscall, which
      could have caused an unecessary additional dropped packet and/or
      bad error messages after failing to send one or more packets from a set.
    * The per-address level udp_recv_width option is now correctly limited to
      a value of 64 (previously it was being incorrectly limited to 32).
    * plugin_multifo no longer pointlessly limits to 64 addrs per family
    * plugin_extmon bugfix for bad timeout/interval behavior if either >255s
    * if the stats http socket failed to bind() on startup, the daemon
      could carry on anyways, causing it to bind to a different, arbitrary
      port number
    * Fixed autoconf 2.63 compat when running autoreconf (broken in 2.1.0)

2.1.2-1 has been upload to unstable and has migrated to testing already.

(I can attach a full debdiff if requested, essentially all upstream and same to
jessie->stretch diff; let me know)

Thanks for the consideration,
Faidon

1: https://github.com/paravoid/gdnsd/commits/debian
2: https://github.com/gdnsd/gdnsd/commits/2.1.x

--- End Message ---
--- Begin Message --- 
Version: 8.1

Hi,

The fix discussed in this bug was released to stable as part of the 8.1
point release earlier today.

Regards,

Adam

--- End Message ---
Reply to: