[00:10] <slangasek> blkperl: hey, what's the schedule look like for the 30th?
[00:10] <blkperl> slangasek: checking now
[00:11] <blkperl> slangasek: open
[00:11] <slangasek> well, er
[00:11] <slangasek> I mean: what time am I supposed to be somewhere and talking :)
[00:11] <slangasek> if we're still on for that?
[00:11] <blkperl> slangasek: 4pm @ PSU Fab 86-01
[00:11] <slangasek> ok
[00:12] <blkperl> slangasek: I need a bio, title and small summary of your talk :)
[00:12] <slangasek> hmmm do you have the first two of those from last time?
[00:12] <slangasek> or the first one
[00:13] <blkperl> right... let me find that
[00:13] <blkperl> success i have it
[00:14] <blkperl> slangasek: alright so I just need a Topic and Summary
[00:14] <slangasek> topic wuz "Secure Boot and Linux"
[00:14] <slangasek> summary I'll send along :)
[00:15] <bkerensa> slangasek: oh so we will finally have a expert talk about Secure Boot in Portland :)
[00:16] <bkerensa> blkperl: ping me the calagator link when its done
[00:16] <slangasek> have there been non-experts talking?
[00:19] <bkerensa> slangasek: idk is Vincent Zimmer, Intel a expert on Secure Boot on Linux?
[00:19] <slangasek> he might be? :)
[00:20] <bkerensa> slangasek: he has a lot of patents... looks like well over 50
[00:20] <bkerensa> :P
[00:22] <slangasek> oh right, he's the one who gave the PLUG talk that I missed
[00:23] <slangasek> anyway, my notes say that yes, he is a Secure Boot expert ;)
[00:25] <blkperl> bkerensa: might not be open to the public, we will see
[00:33] <bkerensa> blkperl: not for me :) I will be on vacation still probably
[01:44] <bkerensa> hi dogweather
[01:44] <dogweather> Hey, how's it going?
[02:21] <bkerensa> dogweather: good :) just studying composting :)
[02:23] <dogweather> Interesting. Trying to fix the desktop?
[02:43] <bkerensa> dogweather: no :) trying to fix the abundance of leaves that keep dropping on my driveway :)
[02:45] <dogweather> Ah HAH. Composting, no compositing.
[03:05] <cy1> bkerensa: I been composting for years! It's really fun.
[03:44] <dogweather> I'm working on yet another "awesome idea for a website". Sometimes I think I'm out of control.
[03:52] <bkerensa> cy1: what do you use as accelerator?
[04:03] <cy1> bkerensa: ...patience?
[04:03] <bkerensa> cy1: my tree does not permit patience
[04:03] <bkerensa> :)
[04:04] <bkerensa> sugar and potatoes FTW
[04:04] <cy1> bkerensa: I compost away from trees.
[18:37] <blkperl> slangasek: have you sent the summary along yet?
[20:57] <bkerensa> slangasek: for some reason submittodebian adds +Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
[20:57] <bkerensa> +XSBC-Original-Maintainer: Nicolas Bertolissio <nico.bertol@free.fr>
[20:57] <bkerensa> to 1 out of 5 patches it send to debian
[20:57] <bkerensa> =/
[20:58] <bkerensa> slangasek: I assume if I was doing my work in a debian chroot I would not run into this?
[20:59] <slangasek> bkerensa: are you sure that change isn't in the tree?  Because Ubuntu policy requires that change to the maintainer field in packages whose source is modified in Ubuntu; the 'update-maintainer' script exists to streamline that exact change
[21:00] <bkerensa> slangasek: I am totally sure... it keeps assuming the fix is landing in Ubuntu for every few patches I send up and adds those fields
[21:00] <bkerensa> :P
[21:00] <slangasek> bkerensa: I filed a bug against ubuntu-dev-tools a while ago asking for maintainer field changes to be automatically stripped out of diffs by submittodebian... I thought that got fixed, but maybe there are still bugs
[21:00] <bkerensa> ok
[21:00] <bkerensa> yeah that and the template are driving me nuts :) its a great tool but a bit touchy
[21:00] <slangasek> bkerensa: er, I can see no reason at all that submittodebian would be *adding* such a change to the diff it sends
[21:01] <bkerensa> yeah
[21:01] <bkerensa> exactly
[21:01] <slangasek> are you *really* sure it's not in your local tree?
[21:01] <bkerensa> 100%
[21:01] <slangasek> blkperl: haven't sent it yet... can do today-ish... email I should send it to?
[21:01] <bkerensa> slangasek: 100% the only change I am making is to the control file to add a single depends... nothing is being changed except depends line
[21:02] <bkerensa> slangasek: blkperl@cat.pdx.edu
[21:03] <slangasek> bkerensa: what version of ubuntu-dev-tools are you using?
[21:04] <bkerensa> slangasek: 0.143ubuntu0.1
[21:04] <slangasek> so, I have that here, and submittodebian definitely doesn't contain any code to add update-maintainer-esque changes
[21:05] <slangasek> so I think that change really is present in the tree you're running it from
[21:05] <bkerensa> but we dont even have the packages I'm working on in Ubuntu
[21:05] <bkerensa> :s
[21:05] <bkerensa> at least in the last case I ran into
[21:06] <bkerensa> hmm
[21:06] <bkerensa> ok I will look a bit more
[21:13] <slangasek> bkerensa: so maybe this is the issue you're seeing: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1021917
[21:13] <slangasek> which suggests that my previous bug report about this *was* closed, even though I'm not seeing it in the code
[21:13] <slangasek> oh, there it is: from ubuntutools.update_maintainer import update_maintainer, restore_maintainer
[21:13] <slangasek> so yeah, bug in submittodebian of some sort
[21:14] <bkerensa> slangasek: I just did a screencast with a fresh source package
[21:14] <bkerensa> submittodebian is definately adding changes
[21:14] <bkerensa> :x
[21:14] <slangasek> yep, per the above
[21:14] <bkerensa> oh ok
[21:15] <slangasek> so the right fix here would be for submittodebian to unapply update-maintainer changes in both the source and target versions
[21:15] <bkerensa> +1
[21:17] <bkerensa> slangasek: so until thats fixed if I just did my fixes in debian chroot would it still make add those changes?
[21:18] <slangasek> bkerensa: I wouldn't expect that to make any difference
[21:19] <bkerensa> ok
[23:09] <blkperl> slangasek: what bkerensa said :)