[00:13] <fbond> Can anyone remove a package from my PPA for me?
[00:14] <fbond> I made a versioning error and I need to wipe out the old version of a package to correct it.
[00:15] <Fujitsu> fbond: Please ask a question on the launchpad project.
[00:15] <fbond> Fujitsu: will do.
[04:27] <jamesh> PPAs are pretty cool unless you get stuck behind the ubuntu-langpack builds
[04:28] <Hobbsee> heh :)
[04:28] <Hobbsee> jamesh: nothing you can do about them either, unless you have root access to those buildds.
[04:29] <jamesh> I've just been playing round with packaging a newer version of bzr-pqm
[04:31]  * Hobbsee wasn't aware that that was public.
[04:31] <jamesh> Hobbsee: bzr-pqm is just a plugin to submit PQM messages
[04:32] <jamesh> an old version of it is even packaged in Ubuntu
[04:32] <Hobbsee> ahh
[04:32] <jamesh> the actual PQM server software is available at https://launchpad.net/pqm
[04:32] <spiv> Both bzr-pqm and PQM have always been public.
[04:32] <jamesh> I don't know if that is packaged, since it is a pain to set up
[04:34] <Hobbsee> neat!
[05:09] <Hobbsee> jamesh: it appears you're in luck.  this appears to be the last lot of langpacks
[05:09] <Hobbsee> as in, the 3 building now
[05:37] <poolie> is there a shortcut url for ~me?
[05:37] <poolie> i thought it was launchpad.net/+me but that doesn't work
[05:38] <Fujitsu> poolie: /people/+me
[06:35] <poolie> thanks
[06:35]  * poolie tries a PPA upload
[06:35] <poolie> how exciting
[06:38] <Fujitsu> Have you activated it yet? I can't see it, though LP might be hiding it from me because it has no uploads.
[06:43] <poolie> woot
[06:43] <poolie> https://edge.launchpad.net/~bzr/+archive
[06:50] <poolie> so to get a package built for multiple ubuntu versions
[06:50] <poolie> do i need to upload several times?
[07:00] <Fujitsu> poolie: Correct. With different version numbers.
[07:00] <Fujitsu> Appending ~gutsy1, ~feisty1, etc. is the norm.
[07:01] <poolie> lifeless says those should be omitted
[07:01] <Fujitsu> I say they shouldn't be.
[07:01] <Fujitsu> The packages share the same pool, so the versions must be different.
[07:03] <Fujitsu> Also, why is it a native package?
[07:05] <poolie> it's not, or at least it's not meant to be ?
[07:05] <lifeless> shouldn't be
[07:05] <lifeless> oh, if PPA has one pool then yes you need different qualifiers.
[07:05] <lifeless> Yet another reason not to use PPA :(. I hope they get this fixed soon.
[07:06] <Fujitsu> It is, but shouldn't be. You need the .orig.tar.gz in the parent directory, and to have a hyphen somewhere in the version.
[07:06] <Fujitsu> This is intended behaviour.
[07:06] <Fujitsu> I wouldn't call it a bug.
[07:06] <lifeless> Fujitsu: thats ok, I'll do that.
[07:06] <Fujitsu> Allowing the same version in multiple distroseries is evil.
[07:06] <Fujitsu> (unless they're inherited from lower ones)
[07:06] <poolie> oh, i see, it's the missing hyphen
[07:07] <poolie> so what would be a better name? 1.0-1bazaar1?
[07:07] <Fujitsu> 1.0-1~bazaar1
[07:07] <poolie> ok
[07:07] <lifeless> Fujitsu: if you have distro contents files it's functional but ugly to require the person requesting the build to manage the set of target distros. Bad UI.
[07:08] <lifeless> poolie: if you are reusing my packaging you want 1.0-1~bazaar1~gutsy1
[07:08] <lifeless> erm
[07:08] <Fujitsu> lifeless: Different distros have different build environments. There's no other way to do it.
[07:08] <lifeless> 1.0-1~bazaar1gutsy1
[07:08] <lifeless> etc
[07:08]  * Fujitsu would use ~bazaar1~gutsy1
[07:08] <poolie> 1.0-1~bazaar1-gutsy1
[07:08] <lifeless> Fujitsu: Consider it a challenge not something to lay down the law on
[07:08] <lifeless> poolie: no -
[07:09] <lifeless> Fujitsu: gutsy isn't before baazaar. only one ~
[07:09] <poolie> because the digits implicitly separate parts
[07:09] <poolie> ?
[07:09] <Fujitsu> lifeless: I would normally upload 1.0-1~bazaar1 to Hardy, then 1.0-1~bazaar1~gutsy1 to Gutsy, etc.
[07:09] <Fujitsu> It's how backports are done, and consistency is good.
[07:10] <lifeless> poolie: also, I wouldn't suggest sorting below debian/ubuntu builds
[07:10] <lifeless> poolie: because you're wanting to override, not underride
[07:10]  * Fujitsu would definitely advise sorting below them.
[07:10] <lifeless> Fujitsu: is today your 'disagree with everything' day?
[07:10] <Fujitsu> Isn't the purpose to just backport 1.0 to previous releases?
[07:10] <lifeless> no
[07:10] <lifeless> or at least it hasn't been for the last X period.
[07:10] <lifeless> sigh, I've been sucked into work.
[07:11] <lifeless> BYE
[07:11] <poolie> i want to be above eg 0.91, but below the "official" 1.0
[07:11] <poolie> bye!
[07:11] <Fujitsu> That's what I thought you were trying to do, right.
[07:13] <Fujitsu> So 1.0-1~bazaar1~gutsy1, with the use of the second tilde being debatable.
[07:25] <ubotu> New bug: #177087 in soyuz "+archive has headings mixed up" [Undecided,New] https://launchpad.net/bugs/177087
[07:26] <jamesh> Fujitsu: is there any reason for using Ubuntu release codenames rather than version numbers?
[07:27] <jamesh> Fujitsu: since that makes 1.0-1~bazaar1~gutsy1 older than 1.0-1~bazaar1~warty1, which seems wrong
[07:28] <jamesh> (not that people are going to be building new warty packages, but the point still stands)
[07:37] <poolie> otoh that's a good reason for ubuntu to stick to alpha numbers
[07:37] <poolie> leaving open the issue of what happens after the zesty zebra
[08:56] <peepo> anyone about?
[08:56] <peepo> I filed various inkscape bugs as "peepo"
[08:56] <peepo> but launchpad doesn't recognise my email address
[08:57] <peepo> is that 'normal'
[08:57] <peepo> ie do I need separate accounts, to file and review bugs?
[09:00] <peepo> hello?
[09:00] <peepo> there's no wfm so what's next best?
[09:00] <BjornT> peepo: you have to activate your account in launchpad
[09:00] <BjornT> peepo: if you go to https://edge.launchpad.net/~peepo/, you'll see there's a "Hey, I'm Peepo" link
[09:00] <peepo> later
[09:00] <peepo> https://bugs.launchpad.net/inkscape/+bug/165804
[09:00] <ubotu> Launchpad bug 165804 in inkscape "GTK-quartzvm detached toolbar stay on top even when inactive" [Low,Incomplete]  - Assigned to Mjwybrow (mjwybrow)
[09:40] <ubotu> New bug: #177108 in malone "Bug pages do not show project/distro logo any more" [Undecided,New] https://launchpad.net/bugs/177108
[10:30] <Fujitsu> jamesh: I didn't define the standard. It has been used by backports for a number of years. Besides, releases are in alphabetical order since Breezy, and will remain so.
[10:30] <jamesh> Fujitsu: ... until Z
[10:31] <jamesh> as poolie said
[10:31] <Fujitsu> jamesh: True. Which is a while off.
[10:32] <jamesh> Fujitsu: it seems stupid to rely on a convention that will eventually break, and we haven't even consistently followed in the past
[10:32] <Fujitsu> Right. (though it's not so much not following it as it didn't exist)
[10:32] <jamesh> especially when there is an alternative that has been consistently followed and won't break (i.e. that Ubuntu's version number will always increase)
[10:32] <Fujitsu> I'm not sure why version numbers aren't used, and it seems strange not to.
[10:32] <Fujitsu> Right.
[10:41] <ubotu> New bug: #177119 in malone "checkwatches fails trying to updated a conjoined bugtask" [High,Confirmed] https://launchpad.net/bugs/177119
[10:41]  * Fujitsu wonders where one would have a conjoined task with a watch.
[10:42] <Fujitsu> Ah, so it shouldn't be allowed. I see.
[10:46] <kiko> yeah, it's a bug
[10:46] <kiko> as usual :)
[11:20] <ubotu> New bug: #177125 in malone "update-manager crashes" [Undecided,New] https://launchpad.net/bugs/177125
[11:35] <ubotu> New bug: #177131 in launchpad "No way to delete or remove a release" [Undecided,New] https://launchpad.net/bugs/177131
[11:36] <frenchy> Re 177131: Oh, I hear that!
[11:39] <frenchy> Why don't we show a list of current bugs when we click on the bugs tab?  It seems inconsistent with the rest of the site.
[11:40]  * Fujitsu likes the way sourcepackages work (ie. like that, without the graph etc.)
[12:02] <frenchy> Don't get me wrong, I like the graph, it could go above "Key contacts".
[12:02]  * Fujitsu thought the graph was going away soon anyway.
[13:05] <Hobbsee> kiko: ping
[13:07] <mtaylor> funny, I was just going to also say kiko: ping
[13:08] <kiko> mtaylor, Hobbsee: oink
[13:09] <Hobbsee> kiko: would have thoguht that with using ppa as a component name...commercial partners may not like it, for the private repositories.
[13:09] <Hobbsee> no idea how public you wan't that
[13:10] <Hobbsee> (or discussions about it)
[13:22] <mtaylor> kiko, Hobbsee: ppa in the component name doesn't bother me so much...
[13:22] <kiko> me neither
[13:22] <mtaylor> could also stand for "private package archive" :)
[13:22] <kiko> nor do I think it'd bother commercial partners
[13:22] <kiko> but we'll need to investigate that further
[13:22] <kiko> it has some unwanted soyuz consequences
[13:23] <mtaylor> kiko: so did the things in that other mail all sound doable? 
[13:23] <mtaylor> and/or make sense?
[13:23] <kiko> mtaylor, the one with a large number of concerns?
[13:23] <mtaylor> yes
[13:23] <kiko> I didn't read that one :) I just read the reply
[13:23] <mtaylor> hehe
[13:23] <mtaylor> it's too long
[13:23] <mtaylor> I think I started to ramble
[13:23] <kiko> yeah. but somebody else should read it -- bigjools or cprov-out 
[13:23] <kiko> and if not holler
[13:24] <mtaylor> kiko: statik told me I should get you to comment on it
[13:24] <mtaylor> kiko: wait. perhaps we're talking about different mails
[13:26]  * Hobbsee notes that the docs could really do with a rewrite, now that the target audience has changed.
[13:27] <mtaylor> kiko: I was talking about the email in the "Re: Monty in Brazil and PPAs" thread
[13:28] <Hobbsee> mtaylor: oh, that one.
[13:29] <kiko> mtaylor, oh! I think that's all doable
[13:29] <mtaylor> kiko: ok - great! :) 
[13:29] <kiko> we are talking about different emails.
[13:30] <mtaylor> it started to seem that way
[13:30] <kiko> it does require some rather minor engineering work on our end -- the debian import in particular
[13:30] <kiko> but we have wanted to do that anyway, so having some pressure on it would be good.
[13:30] <mtaylor> glad I can help, then 
[13:31] <mtaylor> anything else you'd like me to add to the list of things we need? 
[13:31] <kiko> hah! not right now -- this has been a busy december as it is
[13:32] <mtaylor> good. well I'm going to chat this week with statik and the businessy folks on my side hopefully and see what we can get worked out
[13:32] <Hobbsee> FWIW, i gave mrevell a list of questions that would be good to answer in a ppa faw
[13:32] <kiko> mtaylor, okay, am very much looking forward to that.
[13:32] <Hobbsee> er, faq
[13:32] <Hobbsee> no idea if you guys will find it useful.
[13:32] <kiko> Hobbsee, you did? I'll see that julian and cprov look at it and make it happen
[13:33] <Hobbsee> kiko: cool, although i suspect it'll be mroe useful for someone to write who *doesn't* know soyuz inside out, and who is more of a new person looking in
[13:34] <bigjools> well give me a chance to do it and then you can decide that
[13:34] <Hobbsee> bigjools: by all means.
[13:35] <bigjools> cool
[13:35] <Hobbsee> bigjools: http://rafb.net/p/9eO3Kc15.html was the list.
[13:35]  * Hobbsee can email it, etc
[13:35] <bigjools> I got it, thanks
[13:36] <kiko> good ole rafb
[13:37] <Hobbsee> looks like there's the ppa documentation thread with a few more bits in it, too
[14:00] <ubotu> New bug: #177162 in loggerhead "codebrowse doesn't show content of added files on revision page" [Undecided,New] https://launchpad.net/bugs/177162
[15:13] <MvG> Hi! There is a bug in the inkscape bug database on launchpad, which was written by me ages ago. However the system doesn't seem to have an account for me, at least for any of the mail addresses I usually use. Were the inkscape bugs migrated from somewhere else? If so, what happened to accounts?
[15:15] <ubotu> New bug: #177167 in launchpad "Incorrect email subject when user joins an open team" [Undecided,New] https://launchpad.net/bugs/177167
[15:23] <radix> MvG: I suggest reading the paragraph at https://edge.launchpad.net/people and probably clicking the link in it
[15:23] <radix> hmm, actually
[15:23] <radix> if you don't already have another account...
[15:23] <radix> there's probably a way to claim an account without creating a separate one
[15:24] <radix> MvG: actually, I bet if you try to register with the email address that they already have for you it'll ask if you want to claim the account
[15:25] <MvG> radix: OK, I had a closer look at the last mail I got from the system, and found it was sent to my sourceforge mail address. With that I could claim the account. Thanks.
[15:26] <radix> MvG: I'm not a LP dev, so these are mostly guesses :)
[16:23] <MattCampbell> If I initially pushed a branch to LP using bzr+ssh using bzr 1.0rc3, is there any risk of braking it if I then bind to it using sftp, again running bzr 1.0rc3, and commit that way?
[16:23] <MattCampbell> keeping in mind that LP is running bzr 0.92
[16:37] <MattCampbell> It should be documented somewhere that bzr 1.0 users need to use sftp, not bzr+ssh, to commit to bzr branches at LP.
[16:38] <mwhudson> launchpad will be running 1.0 by, uh, tomorrow i think
[16:38] <MattCampbell> Cool, thanks.
[16:38] <MattCampbell> the joys of being an early adopter :)
[16:41] <mwhudson> yar
[16:55] <ubotu> New bug: #177188 in malone "+editstatus doe not check that the bug was converted into a question" [High,In progress] https://launchpad.net/bugs/177188
[18:14] <jonasbjork> hi ppl!
[18:14] <jonasbjork> i am trying to import a cvs-repo into launchpad
[18:14] <jonasbjork> no sucess at all
[18:14] <jonasbjork> cvs-repo: :pserver:anonymous@cvs.fritis.berlios.de:/cvsroot/fritis
[18:15] <mwhudson> jonasbjork: what project/series?
[18:15] <mwhudson> jonasbjork: oh, https://edge.launchpad.net/pyrisk/java-deprecated right?
[18:15] <jonasbjork> mwhudson: no?
[18:16] <mwhudson> oops
[18:16] <jonasbjork> or, well that seems to be kind of what i want
[18:16] <jonasbjork> but for another project ;)
[18:16] <mwhudson> pretend i didn't mention that project
[18:16] <mwhudson> jonasbjork: which?
[18:16] <jonasbjork> that you linked to
[18:16] <mwhudson> jonasbjork: i am a vcs-imports operator
[18:16] <jonasbjork> seems to be a cvs imported project
[18:16] <mwhudson> jonasbjork: tell me which project you are trying to set up an import for
[18:16] <jonasbjork> cvs-repo: :pserver:anonymous@cvs.fritis.berlios.de:/cvsroot/fritis
[18:17] <jonasbjork> my launchpad project is "Fritis"
[18:18] <mwhudson> jonasbjork: you need to enter the details on https://edge.launchpad.net/fritis/trunk/+source
[18:19] <jonasbjork> ok found it
[18:20] <jonasbjork> may i ask, can i import the cvs-code and start use bazaar instead of berlios-cvs?
[18:21] <kiko-phone> yes!
[18:22] <mwhudson> jonasbjork: that's the idea :)
[18:23] <jonasbjork> as far as i understand my project will be mirrored from berlios
[18:23] <mwhudson> yes
[18:23] <jonasbjork> but launchpad makes an own repository for it and i can work with that?
[18:23] <jonasbjork> i'm a total newbie at this as you might understand ;)
[18:24] <mwhudson> what you say is true, though not necessarily a helpful way of saying things
[18:24] <mwhudson> jonasbjork: have you used bazaar at all?
[18:24] <jonasbjork> mwhudson: nope, i'm a cvs/svn guy
[18:25] <jonasbjork> read some tutorial that explained how to use bazaar
[18:25] <jonasbjork> bzr command that is
[18:25] <mwhudson> so yes, launchpad makes its own repository containing a mirror of the cvs repository
[18:26] <mwhudson> then you will get a copy of this repository and can commit to it, pull in changes from the cvs mirror, push it to launchpad etc
[18:26] <mwhudson> so you use launchpad's repository as a data source, but you won't be writing to it
[18:27] <jonasbjork> ok, so i still commit to cvs.berlios.de ?
[18:27] <mwhudson> uh
[18:27] <mwhudson> maybe
[18:27] <mwhudson> depends what you're trying to achieve
[18:27] <radix> you *can* still commit to the CVS server, and the launchpad mirror will be updated regularly
[18:28] <radix> or, you can make branches from the LP mirror and use bzr to do your work.
[18:28] <kiko-phone> if you want to migrate and then abandon berlios
[18:28] <kiko-phone> then mwhudson can help you more. :)
[18:28] <jonasbjork> but i should start using my bazaar repo when it is imported from cvs?
[18:28] <jonasbjork> ok, think i get it now
[18:29] <jonasbjork> i'll just wait for my repo to be imported and try then 
[18:30] <mwhudson> jonasbjork: i've started the import
[18:30] <mwhudson> it can take anything from a few minutes to several days
[18:30] <jonasbjork> ok
[18:30] <jonasbjork> Import status:  Processing
[18:30] <jonasbjork> it changed ! :)
[18:30] <jonasbjork> mwhudson: thanks for your help
[18:30] <mwhudson> jonasbjork: np
[19:04] <bdmurray> I'm looking at the upstream watch for bug 84603 and it seems to be out of sync
[19:04] <ubotu> Launchpad bug 84603 in linux "Hard disk I/O randomly freezes when hald is running and optical drive is empty" [Unknown,Confirmed] https://launchpad.net/bugs/84603
[19:05] <bdmurray> Any malone people around?
[19:42] <mwhudson> jonasbjork: your import is failing in a mysterious (to me) way
[19:43] <mwhudson> jonasbjork: i'll have to look at it tomorrow
[19:51] <ubotu> New bug: #177230 in malone "upstream bug watch for bug 84603 is incorrect" [Undecided,New] https://launchpad.net/bugs/177230
[19:51] <ubotu> New bug: #177232 in malone "linux-source-2.6.24 package shouldn't allow bug reports" [Undecided,New] https://launchpad.net/bugs/177232
[19:53] <jonasbjork> mwhudson: ok, thanks for beeing helpful
[20:39] <JordanC> Hey folks
[20:39] <JordanC> Anyone else have any troubles with clearsigning the Ubuntu CoC
[20:39] <JordanC> I did it, but when I paste the file contacts there are errors
[20:40] <JordanC> (7, 9, 'No public key')
[20:40] <ubotu> New bug: #177241 in launchpad "It's difficult to tell that your application for official mirror status was declined" [Undecided,New] https://launchpad.net/bugs/177241
[22:18] <soren> JordanC: Did you upload your key first?
[22:18] <soren> #launchpad - where all your patience are belong to us
[22:19] <JordanC> It's done now
[22:19] <soren> JordanC: Oh, cool.
[22:19] <JordanC> oh
[22:19] <JordanC> No it's not
[22:19] <JordanC> :/
[22:29] <poolie> does anyone know if there's a limit on the size of release download files?
[22:42] <Rinchen> bac, ^^
[23:15] <poolie> Rinchen, fyi, Szilveszter did successfully upload his 30MB mac installer
[23:15] <poolie> but when john tried, he got a 400 error
[23:15] <Rinchen> interesting
[23:15] <poolie> which hopefully turned into an oops
[23:16] <poolie> maybe it'd be good to have either a faq or display in the upload dialog about the limit, if any
[23:16] <JordanC|Code> Hey sexy launchpadders
[23:17] <bac> poolie: the upload limit is 30Mb
[23:17] <Rinchen> I knew bac is faster than grep ;-) 
[23:17] <poolie> heh
[23:18] <poolie> bac, Rinchen, it's a nice feature btw
[23:18] <Rinchen> I'm still greping to find the answer :-)
[23:18] <bac> Rinchen: you're just lucky.  i only woke up 2 minutes ago
[23:18] <Rinchen> bac where do we set that limit? hardcode, config, or zope-thing?
[23:18] <bac> bac@sapa:~/canonical/lp-branches/feeds-branches/configs/default$ grep size launchpad.conf 
[23:18] <Rinchen> ah thanks
[23:19] <bac>  max_productrelease_file_size 31457280
[23:19] <Rinchen> well, that's why I don't see it.. I don't have feeds-branches, only trunk
[23:20] <poolie> it looks like we just scraped under this time
[23:20] <bac> Rinchen: no, no...it's been in trunk for ages
[23:20] <poolie> there are open source releases which are larger...
[23:20] <bac> that's just the branch i was sitting in
[23:20] <Rinchen> ah..ok, I'll keep looking. my interest is piqued
[23:21] <bac> poolie:  we can bump that up.  the survey i did at the time seemed to indicate 30Mb was a good limit.  i think we based it off the openoffice installer size
[23:21] <poolie> this one is kind of surprisingly large
[23:21] <poolie> but the convention for mac stuff is to ship all the dependencies in one blob
[23:22] <poolie> so it's big
[23:22] <bac> poolie:  ah, ok.  mac stuff we didn't take into account
[23:22] <bac> poolie:  want to throw out a number?
[23:23] <Rinchen> bac, ok, I found it ...and also realized the pain of the config system in the process
[23:23] <poolie> i'd say, take the largest example you've heard of and double it
[23:23] <poolie> so, 60MB?
[23:24] <poolie> is anything going to break if it gets larger?
[23:24] <poolie> i see there's some potential for abuse, whatever the size
[23:24] <bac> poolie: i assume nothing would break but that hasn't been tested yet...
[23:24] <Rinchen> bac, db timeouts?
[23:25] <bac> Rinchen: doubtful.  the blob is stored on the file system with only references to it in the db, as done by the librarian
[23:25] <Rinchen> ah, nifty