[00:13] <ari-tczew> there is a bug in LP accounts related to Ubuntu - ~ubuntu-devel-discuss-lists should be merged into ~ubuntu-dev
[00:17] <ovnicraft> hi folks, i want to know if there is any official support about multibranchs in lp?
[00:23] <wgrant> ovnicraft: multibranchs?
[00:32] <wgrant> CarlFK: No, you still have to upload individually.
[00:33] <CarlFK> wgrant: but someday, right? :)
[00:33] <wgrant> ari-tczew: That's probably a bit difficult at the moment. ~ubuntu-dev needs the ubuntu-reviews ML as its contact address.
[00:33] <wgrant> CarlFK: Maybe. What is your use case?
[00:33] <wgrant> CarlFK: For the common daily builds case, the source package recipes beta may be of interest.
[00:34] <ari-tczew> wgrant: is it possible to fix? we shouldn't supply packages with non-existing maintainer
[00:34] <CarlFK> wgrant: not having to maintain multiple configs
[00:34] <wgrant> ari-tczew: That affects nothing, though.
[00:34] <wgrant> CarlFK: For what?
[00:34] <CarlFK> wgrant: some python code i wrote
[00:35] <wgrant> CarlFK: But releases? Daily builds?
[00:35] <CarlFK> just releases
[00:35] <wgrant> Since it's Python, have you considered just uploading to the lowest series then copying up?
[00:35] <wgrant> That often works for Python things.
[00:36] <CarlFK> copying up?
[00:36] <wgrant> CarlFK: Upload to, say, Hardy, then copy the binaries to Karmic/Lucid/Maverick.
[00:37] <wgrant> CarlFK: In a lot of cases that will work.
[00:37] <CarlFK> cool
[00:58] <ia> hello. I've clashed with some strange problem in [my] PPA - i can't download orig.tar.gz [via web interface]. dsc, deb and diff.gz files available for download, but when I try to download orig.tar.gz, I've got error page (ID OOPS-1772N73, for example). I will be appreciate for any clues about this problem. Thanks.
[01:00] <wgrant> ia: That's probably bug #522800. Can you 'apt-get source' the package instead?
[01:09] <ia> wgrant: thanks for answer, looks like that bug this is it, but 'apt-get source' tells that "Unable to find a source package".
[01:14] <wgrant> ia: Which PPA, and which package?
[01:20] <ia> wgrant: here - https://launchpad.net/~iaz/+archive/battery-status/+packages (the same one orig.tar.gz for lucid and karmic)
[01:24] <wgrant> ia: http://launchpadlibrarian.net/49107169/battery-status_0.1.1.orig.tar.gz
[01:37] <ia> wgrant: thanks a lot for such operative help! But could you tell me, please, does exist some way to figure out this magic number (49107169) in link for some other tarball in the other PPA? (just in case if i've clashed with this problem again)
[01:39] <wgrant> ia: I found the SHA1 of the orig.tar.gz in the dsc, and searched for it at http://launchpadlibrarian.net/search?digest=78fbe780eb8ae349a524399517681579ce34bc3e
[01:41] <ia> wgrant: great advice. Thanks again!
[02:01] <lamont> wgrant: that's crazy
[02:03] <wgrant> lamont: Howso?
[02:08] <lamont> searching by digest.  crazy in a totally cool way
[02:09] <wgrant> Ah, yes.
[02:09] <wgrant> It can be handy.
[02:09] <wgrant> (I used it to grab buildd chroots for a while, but then I exported the URL directly)
[02:13] <lamont> ah.  I just cheat and use manage-chroot.py to get the chroot tarball.
[02:13] <lamont> or build a fresh one
[02:13] <wgrant> Yeah, not really an option for me.
[10:58] <Zanko> hi
[10:59] <Zanko> i would like some help putting stuff on my ppa
[10:59] <Zanko> that's first time i use ppa so i'm not sure what i did wrong
[11:00] <Zanko> anyway here is the problem : i uploaded package with dput specifying the ppa name, it seemed to work
[11:00] <Zanko> but i have nothing on the ppa page
[11:01] <wgrant> Zanko: Was your changes file signed by a key associated with your Launchpad profile.
[11:01] <Zanko> i verified that changes file is signed with a key that launchpad know about
[11:01] <Zanko> yes
[11:02] <wgrant> What's your Launchpad username? Can you pastebin your changes file?
[11:02] <Zanko> my username is zanko
[11:03] <Zanko> and here is the changes file : http://pastebin.com/Sj1qmMzc
[11:04] <wgrant> gpg: Signature made Sun 07 Nov 2010 12:16:46 EST using RSA key ID 6E898547
[11:04] <wgrant> gpg: Can't check signature: public key not found
[11:05] <wgrant> The Internet does not know about that key.
[11:06] <Zanko> but this is the key associated with my launchpad profile
[11:06] <wgrant> No, that's 313297AB
[11:07] <Zanko> true
[11:07] <Zanko> i don't understand, where debuild get his key ?
[11:07] <Zanko> i only have one key in seahorse
[11:08] <wgrant> What does 'gpg --list-secret-keys' say?
[11:09] <Zanko> it has a line mentionning the bad key (ssb   4096R/6E898547 2009-09-22)
[11:10] <wgrant> Is it under the main 313297AB key?
[11:11] <wgrant> I wonder if you have a new subkey that you haven't pushed.
[11:12] <Zanko> yes it is
[11:12] <wgrant> Do you recall creating that subkey?
[11:12] <wgrant> It's some 2.5 years newer.
[11:12] <Zanko> not sure
[11:13] <Zanko> so if i update the key on my profile it will be ok or do i need to reupload package after ?
[11:14] <wgrant> Push the key up (gpg --keyserver keyserver.ubuntu.com --send-key 313297AB), and tell me when that's done.
[11:14] <wgrant> I'll check that it's correct, and then you can upload the package again.
[11:15] <Zanko> done
[11:15] <wgrant> Hm, that's not it. Can you pastebin the output of 'gpg --list-secret-keys'?
[11:17] <Zanko> http://pastebin.com/iAv9nbRr
[11:17] <wgrant> Ah.
[11:17] <wgrant> I wonder if there's a cache in the way.
[11:20] <geser> the LP keyserver knows the new subkey now
[11:21] <wgrant> Not for me. The proxy must hate me.
[11:21] <geser> http://keyserver.ubuntu.com:11371/pks/lookup?search=0x3B0AD97C13C1439B4C0EA8648A6E3375313297AB&op=vindex lists it
[11:21] <wgrant> Ah, requesting it directly works.
[11:21] <geser> didn't tried to fetch it myself yet
[11:21] <wgrant> Zanko: Upload your package again.
[11:21] <wgrant> It should work this time.
[11:23] <Zanko> done
[11:24] <wgrant> It should hopefully appear in a minute or so.
[11:24] <Zanko> ok
[11:24] <Zanko> thanks a lot !
[11:24] <wgrant> Multiple subkeys always confuse things :(
[11:24]  * Zanko refresh the ppa page every second
[11:25] <wgrant> Upload are only processed every 5 minutes :)
[11:25] <geser> Zanko: you should get a mail when it got accepted
[11:25] <Zanko> ok
[11:25] <wgrant> Odd that it's not there.
[11:25] <wgrant> Check your inbox.
[11:26] <Zanko> crap
[11:26] <Zanko> Rejected:
[11:26] <Zanko> Unable to find distroseries: unstable
[11:26] <Zanko> Further error processing not possible because of a critical previous error.
[11:26] <wgrant> Zanko: debian/changelog is wrong.
[11:26] <wgrant> It needs to specify your target Ubuntu series (eg. 'maverick'), not 'unstable' (which is a Debian series).
[11:27] <Zanko> so i have to do a package per-distro, even if the same package works on multiple distros ?
[11:28] <wgrant> Do the same binaries work on multiple?
[11:28] <wgrant> Each source package can build in at most one series.
[11:28] <Zanko> yes (and no binaries, only python)
[11:28] <wgrant> But if the binaries work across multiple series, then you can copy.
[11:28] <wgrant> So I'd upload to the lowest series, and then copy the binaries up.
[11:28] <wgrant> Right, but you still have binary packages.
[11:29] <wgrant> They just don't contain any real binaries.
[11:32] <Zanko> hopefully it works this time
[11:35] <wgrant> 'twould appear not.
[11:44] <Zanko> Rejected:
[11:44] <Zanko> Source/binary (i.e. mixed) uploads are not allowed.
[11:44] <wgrant> You need to give debuild the '-S' flag.
[11:51] <Zanko> Accepted !
[11:52] <Zanko> thanks for your help folks !
[11:59] <wgrant> Excellent.
[13:01] <Dominic> hi all.  On a branch that's already in merge review, I've committed without my e-mail address set in bzr whoami.  Will lp be happy if I uncommit a few times, then recommit and push back to the branch (presumably with --overwrite)?
[13:02] <wgrant> Dominic: The revisions will show up *after* any existing comments on the MP, but yes, it should be fine.
[13:02] <Dominic> wgrant: great, thank you
[13:09] <Zanko> if i install packages from my ppa, it says they're "non authentified" while my key has correctly been obtained by add-apt-repository, why is that ?
[13:10] <wgrant> Zanko: I suspect that it took a while to generate the key, so the initial packages weren't signed. When you next upload or copy something, it should all be signed.
[13:10] <Zanko> ok, thx
[13:13] <Zanko> also, even if it's not really launchpad related, do you know how to tell debuild to ignore bzr stuff ? I tried to add -i as suggested on lintian doc, but it is still complaining that "diff-contains-bzr-control-dir"
[13:14] <wgrant> Zanko: -i excludes .bzr and co. from the .diff.gz. But you've built a native package, which doesn't have a .diff.gz.
[13:14] <wgrant> Is that deliberate?
[13:14] <wgrant> (there's no orig.tar.gz)
[13:18] <Zanko> that's not deliberate, (i'm discovering debian packaging and don't really know about all its subtleties yet)
[13:23] <Zanko> after reading some doc it seems i should switch to a non-native package
[17:27] <psusi> I'm getting an invalid stacked location error but the branch seems to work anyhow, what's the deal?  https://code.launchpad.net/~psusi/ubuntu/natty/parted/drop-dmraid-regression-patch
[19:29] <psusi> I'm getting an invalid stacked location error but the branch seems to work anyhow, what's the deal?  https://code.launchpad.net/~psusi/ubuntu/natty/parted/drop-dmraid-regression-patch
[20:03] <ProfNoel>  /j #facil
[20:03] <ProfNoel> oups sorry
[20:04] <ProfNoel> sound like spam, just make an extra space
[21:02] <thumper> psusi: did you manually stack it?
[21:05] <psusi> thumper, if you mean I had to add --stacked when pushing, yes
[21:05] <psusi> was't sure why I had to do that either
[21:05]  * thumper thinks
[21:05] <psusi> since I just pulled from the main branch, made a small change, then pushed to my personal branch... last time I did that it auto stacked
[21:06] <psusi> but this time it started uploading everything so I aborted, deleted the branch on lp, then did it again with --stacked
[21:06] <thumper> hmm...
[21:06] <thumper> it should autostack...
[21:06] <thumper> if it isn't, it's a bug
[21:06] <psusi> and the lp branch pages seems to correctly show all of the history, so it MUST be pulling from the stack
[21:07] <psusi> right?
[21:07] <psusi> so that error doesn't make sense
[21:07] <thumper> psusi: the reason it gives that error on the screen is that "officially" what you've stacked on isn't supported, and in fact didn't exist when we wrote that bit
[21:07] <thumper> but it is valid from the client side
[21:07] <thumper> so the client is happy
[21:07] <thumper> and the scanner is happy (ish)
[21:08] <thumper> but the bit of code that determins the stacked on branch isn't
[21:08] <thumper> so that bit is a bug
[21:08]  * thumper needs to relocate, so will be offline for a bit
[21:09] <psusi> I was wondering why the %2B is in there...