[00:26] <TheLordOfTime> anyone here able to help me resolve an issue with quilt patches?
[00:26] <TheLordOfTime> i'm trying to write a quilt patch using quilt new [patchname], quilt add [relevantfile], edit the file, do quilt refresh...
[00:27] <TheLordOfTime> after that point, should quilt pop remove the codechanges?
[00:27] <TheLordOfTime> or rather undo the changes i did when i edited the file?
[00:27] <TheLordOfTime> because in the current case, the patches all get their diff stuff, which then doesn't apply.
[00:27] <TheLordOfTime> complains about the headers :/
[00:29] <RAOF> TheLordOfTime: quilt refresh will *not* pop the changes. It'll just update the diff.
[00:29] <TheLordOfTime> you missed a line
[00:29] <RAOF> If you want to pop the changes off, you'll need to ‘quilt pop’
[00:29] <TheLordOfTime> <TheLordOfTime> after that point, should quilt pop remove the codechanges?
[00:29] <RAOF> Ahem.
[00:29] <RAOF> So I did.
[00:29] <TheLordOfTime> after i said what i've doen :p
[00:29] <RAOF> Move along :)
[00:29] <TheLordOfTime> RAOF, but then when i go quilt push -a to check if it works with all the other patches, it errors
[00:30] <TheLordOfTime> lemme see if i cant dredge up the logs
[00:30] <RAOF> Yeah, that'd be helpful.
[00:31] <TheLordOfTime> ... okay, the patches disappeared, i wonder if my system segv'd...
[00:31] <TheLordOfTime> give me a moment.
[00:40] <TheLordOfTime> ... huh
[00:40] <TheLordOfTime> that's... interesting.
[00:40] <TheLordOfTime> apparently its not erroring now
[00:40]  * TheLordOfTime wonders if the dget on the package was broken.
[00:42] <RAOF> Hurrah for the passive fix :)
[00:42] <TheLordOfTime> well, lets hope adding the next CVE patch and the one after don't cause this breakage
[00:42] <TheLordOfTime> not to mention lets hope quilt correctly adds the dep3 tags
[00:42] <TheLordOfTime> since it failed to do that last time when i told it to
[00:42] <TheLordOfTime> but first...
[00:43] <TheLordOfTime> COFFEE
[00:54] <TheLordOfTime> is there an easy way to add DEP3 tags to a quilt patch?
[00:54] <TheLordOfTime> rather than me hand-adding them.
[01:07] <RAOF> TheLordOfTime: I don't know; I generally get the DEP3 tags from the VCS I did the patch in.
[04:55] <Guest95055> micahg: you awake still?
[04:55] <Guest95055> argh
[04:55] <micahg> can I deny it?
[04:55] <Guest95055> sorry this is mfisch
[04:56] <Guest95055> micahg: so a question on a new rev of transmission
[04:56] <Guest95055> micahg: I pulled it down and built it and it requires no changes at all
[04:56] <Guest95055> micahg: I mean just uscan/uupdate and build, well a small changelog edit
[04:56] <Guest95055> micahg: but it generates a 3.7MB debdiff
[04:57] <Guest95055> is that still what I should attach to the bug?
[04:57] <micahg> well, we're "in-sync" with Debian, maybe get it updated there first?
[04:57] <micahg> (it's a merge)
[04:58] <Guest95055> we have a couple changes from debian
[04:58] <micahg> right, but Debian has 2.73 as well
[04:58] <Guest95055> getting it updated there would certainly avoid us having a 96644 line debdiff to read
[04:58] <Guest95055> micahg: thanks
[04:59] <micahg> Guest95055: you diff the debian dir instead of the whole thing
[04:59] <micahg> but either way, I think it's best at this point if the Debian maintainer is open (which he appears to be) is to get it there first
[04:59] <Guest95055> micahg: with a debdiff?
[04:59] <micahg> yeah
[04:59] <Guest95055> interesting
[05:00] <Guest95055> our bzr is way outdated because I tried that route as well
[05:00] <Guest95055> micahg: okay thanks for the advice
[05:00]  * Guest95055 keeps smacking the nickserver without much luck
[05:01] <Unit193> Guest95055: /msg nickserv release nick pass
[05:01] <mfisch> thanks, I was tyring to ghost it instead
[05:01] <Unit193> Sure.
[07:55] <dholbach> good morning
[15:17]  * Laney arghs at mysteriously losing a tab with a fairly lengthy bug comment in it
[15:17] <Laney> there must be an extension to get form content back
[15:19] <micahg> Laney: undo close tab?
[15:19] <Laney> no
[15:19] <Laney> just got some random tabs
[15:19] <Laney> i thought perhaps i accidently navigated away, but going back just took me elsewhere :(
[15:20]  * Laney retypes
[18:05] <micahg> Rhonda: well, no change backports are a little easier than changeful ones
[18:05] <xnox> Laney: in chromium it prevents me from navigating away/closing if there is "typed" content that I may destroy by going away.
[18:06] <Laney> mmm, I don't think FF does that
[18:06] <Laney> some websites do though
[18:06] <micahg> Feed the Google with more content...
[18:08] <xnox> my approach to privacy is to generate as much FUD content about me as possible, then it makes it harder to find the gems of personal information that did leak through.
[18:08] <xnox> if one is over-cautious, the only bit of private information that will eventually leak will also end up on top the front page search result for your name.
[18:09] <micahg> xnox: so, that story about you braving the rapids by Tiera Del Fuego is a cover?
[18:09]  * xnox no comment
[18:12] <xnox> micahg: so what is the process for $universe package USN?
[18:13] <micahg> xnox: none
[18:13] <xnox> micahg: do I make patches for affected releases & subscribe security-sponsors?
[18:13] <xnox> micahg: does it even go into -security pocket? or simply -updates?
[18:13] <micahg> xnox: yep (ubuntu-security-sponsors)
[18:13] <xnox> ack.
[19:00] <oVeRMiND> hello world!
[21:11] <jtaylor> micahg: why does backportpackage print build depende twice? :( e.g. 1091411
[21:11] <jtaylor> and ping ipython :)
[21:16] <jtaylor> nevermind seems fixed in trunk
[21:20] <Laney> oh backports
[21:20] <Laney> I hope to find more time for you
[21:38] <micahg> jtaylor: can it wait until next week when I'm on vacation?
[21:39] <jtaylor> sure
[21:39] <micahg> no idea why it does that (ISTR a bug being filed and maybe even fixed0