[11:59] <vrederv> How do I use the web API to fetch the version of a package?
[12:00] <cjwatson> easiest if you have it in the form of a source package name, then you'd use archive.getPublishedSources
[12:01] <cjwatson> something like http://paste.ubuntu.com/23672829/
[12:01] <cjwatson> https://launchpad.net/+apidoc/devel.html#archive-getPublishedSources
[12:02] <cjwatson> you can use archive.getPublishedBinaries if you really need to go by binary package name, in which case you also need to specify the architecture
[12:02] <cjwatson> In [1]: lp.distributions['ubuntu'].main_archive.getPublishedBinaries(binary_name='man-db', exact_match=True, distro_arch_series='/ubuntu/zesty/amd64', pocket='Release', status='Published')[0].binary_package_version
[12:02] <cjwatson> Out[1]: u'2.7.6.1-1'
[12:03] <vrederv> thank you ... I am not using the Python module
[12:03] <cjwatson> you'll have to derive the required requests from the above then, but it's a pretty regular transformation
[12:04] <cjwatson> https://help.launchpad.net/API/Hacking
[12:05] <vrederv> Let's take Ubuntu's apache2 package as an example, the site is https://launchpad.net/ubuntu/+source/apache2
[12:06] <vrederv> The archive URL should be https://api.launchpad.net/1.0/ubuntu/+archive/apache2
[12:07] <cjwatson> no it shouldn't
[12:07] <vrederv> alright what should it be?
[12:07] <cjwatson> /ubuntu/+archive/primary is the archive; apache2 is not an archive
[12:08] <vrederv> So https://api.launchpad.net/1.0/ubuntu/+archive/ubuntu/+archive/primary ?
[12:08] <cjwatson> $ curl -s 'https://api.launchpad.net/devel/ubuntu/+archive/primary?ws.op=getPublishedSources&source_name=apache2&exact_match=true&distro_series=/ubuntu/zesty&pocket=Release&status=Published' | jq '.entries[0].source_package_version'
[12:08] <cjwatson> "2.4.23-7ubuntu1"
[12:08] <cjwatson> (remove the duplicate /ubuntu/+archive segment from yours)
[12:09] <vrederv> thank you!
[12:09] <cjwatson> you're welcome
[13:30] <clivejo> Hi folks, can an existing LP bug be converted into an SRU, or should a brand new bug be submitted for the SRU?
[13:32] <cjwatson> clivejo: that's an SRU team question rather than an LP question.  but anyway, usual practice is that if the existing bug is just for the one thing that's being changed in the SRU, then it's fine to reuse it, otherwise file a new bug
[14:29] <smoser> where do i configure webhooks for https://code.launchpad.net/cloud-init ?
[14:29] <smoser> i can't seem to find it poking around in the ui
[14:37] <cjwatson> smoser: some things are only on the repository page and not on the code index, somewhat confusingly
[14:37] <cjwatson> smoser: so follow the "lp:cloud-init" link and then "Manage webhooks" under there
[14:38] <smoser> hm.
[14:38] <smoser> i swear i looked there. or at least had some other view of that repo. thank you !
[14:38] <cjwatson> np
[14:38] <cjwatson> the code index has a sort of partial view - I have a batch of UI changes in progress to try to make things clearer there
[14:39] <smoser> ok. i also looked https://code.launchpad.net/cloud-init
[14:39] <smoser> i did read the docs... so if they had some "git hooks configure at a url like ...." then i'd have probably not bothered you
[14:39] <smoser> thank you though.
[14:40] <cjwatson> well, it's a UI bug really.  there should just be a "Manage webhooks" link right there.
[19:51] <rlaager> cjwatson: No answer on https://answers.launchpad.net/launchpad/+question/407771 in three days. He is still unable to login.
[19:52] <nacc> rlaager: could just be timing, holidays and all
[19:53] <rlaager> nacc: Sure. I have no idea what the commercial support process is supposed to look like. This is preventing him from pushing stuff to our paid-for private PPA.
[19:53] <cjwatson> I've been the only LP staff person on duty and I've had a hellish deadline to meet before end of year
[19:54] <cjwatson> also not sure anyone said it was commercial ...
[19:54] <nacc> rlaager: right, i'd never have known it was commercial myself :)
[19:55] <rlaager> cjwatson: It sounds like your other thing is more important. We can wait.
[19:55] <cjwatson> I'm done for the year
[19:55] <cjwatson> But let me see if I can figure something out
[19:56] <user0> Hi, I've got the same problem as that 407771. I think this happened to me 3 months ago when I created the account, so I let it time :-) But still Oops-* all time now.
[19:57] <user0> can't access https://launchpad.net/people/+me/
[19:57] <cjwatson> user0: what's the OOPS ID?
[19:58] <user0> OOPS-8748ac6f6e9da2126007ef4659c66de4 , right now
[19:58] <ubot5`> https://oops.canonical.com/?oopsid=OOPS-8748ac6f6e9da2126007ef4659c66de4
[19:59] <cjwatson> ok, will look into both once a sysadmin responds to my query
[19:59] <rlaager> Also for reference: My existing account can login (in new browser sessions) just fine. We tried a couple different browsers for his, and it reproduces in both of them.
[19:59] <cjwatson> rlaager: yeah, it's specific to his account because he previously had an autocreated person record due to a translation import
[20:00] <cjwatson> neither the behaviour of your account nor the browser is relevant - the OOPS uniquely identifies the problem
[20:01] <cjwatson> this is all https://bugs.launchpad.net/launchpad/+bug/1607242, just need to get a sysadmin to tell me what the new openid association in the DB is so that I can request the proper merge
[20:01] <ubot5`> Ubuntu bug 1607242 in Launchpad itself "Logging into a placeholder person OOPSes if email address already on another person" [Critical,Triaged]
[20:14] <cjwatson> Er, s/translation/bug comment/ in my comment above.
[20:34] <cjwatson> rlaager,user0: should work now
[20:34] <cjwatson> sorry for the delay
[20:39] <rlaager> cjwatson: Thanks!
[21:02] <user0> Wow!!!
[21:02] <user0> thank you very much cjwatson
[21:03] <user0> Hopefully I found this IRC @ https://help.launchpad.net/Oops
[21:03] <user0> thumbs up