[10:17] <rye> hi, you may receive a bogus oops-tools summary sent from buffaloberry, please ignore that, I ran the wrong script :(
[12:07] <allenap> I seem to be subscribed to several private PPAs that I have no recollection of. Is that normal? How can I unsubscribe?
[12:07] <wgrant> allenap: You've probably inherited them through team memberships.
[12:08] <wgrant> Subscriptions just grant you access -- they don't give you additional notifications.
[12:08] <allenap> wgrant: Okay. I just ignore them then?
[12:08] <wgrant> allenap: Indeed.
[12:08] <allenap> wgrant: Cheers :)
[12:09] <shadeslayer> can someone edit the VCS imports of https://code.launchpad.net/~vcs-imports/ktorrent/trunk
[12:10] <shadeslayer> the new git urls are : git://git.kde.org/libktorrent
[12:10] <shadeslayer> and git://git.kde.org/ktorrent
[12:10] <jelmer> shadeslayer: hi
[12:10] <shadeslayer> jelmer: heya :D
[12:11] <jelmer> shadeslayer: you need to add a new import, we can change lp:ktorrent to point at that new branch.
[12:11] <shadeslayer> ah ok
[12:11] <shadeslayer> hold on then :)
[12:12] <shadeslayer> jelmer: https://code.launchpad.net/~neon/ktorrent/trunk
[12:13] <shadeslayer> seems i need a new project for libktorrent
[12:14] <jelmer> there's a difference between ktorrent and libktorrent?
[12:14] <jelmer> shadeslayer: I've fixed lp:ktorrent
[12:15] <shadeslayer> ah thanks
[12:15] <shadeslayer> and yeah
[12:15] <shadeslayer> they split out the ktorrent shared libraries
[12:15] <shadeslayer> should i just register libktorrent under the same project or just give it a different branch name?
[12:16] <shadeslayer> s/same/different
[12:17] <shadeslayer> jelmer: ^^
[12:17] <jelmer> shadeslayer: That's a good question, I guess a different project is appropriate.
[12:17] <shadeslayer> okay
[12:25] <shadeslayer> jelmer: can you move https://code.launchpad.net/~neon/libktorrent/trunk to launchpad.net/libktorrent
[12:26] <jelmer> shadeslayer: done
[12:26]  * jelmer wonders who is CHR today
[12:26] <shadeslayer> thanks! :)
[13:59] <patdk-wk> how often does the repository for a ppa add new packages?
[13:59] <patdk-wk> wondering if it's dynamic or like a 30min fixed loop or something, so I have an idea how often not to check it :)
[14:00] <bigjools> patdk-wk: it depends mostly on the load of the system, it can vary between 5 minutes and 40 minutes
[14:00] <patdk-wk> heh, mine seem to always be up near 40min, so I thought it might be a timed thing, instead of load based
[14:04] <bigjools> there's a lot of load lately, I'm working on a fix to speed it up as well
[14:07] <patdk-wk> nice
[14:40] <patdk-wk> strange, it was working last night, but no longer :(
[14:40] <patdk-wk> W: Failed to fetch http://ppa.launchpad.net/patricidk/general-lucid/ubuntu/dists/lucid/main/binary-amd64/Packages.gz  404  Not Found
[14:42] <patdk-wk> oh, seems add-apt doesn't do any good checking
[14:42] <patdk-wk> even though it told me it failed, it added the broken ppa anyways
[14:45] <bigjools> patdk-wk: you've spelled "patrickdk" wrong ...
[14:45] <patdk-wk> I noticed
[14:45] <patdk-wk> but add-apt added it anyways :( even though it didn't exist
[14:46] <patdk-wk> it yelled at me, so I didn't think it would have added it
[15:06] <leonardr> sinzui, i'm trying to understand something jml said and gary says you'll be able to explain it
[15:06] <jml> hah
[15:06] <leonardr> or, if jml is still around, he can do it (sorry, jml, i keep forgetting you're in england)
[15:07] <sinzui> Wow. that was hard to understand. I hope the question is easier
[15:07] <leonardr> jml, what do you mean by "project Foo and all of its downstreams"? what are the downstreams and how is that relationship represented in launchpad?
[15:08] <jml> leonardr: oh right. a Product and its linked source packages in various distros.
[15:08] <jml> leonardr: with our current data set, I believe that would be Ubuntu, but as the derived archive work progresses it could involve other distros as well
[15:08] <leonardr> ok, processing...
[15:09] <jml> to pick a bad example, Banshee is an upstream Product, people file bugs there and on the ubuntu/+source/banshee source package
[15:10] <jml> but then for reasons unknown to mankind, Banshee becomes an integral part of Linaro, which is (will be) modelled as a derivative of Ubuntu
[15:10] <leonardr> jml: would it make conceptual sense to navigate from a project to a collection of its distro_source_packages?
[15:10] <leonardr> (finish your parable first)
[15:10] <jml> oh, and we're also in this future maintaining a full mirror of Debian's bugs
[15:11] <jml> it's highly likely that someone would want to search through the banshee bugs in all of those areas: upstream, ubuntu, linaro, debian
[15:12] <jml> maybe when this becomes more likely we could introduce different data models, but the use case remains... it's exactly the sort of thing Launchpad should do.
[15:12] <jml> leonardr: thinking...
[15:12] <leonardr> actually, scratch that question for the moment
[15:12] <leonardr> here's a better question
[15:12] <leonardr> there's a bug in banshee-in-linaro
[15:13] <leonardr> how would you navigate from the bug to the banshee product?
[15:14] <jml> leonardr: probably with a more expanded version of the Ubuntu-specific things we have already: https://bugs.launchpad.net/banshee
[15:15] <jml> (or see https://bugs.launchpad.net/do for a project that has bugs in both the upstream & Ubuntu)
[15:16] <leonardr> jml: i'm talking about one specific bug. it would have a bug_target, right?
[15:16] <leonardr> and the bug_target would either be banshee, or it would be banshee-in-linaro
[15:16] <jml> leonardr: oh right, sorry, I had it around the wrong way...
[15:16] <leonardr> and if it was banshee-in-linaro, then banshee-in-linaro would have some kind of link to banshee
[15:16] <jml> yes
[15:17] <leonardr> ok, i can work with that, thanks
[15:17] <jml> although I imagine a more common use would be simply clicking some kind of link saying "this also affects upstream", but what you describe would probably be there
[15:17]  * leonardr thinking in terms of the data structures
[15:18] <jml> leonardr: fwiw, banshee and banshee-in-linaro (linaro/+source/banshee) would be of two different types
[15:18] <jml> Product and DistributionSourcePackage
[15:18] <leonardr> good to know
[15:18] <jml> they probably both implement some of the same interfaces though
[15:18] <leonardr> yeah, like IBugTarget
[15:19] <jml> indeed
[15:21]  * jml retreats back to his cave
[16:07] <leonardr> jml: i'm back
[16:07] <leonardr> let's talk about "Ubuntu and its derivatives"
[16:07] <nigelb> I think he went back to his cave
[16:07]  * leonardr lives in hope that jml has irc in his cave
[16:07] <nigelb> :p
[16:08] <leonardr> in your second example you mention bugs "in Ubuntu and its derivatives"
[16:08] <jml> leonardr: yes.
[16:09] <leonardr> a bug would be associated with Ubuntu through bug/bug_target/distribution, and only if the bug_target was a distribution source package
[16:09] <leonardr> is that right?
[16:09] <jml> leonardr: yes, that's right.
[16:10] <leonardr> suppose instead a bug is associated with a derivative of ubuntu
[16:10] <jml> leonardr: and, conceptually, a distribution would have a derivative_distributions collection associated with it. (I don't know how that is actually implemented in the data model)
[16:10] <jml> ok.
[16:10] <leonardr> how is that derivative related to ubuntu?
[16:10] <leonardr> ok
[16:10] <leonardr> so there'd be some kind of 'parent_distribution' on kubuntu
[16:10] <jml> leonardr: probably there's a distribution.derived_from property
[16:10] <jml> yeah
[16:11] <leonardr> and i imagine that can be recursive
[16:11] <jml> and probably, Linaro rather than kubuntu for an actual real-world example
[16:11] <jml> leonardr: as in more than one layer of derivation? yes.
[16:12] <leonardr> all right
[16:13] <jml> leonardr: anything else?
[16:14] <leonardr> jml: that should be it
[16:14] <jml> leonardr: cool. thanks.
[16:25] <Pegasus_RPG_> hello. When we make release branches off of trunk, should we not stack them?
[16:25] <Pegasus_RPG_> Or does it matteR?
[16:29] <yofel> could someone help me retry https://launchpad.net/~kubuntu-ppa/+archive/staging/+build/2073902/+retry - it times out (Error ID: OOPS-1797K1474)
[16:32] <AJenbo> Hi i'm not reciving any confirmation after uploading packages to my ppa
[16:32] <AJenbo> It has been over a week
[16:32] <AJenbo> https://launchpad.net/~ajenbo/+archive/id-game-ports
[16:33] <jelmer> AJenbo: did you receive any email confirming that your packages were accepted or rejected?
[16:34] <jelmer> before they were even built, I mean
[16:34] <jelmer> were the packages signed with your GPG key as registered on Launchpad, and did they list a correct email address ?
[16:36] <AJenbo> yes
[16:36] <AJenbo> no i did build the packages
[16:37] <AJenbo> http://ubuntu.pastebin.com/exYnbyWK
[16:38] <AJenbo> jelmer, I'm actually beginning to doubth that it was the same pgp key, as i can't seam to match the 2048R/9647A895 in LP with the keys on my machine
[16:39] <AJenbo> But when i try to insert the Fingerprint of the key LP just rejects it
[16:40] <jelmer> AJenbo: You can't upload binary packages to PPA's, only source packages.
[16:41] <bigjools> AJenbo, jelmer: https://answers.edge.launchpad.net/soyuz/+faq/227
[16:41] <jelmer> bigjools: thanks
[16:42] <AJenbo> jelmer, it has all the source, i don't want to upload the bin just the source, am i doing some thing wrong?*
[16:44] <jcsackett> Pegasus_RPG_: generally it's okay to make stacked branches. http://doc.bazaar.canonical.com/latest/en/user-guide/stacked.html
[16:44] <AJenbo> jelmer, do i need to clean out some thing after test building before i upload?
[16:45] <patdk-wk> I just rebuild with -S
[16:45] <jelmer> AJenbo: To build just the source you need an option to whatever you're using to build (e.g. debuild -S). #ubuntu-packaging is probably more appropriate for this sort of question.
[16:46] <AJenbo> Hmm LP says Oops when i try to set up my PGP key
[16:46] <AJenbo> Error ID: OOPS-1797O1497
[16:46] <jcsackett> abentley: can you help out yofel with what looks like a ppa build timeout issue, or should i ping someone else?
[16:47] <yofel> jcsackett: it seems like it builds now after refreshing the page a few times, even with the timeout error
[16:47] <bigjools> jcsackett: it;'s working for hgm now
[16:48] <jcsackett> yofel, bigjools: cool, glad to hear it. :-)
[16:48] <bigjools> yofel: there's an auto-retry for dependency-wait builds
[16:48] <abentley> jcsackett: please see if someone from soyuz is available.  I've got a lot of Release Manager stuff to do at the moment.
[16:48] <bigjools> you don't need to hit retry
[16:48] <jcsackett> abentley: issue seems to be resolved. and i forgot you were in RM mode--that trumps. :-)
[16:48] <yofel> ah, well, it builds so I'm happy
[17:12] <AJenbo> Ok that seamed to help, now i got an email, but
[17:12] <AJenbo> Unable to find distroseries: unstable
[17:12] <AJenbo> I guess that i have to change it to maverick
[17:23] <AJenbo> Accepted :)
[17:23] <AJenbo> thanks or the help guys
[17:36] <RichW> Why does my branch have a funny url (lp:hypernucleus-server)? https://code.launchpad.net/~richies/hypernucleus-server/PyramidPort
[17:36] <RichW> Shouldn't it have pyramidport on the end of it?
[17:36] <RichW> nvm i think i understand
[17:46] <AJenbo> does some one know how to generate a finger print for the ppa?
[17:51] <maxb> AJenbo: I'm not sure quite what you mean, can you explain a bit more?
[17:51] <guilhembi> Hello, we MySQL have an issue, a LP branch which has stopped mirroring, is there any LP admin here who could help?
[17:51] <cody-somerville> losas: ^^
[17:51] <AJenbo> sudo apt-add-repository ppa:ajenbo/id-game-ports
[17:52] <AJenbo> Error: can't find signing_key_fingerprint at https://launchpad.net/api/1.0/~ajenbo/+archive/id-game-ports
[17:52] <AJenbo> maxb, ^
[17:52] <maxb> AJenbo: A recently created PPA? The key is generated a short while after the first upload to the PPA
[17:52] <AJenbo> ok, ill give it some time then :)
[17:53] <maxb> It looks like it has happened now
[17:56] <ahasenack> is there any way to speed up the publication of a package in a ppa? LP says "published 37 minutes ago", status published, but at the same time says "Note: Some binary packages for this source are not yet published in the repository."
[17:56] <ahasenack> isn't that a lie when it says "published"?
[17:56] <ahasenack>  i386 - Pending publication
[17:56] <bigjools> ahasenack: source is published, binaries are not
[17:56] <jcsackett> guilhembi: an admin should be responding shortly, per cody-sommerville's request.
[17:56] <ahasenack> bigjools: saying "status: published" can be quite misleading then as a summary
[17:57] <mbarnett> guilhembi: what branch are you having an issue with?
[17:57] <ahasenack> bigjools: anyway, the binary is built, it's just another cron job that has to kick in to actually make it visible for apt-get?
[17:57] <bigjools> ahasenack: see bug 657633
[17:57] <guilhembi> mbarnett: this one:
[17:58] <guilhembi> https://code.launchpad.net/~mysql/mysql-server/mysql-trunk
[17:58] <guilhembi> mbarnett: and this one:
[17:58] <bigjools> ahasenack: yes you need to wait, we've got a slow publisher at the moment because of a couple of bugs and larger load than usual
[17:58] <guilhembi> https://code.launchpad.net/~mysql/mysql-server/mysql-trunk-bugfixing
[17:58] <bigjools> 40mins tops
[17:58] <guilhembi> they have "next mirror: disabled". I'd like them to be kicked off, so that they mirror again.
[17:58] <ahasenack> bigjools: ok, thanks
[17:58] <mbarnett> guilhembi: i see that mirroring is disabled.  let me see if i can figure out why.
[17:59] <bigjools> ahasenack: it should speed up considerably next time we release, I just fixed a nice bug
[17:59] <guilhembi> mbarnett: for mysql-trunk, I think it's because we renamed the branch on our side, but I updated that in  LP ~8 hours ago,
[17:59] <guilhembi> and it hasn't woken up since then.
[17:59] <AJenbo> maxb, the command is still complaning, guess it has a stupid cache some where
[17:59] <guilhembi> mbarnett: for trunk-bugfixing, I don't know the reason.
[17:59] <maxb> AJenbo: hmm, let me try it....
[17:59] <ahasenack> bigjools: \o/
[18:00] <maxb> AJenbo: fails here too. I am confused.
[18:00] <AJenbo> maxb, removing it and then adding it solved it
[18:00] <maxb> AJenbo: removing what?
[18:01] <AJenbo> sudo apt-add-repository --remove ppa:ajenbo/id-game-ports
[18:04] <AJenbo> maxb, but the ppa makes software center crash x(
[18:09] <AJenbo> apt-add-repro added "src http://ppa....." instead of "deb http://ppa....." x(
[18:35] <yofel> me again, this time I have a build that's stuck uploading.. https://launchpad.net/~kubuntu-ppa/+archive/staging/+build/2073903
[18:37] <jcsackett> StevenK: are you available to help out yofel with a build issue?
[19:34] <jfi> Hello, is there a way to check a package before uploading it into ppa? to check that it will not be rejected for trivial reasons
[19:45] <AJenbo> http://pastebin.com/fQ1zZa8G
[19:45] <AJenbo> when i install packages from my PPA i get rejected with a message about them beeing a non trusted source
[19:56] <maxb> AJenbo: An annoyance with the new PPA process is that the PPA key generation will only be initiated after the first publication of a package, and the PPA will only be signed by the key when some other event causes republication of the PPA
[19:56] <maxb> If you upload another package, or a new version of an existing package, the problem should resolve itself
[20:30] <AJenbo> maxb, ok stupid, but ill give it a go :)
[21:24] <maxb> AJenbo: Yes, it is stupid. It's bug 374395. One day.... :-)
[21:32] <bjf> i'm getting a "Code Update In Progress" when attempting to access the staging server, any guess on when this will be available?
[21:35] <jcsackett> bjf: it can depend on what happens during the update, but in my experience not too long.
[21:36] <bjf> jcsackett, thanks, i'll give it some more time
[22:12] <lifeless> bjf: we're doing a full restore.
[22:12] <lifeless> bjf: be 24 hours or so
[22:12] <bjf> lifeless, ouch
[22:12] <lifeless> bjf: you could use qastaging
[22:12] <bjf> lifeless, ok, will try that
[22:13] <bjf> lifeless, Service Temporarily Unavailable   (qastaging)
[22:34] <maxb> How come jaunty is not present under PPA supported series at https://launchpad.net/ubuntu/+ppas, but it still accepts uploads?
[23:30] <achiang> lamont: hi, are the buildds ... cranky right now?
[23:32] <wgrant> achiang: What's up?
[23:32] <wgrant> They look OK to me.
[23:33] <achiang> wgrant: hm, i uploaded a package to a PPA (private, OEM) about 30 minutes ago, and haven't received mail that it was accepted yet
[23:33] <wgrant> achiang: That's well before it gets near the buildds.
[23:33] <wgrant> So it's well before it enters lamont's domain.
[23:33] <achiang> wgrant: ok, sorry for the noise then
[23:33] <wgrant> Let's see..
[23:34] <wgrant> Uploads are being processed OK at the moment. Are you sure you signed it properly and everything?
[23:35] <achiang> wgrant: pretty sure. i have something set in my dput.cf that won't let me upload unless it's signed
[23:36] <achiang> wgrant: some things are moving again. this is probably an oem specific thing, please don't waste any more time on me. :)
[23:38] <achiang> wgrant: although maybe you could help answer me another question -- in a debian/control file, i have Architecture: all which means it is architecture independent. i currently see it building in launchpad with a little i386 icon. is that just the default for an "all" build?
[23:42] <wgrant> achiang: Right, Architecture: all is built on i386 at the moment.
[23:42] <achiang> wgrant: ok, thanks