Please backport unbound 1.4.18-1 (universe) from quantal

Bug #1158766 reported by Michael Vogt
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Precise Backports
Fix Released
Undecided
Unassigned

Bug Description

Please backport unbound 1.4.18-1 (universe) from quantal to precise.

Reason for the backport:
========================
The newer version of unbound supports round-robin rrset DNS.

Testing:
========
Mark off items in the checklist [X] as you test them, but please leave the checklist so that backporters can quickly evaluate the state of testing.

You can test-build the backport in your PPA with backportpackage:
$ backportpackage -u ppa:<lp username>/<ppa name> -s quantal -d precise unbound

* precise:
[no] Package builds without modification
[x] libunbound2 installs cleanly and runs
[x] unbound installs cleanly and runs
[x] python-unbound installs cleanly and runs
[x] unbound-anchor installs cleanly and runs
[x] unbound-host installs cleanly and runs
[x] libunbound-dev installs cleanly and runs

Reverse dependencies:
=====================
The following reverse-dependencies need to be tested against the new version of unbound. For reverse-build-dependencies (-Indep), please test that the package still builds against the new unbound. For reverse-dependencies, please test that the version of the package currently in the release still works with the new unbound installed. Reverse- Recommends, Suggests, and Enhances don't need to be tested, and are listed for completeness-sake.

libunbound2
-----------
* autotrust
  [x] precise (Reverse-Depends)
* opendkim
  [x] precise (Reverse-Depends)

unbound
-------

python-unbound
--------------

unbound-anchor
--------------

unbound-host
------------

libunbound-dev
--------------
* autotrust
  [x] precise (Reverse-Build-Depends)
  [x] precise (Reverse-Build-Depends)
* opendkim
  [x] precise (Reverse-Build-Depends)
  [x] precise (Reverse-Build-Depends)

Revision history for this message
Michael Vogt (mvo) wrote :

This reverts
"""
  * Build-depend on libldns-dev (>= 1.6.13~) for ECDSA support.
"""
from the "unbound (1.4.17-2) unstable; urgency=low" upload.

but otherwise a stock backport.

Michael Vogt (mvo)
description: updated
Revision history for this message
Michael Vogt (mvo) wrote :

Note that I'm happy to do the upload/backport of this to precise-backports I'm just not very familiar with the policies of the backports team but if you help me a bit I can probably do all the heavy lifting myself :)

Revision history for this message
Michael Vogt (mvo) wrote :

So far this got only light testing, but we will use the backport unbound on our production DNS soon so we should have much more data in a couple of days.

Revision history for this message
Iain Lane (laney) wrote : Re: [Bug 1158766] Re: Please backport unbound 1.4.18-1 (universe) from quantal

On Fri, Mar 22, 2013 at 02:33:06PM -0000, Michael Vogt wrote:
> Note that I'm happy to do the upload/backport of this to precise-
> backports I'm just not very familiar with the policies of the backports
> team but if you help me a bit I can probably do all the heavy lifting
> myself :)

Sounds fine to me if you've tested it to work. Approved by
ubuntu-backporters.

I don't mind if you would like to upload - I'll review in the queue if
so.

Some tips.

Changelog/changes target precise-backports
Version <version being backported>~ubuntu12.04.1
Changelog message "Source change backport to Precise (LP: #xxxx)
    - List of changes"
debuild -S -v<version in precise>
Diff the minimal required to effect the backport.

--
Iain Lane [ <email address hidden> ]
Debian Developer [ <email address hidden> ]
Ubuntu Developer [ <email address hidden> ]

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your feedback and your approval for the backport!

We are still testing the backport in our environment. But in the meantime the full debdiff with debian/changelog. I'm happy to upload this once we are finished with the testing.

Revision history for this message
Felix Geyer (debfx) wrote :

This seems to have landed in precise-backports already.

Changed in precise-backports:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.