[08:07] <dholbach> good morning
[08:14] <cemc> broder: ping. pdns-recursor landed in -backports, except hardy
[08:14] <broder> cemc: yeah, it's stuck in binary NEW, because the hardy version didn't have the -dbg package
[08:14]  * broder goes and pokes someone
[08:30] <broder> cemc: looks like we're still waiting on the powerpc build: https://launchpad.net/ubuntu/+source/pdns-recursor/3.3-2~hardy1/+build/2930110
[08:31] <broder> but one of the admins went and scored it up, so it should run soon
[08:31] <cemc> broder: nice, thanks
[10:17] <broder> tumbleweed: http://paste.ubuntu.com/740052/
[10:17] <broder> (first time running not-from-bzr)
[10:21] <broder> also, http://pastebin.ubuntu.com/740055/
[10:58] <Laney> tumbleweed: in the absence of anything else, should we see if created_before_date can be done?
[11:03] <dholbach> tumbleweed: thanks for your fix for 781003
[11:07] <Laney> i approve of this udt release
[11:07]  * Laney seal of approval
[11:19] <tumbleweed> dholbach: np. Should have done it ages ago. I don't know why I was thinking it'd be more invasive...
[11:19] <tumbleweed> broder: urgh, that's pretty obvious in hindsight
[11:19] <tumbleweed> Laney: clearly you haven't run into the bug broder pointed out :)
[11:19] <Laney> hah
[11:20] <Laney> i run it out of bzr
[11:21] <tumbleweed> broder: hrm, not so sure about the second one. I'll have to reproduce it, I guess
[11:21] <tumbleweed> anyway, I'd better race another upload through, without waiting for lp to pick it up from debian. broken requestsync and submittodebian... :/
[11:22] <Laney> syncpackage --no-lp is fine if it's pressing imho
[11:22] <tumbleweed> yeah
[11:24] <dholbach> :)
[12:01] <tumbleweed> broder: any ideas about that requestbackport issue? the development launchpads are all too out of date to test it on
[12:29] <tumbleweed> broder: your problem now: https://bugs.launchpad.net/oneiric-backports/+bug/891112
[14:57] <CarlFK> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/squid-deb-proxy/oneiric/view/head:/debian/squid-deb-proxy.templates
[14:58] <CarlFK> shouldn't I be prompted with those questions when I install that?
[15:03] <tumbleweed> CarlFK: no, because they use low priority
[15:03] <tumbleweed> we don't want to show every question. Only questions where there is no sensible default
[15:16] <CarlFK> tumbleweed: where is the priority set?
[15:16] <tumbleweed> CarlFK: in the config script. But you don't want to change those priorities, they look right
[15:18] <CarlFK> tumbleweed: wasn't thinking of chaning, just trying to figure out how it works
[15:18] <CarlFK> is "config script" = http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/squid-deb-proxy/oneiric/view/head:/debian/squid-deb-proxy.config
[15:18] <CarlFK> db_input *low* squid
[15:19] <CarlFK> got it
[15:46] <broder> tumbleweed: ok. maybe it's a credential issue or something. i'll bother #launchpad if i run into it again
[15:46] <tumbleweed> broder: no, it was a bug, I had \n in the title
[15:46] <broder> ah, i see
[16:45] <roaksoax> dholbach: howdy! I was wondering if the documentation somewhere on udd shows and explains what are the files created when merging (such as <file>.THIS and <file>.OTHER)
[16:46] <dholbach> barry, ^ do you know?
[16:47] <barry> roaksoax: that's a more general bzr question, but i'm positive i've seen some documentation on that.  /me searches
[16:48] <roaksoax> barry: thanks!
[16:48] <chrisccoulson> something like http://doc.bazaar.canonical.com/bzr.0.92/en/user-guide/conflicts.html ?
[16:50] <dholbach> http://doc.bazaar.canonical.com/bzr.2.4/en/user-guide/resolving_conflicts.html
[16:50] <barry> chrisccoulson: yep, that's it thanks
[16:50] <dholbach> (in the recent version)
[16:50] <barry> dholbach: that's the other one i was thinking about
[16:50] <roaksoax> chrisccoulson barry: yep. cool! Thanks! ;)
[17:04] <l3on> Hi all... Is there somone that would review some of my proposing merges ? :)
[17:04] <l3on> *someone
[17:28] <Kiall> If there anyone around familiar with git-buildpackage? Was hoping someone could help me understand its submodule support. Specifically, Keeping the debian folder in 1 branch, and overlaying that onto a tag with submodules... Everything bar the submodules works, and I'm not sure if I've set something up wrong, of if I'm trying to do something unsupported. Thanks :)
[18:19] <Majost> Hello, I am trying to create a new CDBS package in 11.10 -- and I discovered the cdbs option is missing from dh_make
[18:19] <Majost> Is there a new way to use the CDBS packaging template?
[18:24] <Majost> ahh
[18:24] <Majost> nm
[18:25] <Majost> just looked at the dh-make changelog and saw it was changed to a rules format
[20:13] <broder> Majost: i would recommend using dh these days instead of cdbs, unless you have a specific reason not to. i think most people in here would probably do the same.
[20:16] <Majost> I always found cdbs pretty easy to use for most stuff
[20:17] <Majost> whats the reason for the shift to dh and phasing out of cdbs?
[20:17] <tumbleweed> I always find I have to read the source code when I want to do anything non-trivial with it
[20:17] <tumbleweed> the same applies to dh, I suppose, but that's way more readable
[20:17] <mok0> Majost: Beats me. dh sucks imho
[20:17] <Majost> hah
[20:18] <mok0> cdbs is clean gnumake macros
[20:18] <broder> i used to be a big fan of cdbs too, before dh 7 came out, but with dh 7 i'd argue you get all of the benefits of cdbs (which are basically a short rules file) without the pain of having to understand their abuse of make syntax just to change the arguments to a debhelper script
[20:18] <mok0> broder: I very much prefer a hand-crafted rules file
[20:18] <Majost> hrm
[20:19] <mok0> or cdbs
[20:19] <broder> mok0: yeah, i hate those. they're terrible violations of DRY
[20:19] <Majost> broder: I will have to try out dh7 with my next package
[20:19] <mok0> broder: thing is, no 2 packages are alike
[20:19] <Majost> I've already finished the package I started earlier
[20:19] <broder> that's not true. most packages are at least 75% alike
[20:19] <mok0> broder: not the ones I've worked with
[20:19] <broder> have you ever built a package you didn't call dh_md5sums or dh_installdeb on?
[20:20] <tumbleweed> mok0: I can find you the same bug in many many packages' debian/rules files
[20:20] <broder> or any of the dozen others that you never touch, but have to remember to call in the right order lest something blow up?
[20:20] <mok0> broder:  no :-)
[20:20] <tumbleweed> getting them fixed one maintainer at a time is crazy-slow
[20:20] <mok0> broder: There are a few idioms that are repeated, yes
[20:21] <broder> mok0: i disagree. i think that *most* idioms are repeated
[20:21] <broder> and dh 7 lets you capture just the things that are non-standard, however many of those things there may be
[20:21] <mok0> broder: you are permitted to disagree :-)
[20:22] <mok0> broder: anything non-standard and dh7 lets you down
[20:22] <broder> nah, override_dh_auto_build: and you can do whatever you want
[20:23] <mok0> broder: oh, and what does that do to the "simple" rules file? :-)
[20:23] <mok0> I don't find a bunch of overrides easier to understand
[20:23] <tumbleweed> mok0: it keeps it simple, with your rules file only declaring how it differs from the norm
[20:23] <broder> mok0: it makes about 3 lines longer, but you *still* don't have to write all of the standard dh_* idioms by hand
[20:24] <mok0> broder: I like to see what's going on
[20:25] <mok0> but when I'm lazy, I like cdbs :-)
[20:31] <Laney> must be crazy, I'm running ./rocketfuel-setup
[20:32] <tumbleweed> eep why?
[20:32] <Laney> fancied seeing how hard fixing LP bugs are
[20:32] <tumbleweed> you realise we'll all remember that now... :)
[20:33] <Resistance> lol
[20:33] <nigelb> Laney: \o/
[20:33] <Laney> the real one I want to fix is NotAutomatic for PPAs
[20:33] <nigelb> Famous last words...
[20:33] <Laney> nigelb is going to mentor me!
[20:33] <nigelb> what! No!
[20:33] <nigelb> Anything touching or going anywhere nearby Soyuz and I will run in the other direction.
[20:33] <broder> awesome! i successfully stalled long enough that somebody else is looking into it! :)
[20:34] <tumbleweed> Laney: after that, sync sponsorship
[20:34] <Laney> heh
[20:34] <Laney> i tried again to get that escalated today
[20:36] <Laney> if only it was doing bzr branch lp:launchpad in parallel with this massive package install
[20:36] <tumbleweed> yeah, that's a non-trivial checkout
[20:37]  * tumbleweed has one on a machine far away, with real bandwidth
[20:59] <Laney> zzzzzzzzzz
[21:00] <Laney> losing the will to live
[21:00] <Resistance> anyone able to give me some pointers about setting up a packaging recipe?
[21:00] <Resistance> in launchpad
[21:00]  * Resistance has no clue how to begin, or if it'll even work
[21:00] <Laney> #launchpad is the best place for that
[21:00] <Resistance> true, but they havent been much help when i ask in the past ;P
[21:02] <tumbleweed> Resistance: it's pretty straight-forward. Setup a vcs-import (if necessary). Create a branch with the contents of debian. Write a 3 line recipe. Test locally with bzr dailydeb
[21:03] <Resistance> tumbleweed:  the lack of examples or documentation is what gets mew
[21:03] <broder> Resistance: https://help.launchpad.net/Packaging/SourceBuilds/Recipes
[21:03] <Resistance> broder:  and that's been changed in the past 6 months?
[21:04] <Resistance> actually this is a different page
[21:04] <Resistance> :p
[21:04] <Resistance> thanks
[21:04] <broder> Resistance: i just googled for [launchpad recipe]
[21:04] <Resistance> lol
[21:12]  * Laney cries on nigelb's shoulder
[21:12]  * Resistance hands Laney a box of tissues
[21:34] <Majost> Could someone tell me if I need to include the autogenerated quilt patches when adding it to my source control?
[21:35] <Majost> I tried cloning without them, and I get build errors.... so I am not sure if I am just passing dpkg-buildpackage the wrong arguments or if I need to include it
[21:35] <JackyAlcine> Hey, guys, when I used dput, I put "ubuntu" instead of "ppa". I'm hoping that I didn't mess anything up. >_<
[21:37] <Majost> s/adding it/adding my debianization/
[21:39] <jtaylor> autogenerated quilt patch?
[21:39] <jtaylor> that should be avoided
[21:39] <nigelb> Laney: heh, what happened?
[21:40] <Laney> JackyAlcine: do you have upload access?
[21:40] <Laney> nigelb: sloooooooooooow
[21:40] <Laney> there were several huge bzr checkouts
[21:40] <nigelb> Laney: I wanted to contribute to LP over a year. I kept being stopped because the downloading would stop at some point and I'd be stuck
[21:41] <Laney> and now bin/buildout is taking forever
[21:41] <Laney> heh
[21:41] <Laney> thank god for fast broadband
[21:41] <nigelb> heh
[21:41] <JackyAlcine> Laney: I'm not sure, I'm not an official Ubuntu package maintainer so I don't think that I've done too much harm.
[21:42] <Laney> if you don't have access to upload to the archive then you can't have caused any problems
[21:42] <ajmitch> there'd be trouble if any random person could screw up the archive :)
[21:42] <JackyAlcine> But I wanted to warn in advance. It was only the .changes for my wintermute binary package.
[21:42]  * JackyAlcine exhales a sigh of relief.
[21:43] <Laney> i used to play a mud called wintermute
[21:45] <JackyAlcine> Another question: can you only upload to a PPA via ftp? How about rsync or https?
[21:45] <JackyAlcine> I got an error using rsync, and plain http failed.. :/
[21:48] <Laney> ftp or sftp
[21:50] <JackyAlcine> Thanks again, Laney.
[22:06] <Laney> yay! launchpad.dev is alive!
[22:12] <iamfuzz> Laney, launchpad.dev?  you setup your own LP install?
[22:12] <Laney> sure did
[22:12] <Resistance> Laney:  you're going to fix that bug you mentioned earlier right?
[22:13] <Resistance> ;P
[22:13] <Laney> baby steps
[22:16] <iamfuzz> Laney, funny, I'm going to be doing that tomorrow :-)
[22:16] <iamfuzz> Laney, how difficult was it?  Soyuz up too?
[22:17] <lifeless> iamfuzz: https://dev.launchpad.net/Running/LXC + https://dev.launchpad.net/Soyuz/HowToUseSoyuzLocally
[22:17] <lifeless> iamfuzz: its quite straight forward
[22:17] <iamfuzz> lifeless, awesome
[22:17] <iamfuzz> lifeless, LP been quite snappier since you came aboard there
[22:18] <lifeless> thanks
[22:18] <lifeless> we're making progress
[22:21] <Laney> yeah, I haven't soyuzed yet
[22:21] <Laney> it was pretty painless besides taking some time
[22:40] <Laney> iamfuzz: I recommend you let it download overnight :-)
[22:41] <iamfuzz> Laney, lol that big huh
[22:42] <lifeless> its a little heavy :)
[22:43] <Laney> just not that fun to stare at
[23:21] <tumbleweed> Laney: just got to the bottom of another bug in lp-udd, that was making oneiric unimportable (I thought I was running into random timeouts / lp maintainance, but it was a python bug...)
[23:21] <Laney> hah
[23:22] <Laney> in python core?
[23:22] <tumbleweed> already fixed in 2.7 http://bugs.python.org/issue10963
[23:23] <Laney> isn't that the one we saw before?
[23:23] <tumbleweed> we weren't using comminicate, we were just running into the problem of trying to write too much into the subprocess, when it was blocking because we weren't reading its output
[23:24] <tumbleweed> the solution to that is to use communicate(), but then this bug...
[23:24] <Laney> yes, that's why I stopped using communicate before
[23:24] <tumbleweed> sbcl had many lines of changelog fixed in one upload
[23:25] <tumbleweed> err, a big merge
[23:25] <iamfuzz> lifeless, is ppa privatization available in the open source dump?
[23:25] <iamfuzz> granted it'll be running internally anyway but still nice to have that granular level of control
[23:25] <lifeless> iamfuzz: EPARSE
[23:54] <lifeless> iamfuzz: (I'm not sure what you man)
[23:54] <lifeless> *mean*