Bug#703902: [Piuparts-devel] Bug#703902: adequate testing

2013-05-22 Thread Holger Levsen
Hi, adequate is now installed on piu-slave-bm-a.d.o and the patch has been applied there too, IOW all new piuparts tests running there will fire up adequate at the end \o/ Plus I rescheduled these (known failing) packages in sid + wheezy, so tomorrow we shall have some failures found: openssh

Bug#703902: [Piuparts-devel] Bug#703902: adequate testing

2013-05-21 Thread Holger Levsen
On Dienstag, 21. Mai 2013, Jakub Wilk wrote: > Now tracked as #709187. > Nah, /usr/share/doc/ is already whitelisted. :) > Now tracked as #709192. > And I've just uploaded adequate_0.5.2~bpo70+1 to backports-master. cool! :-) signature.asc Description: This is a digitally signed message part.

Bug#703902: adequate testing

2013-05-21 Thread Jakub Wilk
* Holger Levsen , 2013-05-21, 13:18: FWIW, this is a false-positive: apport never imports these files[0], so there's no benefit from byte-compilation. I'll whitelist /usr/share/apport/package-hooks/ in the next release. good, thanks. Now tracked as #709187. python-apt-common: py-file-not-by

Bug#703902: adequate testing

2013-05-21 Thread Jakub Wilk
* Holger Levsen , 2013-05-21, 12:55: root@matrix:~# adequate --all openssh-client: py-file-not-bytecompiled /usr/share/apport/package-hooks/openssh-client.py FWIW, this is a false-positive: apport never imports these files[0], so there's no benefit from byte-compilation. I'll whitelist /usr/

Bug#703902: [Piuparts-devel] Bug#703902: Bug#703902: adequate testing

2013-05-21 Thread Holger Levsen
Hi Andreas, On Dienstag, 21. Mai 2013, Andreas Beckmann wrote: > I just started running adequate in my instance, too. \o/ :) > Do you have some examples for inadequate packages that I could retest? root@matrix:~# adequate --all openssh-client: py-file-not-bytecompiled /usr/share/apport/package-

Bug#703902: [Piuparts-devel] Bug#703902: adequate testing

2013-05-21 Thread Andreas Beckmann
On 2013-05-18 15:33, Jakub Wilk wrote: > * Holger Levsen , 2013-05-18, 14:22: >> did you run adequate against the archive? did it give adequate >> results? or should we expect a lot of issues when running it against I just started running adequate in my instance, too. Do you have some examples for

Bug#703902: [Piuparts-devel] Bug#703902: adequate testing

2013-05-18 Thread Dave Steele
On Sat, May 18, 2013 at 9:54 AM, Holger Levsen wrote: > >> I do however test every release by running --all on my own system. >> Currently adequate emits tags for about 3% packages here. > > 3% of 40k means... about 1200 issues to be fixed. whoa. So we'll indeed start > with warnings only. > > If

Bug#703902: adequate testing

2013-05-18 Thread Holger Levsen
Hi, On Samstag, 18. Mai 2013, Jakub Wilk wrote: > I haven't run it archive-wide. ok. > I do however test every release by running --all on my own system. > Currently adequate emits tags for about 3% packages here. 3% of 40k means... about 1200 issues to be fixed. whoa. So we'll indeed start w

Bug#703902: adequate testing

2013-05-18 Thread Jakub Wilk
* Holger Levsen , 2013-05-18, 14:22: did you run adequate against the archive? did it give adequate results? or should we expect a lot of issues when running it against 40k packages? I haven't run it archive-wide. I do however test every release by running --all on my own system. Currently a

Bug#703902: adequate testing

2013-05-18 Thread Holger Levsen
Hi Jakub, did you run adequate against the archive? did it give adequate results? or should we expect a lot of issues when running it against 40k packages? cheers, Holger, just curious! :-) signature.asc Description: This is a digitally signed message part.