[12:06] <Laney> is there any way to get a list of bugs closed by an upload?
[12:07] <Laney> I want Closes: and Launchpad-Bugs-Fixed: equivalents
[12:08] <Laney> Also Original-Maintainer
[12:08] <Laney> (to be clear, I'm talking about access from the API)
[12:25] <wgrant> Laney: An upload?
[12:26] <Laney> Erm, what's that in LP terminology? Publishing record?
[12:26] <Laney> What would be in a changes file.
[12:26] <wgrant> Well, it depends what you mean by upload.
[12:26] <wgrant> What do you want to do?
[12:26] <Laney> I upload a package. I want to find out what LP bugs it closed.
[12:26] <wgrant> Remember that there are real syncs from Debian now, for which there is not even the fake LP-generated changes file.
[12:27] <Laney> this is why I'm trying to use the API instead of the mailing list archives now
[12:27] <Laney> I need to know how to get all of the data I was getting from the fake change files
[12:28] <wgrant> For now it may be best to run the usual regexp over the changelog entries that are sent to the list.
[12:28] <Laney> can I get the changelog through the API?
[12:29] <Laney> what about Original-Maintainer? LP holds that data — can it be exposed?
[12:30] <wgrant> We could expose the entire changelog easily.
[12:30] <wgrant> Since it's stored in the librarian.
[12:31] <Laney> Alright, I'm going to file bugs asking for both of those things then
[12:31] <wgrant> Argh, can't ssh into the DC. Give me a sec to check on Original-Maintainer another way...
[12:31] <Laney> ok
[12:35] <wgrant> Laney: It looks like we don't actually know Original-Maintainer. Pages like https://launchpad.net/ubuntu/+source/dpkg/1.16.0~ubuntu7.1 are a lie -- that's just the maintainer.
[12:36] <Laney> hrm
[12:38] <Laney> I suppose I can parse the dsc
[12:38] <Laney> this is getting uglier than the scraping-changes-mboxes way though :(
[12:38] <wgrant> Why do you want it?
[12:38] <Laney> forhttp://udd.debian.org/schema/udd.html#public.table.ubuntu-upload-history
[12:39] <wgrant> Ah.
[12:42] <wgrant> So, you should probably convince us to expose the changelog, then you can check for bugs fixed since the previous version you know about. And probably just grab the DSC to get Original-Maintainer for now.
[12:47] <Laney> ah, the .dsc has a predictable URL. That's good.
[12:48] <wgrant> Laney: Remember that epochs are special, though :)
[12:48] <wgrant> Laney: You might want to use the sourceFileUrls method on SPPH
[12:48] <Laney> didn't see that. ta.
[13:56] <tumbleweed> Laney: damn, you just pointed out a bug in code I wrote this morning
[13:56] <tumbleweed> ubuntu packages won't all have .changes files any more :/
[13:57] <Laney> It would be easier if native syncs just generated fake ones
[13:57] <tumbleweed> wgrant: yes, plase give us API access to the changelog
[13:59] <wgrant> Laney: That's very difficult to model sensibly.
[13:59] <wgrant> Probably better to fix the few consumers rather than continue the hacks.
[14:02] <wgrant> (introducing changes files for copies would require significant API breaks too)
[21:21] <bulldog98> where would I have to implement a cia hook for launchpad?