[04:01] <mfisch> TheMuso`: ping
[04:02] <mfisch> I have an odd situation with speakup
[04:03] <mfisch> We can sync with debian since the binaries are now in the kernel according to TheMuso`
[04:03] <mfisch> the only binary built anymore is speakup-doc
[04:03] <mfisch> so if I sync to debian, then we will have a newer speakup-doc, but still the old binary speakup package I assume?
[07:28] <dholbach> good morning
[07:45] <Noskcaj> evening dholbach. Would you mind giving me a testimonial for https://wiki.ubuntu.com/Noskcaj/MOTU ?
[07:46] <Noskcaj> I won't actually have the meeting till january when i have school holidays
[07:46] <Noskcaj> And it probably has to be be email because of my timezone
[07:46] <dholbach> Noskcaj, sure
[07:47] <dholbach> Noskcaj, I'd recommend you use https://wiki.ubuntu.com/UbuntuDevelopment/DeveloperApplicationTemplate as a template for the application
[07:47] <Noskcaj> thanks
[07:48] <Noskcaj> will do
[07:49] <dholbach> :)
[07:50] <Noskcaj> should i still have a separate page for the MOTU application or just use my main one?
[07:51] <dholbach> one should be enough
[08:24] <Noskcaj> dholbach, https://wiki.ubuntu.com/Noskcaj should be close enough
[08:26] <dholbach> cool
[08:30]  * Noskcaj wishes alioth was less broken so he could get a list of people who have sponsored stuff for him
[08:35]  * Zhenech hands Noskcaj "who-uploads"
[08:36] <Noskcaj> um?
[08:36] <Noskcaj> i.e. the sponsorship miner
[08:43] <Zhenech> it should give you who uplaoded which package, so your sponsors
[19:45] <Ampelbein> Where would I investigate why dbus-sharp 0.8.0-1, uploaded to debian 32 days ago, didn't make it automatically into trusty yet?
[19:46] <Ampelbein> The Ubuntu package does not have local changes as far as I can tell (https://launchpad.net/ubuntu/+source/dbus-sharp)
[19:52] <Noskcaj> Ampelbein, I don't know the exact reason, but it's probably because dbus-sharp is FTBFS everywhere
[19:53] <Ampelbein> The source package isn't even in Ubuntu?
[19:54] <Ampelbein> And I don't see it FTBFS in Debian either.
[19:57] <geser> I see no reason why it shouldn't got auto-synced
[20:01] <Ampelbein> So, if I manually used syncpackage it wouldn't cause the world to collapse into a super black hole?
[20:02] <geser> no :)
[20:02] <geser> using syncpackage would be what I would try if was on my Ubuntu system right now
[20:04] <Noskcaj> Ampelbein, It looks like it was never built on debian. I think it has to before we sync it
[20:04] <Ampelbein> Wouldn't that mean that we would never get pure arch:all packages since they technically are never built on Debian's build servers?
[20:05] <Ampelbein> If I understand Debian correctly, arch:all packages are build and uploaded by the developers instead of being built.
[20:05] <geser> Noskcaj: the arch:all deb was uploaded with the source (as is required by Debian) so there is no build log for it available in Debian
[20:06] <geser> It would be news to me if the autosync would care about FTBFS in Debian
[20:06] <Ampelbein> Anyway, syncpackage did succeed and the package is now in trusty.
[20:06] <Noskcaj> ok. Ignore everything i said
[20:07] <Ampelbein> Thanks to both of you, Noskcaj and geser for checking if I missed something obvious.
[21:07] <Ampelbein> Great. I upload a fix for a package that failed on amd64. Build succeeds locally in sbuild. On the auto-builders? All arches fail.