[13:20] <kyrofa> cjwatson, the snap builders are dreamy by the way. My only complaint is that the proxy is a little flaky sometimes (I get errors about it needing authentication sometimes)
[13:20] <kyrofa> cjwatson, any chance the snap builders are somehow exposed in the python API?
[13:21] <cjwatson> flaky> do file bugs about that kind of thing with specific references.  it may be that the timeout is too low
[13:21] <cjwatson> kyrofa: API> how do you mean?
[13:22] <kyrofa> cjwatson, can I request a snap to be built from a script after I push instead of having to login and do it?
[13:22] <kyrofa> (via the website)
[13:23] <cjwatson> kyrofa: absolutely - https://launchpad.net/+apidoc/devel.html#snap-requestBuild
[13:23] <kyrofa> cjwatson, yessss
[13:24] <kyrofa> cjwatson, nice work :)
[13:24] <cjwatson> we tend to do API first when it's reasonable to do so
[13:25] <cjwatson> auth tokens are supposed to live for 15 minutes after the build is dispatched
[13:26] <cjwatson> if the error was after that point, we may need to tweak the timeout; if it was before that point, something more complicated is wrong
[14:20] <chrisr_> I am strugglyng for several days now to upload a new cpp-ethereum package to https://launchpad.net/~ethereum/+archive/ubuntu/ethereum . A similar package works for another sub-ppa: https://launchpad.net/~ethereum/+archive/ubuntu/ethereum-dev
[14:20] <chrisr_> Now I uploaded the package manually https://gist.github.com/chriseth/2283063b62adaf687a7e5b47e0efe4d6 - but I neither see it on the website nor did I get a rejection mail
[14:21] <chrisr_> is it possible that the package is blocked from building?
[14:21] <chrisr_> (sorry, I don't have access to the main email address that is associated with that ppa)
[14:25] <dobey> was the source package signed with a key that is expired (or just not signed)?
[14:25] <chrisr_> the packages that are working and the ones that are not working use the same script just with different parameters
[14:25] <chrisr_> ah, but I might not have uploaded my key for the manual upload
[14:33] <chrisr_> For such an error, do I have to increment the version number?
[14:39] <dobey> no
[14:39] <dobey> because the packages wer enot uploaded
[14:44] <chrisr_> ok, uploaded with dput -f 10 minutes ago and still no email and nothing on https://launchpad.net/~ethereum/+archive/ubuntu/ethereum/+builds?build_text=&build_state=all (note the package is called cpp-ethereum) :-(
[14:51] <cjwatson> 2016-04-04 14:37:19 INFO    Failed to parse changes file '/srv/launchpad.net/ppa-queue/incoming/upload-ftp-20160404-143622-029858/~ethereum/ethereum/cpp-ethereum_1.2.3~trusty-0ubuntu4_source.changes': GPG verification of /srv/launchpad.ne
[14:51] <cjwatson> t/ppa-queue/incoming/upload-ftp-20160404-143622-029858/~ethereum/ethereum/cpp-ethereum_1.2.3~trusty-0ubuntu4_source.changes failed: Verification failed 3 times: ["(7, 9, u'No public key')", "(7, 9, u'No public key')", "(7, 9, u'No public
[14:51] <cjwatson> key')"]
[14:51] <cjwatson> are you sure you signed it, and that the key you signed it with is associated with your LP account?
[14:52] <cjwatson> may also be worth retrying given that you only uploaded the key today; it could have taken the keyserver a while to notice
[14:52] <cjwatson> is http://keyserver.ubuntu.com:11371/pks/lookup?fingerprint=on&op=index&search=0x3767635665B80533C6D94F09495C57E6E7A63463 the right key?
[14:54] <chrisr_> yes, it's the right key
[14:55] <chrisr_> "retrying" is "dput -f" or increment version suffix + dput?
[14:55] <chrisr_> I associated the key only afterwards, so that might very well be it
[14:55] <chrisr_> (though the original issue with our automation not being able to create packages is a different thing)
[14:58] <cjwatson> dput -f
[14:58] <cjwatson> dobey is right that you don't need to change the version number since the upload wasn't actually processed
[15:07] <chrisr_> still neither mail nor info on the ppa
[15:45] <Laney> http://archive.ubuntu.com/ubuntu/dists/xenial/main/i18n/ doesn't contain Translation-* for non-en but other releases do - bug?
[15:45] <mvo> hi, I wonder what happend to my upload of https://launchpad.net/ubuntu/+source/ddtp-translations/20160323.1 ?
[15:45] <Laney> ha
[15:45] <Laney> cjwatson: ^- fallout from recent work?
[15:46] <cjwatson> it's possible.  I don't have time to look today - could you file a bug?
[15:46] <Laney> okay
[15:47] <mvo> could you do that Laney? I'm still in a meeting, I would be very thankful
[15:47] <Laney> ok
[16:04]  * mvo hugs Laney
[18:29] <pouet12345> hello
[18:30] <pouet12345> is there debian packages for launchpad server ?
[18:30] <pouet12345> .deb
[18:30] <dobey> no
[18:31] <dobey> launchpad isn't really designed to be run externally from launchpad.net
[18:32] <pouet12345> is it opensource ?
[18:32] <pouet12345> dobey, ok so it's similar to github rules ?
[18:33] <pouet12345> only open source projects are free
[18:33] <pouet12345> in fact I am looking for something similar to github for my private use
[18:33] <pouet12345> on my machines
[18:35] <dobey> i don't know what rules you're talking about
[18:35] <dobey> launchpad the software is open source
[18:35] <dobey> it's simply not built to be run as a private instance (it's not really supported to do so)
[19:00] <exfalso> hi, first time ppa user. I'm trying to upload a package using dput. It successfully finished with `Successfully uploaded packages.`, exit code 0, however no email was sent and it didn't appear on launchpad. Then I realized I didn't add my gpg key. I did this now, verified it etc, but not sure how to proceed. dput now says `Package has already been uploaded to ppa on ppa.launchpad.net`, but it's not
[19:00] <wxl> hey i'm intending to deactivate https://launchpad.net/~lubuntu-qa/+mailinglist but how can i get the archives to save them?
[19:00] <exfalso> there
[19:02] <nacc> exfalso: you can force it, but it might complain that the version is not good, as lp tends to enforce that the versions change
[19:02] <nacc> exfalso: it's just seeing the .upload file in the cwd, iirc
[19:03] <exfalso> nacc: good stuff, i just removed the .upload and now it uploaded again
[19:08] <tgm4883> Shouldn't this have died after a timeout  https://launchpad.net/~mythbuntu/+archive/ubuntu/master-building/+build/9528998
[19:17] <dobey> exfalso: if you didn't get an e-mail, then most likely the source package was not signed, or was signed with a key that launchpad doesn't know about
[19:36] <cjwatson> tgm4883: there's a bug in the timeout handling that unfortunately some builds run into if they leave processes lying around after the build.  You should have a "cancel build" link
[19:36] <cjwatson> it's a known bug but quite hard to fix (requires migrating launchpad-buildd from sbuild's sudo mode to schroot mode)
[19:37] <tgm4883> cjwatson: ok thanks for the info. I just cancelled it, just wanted to verify it wasn't super weird I should be worried about
[19:37] <cjwatson> it is super weird but it is a piece of super weirdness we know about ;-)
[19:38] <cjwatson> and not just you
[22:42] <oparoz> Is there a good guide on setting up a git project on launchpad?
[22:53] <blr> hi oparoz, this is what we have currently https://help.launchpad.net/Code/Git
[22:54] <oparoz> Thanks blr. It doesn't work for me as git bash is not connecting. It keeps asking for my passphrase and then gives me a fatal: Could not read from remote repository
[22:55] <oparoz> blr Not sure if there is anything to do before being able to push or even fetch
[22:56] <blr> oparoz: do you have an ssh key associated with your user?
[22:57] <oparoz> blr, yes I do
[22:57] <oparoz> blr I have a .ssh/config with Host git.launchpad.net
[22:57] <oparoz> blr IdentityFile and User as well
[22:58] <blr> and you're pushing to git+ssh://git.launchpad.net/project-name?
[22:58] <oparoz> blr: I did a: $ git remote add launchpad git+ssh://git.launchpad.net/oc-snap
[22:59] <oparoz> blr and git fetch launchpad
[22:59] <blr> and `git push launchpad master` fails?
[23:00] <oparoz> blr. Yes, same problem after the 3 failed password, I get: Permission denied (publickey). fatal: Could not read from remote repository.
[23:00] <oparoz> blr, I'm on Windows btw..
[23:01] <blr> hmm okay, this is on msysgit?
[23:01] <oparoz> blr - Does the comment in the public key need to match something locally?
[23:02] <oparoz> blr: It's called git bash and using MINGW64
[23:03] <oparoz> blr: The same repo is pushing to Github
[23:04] <wgrant> oparoz: What happens if you enter the right password?
[23:04] <wgrant> Failing the key's password prompts won't get you very far.
[23:04] <oparoz> wgrant: The password is fine, it's just being refused by the remote server
[23:04] <wgrant> oparoz: git.launchpad.net's SSH server will never ask for a password.
[23:04] <wgrant> It only accepts key authentication.
[23:05] <wgrant> Any password prompt is a local thing.
[23:05] <oparoz> wgrant: What I mean is that it shoult be authenticated locally and pushing something to be validated on the server, which is not recognized
[23:05] <wgrant> But you say that the permission denied error from the server only occurs after three failed password attempts.
[23:06] <wgrant> Those password attempts must be to unlock the key; if you fail them all it's not going to work.
[23:06] <oparoz> wgrant: I can load the key in pageant per example, I'm being asked for a password and it's accepted the first time
[23:06] <oparoz> wgrant: Maybe it's a local problem with the password not being properly validated by git bash
[23:07] <wgrant> That seems most likely, unless your Launchpad username is misconfigured in your client.
[23:08] <oparoz> wgrant: It does have a hyphen, should that be escaped?
[23:12] <wgrant> oparoz: Shouldn't need to be.
[23:12] <wgrant> oparoz: What happens if you ssh -v olivier-interfasys@git.launchpad.net?
[23:14] <oparoz> wgrant: exact same thing
[23:14] <oparoz>  Authenticating to git.launchpad.net:22 as 'olivier-interfasys'
[23:14] <oparoz> Host 'git.launchpad.net' is known and matches the RSA host key.
[23:14] <oparoz> Authentications that can continue: publickey
[23:15] <oparoz>  Trying private key
[23:15] <oparoz> wgrant: must be local decoding
[23:16] <oparoz> wgrant: Maybe the key needs to be converted
[23:16] <oparoz> Nah, it would get rejected from the start
[23:17] <oparoz> wgrant: I should have generated the key using openssh...
[23:19] <oparoz> wgrant: Yeah, that was it...
[23:19] <oparoz> Thank you wgrant and lbr for your help
[23:19] <wgrant> oparoz: What was the problem?
[23:20] <oparoz> wgrant: I had forgotten, when I import server keys, they're in the OpenSSH format and work fine, but I followed the launchpad ssh keys guide for Windows
[23:21] <oparoz> wgrant: And it assumes people are going to use the putty suite only
[23:22] <oparoz> wgrant: But git bash and most dev tools will use ~/.ssh
[23:24] <wgrant> oparoz: Ah, right. Those instructions predate git support, so it possibly makes sense to revise them.
[23:26] <oparoz> wgrant: Yeah, a little addendum mentioning how to use those keys with software which don't use pageant
[23:28] <oparoz> wgrant: But it's disappointing that the error message wasn't clearer. It should detect that the format of the key is wrong. One app gave me a hint, but I didn't understand it. It said the aes256-cbc wasn't supported...
[23:29] <wgrant> Sounds like an OpenSSH problem.
[23:29] <oparoz> wgrant: Indeed
[23:32] <oparoz> But it's really cool to be able to build snaps fro Launchpad
[23:32] <ajmitch_> wgrant: LP is now rejecting dsa ssh keys now, right?
[23:35] <ajmitch_> either that or it's the client-side ssh configuration for me after upgrading to xenial
[23:42] <oparoz> Is there some information on the building infrastructure? I see "arm64 armel armhf (virtual)" and was wondering on what type of metal this was running
[23:45] <wgrant> oparoz: They're arm64 OpenStack instances on HPE Moonshot m400 cartridges.
[23:46] <cjwatson> ajmitch_: LP isn't, but xenial's OpenSSH client no longer sends them.  http://www.openssh.com/legacy.html
[23:47] <cjwatson> (LP possibly should)
[23:48] <ajmitch_> cjwatson: yeah, I'd noticed that it was no longer accepting them, I wasn't sure whether the LP key rejection was client-side or not
[23:48] <ajmitch_> I am finding it's not accepting ecdsa or ed25519 public keys though, haven't checked for an LP bug yet
[23:49] <cjwatson> ajmitch_: That's known; the libraries we use aren't up to the job yet.
[23:49] <ajmitch_> alright
[23:49] <cjwatson> RSA > DSA
[23:49] <oparoz> Thank you wgrant
[23:49] <cjwatson> So switch to 4096-bit RSA as a starting point
[23:51] <cjwatson> ajmitch_: (LP doesn't use a standard OpenSSH server or similar, because we need much more control over what users are allowed to do, how they're authenticated, etc.; some of our endpoints even implement custom SFTP filesystem namespaces.  So we use Twisted for that, but some of its crypto still needs some improvement.  https://bugs.launchpad.net/launchpad/+bug/907675)
[23:51] <ubot5`> Launchpad bug 907675 in Launchpad itself "Add support for ECDSA and Ed25519 SSH keys" [Low,Triaged]
[23:54] <ajmitch_> right, I'd known it was a custom ssh server, hopefully twisted can catch up