[Bug 684842] Re: Please backport git 1.7.3.2 to Maverick

2011-05-26 Thread angelsl
That would be fine, however I have updated to Natty so I don't need it anymore. Thanks a lot for replying though. -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to maverick-backports. https://bugs.launchpad.net/bugs/684842 Title:

[Bug 684842] Re: Please backport git 1.7.3.2 to Maverick

2011-05-26 Thread Evan Broder
** Changed in: maverick-backports Status: Incomplete = Won't Fix -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to maverick-backports. https://bugs.launchpad.net/bugs/684842 Title: Please backport git 1.7.3.2 to Maverick --

[Bug 783006] Re: Please backport focuswriter 1.3.2.git.69e4975b-1 from oneiric to lucid, maverick, natty

2011-05-26 Thread Eliah Kagan
I tested focuswriter 1.3.2.git.69e4975b-1~lucid1~ppa2 from the PPA on Lucid. It installed and ran without problems. Unlike the Maverick version, no text was printed to stderr as it ran. ** Changed in: lucid-backports Status: Incomplete = Confirmed -- You received this bug notification

[Bug 783006] Re: Please backport focuswriter 1.3.2.git.69e4975b-1 from oneiric to lucid, maverick, natty

2011-05-26 Thread Eliah Kagan
(In case it's relevant, even though it doesn't have to be tested on multiple architectures--this Lucid system was also i386.) -- You received this bug notification because you are a member of Ubuntu Backporters, which is the registrant for natty-backports. https://bugs.launchpad.net/bugs/783006

[Bug 783006] Re: Please backport focuswriter 1.3.2.git.69e4975b-1 from oneiric to lucid, maverick, natty

2011-05-26 Thread Evan Broder
Great. ACK from backporters. ** Changed in: lucid-backports Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Backporters, which is the registrant for natty-backports. https://bugs.launchpad.net/bugs/783006 Title: Please backport

[Bug 721886] Re: Please backport tor-arm 1.4.0.1-2 from natty to lucid, maverick

2011-05-26 Thread Damian Johnson
Thanks Evan. I've tested the packages, using them to monitor a Tor relay. Both look good. -Damian ** Changed in: lucid-backports Status: Incomplete = Confirmed ** Changed in: maverick-backports Status: Incomplete = Confirmed -- You received this bug notification because you are

[Bug 721886] Re: Please backport tor-arm 1.4.0.1-2 from natty to lucid, maverick

2011-05-26 Thread Damian Johnson
Ack, missed the last bit of the comment - I installed and ran them both on karmic but not maverick/lucid. This is a pure python package and been exercised on several Debian, Ubuntu, Gentoo, Arch Linux, and Slackware versions already without any platform-specific issues. If it's really _vital_ that

[Bug 721886] Re: Please backport tor-arm 1.4.0.1-2 from natty to lucid, maverick

2011-05-26 Thread Evan Broder
Our experience has been that this test is not pointless, which is why it is a hard requirement for the backports process. Testing inside of a lucid/maverick chroot is acceptable, but testing on a different release is not. ** Changed in: lucid-backports Status: Confirmed = Incomplete **

[Bug 721886] Re: Please backport tor-arm 1.4.0.1-2 from natty to lucid, maverick

2011-05-26 Thread Damian Johnson
Found a volunteer that tested on lucid (10.04), still trying to find someone with maverick. ** Changed in: lucid-backports Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to lucid-backports.

[Bug 788818] Re: Assertion failure when unbound generates an empty error reply in response to a query

2011-05-26 Thread Scott Kitterman
Fixed in oneiric. unbound (1.4.10-1ubuntu1) oneiric; urgency=low * Merge from debian unstable. Remaining changes: - Fix build to work with default python other than python2.6 - Generalize install rule in debian/python-unbound.install - Use pyversions -d to determine where to

[Bug 788818] Re: Assertion failure when unbound generates an empty error reply in response to a query

2011-05-26 Thread Scott Kitterman
The actual upstream change once you filter through all the tool cruft between 1.4.9 and 1.4.10. Also confirmed by looking at the upstream svn. See svn diff -c2419 in http://unbound.nlnetlabs.nl/svn/trunk/ . I may get time for debdiffs later, but here's the basic patch in case someone wants to

[Bug 654591] Re: Please backport boinc 6.10.58+dfsg-3 and boinc-app-seti 5.13+cvs20060510-7 from Maverick to Lucid

2011-05-26 Thread Evan Broder
ACK from backporters. ** Summary changed: - Please backport boinc and boinc-app-seti from Maverick to Lucid + Please backport boinc 6.10.58+dfsg-3 and boinc-app-seti 5.13+cvs20060510-7 from Maverick to Lucid ** Changed in: lucid-backports Status: Confirmed = In Progress ** Changed in:

[Bug 788818] Re: Assertion failure when unbound generates an empty error reply in response to a query

2011-05-26 Thread Scott Kitterman
debdiff for Natty. -- You received this bug notification because you are a member of Ubuntu Backporters, which is a direct subscriber. https://bugs.launchpad.net/bugs/788818 Title: Assertion failure when unbound generates an empty error reply in response to a query -- ubuntu-backports

[Bug 788818] Re: Assertion failure when unbound generates an empty error reply in response to a query

2011-05-26 Thread Scott Kitterman
Remembered to add the bug number to debian/changelog ** Patch added: Natty debdiff again https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/788818/+attachment/2144271/+files/natty.debdiff ** Changed in: unbound (Ubuntu Natty) Status: Triaged = Confirmed -- You received this bug

[Bug 788818] Re: Assertion failure when unbound generates an empty error reply in response to a query

2011-05-26 Thread Scott Kitterman
Testing done for Natty: None - This is the same change to 1.4.9 that upstream made for 1.4.10. -- You received this bug notification because you are a member of Ubuntu Backporters, which is a direct subscriber. https://bugs.launchpad.net/bugs/788818 Title: Assertion failure when unbound