[03:14] <wxl> is there somewhere i can find a list of the machines amd64+mac is KNOWN to be targeted at? the info i have found is incredibly vague and ambiguous
[04:38] <pitti> Good morning
[05:09] <DalekSec> Howdy.
[09:23] <pitti> jibel: do you keep retrying gem2deb?
[09:23] <pitti> jibel: it looks genuinely broken, I suppose the new version in -proposed tries to download something and times out during the test
[09:23] <jibel> pitti, I blindly retried a bunch of unmet deps failures
[09:24] <pitti> jibel: ah yes, so did I; that was the KDE stack which was uninstallable last night on one arch
[09:24] <jibel> to fix some of the kde tests
[09:24] <jibel> right
[09:26] <pitti> jibel: lintian kicked, too, FTR
[09:26] <pitti> jibel: but it seems rebuilding the VM helped a lot
[09:26] <pitti> wrt. the timeouts
[09:27] <jibel> pitti, indeed. Do you know why lintian failed?
[09:27] <pitti> jibel: the "tar EOF" race condition agai
[09:27] <pitti> n
[09:27] <jibel> k
[09:27] <pitti> which I've never been able to understand or reproduce :(
[09:27] <pitti> I stared at the pipelining for two hours or so
[18:27] <wxl> balloons: any reason why the call for testing a2 didn't go out to the mailing list or anywhere? might have been here but if it was, it got lost in a sea of chats
[18:28] <balloons> wxl, nope, no specific reason, you didn't miss it
[18:29] <wxl> balloons: ok, cuz i realized it at the last freaking minute. my life's too busy to not rely on notices and schedules and such, so i beg you to make sure one goes out next time. or at least ping me ;)
[18:35] <balloons> wxl, yes, ofc! The notice should have gone out
[18:36] <wxl> balloons: if only we could schedule it like we do the releases. seems like we should but i don't know enough of the factors to knwo why that's not the way things are done.
[18:53] <balloons> wxl, yea, since it's adhoc now, it's a bit more scattered
[18:54] <wxl> balloons: well it's mostly been working so i guess it's no big :)