[00:00] <Meths> hmmm, not up to date yet.
[00:05] <Meths> Almost there :)
[00:06] <rockstar> Meths, link?
[00:07] <Meths> It's up to date now :)
[01:28] <mathepic> Is there any way to report a project that is stupid and probably a copyright/trademark infringement?
[01:29] <wgrant> mathepic: Maybe ask a question at https://answers.launchpad.net/launchpad/+addquestion. That'll get an admin looking at it.
[01:30] <mathepic> I discovered a project called "Windows 9" that has one file of Python code and two "stable" releases
[01:31] <mathepic> Which both happen to be released on the same day
[01:31] <mathepic> I just checked, its also the same day they registers
[01:31] <mathepic> registered
[01:32] <mathepic> The description is pitiful. "I am writing a new operating system and it will be awesome."
[04:04] <mzz> heh. What would be my chances of getting lp:~me/+crap/... aliased to lp:~me/+junk/... ? :)
[04:23]  * mzz wonders how he ended up on the "beta testers team" (the timeout error page says he is) and how to get back out of it
[04:31] <spiv> mzz: you can probably just go to launchpad.net/~launchpad-beta-testers or your own user page and remove yourself
[04:34] <mzz> "You are not a member of this team. "
[04:35] <spiv> mzz: odd.  Maybe you followed someone else's link to edge.launchpad.net/... rather than just launchpad.net/...?
[04:35] <mzz> spiv: I'm also not seeing edge.launchpad.net in the urls. The only beta tester-ish thing I've noticed is getting that message on timeouts.
[04:36] <spiv> Oh, right.  I think there may be a known bug with that message.
[04:37] <mzz> hmm, I'd just add that +crap alias locally, but I'd start putting it in urls I hand out to others, so that doesn't really work. I should just use this service more so I remember it right, I guess.
[04:38] <mzz> (it is a pretty convenient way to share code)
[04:53] <wgrant> Right, the logic used to show that message is inverted.
[04:54] <wgrant> Bug #403863
[05:05] <mzz> ah, I just searched in "launchpad"
[05:06] <mzz> thanks
[05:09] <wgrant> mzz: Yeah, Launchpad itself uses projects a bit strangely.
[05:10] <mzz> heh, I was assuming it was more like "I didn't bother to find out how it's split into projects"
[05:11] <wgrant> In future, either work out the sub-project or look in launchpad-project (a project group containing the rest)
[05:11] <wgrant> launchpad-project is not, despite its name, a project.
[05:11] <mzz> I was assuming launchpad was what launchpad-project is
[05:12] <mzz> and yeah, a search on https://bugs.launchpad.net/launchpad-project gives me that bug just fine
[05:12] <wgrant> Great.
[06:02] <MTecknology> You guys can help debug apport issues?
[06:03] <wgrant> MTecknology: Unlikely. apport just uses Launchpad.
[06:03] <MTecknology> Logging into Launchpad... You have to allow "Change anything" privileges.   Downloading bug information...   Error connecting to Launchpad: [Errno 0] Error
[06:03] <MTecknology> wgrant: I'm jsut hoping
[06:03] <wgrant> Are you firewalled?
[06:03] <MTecknology> not sure....
[06:04] <MTecknology> what needs to be open for it?
[06:04] <wgrant> 443
[06:04] <wgrant> (TCP)
[06:04] <MTecknology> oh - he's doing it from a chroot
[06:05] <wgrant> wget https://launchpad.net/
[06:08] <MTecknology> wgrant: interesting.. http://pastebin.ubuntu.com/289826/
[06:09] <wgrant> MTecknology: Maybe the chroot doesn't have /dev mounted.
[06:11] <MTecknology> wgrant: doesn't look like he did that - thanks
[08:16] <fale> hello :)
[08:16] <wgrant> fale: So, have you tried uploading again?
[08:17] <fale> wgrant: yes, third time... always the same result :(
[08:17] <wgrant> fale: Tried uploading a different (maybe smaller) package?
[08:18] <fale> wgrant: a copule of days ago
[08:18] <fale> wgrant: w/out any problem
[08:18] <wgrant> fale: Hm. Possibly the server-side problem appearing again, then. Nobody is likely to be around on a weekend to help you debug further, though.
[08:19] <fale> wgrant: I see :(
[08:19] <wgrant> fale: Could you try uploading from a host on another network?
[08:19] <fale> I'll check again on monday, than ;)
[08:19] <fale> I can try today afternoon
[08:20] <wgrant> I think it's worth a try.
[08:20] <wgrant> FTP :(
[08:21] <fale> thankyou
[11:37] <Phurl> https://code.launchpad.net/~ubuntu-l10n-sq/+junk/LaunchPadUpload Here is the working branch of the upload tool.
[11:37] <Phurl> you can upload translations with it
[12:27] <stefanlsd> Is it possible to use wildcards or regex with the api. im trying to search for a version with getpublisedsource and want to do a match
[12:34] <wgrant> stefanlsd: Unfortunately not. The name can be a sub-string, but the version must be an exact match.
[12:47] <stefanlsd> wgrant: kk. thanks. you wouldnt perhaps know if it would be possible to pull out only the latest version with getpublishedsource. eg. if updates or security has a later version than release (it always should), i would only like the latest version...
[12:57] <wgrant> stefanlsd: They should be returned in descending version order, I think.
[12:58] <wgrant> So getPublishedSources(distroseries=hardy, name='package')[0] should be the latest.
[13:16] <stefanlsd> wgrant: mm. yeah. thanks. its a bit of a pain as i need to compare all of them (so need to loop thru all) and using the date_published to compare if its later, but im picking up the update in security and updates.
[13:17] <wgrant> stefanlsd: What exactly are you trying to do?
[13:19] <stefanlsd> wgrant: http://people.ubuntu.com/~stefanlsd/synclist.html was a first run. so trying to help the security team by taking the debian DSA announcements and compare that to what versions we have in ubuntu. i think we managed to sync approx 50 security fixes already. so essentially, i loop through all versions published in ubuntu and compare to debian version. im getting false positives now as we only
[13:19] <stefanlsd> had for eg 3.2.1 in release and that matched. now we have 3.2.1ubuntu1.1 (which i pick up as fixed) but then i loop over 3.2.1 and it says need a fix
[13:20] <stefanlsd> so ideally, i want to return only the latest version of a package.
[13:21] <TDJACR> Launchpad keeps timing out when I report bugs.
[13:21] <TDJACR> (Error ID: OOPS-1379B1626)
[13:21] <wgrant> TDJACR: Try shortening the initial summary, then restoring the full one once you see the list of duplicate candidates.
[13:21] <TDJACR> Okay
[13:22] <wgrant> stefanlsd: Why don't you just stop at the first one>
[13:22] <stefanlsd> wgrant: i've made some code to check previous version date, and if its greater than current version from same distro_series, ignore it, thats not working as the getpublishedsource loops over security and then updates
[13:23] <stefanlsd> wgrant: mm. sometimes we have the same version in other distro_series
[13:25] <TDJACR> cool, thanks.
[13:25] <wgrant> TDJACR: Great.
[13:25] <wgrant> stefanlsd: You know you can restrict it to just one pocket, right?
[13:26] <stefanlsd> wgrant: mm. yeah. was just thinking bout that now. maybe if security is empty, check release... thanks. will work on that a bit...
[13:44] <stefanlsd> wgrant: getpublishedsource returns in a funny order. http://paste.ubuntu.com/290050/    updates, security before release.
[13:45] <stefanlsd> looks like it sorts by version
[14:38] <idnar> is branch scanning (or whatever it's called) stuck again?
[14:39] <idnar> (I pushed a branch over 30 minutes ago, and it's still sitting at "Updating branch...")
[14:53] <jml> idnar, yeah, it is.
[15:08] <jml> idnar, I don't know what to actually do about it though.
[15:10] <idnar> jml: whip the launchpad gnomes harder ;)
[15:11] <jml> idnar, there's some sort of bug in the code that gets it stuck. I don't have any gnomes I can whip to get it unstuck.
[15:12] <idnar> ah, I guess that would require whipping some developers
[15:15] <jml> idnar, well, I actually need someone with permission to kill a particular process on a particular machine. We don't have 24/7 coverage though.
[15:15] <idnar> *nod*
[15:15] <idnar> it's not a big deal for me right now, I just wanted to make sure someone was aware of the problem at least
[15:16]  * jml does the proper thing.
[15:37] <Brucevdk> Hi, the documentation on creating and uploading packages to your team PPA states: "You should also ensure that the email address and GPG key you use with dput are the same as those associated with your Launchpad account." -- However, one of our team members signed the package with his personal key (which may not be associated with his Launchpad account) and now users are saying they cannot verify the packages (http://code.google.com/p/rabbitvcs/issues/
[15:37] <Brucevdk> detail?id=191)
[15:38] <Brucevdk> So, if he associates his key with his Launchpad account it should all work? Is it Launchpad that signs it automatically with the team key (in our case: gpg: key 34EF4A35: “Launchpad RabbitVCS”)?
[15:38] <Brucevdk> Or are we supposed to sign it with the team key?
[15:50] <vxnick> is it possible to delete a bug in a project I own?
[16:14] <jml> vxnick, it's not possible to delete bugs at all
[16:14] <vxnick> jml: alright, thanks for letting me know
[16:14] <jml> vxnick, you can mark it as Invalid or Won't Fix, which amounts to the same.
[16:14] <vxnick> yeah, that's what I've done
[16:15] <vxnick> is it acceptable to use the bug tracker for features? I noticed blueprints does much the same thing, but I don't know whether that's suited to smaller feature requests
[16:18] <Phurl> hi all there is an push active for 2 hours here https://code.launchpad.net/~jamesmikedupont/introspectorreader/wikipedia-strategy
[16:18] <jml> vxnick, the launchpad team use the bug tracker for features
[16:18] <vxnick> jml, many thanks
[16:19] <jml> Phurl, yeah, sorry about that. see the topic.
[16:19] <Phurl> ahh thanks
[16:19] <Phurl> at least it is not just me ;)
[16:19] <cyberorg> hi can i upload file on launchpad, for normal http/ftp download, not commit via bzr?
[16:19] <jml> Phurl, you might also want to subscribe to our launchpadstatus feed on identi.ca
[16:19] <jml> cyberorg, yes you can.
[16:20] <Phurl> ok
[16:20] <Phurl> thanks
[16:20] <jml> cyberorg, but I don't know how to do it off the top of my head & I'm about to head out to grab a coffee :)
[16:20] <cyberorg> jml, cool, any docs where i can find out how?
[16:21] <jml> cyberorg, help.launchpad.net & the launchpad tour (linked from the home page, iirc)
[16:21] <cyberorg> jml, yeah looking at that, couldn't spot what i am looking for
[16:22] <jml> https://help.launchpad.net/Projects/FileDownloads
[16:23] <maxb> cyberorg: I believe the key is that you add them to a release of a project.
[16:23] <maxb> e.g. https://staging.launchpad.net/wibble/trunk/one/+adddownloadfile
[16:24] <cyberorg> maxb, i saw https://help.launchpad.net/Projects/FileDownloads but that talks about making a "release" i just want to upload a random file for people to download
[16:24] <maxb> in what context?
[16:26] <cyberorg> maxb, i have nbd rpm for centos, that is required by centos users to use opensuse kiwi-ltsp, the project is now hosted at launchpad
[16:26] <AskHL_> I'm using Launchpad to host a small project and would like to make a personal package archive.  The packaging files (debian/control, rules and so on) should go into some kind of version control system, I presume.  Is it appropriate to have these in the project trunk branch?  Maybe it wouldn't be all that nice to have the standard, downloadable tarballs (from bzr export --format tgz) include this.  How do people usually manage this sort of thing?
[16:26] <cyberorg> the rpm is "unofficial"
[16:26] <maxb> I don't think Launchpad supports arbitrary file downloads other than in the context of Project->Series->Release
[16:26] <cyberorg> maxb, even if it is related to project?
[16:30] <maxb> Have a look at the dummy arrangement I've just set up on https://staging.launchpad.net/wibble
[16:30] <maxb> I don't think there's a better way
[16:43] <cyberorg> maxb, https://staging.launchpad.net/wibble/trunk/one/+adddownloadfile says " Sorry, you don't have permission to access this page. "
[16:44] <maxb> sure, I created the project so I'm its admin
[16:44] <maxb> On your own project, however, it should work
[16:44] <maxb> Or if you like, tell me your LP id
[16:44] <maxb> and I'll reconfigure the toy one so you can play with i
[16:44] <maxb> t
[16:46] <cyberorg> maxb, https://launchpad.net/kiwi-ltsp is the project, cyberorg is the id
[16:48] <cyberorg> or may be it is jigish-gohil
[16:49] <maxb> ok, you should now be able to play with the wibble project on staging
[16:51] <cyberorg> maxb, cool, got uploaded, now how do i upload to kiwi-ltsp project?
[16:53] <maxb> First go to the project's root page, and "Register a series" to hold these miscellaneous/supplementary files
[16:54] <maxb> Within the series, create a 'release', as part of the process you'll also be guided to create a new 'milestone'
[16:54] <maxb> You'll then be able to attach files to the release
[16:57] <cyberorg> maxb, done, thanks :)
[17:05] <cyberorg> thanks jml and maxb 'night
[17:11] <detly> hi, I need some help with using our ppa
[17:11] <detly> specifically, with having the packages authenticate
[17:11] <detly> the help page says "Launchpad generates a unique key for each PPA and uses it to sign any packages built in that PPA. "
[17:12] <detly> but of course, to upload it, I needed to sign it with my personal signature
[17:12] <detly> so now users report that it does not authenticate
[17:12] <detly> (also: "Your key, and instructions for adding it to Ubuntu, are shown on the PPA's overview page. " ... whereabouts?)
[17:22] <mathepic> I haven't tried to bother with PPA yet. I haven't ever been able to get packaging to work for me.
[17:22] <detly> well, the packaging itself isn't an issue
[17:23] <detly> just this authentication mechanism
 (also: "Your key, and instructions for adding it to Ubuntu, are shown on the PPA's overview page. " ... whereabouts?)
[17:28] <maxb> Under "Technical information", I think
[17:29] <maxb> "Technical details about this PPA"
[17:29] <detly> that just shows the key, and info for *users* to add it
[17:29] <detly> it doesn't tell me how to get launchpad to sign the package
[17:29] <maxb> It just does.
[17:30] <maxb> Or rather, it doesn't sign the package, it signs the repository indices
[17:30] <maxb> Which is your PPA?
[17:30] <detly> rabbitvcs
[17:30] <detly> a user reported the problem at http://code.google.com/p/rabbitvcs/issues/detail?id=191
[17:30] <Brucevdk> https://launchpad.net/~rabbitvcs/+archive/ppa -- linkified
[17:33] <maxb> OK, I think the problem is that Launchpad only generates a key for a PPA *after* the first upload, and then only signs the repository after subsequent uploads
[17:33] <maxb> (or anything which causes republishing)
[17:33] <detly> interesting
[17:34] <detly> so I should just re-upload?
[17:34] <maxb> that would work, or, you could copy another package into the PPA, wait for it to publish, and then delete it again
[17:34] <maxb> e.g. https://edge.launchpad.net/~mercurial-ppa/+archive/ppa/+copy-packages?field.name_filter=&field.status_filter=&field.series_filter=
[17:35] <detly> here we go :)
[17:37] <mathepic> Is there currently any difference between beta launchpad (Edge environment) and the regular one?
[17:38] <maxb> detly: N.B. I think each series is published independently
[17:39] <detly> ah, I might have to rebuild it for the others then
[17:39] <detly> btw, you know you have svn control folders in that source package/
[17:40] <maxb> It's not as if I was putting particular care into packaging it :-)
[17:40] <detly> :P
[17:41]  * maxb grumbles at Chromium monopolizing the buildds
[17:45] <detly> so is that behaviour known or expected? or is it a bug?
[17:47] <Brucevdk> and... is it documented anywhere?
[17:48] <AskHL_> I created new branch and pushed some files to it.  It has now been more than an hour and it still says 'Updating branch...' and that it may take a few minutes.  The files I committed are around 4kB.
[17:49] <AskHL_> Is this normal?
[17:50] <AskHL_> When pushing, I had to give it the --use-existing-dir command, otherwise it complained about the target not being a valid bzr branch.
[17:51] <mathepic> What did you say about --using-existing-dir?
[17:51] <mathepic> I accidentally closed out my client.
[17:51] <AskHL_> mathepic, "When pushing, I had to give it the --use-existing-dir command, otherwise it complained about the target not being a valid bzr branch."
[17:52] <mathepic> To launchpad?
[17:52] <AskHL_> Yes.
[17:52] <mathepic> Its always done that to me.
[17:52] <AskHL_> Okay, so presumably this is normal when pushing to the branch for the first time, correct?  I just thought it might be related to the perpetual updating...
[17:52] <mathepic> It should only happen on the first push
[17:53] <mathepic> After that, the .bzr directory should exist
[17:54] <AskHL_> mathepic, thank you
[17:54] <AskHL_> Should I delete the branch and push again?
[17:54] <mathepic> No
[17:55] <mathepic> The branch should work fine
[17:55] <mathepic> You just have to supply the --using-existing-dir to create it the first time
[17:55] <mathepic> Then you can push normally
[17:56] <AskHL_> mathepic, the problem is that it has been updating the branch for more than an hour, so how long should I wait?
[17:56] <hyperair> hello there. is there a way i can find a launchpad bug number based on the remote bug tracker number?
[17:57] <hyperair> e.g. i have bugzilla.gnome.org bug #NNNNNN and i'd like to find the LP bug linked to it
[17:58] <mathepic> Hmm
[17:58] <mathepic> It says in the topic is that the are delays
[17:59] <mathepic> I'm thinking its a problem occuring with Launchpad
[17:59] <mathepic> I'll see if any of my pushes have worked
[17:59] <mathepic> None of today's pushes have worked.
[18:00] <mathepic> Well, they worked but haven't been process
[18:00] <AskHL_> mathepic, so I see.  Sorry for not reading the topic.  Thank you for the help, mathepic
[18:00] <mathepic> processed
[19:47] <sproaty> I just uploaded a package via dput, and it's said everything's fine -- http://www.pastebin.org/42619 - however https://launchpad.net/~sproaty/+ppa-packages is listing none. Does it take a while?
[19:48] <akheron> sproaty: my guess is that the listing only shows built packages
[19:49] <sproaty> yeah, I wasn't sure how long building took since it didn't mention it on the help page
[19:49] <akheron> usually something like ten minutes
[19:50] <akheron> for a small package, i guess that e.g. libc takes a lot longer to build :)
[19:50] <sproaty> ah I had a rejection email
[20:06] <sproaty> whoops I was making my package with dpkg-build; had to use debuild -S
[20:11] <sproaty> badass, it worked :)
[20:12] <akheron> :)
[20:13] <sproaty> I had to change my changelog where it was listed as "unstable", to "jaunty" -- however, is there a way to target *any* ubuntu version? Mine's not tied to any specifically
[20:14] <akheron> you can upload packages to different ubuntu versions without changing the changelog
[20:15] <sproaty> ah yeah, editing dput.cf
[20:15] <akheron> yes
[20:16] <sproaty> like  this -- or must sections be unique? http://www.pastebin.org/42625
[20:16] <akheron> you'll need to rename the section
[20:16] <akheron> like whyteboard-intrepid
[20:16] <sproaty> ah, cheers
[20:17] <akheron> and remember that you cannot upload the same version to both jaunty and intrepid
[20:17] <akheron> you either upload to intrepid and copy the package to jaunty or use different versions for different series
[20:17] <sproaty> you can only copy packages into newer versions?
[20:24] <akheron> you can copy to older, too, but executables are likely to break because of libc version bumps
[20:25] <akheron> if your package doesn't contain any compiled code, then it's ok
[20:25] <akheron> but generally, I think that copying is bad
[20:26] <sproaty> it's all python :)
[20:27] <akheron> python versions change too across ubuntu versions
[20:29] <sproaty> true, maybe it's best if I do like jaunty/intrepid/hardy packages
[20:29] <akheron> yea
[20:29] <sproaty> not sure how far back to go
[20:29] <akheron> it's explained in launchpad help, too
[20:29] <akheron> it's up to you :)
[20:30] <akheron> but I don't really see a reason to support anything else than the latest LTS release and the newest normal release
[20:30] <sproaty> thank you very much for you help, it has been very helpful and very appreciated :)
[20:30] <akheron> i.e. hardy and jaunty at the moment
[20:30] <akheron> np, happy to help :)
[20:30] <sproaty> had a few people complain my .deb was only for amd64 :(
[20:31] <akheron> is it all python after all then?
[20:31] <sproaty> yes, using wxPython for its GUI - but I'm sure that wx's package name has changed from ubuntu release to release
[20:32] <akheron> you can use Architecture: all for pure-python packages
[20:33] <sproaty> ah, nice
[20:33] <akheron> no more whining from x86 folks :)
[20:34] <sproaty> oh wait I have that, it's because dpkg-builder was just using my system as its base
[20:35] <akheron> hmm
[20:36] <sproaty> ubuntu will build it for all architectures
[22:08] <sproaty> hmm, my build failed because xdg-icon-resource was not found on the build machine. What can I do about that, as I'm using it to install my application's icon
[22:14] <wgrant> sproaty: Build-Depend on whatever package provides it.
[22:16] <sproaty> wgrant,  so, in control:  Build-Depends: debhelper (>= 7), xdg-icon-resource ?
[22:16] <wgrant> sproaty: That package does not exist. You need to figure out which package provides the xdg-icon-resource binary.
[22:17] <sproaty> ah
[22:22] <sproaty> can I cancel packages waiting to build - gotta reupload them since they'll fail too
[22:22] <sproaty> PPAs*
[22:22] <wgrant> sproaty: No, you can't cancel a build.
[22:23] <wgrant> sproaty: But if you upload a new source before the old one starts building, the old builds should be skipped.
[22:23] <sproaty> ah, excellent, thank you.
[23:37] <clsk> hello... is it possible to change my email address in launchpad?
[23:38] <clsk> for my user account that is of course
[23:39] <wgrant> clsk: Of course. If you click on your name in the top right of any Launchpad page, you'll see an edit icon just near the email addresses.
[23:44] <clsk> wgrant: oh I didn't see that. I as trying to use the change details page...Thank you
[23:51] <luke-jr> my project might be needing a custom repository format. will it be possible to use it with LP?
[23:52] <wgrant> luke-jr: Not really.
[23:53] <wgrant> luke-jr: While you could upload using a dumb protocol, it could not be mirrored or scanned so would never become public.
[23:58] <luke-jr> hrm