On Thu, 26 Dec 2013, Francesco Poli wrote: > > > There are a few more bugs (which render the package unusable, for me) > > listed on the http://bugs.debian.org/apt-listbugs. Notable: 730822, > > Bug #730822 is tagged as "pending": it will be fixed in the next upload > (which will happen as soon as I find a little time to finalize > apt-listbugs version 0.1.12).
Sounds good. > In the meanwhile you may manually fix the issue as explained in > http://bugs.debian.org/730822#17 I obviously missed that :( I'll try it in a jiffy... Alright. That seems to work :) Thanks. > > 725672. Another ruby package, ruby-soap4r, is blamed for the 725672 > > trouble. > > Bug #725672 is a ruby-soap4r issue, as you correctly noticed. > Unfortunately, I don't have the time to study ruby-soap4r internals and > investigate the issue in the hope to devise a fix. > Please cooperate with ruby-soap4r maintainers to find a solution, if > you are able to help. Unfortunately, my ruby fu isn't that strong :) > > It's a bit messy situation right now. Any chance of sorting this out > > soon? apt-listbugs is quite useful to me. I'd hate to loose it. > > I can understand, but you should be able to use apt-listbugs itself to > work around the issues: after downgrading ruby-locale to version > 2.0.9-1, you may use apt-listbugs to pin it to that version until this > bug is fixed. Already done something like that. I've put apt-listbugs on hold. > For the two other bugs, please see the above described suggestions. Done. Cheers, -- Cristian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org