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