[05:43] I try to upload a cinder package to my ppa (with the exact same orig.tar.gz file, sha1sums are equal in .dsc and from my file) but the upload is rejected. [05:43] error is: File cinder_2013.1.3.orig.tar.gz already exists in Primary Archive for Ubuntu [05:44] toabctl: Where did you get that orig.tar.gz? [05:44] It's not the one that Ubuntu has. [05:44] And they have to match. [05:44] wgrant: I guess I uploaded the first version to the archive [05:44] wgrant: and after that, ubuntu uploaded another version to the archive [05:45] wgrant: I used the same version I used for my previous package (https://launchpad.net/~telekomcloud/+archive/eisbrecher/+files/cinder_2013.1.3.orig.tar.gz) [05:45] 2bfeacfaea7be5194587bb932dd8f693 is the correct MD5 hash [05:46] wgrant: and where can I get the orig tarball? [05:46] btw: the upstream release tarball from https://github.com/openstack/cinder/archive/2013.1.3.tar.gz has another md5 [05:47] toabctl: https://launchpad.net/ubuntu/+archive/primary/+files/cinder_2013.1.3.orig.tar.gz [05:47] toabctl: I think that github link is just a tarball of a tag from their git repository. [05:47] Not actually a release tarball. [05:47] https://launchpad.net/cinder/grizzly/2013.1.3 is the official release tarball. [05:50] I'm not sure if GitHub supports actual release tarballs any more. [05:50] wgrant: but the md5sum of this tarball is also different [05:51] oh no. it isn't. sorry [05:52] The Ubuntu tarball matches the official release tarball AFAICT. [06:02] wgrant: works now. thanks for the help! [06:03] toabctl: Excellent, np [07:04] aloha [07:05] Morning czajkowski [07:07] wgrant: howdy doody [08:41] if I delete a package from the ppa, is the orig.tar.gz tarball also deleted? [08:50] toabctl: A record of it is kept. You won't be able to upload a different file with the same name and version even if the old one has been deleted. [08:56] wgrant: hm. so I have to repack the orig.tar.gz tarball? [08:57] toabctl: If you want to upload a different file it needs to have a different name. [09:23] LP seems to be asking me for re-authentication quite a lot. [09:28] also, it seems that it delays an awfully long time when receiving a non-authorized public key? [09:29] time is relative? [09:29] lifeless: well, yes. [09:29] lifeless: but I don't see how that's relevant. [09:30] jml: perhaps a metric on 'awfully long time' would help e.g. wgrant assess whether there is an operational problem or business as usual. [09:30] oh. [09:30] it times out. [09:30] jml: vs you having expectations out of sync with reality ;) [09:30] jml: ah! W/ OOPS or not ? [09:30] sans oops [09:31] IIRC and the infra hasn't been changed too much that implies an haproxy timeout and lp still off in lala land. [09:31] that could be caused by something being stubborn and not honouring timeouts [09:31] interestingly, it's on offering an RSA-CERT public key [09:31] jml: gpg or ssh ? [09:31] a different RSA public key is rejected quickly [09:31] lifeless: sshg [09:33] jml: I haven't heard of RSA-CERT ? [09:33] hmm. [09:33] OK. I don't think I fully understand SSH. [09:34] running ssh-add fixed this. :\ [09:34] jml: oh, did you mean on bzr+ssh w/bazaar.launchpad.net ? [09:35] lifeless: well, ultimately yes, but I stopped using bzr and switched to openssh directly when I realized I was having problems. [09:35] jml: I thought you were talking about updating the keys in the webapp === frankban__ is now known as frankban [10:09] jml: Similar problem to last time? [10:09] yeah, so it seems. [10:09] in fact, it might have been identical. [10:09] jml: Regarding reauthentication, you need to reauthenticate (or re-2FA, if you use 2FA) with the webapp to edit your SSH keys, GPG keys, or email addresses if you haven't authed in the last 5 minutes. [10:10] I think it's 5 [10:10] Maybe 2 [10:10] 2 seems more correct [10:10] it seems like a lot. [10:10] Yeah, I think it's two, because I remember complaining that it was unreasonable. === Mission-Critical is now known as MissionCritical === frankban__ is now known as frankban [13:20] wgrant: hey, got a question about PPA/space ... right now we have kde frameworks 5 dailys at https://launchpad.net/~neon/+archive/kf5/+packages however since the codebase is rapidly changing there's always transitional build and binary issues so I wanted to check if you are ok with us introducing two additional ppas where we would copy binaries after smoke testing (daily snapshot and weekly snapshot). each would need at least 5 gib space as of [13:20] right now. [13:22] apachelogger: That's fine. Link me to them and I can bump their quotas immediately. [13:29] * czajkowski peers at wgrant [13:34] wgrant: cool. looking at the numbers I think going to 10 GiB would be best just in case, 5 would be good for at least a month though ;) https://launchpad.net/~neon/+archive/kf5-snapshot-daily https://launchpad.net/~neon/+archive/kf5-snapshot-weekly [13:36] apachelogger: Done [13:37] wgrant: cheers [14:47] Hi everyone, I'm a launchpad translator who would like to ask you if you have any ideas concerning a problem we're dealing with in our language [14:48] It's a minority language with 2 qualified translators, but we have a third translator delivering bad translations and we have been unable to stop him from joinint language teams [14:49] Is there any way of stopping him short of having to join/create a language team for every launchpad project under the sun? [14:49] We have asked him to stop, but he won't listen :( [14:50] Any ideas will be appreciated :) [14:57] GunChleoc: ask a question at https://answers.launchpad.net/launchpad and provide all the details about the abuse. [14:58] K will do :) [15:17] need help sorting out a private-ppa-key issue, can't obtain access to this private ppa although I'm a member of a team with access https://launchpad.net/~product-strategy-coverity === frankban_ is now known as frankban [15:30] nm got it thanks all :) === frankban_ is now known as frankban === lifeless_ is now known as lifeless === cprov is now known as cprov-afk