[00:03] <blair> checking out the source of python-defaults from bzr doesn't seem to match the history in debian/changelog from apt-get source, i cannot see changes in bzr that correspond to the changelog modifications
[00:04] <blair> i did a "bzr branch http://alioth.debian.org/anonscm/bzr/pkg-python/python-defaults-debian co" and then a "bzr log -v"
[00:22] <Corey> Seeing a weird issue.  Made a few changes, did a git merge from upstream, now the build process is throwing: aborting due to unexpected upstream changes, see /tmp/sa... The problem is that's in a pbuilder chroot which is destroyed before I can read the file.
[00:23] <Corey> I've built all the files it's using for the build (the tarball, the dsc, etc) via script.
[00:26] <Corey> Wait, it may be an outdated pbuilder chroot.
[00:30] <Corey> Yeah, that didn't sort it.
[00:31] <Corey> What does pbuilder see as "upstream" in this context?
[02:09] <barry> tumbleweed, jtaylor: oh well, we have our answer: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659196
[05:26] <zooko> jtaylor: okay, I'm trying this recipe: http://codepad.org/HxE9Do4d
[05:26] <zooko> Thanks!
[05:31] <zooko> Hm, I need to change the debian patches that no longer apply correctly.
[05:33]  * zooko looks for the "fork me" button on https://code.launchpad.net/~ubuntu-branches/debian/sid/pycryptopp/sid
[05:36]  * zooko runs "bzr branch lp:debian/pycryptopp"
[05:42] <RAOF> zooko: Yeah, Launchpad doesn't have a “fork me” button because bzr branches don't require the elaborate set up that git branches do.  ie: If you want to push a bzr branch somewhere, you ‘bzr push $SOMEWHERE’, and it works.
[05:45] <zooko> Where would $SOMEWHERE be for the purpose of forking lp:debian/pycryptopp to ~zooko/debian/pycryptopp in order to offer new versions of the debian patcheas?
[05:45] <zooko> Ideally a bzr-builder recipe will be able to merge/pull/nest/use my resulting "~zooko/debian/pycryptopp" instead of or in addition to lp:debian/pycryptopp.
[05:45] <RAOF> bzr push lp:~zooko/$PROJECT/pycryptopp
[05:46] <zooko> Thanks!
[05:46] <RAOF> $PROJECT is probably pycryptopp in this case; it could also be +junk if you don't want it to show up anywhere.
[05:46] <RAOF> And the final component can be whatever you like.
[05:47] <zooko> Okay.
[06:49] <zooko> If I'm sending an email to submit@bugs.debian.org, is there an email address that I should have it be forwarded to in order to register it in the Ubuntu bug tracking system?
[06:55] <micahg> zooko: https://help.launchpad.net/Bugs/EmailInterface
[06:56] <zooko> micahg: thanks!
[06:56] <zooko> (Unfortunately I already sent the email to debian.)
[06:56] <zooko> I should have waited longer.
[06:57] <micahg> zooko: probably better to do them separately as the control fields are different, but I assume you have a sent mail folder? :)
[06:57] <zooko> Oh, I've already opened it through the web UI on launchpad.
[06:57] <micahg> that works too :)
[06:58] <zooko> I was just curious if telling Debian to send mail to Ubuntu with a pseudo-header would... help.
[06:58] <zooko> Help them link their databases to each other...
[07:00] <micahg> well, you can link to debian in Launchpad and to Launchpad in Debian, the question is which is upstream in this case
[07:05] <zooko> Why is that the question?
[07:05] <zooko> I mean, what does it matter?
[07:06] <micahg> oh, well, in launchpad it doesn't per se, but in Debian, the official "link" AIUI is for bugs forwarded upstream
[07:06] <micahg> you can still include the LP bug # in the report though and some DDs will close the launchpad bug in their changelog as well
[07:06] <zooko> Thanks.
[07:07] <zooko> Is "link" one of the pseudo-headers I can put in debian bug mail?
[07:07] <zooko> I didn't see that, but I searched for "ubuntu", "launchpad", and "url", but not for "link". :-)
[07:08] <micahg> zooko: I think you actually want forwarded for the keyword
[07:08] <micahg> but that should only be use if Debian's not upstream which is usually not the case for an Ubuntu bug
[07:09] <zooko> Hm.
[07:10] <micahg> OTOH, if you're pointing to a bug in a project on launchpad like synaptic or some other thing maintained in Launchpad, it would be quite appropriate to use forwarded in Debian
[07:35] <zooko> Anybody want to help with bzr-builder?
[07:35] <zooko> dpkg-source: error: can't build with source format '3.0 (quilt)': no orig.tar file found
[07:35] <zooko>  
[07:35] <zooko> From this recipe:
[07:35] <zooko> # bzr-builder format 0.4 deb-version {revno}+{revno:packaging}
[07:35] <zooko> lp:pycryptopp
[07:35] <zooko> nest-part packaging lp:~zooko/pycryptopp/debian debian
[07:35] <zooko>  
[07:35] <zooko> Oh well, I have to sleep. Feel free to use that recipe and fix it for me. :-) zooko@zooko.com
[08:51] <dholbach> RainCT, happy birthday! :)
[08:53]  * ajmitch really wants to upgrade his work desktop to precise
[08:54] <dholbach> ajmitch, go go go
[08:55] <ajmitch> dholbach: but it's running lucid, and I sort of need it to work properly still :)
[08:56] <dholbach> ajmitch, maybe you could toy around with the sandbox upgrader first then to see if at least the upgrade path would be alright
[08:56] <ajmitch> though I've been impressed with how well precise has been kept usable, running on my laptop
[08:57] <dholbach> yep
[08:57] <ajmitch> dholbach: I've heard of the sandbox upgrader, but don't know anything about it
[08:57] <dholbach> ask mvo
[08:58] <dholbach> "do-release-upgrade -s" maybe?
[08:58]  * dholbach shrugs
[08:58] <dholbach> I never used it, but heard of it
[08:58] <ajmitch> does it do some overlayfs magic or something to test out an upgrade?
[08:59] <dholbach> aufs it says in --help
[09:00] <ajmitch> same sort of thing I think
[09:00] <ajmitch> I might try it out, I've got a few packages installed on that desktop
[12:37] <G> hey, if a package is in the repos for Ocelot, if there is a [needs-packaging] bug open still, should that just be closed fix released?
[12:37] <zooko> Hello, folks! I'm trying to configure autobuilds of nightly .deb's of a project, and currently it fails with dpkg-source: error: can't build with source format '3.0 (quilt)': no orig.tar file found
[12:37] <zooko>  
[12:39] <zooko> The source is held in bzr, with a ./debian subdirectory, not in an .orig.tar file, but I don't know how to tell "bzr dailydeb" to tell bzr-builder to tell dpkg-buildpackage that.
[12:42] <pabelanger> any sponsors able to look at bug 928499?  I've attached a debdiff
[12:44]  * zooko reads http://raphaelhertzog.com/2010/10/21/the-secret-plan-behind-the-3-0-quilt-debian-source-package-format/
[12:45] <geser> zooko: you might want to ask in #launchpad if nobody here can help you with recipes
[12:51] <zooko> geser: thanks!
[13:56] <Laney> nigelb: dholbach: my attention was just brought (in #-release) to the fact that we are letting uninstallable packages slip through into release. Would you be interested in helping to organise / publicise a challenge to fix some of them?
[13:56] <Laney> http://qa.ubuntuwire.org/debcheck/debcheck.py?list=INDEX&package=&arch=&dist=precise
[13:59] <Daviey> If i know nigelb, he'll have them all fixed by the end of day - himelf.
[14:00]  * Laney prepares the pro-plus infused Red Bull
[14:34] <dholbach> Laney, that'd be awesome - but I'm quite busy right now - maybe somebody can write a mail to u-devel with a list of those?
[14:34] <Laney> ok
[14:35] <Laney> it would be good if you could include it in the development weekly thingy after it's worked out
[14:36] <dholbach> we are going to post the update RSN
[14:36] <dholbach> the next would be next thursday
[14:36] <Laney> yeah, i won't get around to it this week
[14:36] <dholbach> ok, I'm very happy to mention it
[14:36] <Laney> would be a good post-feature-freeze thing anyway
[14:36] <dholbach> yep
[14:37] <Laney> cool beans
[14:37] <dholbach> :-)
[14:46] <zooko> Hm, well I don't see what my problem is, so I think I'll put my recipe into launchpad and see if it works in the launchpad build environment even though it fails locally.
[14:46] <zooko> No, because I don't know what the version number is going to come out to be...
[14:47] <zooko> Sigh.  I guess I'll follow the instructions to use pbuilder to test my recipe...
[14:56] <rigved> hi everyone. i am going through the quickly tutorial and found a few small errors. I am filing bugs for each of these.
[14:57] <rigved> i am plaaning on organising a ubuntu global jam and it would be wornderful it i could use these simple bugs to showcase how launchpad etc. works.
[14:58] <rigved> should i write a comment saying this: Please do not fix this bug as I will use this bug as an example at a Ubuntu Global Jam"?
[14:59] <rigved> should i set the bug as Assigned To me?
[15:29] <brendan0powers> I'm interested in getting a package of mine into universe for 12.04
[15:29] <brendan0powers> But I'd need some changes to the apparmor profiles for bind9, ntp, and dhcpd3
[15:30] <brendan0powers> Is this the right place to ask questions about this?
[15:31] <pabelanger> adam_g: ping
[15:36] <tumbleweed> brendan0powers: speak to the people who usually look after those packages
[15:37] <brendan0powers> Ok, thanks
[15:37] <tumbleweed> how invasive are the changes?
[15:37] <brendan0powers> I don't think they are too invasive
[15:38] <brendan0powers> The profiles need to be extended to allow them to read some files in sambas private directory
[15:38] <brendan0powers> Specific files
[15:38] <tumbleweed> #ubuntu-server maybe?
[15:40] <brendan0powers> I'll talk  to the package maintainers
[15:41] <brendan0powers> I assume that modifying the profiles during installation is not acceptable?
[15:42] <tumbleweed> correct. It'd also help if your application was already in the archives
[15:42] <tumbleweed> and FF is very very soon
[15:43] <brendan0powers> Does the FF include universe?
[15:43] <tumbleweed> yes
[15:43] <brendan0powers> Ah, I was under the impressions that universe froze later
[15:43] <tumbleweed> (although we do grant exceptions)
[15:44] <brendan0powers> Well, the apparmor changes are actually for samba4, not for my package
[15:44] <brendan0powers> I just set up and configure samba4
[15:45] <arand> Is it possible to FFE something in advance? I'm in the process of getting sponsorship for a game in Debian, but it will likely not end up in testing before the FF, and I'd really like for it to be in precise...
[15:45] <tumbleweed> brendan0powers: in that case, those are bugs in the apparmor profiles (IMHO)
[15:46] <tumbleweed> (assuming it's a sane configuration, which it sounds like)
[15:46] <tumbleweed> arand: if it's a leaf package, there shouldn't be any problem
[15:46] <arand> tumbleweed: Leaf in terms of dependencies?
[15:47] <tumbleweed> yes
[15:48] <arand> Hmm, it's actually a leaf, and a leaf-branch in that regard, but as a whole they're a leaf, at least.
[16:08] <stefanct> hi. i am an upstream developer of a package that usually gets into universe by auto-syncing from debian. id like to know what is required to get upload rights to a package (mainly to be able to sync the package after debian import freeze but before ff)
[16:09] <dholbach> hey stefanct
[16:10] <dholbach> stefanct, the application process is explained here: https://wiki.ubuntu.com/DeveloperMembershipBoard/ApplicationProcess
[16:10] <dholbach> stefanct, basically you set up a wiki page (using the template) explaining your involvement, get a few comments from people you've worked with, send a mail to the developer membership board and attend a meeting
[16:11] <stefanct> dholbach: thanks!
[16:11] <dholbach> anytime
[16:11] <mitya57> stefanct, see also https://wiki.ubuntu.com/UbuntuDevelopers#Per-package_Uploaders for more details
[16:12] <mitya57> and, obviously, you can request syncs via launchpad
[16:16] <stefanct> mitya57: have done that for 10.10 https://bugs.launchpad.net/ubuntu/+source/flashrom/+bug/816918
[17:29] <nigelb> Daviey: Thanks for the confidence :P
[17:29] <nigelb> Laney: Atm, I'm out of town on work, so I don't have any available time to be able to commit to anything.
[17:40] <blair> apt-get showsrc python-defaults shows where the package is in debian, but where is it in ubuntu?  i'd like to get copy of the history to reverse merge the removal of python 2.6
[17:47] <blair> ok, found it "bzr branch lp:ubuntu/python-defaults"
[17:56] <adam_g> pabelanger: pong
[17:57] <pabelanger> adam_g: wanted to see if you had some time to checkout bug 928499, since you last uploaded it
[18:00] <Daviey> pabelanger: Leave it with me.
[18:01] <Daviey> pabelanger: drop debian-changes-1:2.5.0.1+dfsg-1ubuntu2 ?
[18:01] <Daviey> .patch
[18:48] <pabelanger> Daviey: ya, not sure what happen there. debian-changes-1:2.5.0.1+dfsg-1ubuntu2 can be removed
[18:53] <Daviey> pabelanger: okay, if nobody gets to it before tomrrow - i'll sponsor it
[18:53] <pabelanger> great, thanks
[18:53] <Daviey> pabelanger: the patch can be dropped, or needs inserting somewhere else.
[18:54] <pabelanger> ya, dropped.  I can upload a new debdiff fixing it
[18:54] <Daviey> pabelanger: BTW, the DEP-3 patches do not seem to follow adherence.. but i might just need to look closer.
[18:54] <pabelanger> ack'd, will update them too
[18:56] <Daviey> pabelanger: great!
[19:14] <pabelanger> Daviey: fixed
[19:14] <pabelanger> thanks again
[19:33] <blair> can i run "debuild -S -sd" on my oneiric box but have it be for a PPA for precise?
[19:34] <Ampelbein> blair: Yes.
[19:34] <blair> thanks!
[19:39] <blair> confirming that the standard for numbering a package one is overriding in a PPA is to append "ppaN" to the ubuntu version number?
[19:40] <Ampelbein> blair: There isn't a official standard, I like the -XubuntuY+ppa1 scheme
[19:42] <blair> ok, so my ppa is for providing python 2.6 modules, so i could number it 2.7.2-9ubuntu2py26.1 instead of 2.7.2-9ubuntu2ppa1
[19:44] <blair> can one only have a single - in the version number, or could i have 2.7.2-9ubuntu2py26-1?
[19:47] <micahg> for the Ubuntu revision, yes, for the upstream part, no
[19:47]  * micahg would suggest +py26ppa1 or something
[19:49] <micahg> blair: BTW, you might want to checkout the backportpackage tool
[19:54] <blair> i like that name suggestion
[19:54] <blair> i'm taking the latest python-defaults, reverse merging the commit from bzr into it and uploading the new thing into github :)