So, far I have been attempting to incorporate your patches into the code, but I have decided to start from scratch again, and try and kill the RC bug (334697), I have been in contact with Aba (Andreas) and we should have some fresh data files built (based off the output of bts2ldap), I'm sure it can be easily phased by apt-listbugs with a bit of work.
The code which i've seen (on the qa.debian.org side), is just making a copy of all the .status files from the bts spool, which I believe sometime soon are going to be no more, which seems to suggest that a complete rewrite of the checking side of the program. Sadly however, it may not be possible to run the code at say midnight when the archive gets updates, due to what I am told is already busy load on qa., so we may need a message in listbugs stating that the data may be upto 12/24 hours out of date, we'll get to that when we come to it. Regards, Nigel [CCed to all relevant bug trackers I think I included all related] On 7/11/06, James Westby <[EMAIL PROTECTED]> wrote:
[Cced the bug again so that there is a record] On (09/07/06 19:09), Nigel Jones wrote: > Hi, I have noticed your interest in Debian bug 374104 [1], the > orphanage of apt-listbugs [2], and I am wondering if you are maybe > planning to ITAing it yourself, if not, I will do so, and if that is > the case, be really keen to fix certain bugs with you, i.e. the ones > you have created patches for etc. As I said in my first mail to the bug I don't really plan to adopt it, just to tidy it up, as the whole package is RC-buggy in my opinion. I have sent patches to the BTS where a clean patch was possible for the bug report, but I have much more done in my local copy. I can let you have my latest source if you let me know how you want it. It is an svn repo that starts from the current unstable package at the moment. I would be interested in working with you until the packages are in a decent shape again, how do you feel about this? My current version (I think) fixes all the bugs that do not require a major overhaul of the code. It also leaves the version tracking etc. problems as it appears the problem is within the code that generates the files that apt-listbugs uses to get the bug states, and I do not have access to that code. I believe that it runs on merkel, so maybe a DD can access it and make it publically available. > > Also out of interest, are you a DD? No, unfortuanately not. I was going to get a QA upload done, but as you are adopting then you can seek out a proper sponsor. James -- James Westby [EMAIL PROTECTED] http://jameswestby.net/
-- N Jones -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
