=== marlinc_ is now known as marlinc [01:33] tsimonq2: taking a look [01:34] tsimonq2: should be safe to sync - I'd do a test build first to ensure that it still doesn't complain about the implicit pointer conversion === JanC is now known as Guest81300 === JanC_ is now known as JanC [22:26] sigh, distro development: [22:28] python-setuptools is held in proposed by the diffoscope autopkgtests which fail for a reason that is 100% not due to setuptools [22:28] diffoscope has its own version in proposed which ftbfs for an entirely different reason [22:41] and it builds in sid [22:41] fabulous [22:43] Sounds like you're having a wonderful day. [22:48] i guess the autopkgtest failure should be hinted [22:48] and the other crud can be left for the next person [22:53] Can I bother you really horribly and request a retry of gocryptfs on the failing arches? [23:28] Unit193: how horrible indeed! [23:28] (done) [23:29] Thanks, good sir. [23:30] what' [23:30] s the easiest way of poking a file into a chroot? [23:31] schroot [23:32] You mean, cp foo.deb /var/cache/pbuilder/build/28204/buildd/ ? :P [23:34] well sbuild for that, yes [23:35] I've only done that once or twice when the build failed and it dumped off into the chroot. Never used sbuild in my life. :3 [23:36] fair enough [23:37] ah both schroots mount a shared scratch area [23:38] grrr http://paste.ubuntu.com/25158654/ [23:38] tdaitx: do you know why the new openjdk-9 package seems to cause an autopkgtest regression (reproducible) on s390x? [23:42] i should go to sleep if slangasek & mwhudson are awake =) [23:47] xnox: you sure you don't want to agonize over details of binutils behaviour changes? [23:49] binutils is dark magic to me, and when the dark magic changes i get very nervous. Cause i'm like - was the previous dark magic too grey?!