[13:48] <pietroalbini> hi! is there a way to get authenticated read-only access with the launchpad api?
[13:49] <pietroalbini> I'm building a script for the italian loco to automatically generate the email aliases configuration file, but not all the addresses are available publicly
[13:50] <pietroalbini> and I'm not comfortable sticking my personal credentials in a script :)
[14:19] <cjwatson> pietroalbini: when you authorise an oauth token you can give it read-only access
[14:20] <cjwatson> pietroalbini: still has to be your personal credentials to some extent though, just a somewhat limited version of those.  we don't have very good limited cred support yet
[14:21] <pietroalbini> cjwatson, thanks! I'll see if it's more convenient to generate a token or create a dummy launchpad account just for this
[14:22] <pietroalbini> cjwatson, is there a way to generate a personal access token from the launchpad UI as other services allows?
[14:23] <cjwatson> pietroalbini: no, you need to either get launchpadlib to do it or use the mechanism documented in https://help.launchpad.net/API/SigningRequests
[14:24] <pietroalbini> cjwatson, thanks, I'll read that page :)
[17:51] <acheronuk> LP having issues? ppa uploads and acceptance emails have been very slow to appear
[17:59] <emoraes25> Greetings dear friends! Please, I need help uploading my package to PPA.
[18:01] <emoraes25> I did a packing only that my tarball contained a mistake that I made during the packaging. I needed to update it with the correct upstream tarball, but I would not like to generate a new version number.
[18:03] <emoraes25>  How can I do it?
[18:03] <acheronuk> you can't upload a new tarball with different contents of the same version as already existed in the ppa
[18:04] <acheronuk> either bump the version, or make a new ppa
[18:10] <emoraes25> The problem is that I am packaging the same version for Debian, and from what I understand, Ubuntu takes to its repositories the new packages of the Debian repositories. I do not like this version of PPA appears as newer than the version that is in Debian. Would there be a way for me to version in Ubuntu so that it looks like the package version was less than the version that will arrive in Debian?
[18:11] <acheronuk> make a new ppa. then you can put whatever version you like in it
[18:11] <emoraes25> For example. The upstream version is 9.0. My package in Debian is 9.0-1. How could I make my PPA not 9.0-2, for example?
[18:12] <emoraes25> Can I delete the current ppa and create a new one with the same name as the previous one?
[18:13] <acheronuk> the -1 or -2 is a debian revision, not a source version
[18:14] <emoraes25> I know, but the source version did not change, I accidentally edited a source package file when I went to package.
[18:14] <cjwatson> you can entirely delete and recreate the archive if you don't need anything old in it, yes
[18:15] <cjwatson> you should probably look at versioning styles that use the ~ syntax though (see Debian policy)
[18:16] <emoraes25> Truth! I actually saw something about it, but I did not quite understand how it works. I will take a look. Thank you!
[18:18] <emoraes25> Thank you all!
[18:19] <acheronuk> emoraes25: at the moment you'll be luck to get any ppa builds uploaded. seems to be borked
[18:19] <cjwatson> OK that's not actually super-helpful to tell people unless you know the problem
[18:20] <cjwatson> acheronuk: Things seem to be running OK at the moment.  If you have a problem then you need to give specifics (archive/package names)
[18:21] <acheronuk> cjwatson: sorry.
[18:22] <acheronuk> cjwatson: ppa:rikmills/staging3  Uploading kalarm_17.04.2-0ubuntu1~ubuntu17.10~ppa10.dsc: done.
[18:23] <cjwatson> 2017-06-08 17:58:14 DEBUG   Rejected:
[18:23] <cjwatson> 2017-06-08 17:58:14 DEBUG   Unable to find kalarm_17.04.2.orig.tar.xz in upload or distribution.
[18:23] <cjwatson> the system sent you a rejection email
[18:23] <acheronuk> no email here!
[18:23] <cjwatson> (seven minutes after you initially asked, admittedly)
[18:24] <acheronuk> though as said, emails have been off the last day or so. had a few come nearly 24hrs after the package upload!
[18:25] <cjwatson> I think that must be a problem somewhere in the email delivery pipeline, rather than in LP.  Received headers are a good tool for investigating this kind of thing
[18:25] <acheronuk> grr. I see the issue in that. gbp-ppa is assuming already uploaded source when it is not
[18:26] <cjwatson> ah, not in fact seven minutes after you initially asked; I think your initial question was in fact about a slightly different version, since I see an earlier rejection of 4:17.04.1-0ubuntu1~ubuntu17.10~ppa10, eight minutes before you asked here
[18:27] <acheronuk> cjwatson: thanks. next time I get a very latest one I'll check. at them moment I don't recall the excact previous ones to check
[18:28] <acheronuk> yes, I did another upload to correct my version
[18:28] <cjwatson> right, I just wanted to make sure that there really was no unexplained delay here.
[18:28] <acheronuk> and a rejection email comes through \o/
[18:29] <acheronuk> that's fine. it's just when packages appear to disappear into nothingness that it gets a tad annoying.
[18:29] <acheronuk> thanks :)
[18:33] <acheronuk> BTW, the rejection email I got was for the 2nd one. still not got the 1st
[18:33] <acheronuk> something somewhere is not behaving well, LP or elsewhere
[18:34] <cjwatson> please check Received headers; they will show the timestamps when the mail was received by various hosts along the way, of which there can easily be quite a lot
[18:34] <cjwatson> I cannot see that information.  Only you can.
[18:35] <cjwatson> a random recent email sent to me by LP got to the first non-Canonical email host in the chain within ten seconds of being sent, so I don't think there's a general enormous queue or anything
[18:46] <acheronuk> my headers appear to show that mail did not get received by google from canonical server for about 30 mins
[18:47] <acheronuk> though my reading of the headers could be suspect :P
[23:54] <gsilvapt> Could someone tell me where I can find information on how to do a proper merge request in launchpad using git?
[23:55] <wxl> gsilvapt: the merge request process is all handled within the LP UI
[23:56] <wxl> i.e. you would commit/push to git, then load up the appropriate branch in the UI, at which point it will present things
[23:56] <clivejo> wxl: where do you push to?
[23:56] <clivejo> I guess you add a remote?
[23:56] <wxl> yep
[23:56] <gsilvapt> yes, but in terms of branches and all that. I cloned the source code and then where should I push the changes? Should I create a branch under my user?
[23:56] <clivejo> the repo is https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/ksnakeduel
[23:56] <clivejo> kubuntu_unstable branch
[23:56] <wxl> ah yes
[23:57] <wxl> push to a branch under your use
[23:57] <gsilvapt> Okay. Makes sense. Do I need specific names to create a branch under my user or not at all?
[23:57] <gsilvapt> Of course, non-sense not included here
[23:58] <wgrant> gsilvapt: ssh://USERNAME@git.launchpad.net/~USERNAME/kubuntu-packaging/+git/ksnakeduel probably makes sense.
[23:58] <clivejo> do you add a remote as git+ssh://git.launchpad.net/~gsilvapt/kubuntu-packaging/+git/ksnakeduel ?
[23:59] <wxl> ssh+git://