Osamu Aoki dixit: >If you happen to worry library dependency, it may help adding
I don’t think so, at least not yet. I couldn’t use the information. >Please remember SC#4 "Our priorities are our users and free software". > >At least you created an iffy user. I wonder what happened on all >security fixes done between upstream release of 2006 and last Debian >package before yours in 2008. ① I’m a user, too. ② I’ve closed about half of the open bugs in cvs, all but one of the bugs reported in Launchpad, written new functionality, etc. when I took over this package; if I created one or two new prob‐ lems, this is a small price to pay – especially since these can be addressed later (i.e. now). ③ I don’t think there were any security related fixes. I remember looking through the patches applied to Debian’s cvs package and porting them over to MirBSD, when needed; testing there; writing documentation for these that were kept, and dropping these that were buggy. If you really wonder I can dig out the relevant info for you, but that doesn’t belong into this bugreport. Or you can take my word on it. ④ If you want to help… regarding point ②, most of the remaining bug reports need to be forwarded upstream (either can’t do in Debian what they want, or won’t do the decision to deviate from upstream) or closed (as done, unreproducible, etc). But I personally think http://qa.debian.org/data/bts/graphs/c/cvs.png shows a good trend. bye, //mirabilos -- Support mksh as /bin/sh and RoQA dash NOW! ‣ src:bash (256 (275) bugs: 0 RC, 177 (192) I&N, 79 (83) M&W, 0 F&P) ‣ src:dash (81 (89) bugs: 3 RC, 43 (46) I&N, 35 (40) M&W, 0 F&P) ‣ src:mksh (2 bugs: 0 RC, 0 I&N, 2 M&W, 0 F&P) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
