Bug#584125: RFH: piuparts.d.o is maintainance hungry
On Dienstag, 31. Mai 2011, Scott Schaefer wrote: please keep bugs cc:ed! :) My bad ... we all learn all the time. its only important to make new interesting mistakes and not to repeat boring old ones :-) see svn+ssh://hol...@svn.debian.org/svn/piuparts/piatti/README.txt Ah... I cloned the entire SVN repo a week ago, but I hadn't looked in the directories other than /trunk. :) I found the main, front page at http://wiki.debian.org/piuparts/, which has the to be written. The README has good info; indeed, it may be entirely adequate. Unfortunately, what I expected was the best info ... the README link to http://svn.debian.org/viewsvn/piuparts/piatti/README.txt?view=markup .. is broken. I expect it is due to Alioth transition. Since it was not important at the time, I was unconcerned. I can assume that is built from, or nearly identical to version in svn:.../piatti/README.txt. yes I've now asked #alioth about the url issue..no reply yet :) I very, very much doubt you are older than me ! hehe + whatever ;) cheers, Holger -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201105310751.58932.hol...@layer-acht.org
Bug#584125: RFH: piuparts.d.o is maintainance hungry
Hi Scott thanks for your offer to help with piuparts! Much appreciated! On Mittwoch, 25. Mai 2011, Scott Schaefer wrote: If you have 10-15 minutes, can you reply with more details re your statement Running p.d.o is quite maintenance-hungry, and what tasks you might be looking to offload. 1. filing bug reports (and following up on them) 2. set up a piuparts master-slave instance yourself and turn those shell scripts grep'ing for certain kinds of errors into better python code ;-) I can explain both tasks in more detail should you be interested. I have reasonable working knowledge of packaging internals/tools, and can likely read/analyze logs. yay! cheers, Holger -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201105301548.00126.hol...@layer-acht.org
Bug#584125: RFH: piuparts.d.o is maintainance hungry
Hi Scott, please keep bugs cc:ed! :) On Montag, 30. Mai 2011, Scott Schaefer wrote: I can explain both tasks in more detail should you be interested. Yes. I am interested. Please provide greater detail when you are able. yay! keep on asking/commenting! Since it appears that most important bug is 526045 well... it has the highest severity for sure... (as its a rather high impact blocker...) - but then there are other things which are blocking/rather very importing too, eg aiding bug filing or better reporting. Those things are harder to file in the BTS (and probably would be severity wishlist then), while they are also very much needed. (ie piuparts-report now runs for several hours each day. if there would be caching of the logfile-analysises this could probably go down to a few minutes, thus taking away load _and_ making development in this area much easier. aiding bugfiling (=sub-automatic bug filing) has obvious benefits to me. bugs not filed are bugs not likely to be fixed, whether they are shown on piuparts.d.o or not...)) but really, pick what interests you! :-) , and from your earlier reply, I will need to setup master/slave to attempt to resolve, I will set this as my goal for next few days. Since README is missing the section on how to do that, I will probably try to produce a document. see svn+ssh://hol...@svn.debian.org/svn/piuparts/piatti/README.txt have you looked at http://wiki.debian.org/piuparts/ ? It has a Howto setup a piuparts test-instance for development which says: *to be written* - maybe you can enhance that and eg. need the link to the above mentioned README.txt?! :) hm, but then this url _is_ mentioned in http://piuparts.debian.org/doc/README.html#_running_piuparts_in_master_slave_mode_piuparts_report_and_the_setup_on_piuparts_debian_org but still - I'm the old fart here and you didnt find the information, so probably _you_ have more useful insight how to improve the docs than I do! ;-) I have limited my work so far to direct (??) mode; i.e. not master-slave. Still in the introductory stage of understanding. Please do not hesitate to tell me if I am headed in wrong direction. direct mode works reasonable well, there is IMO more room for improvement in the parts that deal with processing 30k logs per distro, IOW, large scale testing. but it's also (always) the little things that matter much! cheers, Holger -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201105302326.59341.hol...@layer-acht.org
Bug#584125: RFH: piuparts.d.o is maintainance hungry
On 05/30/2011 05:26 PM, Holger Levsen wrote: Hi Scott, please keep bugs cc:ed! :) My bad ... On Montag, 30. Mai 2011, Scott Schaefer wrote: I can explain both tasks in more detail should you be interested. Yes. I am interested. Please provide greater detail when you are able. yay! keep on asking/commenting! Since it appears that most important bug is 526045 well... it has the highest severity for sure... (as its a rather high impact blocker...) - but then there are other things which are blocking/rather very importing too, eg aiding bug filing or better reporting. Those things are harder to file in the BTS (and probably would be severity wishlist then), while they are also very much needed. (ie piuparts-report now runs for several hours each day. if there would be caching of the logfile-analysises this could probably go down to a few minutes, thus taking away load _and_ making development in this area much easier. aiding bugfiling (=sub-automatic bug filing) has obvious benefits to me. bugs not filed are bugs not likely to be fixed, whether they are shown on piuparts.d.o or not...)) but really, pick what interests you! :-) , and from your earlier reply, I will need to setup master/slave to attempt to resolve, I will set this as my goal for next few days. Since README is missing the section on how to do that, I will probably try to produce a document. see svn+ssh://hol...@svn.debian.org/svn/piuparts/piatti/README.txt Ah... I cloned the entire SVN repo a week ago, but I hadn't looked in the directories other than /trunk. have you looked at http://wiki.debian.org/piuparts/ ? It has a Howto setup a piuparts test-instance for development which says: *to be written* - maybe you can enhance that and eg. need the link to the above mentioned README.txt?! :) hm, but then this url _is_ mentioned in http://piuparts.debian.org/doc/README.html#_running_piuparts_in_master_slave_mode_piuparts_report_and_the_setup_on_piuparts_debian_org I found the main, front page at http://wiki.debian.org/piuparts/, which has the to be written. The README has good info; indeed, it may be entirely adequate. Unfortunately, what I expected was the best info ... the README link to http://svn.debian.org/viewsvn/piuparts/piatti/README.txt?view=markup .. is broken. I expect it is due to Alioth transition. Since it was not important at the time, I was unconcerned. I can assume that is built from, or nearly identical to version in svn:.../piatti/README.txt. but still - I'm the old fart here and you didnt find the information, so probably _you_ have more useful insight how to improve the docs than I do! ;-) I very, very much doubt you are older than me ! I have limited my work so far to direct (??) mode; i.e. not master-slave. Still in the introductory stage of understanding. Please do not hesitate to tell me if I am headed in wrong direction. direct mode works reasonable well, there is IMO more room for improvement in the parts that deal with processing 30k logs per distro, IOW, large scale testing. but it's also (always) the little things that matter much! cheers, Holger -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4de4258a.1010...@neurodiverse.org
Bug#584125: RFH: piuparts.d.o is maintainance hungry
I am interested in helping. In addition, automated testing is one of my interests. I have done my share of QA over the years, though in different environments. I have begun helping out the OpenSSL project to a small degree (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332498), but I do not yet want to commit to something I am unsure wrt to either abilities and/or time. The same would apply to this RFH ... I will begin by looking at what I can do, and, subject to your telling me you no longer need help, we can see how this develops. If you have 10-15 minutes, can you reply with more details re your statement Running p.d.o is quite maintenance-hungry, and what tasks you might be looking to offload. I have reasonable working knowledge of packaging internals/tools, and can likely read/analyze logs. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ddc4937.6060...@neurodiverse.org
