[Piuparts-devel] Bug#526045: Bug#526045: Patch

[Scott Schaefer]

On 06/26/2011 04:17 AM, Holger Levsen wrote:
> Hi Scott,
>
> I've applied your latest patch to trunk now and have been running it the last
> 12h or so on piatti.debian.org, with mixed results:
>
> a.) it's been testing packages now which have not been tested before, so yay.
>
> b.) it broke piuparts-reports, so not so yay.
>
> If you look on eg http://piuparts.debian.org/wheezy/ you'll see the
> distribution links in the menu on the left are broken and all the states are
> displayed wrongly. (Their names are missing, basically.)
>
>
> '
> but logfile contains 'command not found': 5 passed
> but logfile contains update-rc.d issues: 80 passed
>    30612  ' logs
>    '
> due to post-installation maintainer script failed: 5 bugged, 31 failed
> due to files having been modified after purge: 1 failed
> due to errors from cronjob after removal: 5 bugged, 1 failed
> due to post-removal maintainer script failed: 11 bugged, 30 failed
> due to not enough force being used: 1 failed
> due to purge failed due to an unknown reason: 11 bugged, 30 failed
> due to failing to setup a database: 17 failed
>    87  ' logs
> ' logs
>    '  1
>    '  60
>    '  104
>    '  84
>    '  37
>    '  0
>    '  5
>    '  272
>    '  4
>    '  2
>    '  0
>
> Yesterday this looked like this:
>
> successfully-tested
> but logfile contains 'command not found': 5 passed
> but logfile contains update-rc.d issues: 80 passed
>    30638  pass logs
>    failed-testing
> due to post-installation maintainer script failed: 5 bugged, 31 failed
> due to files having been modified after purge: 1 failed
> due to errors from cronjob after removal: 5 bugged, 1 failed
> due to post-removal maintainer script failed: 11 bugged, 30 failed
> due to unclassified failures: 1 failed
> due to not enough force being used: 1 failed
> due to purge failed due to an unknown reason: 11 bugged, 30 failed
> due to failing to setup a database: 17 failed
>    82  fail logs
> bugged logs
>    cannot-be-tested  0
>    essential-required  60
>    waiting-to-be-tested  0
>    waiting-for-dependency-to-be-tested  0
>    dependency-failed-testing  42
>    dependency-cannot-be-tested  0
>    dependency-does-not-exist  173
>    circular-dependency  273
>    unknown  0
>
> So the circular-depends moved to "dependency-cannot-be-tested", which is only
> half right...
>
> I dont have time to look into this the next week, so if you dont reply with a
> fix soon, I'll just revert the commit and wait for a better solution.
>
> (That's fine, I'm not in a hurry, and piuparts.debian.org can be broken for a
> day, no problem...)
>
>
> cheers,
> 	Holger
>    

Um ... This is probably (?) due to addition of new states in packagesdb 
module.

I will try to setup and test here, but I expect it would be much easier 
if I had the log
file output from piuparts-reports (and piuparts-analyze ?).

Is it possible for you to send those to me/point me to URL/dump into 
SVN, etc. ?