[12:42] -queuebot:#ubuntu-release- New: accepted astyle [amd64] (zesty-proposed) [2.06-2]
[12:42] -queuebot:#ubuntu-release- New: accepted astyle [armhf] (zesty-proposed) [2.06-2]
[12:42] -queuebot:#ubuntu-release- New: accepted astyle [powerpc] (zesty-proposed) [2.06-2]
[12:42] -queuebot:#ubuntu-release- New: accepted astyle [arm64] (zesty-proposed) [2.06-2]
[12:42] -queuebot:#ubuntu-release- New: accepted astyle [s390x] (zesty-proposed) [2.06-2]
[12:42] -queuebot:#ubuntu-release- New: accepted astyle [i386] (zesty-proposed) [2.06-2]
[13:59] <mapreri> could somebody please the 'force-badtest diffoscope/all/ppc64el' from pitti's hint file?  I think I have fixed it, and if not, I'm working on it.
[14:00] <mapreri> I mean, please *drop* that hint
[19:26] -queuebot:#ubuntu-release- New sync: golang-github-golang-leveldb (zesty-proposed/primary) [0.0~git20161231.0.3435554-1]
[20:05] <apw> mapreri, gone
[20:06] <mapreri> apw: Thank you
[20:07] <mapreri> (ftr, in my test upload the test passed :))
[20:15] <mapreri> apw: btw, you can also remove your own hint for diffoscope/67/armhf now
[20:15] <mapreri> I'm curious, you (~ubuntu-release) don't seem to clean up your hint files periodically :)
[20:16] <apw> mapreri, we are meant to :)
[20:16] <mapreri> meant to keep stuff, or meant to clean?
[20:16] <apw> mapreri, dropped ...
[20:16] <apw> mapreri, it makes sense to keep them until the version is no longer in any pocket
[20:17] <mapreri> sure
[20:17] <apw> mapreri, and it is all currently manual and i am lazy apparently
[20:17] <mapreri> Debian's release team has a `hint` script which also does cleaning https://anonscm.debian.org/git/mirror/release-tools.git/tree/scripts/hint
[20:18] <mapreri> cleaning there is "moving after a 'finished' hint"
[20:19] <apw> interesting, that does seem like something we should look into, debian is bound to be ahead
[20:27] <acheronuk> apw: can kde-runtime/4:16.12.1-0ubuntu2 be force-badtest or whatever is appropriate?
[20:28] <acheronuk> this is the one where debian dropped the tests, but autotest systems doesn't seem to get the message
[20:30] <acheronuk> maybe it remembers they were there, and needs it to go through once without them. and on next version gone will be the norm?
[20:37] <apw> acheronuk, possible i guess, it does use the Sources file to get the information perhaps it takes an or of the pockets or something
[20:38] <apw> acheronuk, lets try hinting it ...
[20:39] <apw> acheronuk, and done
[20:40] <acheronuk> apw: yep, lets see. I'm mostly still learning with these autotests, so stuff like this is ultimately useful
[20:40] <acheronuk> apw: thx :)
[20:40] <apw> acheronuk, it is not common to remove tests like this, so i am sure we would not notice if it was doing that
[20:44] <acheronuk> apw: well with this package being KDE4 it's likely to be dropped altogether in the nearish future, so you may surmise that debian made the decision with that in mind
[20:44]  * acheronuk shrugs