=== magcius_ is now known as magcius
[02:57] <alexp_sssup> hi everyone
[02:59] <alexp_sssup> I've been trying all day to "dput" a source package to my ppa but, until now, with no success. Package files are uploaded successfully, but then i receive an email notification that the signature check on the package failed because it "cannot find public key"... I've setup my GPG key, of course, any suggestions?
[03:01] <wgrant> alexp_sssup: You are probably dputting to the wrong place.
[03:01] <wgrant> Debian sends that sort of email, but Launchpad doesn't.
[03:01] <wgrant> Can you pastebin the email somewhere?
[03:13] <idnar> The diff has been truncated for viewing.
[03:13] <idnar> nooo :(
[03:15] <alexp_sssup> wgrant: yep, just a sec
[03:16] <alexp_sssup> wgrant: http://pastebin.org/171939
[03:16] <alexp_sssup> it's kind of weird that the upload to my personal ppa succeed, the one to the team PPA fails
[03:18] <alexp_sssup> is there some specific stuff i should do to be a team uploader?
[03:21] <wgrant> idnar: It must have been pretty big...
[03:22] <wgrant> alexp_sssup: Yeah, that's Debian. Not what you want to upload to.
[03:22] <idnar> wgrant: looks like it was truncated at 5000 lines, I'm not sure how big it is in total
[03:22] <idnar> wgrant: oh, it says 9384 lines
[03:22] <idnar> 9384 lines (+2682/-3557) 21 files modified
[03:22] <wgrant> There's nothing special about uploading to a team PPA -- as long as you're a member, and you upload to the right place.
[03:27] <alexp_sssup> wgrant: humm... ok, specifying the ppa on the command line fix the issue (i feel like a newbie now, sorry). I supposed that dput would default on the first configuration in .dput-cf, not on a debian server :-)
[03:29] <alexp_sssup> thanks
[03:29] <alexp_sssup> goodnight
[03:32] <amitprakash> hi.. for libdesktop-agnositc i am getting ..  error: Your Vala compiler version (0, 8, 0) is too old. The project requires when only 0.7.10 is required
[03:34] <wgrant> amitprakash: This is the channel for launchpad.net itself. You will need to find specific support resources for the libdesktop-agnostic project -- this is not the place you're looking for.
[03:34] <amitprakash> ah ok
[03:34] <amitprakash> wgrant, thanks a lot
=== magcius__ is now known as magcius
[08:38] <magcius> How do I delete a project?
[08:48] <wgrant> magcius: You'll need to ask an admin at https://answers.launchpad.net/launchpad/+addquestion.
[08:50] <magcius> wgrant: are you an admin?
[08:51] <magcius> wgrant: if not, you should be. You're always very helpful, and would do a great job.
[08:52] <magcius> wgrant: also, the other answer it referred me to said to file it at launchpad-project
[08:53] <wgrant> magcius: You can't file against launchpad-project itself (it is a project group): it will ask you to file it on one of the subprojects instead.
[08:53] <magcius> wgrant: alright
[09:55] <magcius> wgrant: huh
[09:56] <magcius> wgrant: I just spent 20 minutes trying to understand why it wasn't pulling new revisions when I figured out that it doesn't track when the "lp:foobar" shortname updates
[09:56] <magcius> that seems counterintuitive to the whole point of the shortname updates
[09:56] <magcius> or the shortname, even
[09:57] <wgrant> magcius: Yeah, that's a strange bzr thing (not specific to LP).
[09:57] <magcius> wgrant: wouldn't that be the LP plugin's thing or is the "one:two" URL specifier not LP-specific
[09:58] <magcius> wgrant: the best fix I can think of for that is to make "one:two" a first-class citizen and resolve that as late as possible
[09:59] <Peng_> The LP plugin uses bzr's directory service.
=== ubott2 is now known as ubottu
[10:01] <magcius> Peng_: okay, so why couldn't we, when I say, "bzr get lp:mything", store the literal "lp:mything", and not the resolved URL.
[10:02] <Peng_> "we" here is probably #bzr, and I have no opinion on the matter. I could go either way.
[10:03] <magcius> Peng_: I was more asking if there was anything technical restricting that
[10:03] <magcius> Peng_: but I guess you don't know. Sorry!
[10:03] <wgrant> Asking #bzr or filing a bug against bzr may be a good next move.
[10:03] <Peng_> magcius: Ah. I don't know. In fact, I think you can open up .bzr/branch/branch.conf in a text editor and force it to use the lp: URL.
[10:03] <magcius> Peng_: huh
[10:03] <magcius> wgrant: yeah, I was about to do that
[10:04] <Peng_> For my own use, I'm mostly happy with the current behavior.
[10:04] <wgrant> Most projects don't switch the dev focus around enough for it to bother me.
[10:04] <Peng_> It would confuse me if I suddenly got a different branch when pulling.
[10:04] <magcius> wgrant: that's what I thought too
[10:04] <Peng_> OTOH, back when lp:loggerhead was switched, getting the new branch is the correct behavior.
[10:04] <magcius> wgrant: except that all of Canonical's stuff has moved from foo-bar-developers to canonical-dx-team
[10:05] <Peng_> But, say, lp:mysql (IIRC) points to the current release, and it would confuse me if my 5.0 branch suddenly turned into 5.1.
[10:05] <Peng_> But it's easy enough to work around.
[10:06] <magcius> Peng_: well, I wouldn't clone lp:mysql expecting to get a specific release. It's the development trunk, right?
[10:06] <Peng_> magcius: Yeah, _now_ it is, but it used to be, um, 5.1 in the past.
[10:06] <Peng_> Maybe that was the "trunk" branch. I dunno.
[10:06] <magcius> I don't understand a lot of things.
[10:07] <magcius> For some projects, the "trunk" branch isn't up to date, it's the "lucid" branch
[10:08] <magcius> which really offends me, who is not using Ubuntu
[10:08] <magcius> oh well... there are other parts of bzr that I feel have the wrong motivation
[10:09] <Peng_> "wrong motivation"?
[10:20] <maxb> If a project has non-distro-specific development in a "lucid" branch, then it's the project's fault for having a weird branch naming convention
[10:21] <Peng_> "lucid" is an awesome name for a branch.
[10:22] <wgrant> It's quite reasonable for a project that is developed primarily for Ubuntu's purposes, and within the Ubuntu release cycle.
[10:34] <magcius> Peng_: the "wrong motivation" I can mainly think of is the "Bzr Explorer" application
[10:36] <magcius> Peng_: I just find it's wrong to let the whole slew of Ubuntu GUI users into a SCM. With the way things are worded it brings this awkward "Clippy" hatred back.
[10:40] <magcius> oh
[10:41] <magcius> I think I've said this in this channel, but maybe I should file this:
[10:41] <magcius> http://imgur.com/YbETF.png
[10:41] <magcius> your sliding door needs more width
[10:48] <magcius> I just had another idea
[10:48] <magcius> See the downloads here? https://launchpad.net/bzr
[10:49] <magcius> It would be nice if we could scrap the green box every time and instead have a custom title and icon.
[10:49] <magcius> So we could have "Bazaar 2.2 (Windows Installer)" with a little bzr and windows logo
[10:49] <magcius> instead of "bzr-2.2b2-setup.exe"
=== voRieLLo is now known as voRia
[12:45] <hyperair> is launchpad's email interface working?
[13:05] <thumper> hyperair: I've not seen any emails saying it isn't (and we do get them)
[13:06]  * thumper must sleep now
[13:27] <persia> If anyone is about, the amd64 production build queue has a job that has remained unscheduled for at least 2 hours whilst nothing is building.  Might be worth discovering why and poking it.
[13:51] <hyperair> thumper: i sent an email to new@bugs.launchpad.net earlier, but i didn't get a reply, and the new bug didn't appear.
[13:51] <hyperair> oh well.
[14:46] <nigelbabu> What is wrong with this searchTask? searchTasks(has_patch=True,status=['New','Incomplete','Confirmed','Triaged','In Progress'],tags='patch-forwarded-upstream -patch-accepted-upstream -patch-rejected-upstream patch-forwarded-debian -patch-accepted-debian -patch-rejected-debian')
[14:47] <nigelbabu> if anyone around knows....
[15:33] <james_w> nigelbabu: how do you know it is wrong?
[15:34] <nigelbabu> james_w: python errors
[15:34] <james_w> pastebin the error?
[15:35] <nigelbabu> a minute
[15:36] <nigelbabu> http://paste.ubuntu.com/421704/
[15:36] <nigelbabu> funny thing is instread of whitespace between tags, if I use +, no error but it doesn't work
[15:37] <james_w> ah, you want to catch the error and print the body of the response to find out why it doesn't like it
[15:38] <nigelbabu> come again? I didn't understand.
[15:38] <james_w> use an except lazr.restfulclient.errors.HTTPError, e:
[15:38] <james_w> print e.content
[15:39] <james_w> nigelbabu: http://paste.ubuntu.com/421705/
[15:40] <nigelbabu> trying out
[15:40] <nigelbabu> what does the 'raise' do there?
[15:40] <nigelbabu> NameError: name 'lazr' is not defined
[15:40] <james_w> re-raises the error so that the script will still fail
[15:40] <james_w> ah, "import lazr.restfulclient.errors" just before
[15:41] <nigelbabu> http://paste.ubuntu.com/421708/
[15:42] <james_w> umm, no idea what that means :-)
[15:42] <nigelbabu> If I use +, the error goes away
[15:43] <nigelbabu> but it doesn't really work.
[15:43] <nigelbabu> essentially, my question is how to search for tag combination.
[15:49] <james_w> try tags=['patch', '-patch-accepted-upstream']
[15:52]  * nigelbabu hugs james_w 
[15:52] <nigelbabu> that worked.  someone correct the apidoc
[15:53] <geser> james_w: looks like a bug in the API doc ("Separated by whitespace.") or LP has a different understanding of it.
[15:53] <james_w> huh
[15:54] <nigelbabu> I specifically didn't use the list format because the doc said its separated by whitespace
[15:54] <james_w> nigelbabu: but you did put [] around it
[15:55] <james_w> I think tags='patch -patch-accepted-upstream' would work too
[15:55] <nigelbabu> part of trial and error experiments
[15:56] <nigelbabu> james_w: nope.  throws error.  similar to what I pastebin'd earlier
[15:56] <geser> james_w: tags: [ConstraintNotSatisfied(u'patch -patch-accepted-upstream')] and it was in []
[15:58] <geser> it only works with a list of elements without any whitespace (not even trailing whitespace)
[15:59] <nigelbabu> geser: so definitely apidoc problem?
[15:59] <geser> nigelbabu: yes, please file a bug
[16:00] <nigelbabu> um, against?
[16:00] <james_w> launchpad-bugs
[16:00] <geser> launchpad, it will get reassigned to right sub-project
[17:19] <fperez> Howdy, question on using the API?
[17:21] <fperez> Trying: https://help.launchpad.net/API/Examples#Hello%20Launchpad!
[17:21] <fperez> Doesn't work at all:
[17:22] <fperez> In [28]: launchpad = Launchpad.login_with('hello-world', 'edge')
[17:22] <fperez> ---------------------------------------------------------------------------
[17:22] <fperez> InvalidURIError                           Traceback (most recent call last)
[17:22] <fperez> /usr/lib/python2.6/dist-packages/lazr/uri/_uri.pyc in __init__(self, uri, scheme, userinfo, host, port, path, query, fragment)
[17:22] <fperez>     239             match = uri_pat.match(uri)
[17:22] <fperez>     240             if match is None:
[17:22] <fperez> --> 241                 raise InvalidURIError('"%s" is not a valid URI' % uri)
[17:22] <fperez>     242             self.scheme = match.group('scheme')
[17:22] <fperez>     243             self.userinfo = match.group('userinfo')
[17:22] <fperez> InvalidURIError: "edge" is not a valid URI
[17:22] <fperez> The tip on https://help.launchpad.net/API/Examples#Get%20a%20useful%20error%20message%20from%20launchpadlib
[17:22] <fperez> needs correcting to indicate where HTTPError lives, which is highly non-obvious:
[17:23] <fperez> except lazr.restfulclient.errors.HTTPError, e:
[17:23] <fperez> Because most people will try to use urrlibw.HTTPError and it won't work.
[17:23] <fperez> So now I've modified the example to:
[17:23] <fperez> try:
[17:23] <fperez>     launchpad = Launchpad.login_with('hello-world',
[17:23] <fperez>                                      'https://edge.launchpad.net')
[17:23] <fperez> except lazr.restfulclient.errors.HTTPError, e:
[17:23] <fperez>     print e.content
[17:23] <fperez> else:
[17:23] <fperez>     print 'Hello, %s!' % launchpad.me.display_name
[17:23] <fperez> But I still get an error:
[17:23] <fperez> SyntaxError: undefined entity &nbsp;: line 264, column 17
[17:24] <fperez> That syntax error is coming from somewhere outside my code (I just ran the 5 lines above)...
[17:25] <fperez> Any tips? I'm trying to use the published API to grab IPython's bug history, but none of the published examples I've tried so far work...
[19:30] <magcius> How would people feel about cleaning up the Downloads list?
[19:31] <magcius> As a user, I look at the downloads for https://edge.launchpad.net/bzr and become humbled
[19:31] <magcius> er, I need sleep. Confused
[19:32] <magcius> It would be nice if they dropped the big green download and instead allowed you to set a name and a little icon for downloads: "Bazaar 2.2 beta 2 (Mac OS X)"
[21:15] <moum> Hi, i need help with the Referee header, thx
[21:16] <alkisg> I'm getting server errors for http://bazaar.launchpad.net/~sch-devs/sch-scripts/trunk/revision/109
[21:52] <maxb> alkisg: Given it's the middle of a weekend, you should probably file a question, or be prepared to re-ask on Monday
[21:52] <maxb> moum: If you describe your problem in more detail, you'll be more likely to get help
[21:52] <alkisg> maxb: no problem I was just reporting it, I don't need it fixed, I got everything I need locally :)
[21:52] <alkisg> Have a nice weekend all.
[21:56] <moum> I had a REFERER header request when trying to translate a program, but it works well with Chrome.
[21:56] <moum> However, i dont know why it does not work with firefox
[22:12] <bernie> can someone suggest why my ppa would build a package only for i386 and not amd64 and other archs?
[22:13] <bernie> https://edge.launchpad.net/~codewiz/+archive/ppa/+builds?build_text=&build_state=all
[22:13] <bernie> the package is bitfrost
[22:13] <bernie> debian/control says: Architecture: all
[22:13] <bernie> lfaraone: maybe you know?
[22:17] <james_w> bernie: Architecture: all means build once and use the result on all architectures
[22:17] <james_w> if you want it to build for each architecture you want "any
[22:17] <james_w> "
[22:18] <bernie> james_w: well it's a pure python package, so "all" was probably correct.
[22:18] <bernie> but why wouldn't a n amd64 machine find the package then?
[22:18] <james_w> dunno
[22:21] <maxb> bernie: See, it is published for amd64: http://ppa.launchpad.net/codewiz/ppa/ubuntu/dists/lucid/main/binary-amd64/Packages
[22:39] <bernie> james_w, maxb: problem lied between chair and keyboard.
[22:39] <bernie> thanks for your help
[23:13] <Agafonov> Hi! I have "Internal Server Error" on my branch at bazaar.launchpad.net page. Am I to fill a bug and which project?
[23:17] <Agafonov> ok, here is url: http://bazaar.launchpad.net/~ubuntu-ru-web/ubuntu-ru/smf2-mods/revision/2
[23:19] <Agafonov> ups. all revisions in all branches give error...
[23:31] <manish> wgrant, I hope you there? Have a small doubt on WADL files
[23:33] <manish> wgrant, anyway for your reference. I sent the problem on launchpad list. Look at it at your free time. It would be very kind of you https://lists.launchpad.net/launchpad-users/msg05920.html
[23:48] <wgrant> manish: There is a launchpad-dev@lists.launchpad.net, but launchpad-users is probably the correct place for this.
[23:48] <wgrant> I don't know the internal details of the WADL, unfortunately.