Please backport libnss-cache 0.12-1 (universe) from utopic

Bug #1323161 reported by Jeff Bailey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
trusty-backports
Fix Released
Undecided
Unassigned

Bug Description

Please backport libnss-cache 0.12-1 (universe) from utopic to trusty.

Reason for the backport:
========================
I fixed 0.11-1 in Debian to work on any architecture, such as ppc64el and
arm64, but only 0.10 made it into Trusty.

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 utopic -d trusty libnss-cache

* trusty:
[X] Package builds without modification
[ ] libnss-cache installs cleanly and runs

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

libnss-cache
------------
* nsscache
  [ ] trusty (Reverse-Recommends)

Revision history for this message
Jeff Bailey (jbailey) wrote :

I'm pretty confident that this works on Trusty - I did the work on Trusty on ppc64el and arm64. Reverse dependencies shouldn't matter because the code wasn't changed in any way that affects an architecture for which it already compiled. The code itself wasn't changed significantly, it was mostly tooling. The author tested it on x86 in Debian.

Revision history for this message
Iain Lane (laney) wrote :

Accepted into trusty-backports

Changed in trusty-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.