[04:27] <kbowling> I've uploaded a package for trusty to https://launchpad.net/~llnw/+archive/collectd
[04:27] <kbowling> I then try to upload a package for precise, but I get the email "File collectd_5.4.1-llnw3.tar.gz already exists in collectd, but uploaded version has different contents."
[04:28] <kbowling> tried following https://help.launchpad.net/Packaging/UploadErrors with no luck
[04:28] <kbowling> on the precise and trusty machines, I change debian/changelog to the correct distro and do dpkg-buildpackage -S
[04:30] <kbowling> do I need to somehow embed the release in the dist files?
[05:26] <wgrant> kbowling: You need to change the version in debian/changelog.
[05:26] <wgrant> Otherwise there'd be two collectd packages with version 5.4.1-llnw3, which would be thoroughly confusing to both computers and people.
[05:27] <wgrant> It's common to append something like ~ubuntu12.04.1 to the version for backports.
[05:28] <kbowling> yeah that appears to be it, I'm adding ~trusty and ~precise
[05:28] <wgrant> We used to use codenames, but that breaks after Zany Zebra, so the release's version number is preferred now.
[05:29] <kbowling> why the minor?  is that important?
[05:29] <kbowling> or 12.04 sufficient?
[05:30] <wgrant> 12.04 would be fine.
[05:34] <kbowling> looks like that did it https://launchpad.net/~llnw/+archive/collectd
[05:35] <kbowling> I deleted the whole PPA to clean it; is there a more precise way to clean in the future?
[05:35] <wgrant> Why did it need cleaning?
[05:35] <kbowling> I had a build without a suffix
[05:35] <wgrant> You could have deleted that package.
[05:40] <Terry_ARM> Hi there, my Launchpad-hosted non-PPA project can give me download counts of released packages. Is it possible to get such download counts through python Launchpadlib? I tired but looks like it is not possible.
[05:42] <Terry_ARM> For example, we can see download numbers like 1438, 8070 in page https://launchpad.net/gcc-arm-embedded/+download.
[05:45] <wgrant> Guest80870: Release file download counts aren't exposed through the API.
[05:45] <wgrant> Not yet, at least.
[05:46] <Guest80870> even in the Launchpadlib dev branch?
[05:46] <wgrant> The server defines the API, not the client.
[05:46] <Guest80870> OK. I see. Thank you.
[17:08] <spayno> I had success yesterday with creating my first ppa on launchpad.  It built fine for amd64 and i386.  I'm now wondering if there is a way to have launchpad build for ARM?
[17:24] <dobey> spayno: you can open a question on https://answers.launchpad.net/launchpad to ask to have it enabled on your ppa.
[17:34] <spayno> dobey: thanks! I submitted a question
[17:44] <kbowling> I want to PPA something that manually builds a deb.  any advice on doing this?
[17:45] <kbowling> i.e it doesn't use the typical debian packaging chain
[17:46] <dobey> you can only upload source packages that build with the typical debian packaging chain to a PPA
[20:43] <cjwatson> kbowling: you must implement the standard debian/rules entry points, but beyond that the exact way you build the .deb doesn't matter.  (however not using the typical packaging chain sounds like an epic waste of time)
[22:18] <mapreri> just a quick question: if I ask to get armhf builds in my ppa, is this feature available to all my ppa or to only the one I ask for?
[22:18] <mapreri> wgrant: ?
[22:19] <wgrant> mapreri: It needs to be enabled on a per-PPA basis.
[22:19] <mapreri> wgrant: ok, thanks