[07:16] <dholbach> good morning
[07:58] <Laney> infinity: Good. I had no clue and didn't want to sync-and-find-out-later. Thanks for checking.
[08:00] <infinity> Laney: Turns out the irritating complexity of the patch was still required, but I refreshed it to be based on gcc-4.8 instead of 4.7 and uploaded.
[08:01] <Laney> rockin'
[08:01] <Laney> Assuming mitya57's gdcm works then that should smooth the path for poppler to migrate
[08:14] <Laney> ah, balls, calligra
[10:45] <mitya57> Laney: thanks for uploading xpdf!
[10:45] <Laney> np
[10:45] <Laney> I did a grep and then noticed the stuff is already there ...
[10:45] <Laney> I suppose the remaining issue is missing fixes to that code in poppler.
[10:46] <mitya57> Which fixes?
[10:46] <Laney> As in, if it gets fixes in the future
[10:46] <Laney> keeping it in sync
[10:48] <mitya57> Yes, let's hope Poppler will have less code cleanups in future :)
[10:48] <Laney> ha hahahaha aha. yeah.
[10:49] <Laney> anyway, should be done for now ...
[16:18] <tumbleweed> mfisch, mitya57: welcome to MOTU :)
[16:19] <iulian> Uh-oh!
[16:19] <mitya57> tumbleweed: should/can I take part in MOTU meetings?
[16:20] <tumbleweed> mitya57: MOTU meetings kind of died
[16:21] <mitya57> Hm, looks like that, yes
[16:22] <tumbleweed> if we are going to resurrect them, we'd need a reason
[16:22] <mfisch> thanks tumbleweed
[16:22] <tumbleweed> and somebody to drive them for a few months
[16:23] <Laney> added
[16:23] <Laney> get to breakin'
[16:24] <Laney> https://wiki.ubuntu.com/MOTU/New
[16:24] <Laney> might be a bit ancient but maybe useful
[16:24] <mfisch> proper understanding of dput is useful
[16:25] <mfisch> Laney: whats the general policy on DEP3 headers (adding/updating them)? I know desktop tries to do so
[16:26] <Laney> I'd say it's a good idea and you should do it
[16:26] <Laney> but I don't think there's a policy per se
[16:26] <mfisch> from the ones I've seen sometimes a time machine would help
[16:27] <mfisch> Laney: thanks
[16:27] <Laney> there's a ton of old stuff
[16:27] <Laney> it pays to consider patches when you come across them and help them along in life
[16:27] <mfisch> yeah, I tried one last week and I couldn't figure out where it originated
[16:28] <mfisch> Laney: what are the debian channels you hang out on in order to collaborate better?
[16:28]  * mitya57 always uses DEP-3, and also exports QUILT_REFRESH_ARGS="-p ab --no-timestamps --no-index" to make patches cleaner
[16:29] <Laney> I'm in loads
[16:29] <Laney> good ones might be #debian-devel, #debian-mentors and #debian-gnome
[16:29] <mfisch> those would be good starts, thanks
[16:30] <tumbleweed> while we only have to follow policy, I try to follow best practices, and enforce them on sponsorees
[16:30] <tumbleweed> e.g. DEP-3, DEP-5 on new packages, autopkgtests whenever possible, forward everything upstream, etc etc
[16:32] <mfisch> mitya57: I've not used those flags before, I'll add it to my notes
[16:32] <tumbleweed> mfisch: I belive they are mentioned in the debian new maintainer's guide
[16:33] <mfisch> for the 2 new packages I've done, upstream has been very amenable to taking all the patches, so we dont have any.. so far
[16:33] <mitya57> mfisch: s/my notes/.bashrc/
[16:33] <Laney> .quiltrc
[16:35] <mitya57> that's indeed better, didn't know about that
[16:50] <Laney> argh cdbs argh
[16:53] <Laney> how can I hook into make check?
[17:02] <tumbleweed> the answer to  "how do I ... in cdbs" is always "read the source"
[17:02] <Laney> it's not giving me much
[17:02] <Laney> i'm just overriding the whole target
[17:03] <tumbleweed> you want to add something?
[17:04] <Laney> I want to export FOO=$(mktemp -d), run the testsuite and then remove the directory
[17:05] <Laney> I suppose I could just do it at the top level
[17:06] <Laney> use a fixed directory name, perhaps that's not so bad