[11:29] <free> wgrant: hey there, fyi I merged to lp:txlongpoll that branch with the "make build" fixes. I also set up a web hook to sync lp:txlongpoll with github, in order to have some minimum CI with travis. See https://github.com/CanonicalLtd/txlongpoll and https://travis-ci.org/CanonicalLtd/txlongpoll
[11:41] <wgrant> free: Nice.
[12:35] <ricotz> hi, here are two stuck arm64 builds -- https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+build/9858739 -- https://launchpad.net/ubuntu/+source/firefox/47.0+build3-0ubuntu1/+build/9871854
[12:37] <wgrant> ricotz: I've killed them.
[16:05] <nacc> i must be missing something obvious, have a bug in smbldap-tools, same version is in trusty & xenial. Would like to provide builds in a PPA for both for testing SRU. But can't dput twice (as the upload of the specified version has already happend). And LP copy package to a different series also failed.
[16:05] <nacc> *same version will be in
[16:07] <cjwatson> If you need to build twice then the builds need to have different version numbers.
[16:07] <cjwatson> https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging has advice on versioning that's particularly relevant to SRUs
[16:07] <nacc> thanks, i'll review it
[16:07] <teward> nacc: use the versioning ^ as a guide
[16:08] <teward> make sure Yakkety > Xenial > ... > Trusty > Precise
[16:08] <teward> if you want to see that in action, look at the string of nginx diffs I prepped for the latest security fixes (though security updates, versionstrings still apply)
[16:09] <nacc> teward: cjwatson: thanks!
[16:09] <teward> :)
[16:09] <teward> nacc: the SRU-versioning is most relevant, and usually the nicest guide for how to do it though
[16:09] <teward> which reminds me... thanks for the link cjwatson, I lost that from my bookmarks
[16:42] <Laibsch> Given the last two comments in bug 512764 which are spread 9 months apart, it seems to me that the account of https://launchpad.net/~scott-binrock ought to be closed
[17:43] <ayan> the http://launchpad.net/~user/+git page should have instructions for creating a repo.
[17:46] <ayan> something like:
[17:46] <ayan> You can push (upload) personal branches (those not related to a project) with the following command:  git push --set-upstream  git+ssh://git.launchpad.net/~user/+git/REPOSITORY_NAME master
[17:46] <ayan> that is if that's how it's done.
[17:50] <cjwatson> Laibsch: https://answers.launchpad.net/launchpad for such reports please (I'm at end of day, not thinking about this right now)
[17:50] <nacc> ayan: seems like that's general git remote usage?
[17:50] <Laibsch> OK. Sure. Thanks, cjwatson.
[17:50] <cjwatson> ayan: seems not unreasonable, please file a bug at https://bugs.launchpad.net/launchpad so that the suggestion doesn't get lost
[17:51] <cjwatson> nacc: details of namespacing could be usefully self-documented I think
[17:51] <Laibsch> LP finally has git now?  Awesome stuff.
[17:51] <cjwatson> as of last year
[17:51] <nacc> cjwatson: ack, i think they are somewhere else, just not on that page, you're right
[17:51] <Laibsch> about time ;-)