Please backport znc 1.0-2 (universe) from raring
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Precise Backports |
Fix Released
|
Undecided
|
Micah Gersten |
Bug Description
Please backport znc 1.0-2 (universe) from raring to precise.
Reason for the backport:
=======
ZNC 1.0 is substantially newer than ZNC 0.206. I'd like to see the newer version in Precise.
NOTE: Quantal backport (which needs to be done prior to the precise backport) is in another bug: https:/
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 raring -d precise znc
$ backportpackage -u ppa:<lp username>/<ppa name> -s raring -d quantal znc
* precise:
[X] Package builds without modification
[X] znc installs cleanly and runs
[X] znc-dev installs cleanly and runs
[X] znc-perl installs cleanly and runs
[X] znc-tcl installs cleanly and runs
[X] znc-extra installs cleanly and runs
[X] znc-dbg installs cleanly and runs
[X] znc-python installs cleanly and runs
No reverse dependencies
Related branches
no longer affects: | quantal-backports |
A few things:
(1) znc-dbg is debugging symbols, and according to Micah, if it installs that should be sufficient for checks for that.
(2) Build tests were in my PPA, https:/ /launchpad. net/~trekcaptai nusa-tw/ +archive/ znc
(3) The "Quantal Backports" bug for this is tracked in https:/ /bugs.launchpad .net/quantal- backports/ +bug/1085731. I realize now after-the-fact i should've just filed a backport request for precise with requestbackport, and saved you all the trouble. If applicable, remove "Quantal Backports" from this bug.