[00:38] <spm> superm1: yeah - looking atm - we appear to have a repeat of a problem we had on Sunday.
[00:40] <mkhlnsh> hello. i have an inactive signature of a code of conduct. how can be reactivated?
[00:56] <mkhlnsh> how do i contact a Launchpad adminstrator to reactivate my signature of code of conduct?
[00:57] <persia> mkhlnsh, Just sign it again with your updated key.
[00:58] <mkhlnsh> i didn't change my PGP key; i just deactivated my signature and i want it reactivated back.
[00:58] <wgrant> mkhlnsh: You could ask a question at https://answers.launchpad.net/launchpad
[00:58] <wgrant> Somebody killed the topic again.
[00:58] <persia> Then just sign it again with the same key.
[00:59] <mkhlnsh> then please explyn me why is there this: Once Inactive, a signature can only be reactivated by a Launchpad Administrator. if is not available?
[00:59] <mkhlnsh> s/explyn/explayn
[00:59] <persia> Hrm.  That's unexpected.  You want to ask a question.
[00:59] <wgrant> persia: That's intended.
[00:59] <wgrant> You can workaround it by resigning it, I believe.
[00:59] <persia> wgrant, It is?  Why?
[00:59] <wgrant> But you could just ask a question.
[01:00] <wgrant> persia: Because Launchpad is strange.
[01:00] <wgrant> It has been that way forever.
[01:00] <persia> I know that you can resign for expired keys.  Seems odd you can't for inactive signatures.
[01:00] <persia> Is that just WoT vs. LP DB?
[01:01]  * wgrant -> lecture
[01:03] <mkhlnsh> so, what should I do?
[01:11] <poolie> mkhlnsh: open a question
[01:11] <mkhlnsh> ok
[01:15] <lifeless> superm1: soyuz should be happy again now
[01:16] <lifeless> superm1: we had some db contention issues that are resolved for now
[02:07] <persia> Did someone already file a bug that when someone submits a bug the default is that the bug doesn't affect the submitter?
[03:59] <wgrant> persia: There are several.
[03:59] <persia> Then I won't add another :)
[04:29] <kirkland> hrm, the bug number being a hyperlink at the top of each bug page ... that's something new on edge.launchpad, right?
[04:29] <persia> kirkland, At least it doesn't work that way on lpnet
[04:30] <csilk> packages.ubuntu down?
[04:30] <kirkland> persia: it's kinda annoying, because i usually like to copy-and-paste from there into my changelogs, etc.
[04:30] <kirkland> persia: and a link that just sends me to the same page i'm on is rather useless
[04:31]  * persia has nothing useful to say about the current state of LP UI improvements
[04:31] <Hobbsee> kirkland: i noticed that, too
[04:32] <Hobbsee> kirkland: I did wonder why they implemented that
[04:32] <Hobbsee> beuno: any idea?
[04:32] <kirkland> Hobbsee: thumbs up, or down?
[04:32] <Hobbsee> kirkland: down, for the same use case.
[04:32] <kirkland> probably for consistency
[04:32] <kirkland> but i *really* liked that one not being linked ;-)
[04:32] <Hobbsee> i fail to see why launchpad wants to reimplement the browser's 'reload' button.  I thought the browser button worked fine?
[04:33] <persia> I type the bug numbers rather than copy&paste, but it seems pointless to have a self-reference link when that's already in the location bar of most of the browsers we ship (and the default browser in all flavours but server)
[04:33] <ajmitch> only think I can think of is for context if it's reached from another URL
[04:33] <persia> ajmitch, but that's handled through URL rewriting already.
[04:34] <ajmitch> I won't pretend to know why it was changed then :)
[04:35] <Hobbsee> a "feature", presumably
[04:36] <persia> allows for drag&drop of URL for some browsers, which was probably the considered use case.  That's the advantage of specs that involve wide user review.  I'm looking forward to those.
[04:37] <ajmitch> from what I heard, that'll be soon?
[04:38] <persia> That's seems to be the consensus from those watching these things.
[04:42] <persia> Anyway, the feature is still only on edge.  If you don't like it, file a bug.  There's a chance it won't get to lpnet.
[05:15] <Hobbsee> can i attach multiple files at onceto a bug report yet?
[05:18] <wgrant> Hobbsee: By email, perhaps.
[05:18] <persia> The API still doesn't permit it?
[05:20] <wgrant> It might.
[05:21] <Hobbsee> ffs,launchpad...
[05:21] <Hobbsee> Error ID: OOPS-1027EC19
[05:21] <wgrant> What was it?
[05:21] <Hobbsee> +filebug, for ubuntu.
[05:22] <Hobbsee> Error ID: OOPS-1027EC20
[05:23] <Hobbsee> so, um, how am i supposed to report bugs when I don't know what the source package is now?
[05:23] <persia> Hey.  You got two in a row.
[05:23] <persia> use lpnet?
[05:24] <persia> ask for help in Ubuntu Bugs to find the package?
[05:25] <Hobbsee> persia: that's a good idea.
[05:25] <Hobbsee> oh, there we go.
[05:25] <Hobbsee> took 24 seconds, but did come up with a result.
[05:33] <spiv> Hobbsee: looks like a timeout doing the full text search on your bug title.
[05:34] <Hobbsee> spiv: That's what I thought it might be, yes.
[05:34] <Hobbsee> i'm sure that used to work, too.
[05:35] <spiv> Hobbsee: possibly just an unlucky moment of database contention?  No doubt the real LP devs will look at it properly when they wake up.
[05:35] <Hobbsee> spiv: right.  I reproduced it 3 times on edge, but not on production.  Very odd.
[05:35] <Hobbsee> it must be time to file some more launchpad bugs,too.
[05:41]  * Hobbsee adds https://bugs.launchpad.net/malone/+bug/287935
[06:44] <jamesh> this is a problem with putting all the LP devs in one time zone ...
[06:50] <lifeless> spm: is langpack export running atm ?
[06:50] <lifeless> spiv: the real devs are all in training :P
[06:50] <spiv> lifeless: they have a lunch break, right? ;)
[06:50] <wgrant> This channel seems to be overrun with .au Canonical gods.
[06:51] <lifeless> gods are everywhere
[06:51] <lifeless> so how can they overrun something?
[06:51] <spm> lifeless: not that I can see - just rosetta-approve-imports.py
[06:51] <lifeless> spm: cool;
[06:51] <lifeless> spm: just being...cautious
[06:52] <spm> I can appreciate that :-)
[06:54] <wgrant> Worked out what has been going wrong over the past few days?
[06:54] <spm> lifeless: fwiw langpack (currently) runs Mon, Wed & Sat @ 22:00 BST. hardy, intrepid, intrepid.
[06:55] <spm> wgrant: to fix? yes. To prevent? getting there. :-)
[06:57] <wgrant> spm: Aha. Good. LP does like to die around Ubuntu releases, so it's good to have the problems known about...
[06:59] <spm> heh - so long as it doesn't die on Sundays (again)...
[09:23] <cyberix> Do "affect me"s add to the number of duplicates?
[09:24] <Hobbsee> no
[09:28] <cyberix> So how can I list bugs sorted by the number of "affect me"s?
[09:29] <beuno> cyberix, not yet, no
[09:29] <beuno> you will be eventually  :)
[09:29] <persia> I don't think that is implemented yet : it's planned to be one of the selectable orders, last I heard.
[09:29] <persia> (but beuno really knows)
[09:29] <cyberix> :-D
[09:29] <cyberix> ok
[09:32] <dholbach> hiya
[09:32] <dholbach> is logging in on staging broken right now?
[09:32] <dholbach> for me it doesn't work
[09:33] <beuno> it doesn't for me either
[09:33] <beuno> all LP devs in learning mode
[09:33] <dholbach> it breaks a launchpadlib script for me :)
[09:33] <wgrant> staging's DB is fscked.
[09:33] <dholbach> ahh ok
[09:33] <wgrant> It has none of my teams.
[09:33] <beuno> dholbach, I'll ask as soon as we pause for a bit
[09:34]  * dholbach hugs beuno
[09:34] <wgrant> Wow.
[09:34] <wgrant> That's broken.
[09:34] <dholbach> gracias!
[09:34] <wgrant> https://staging.launchpad.net/projects
[09:34] <Rinchen> siretart, ping
[09:34] <wgrant> 20 projects registered.
[09:34] <wgrant> That wins.
[09:34] <wgrant> Aha. "There are currently 48 people and 17 teams registered in Launchpad."
[09:35] <beuno> ok, it's a known issue
[09:35] <beuno> being worked on
[09:35] <dholbach> rock and roll
[09:35] <beuno> not sure about the ETA though
[09:35] <beuno> trying to learn new skillz, makes actually doing things harder
[09:35] <wgrant> What kind of skillz?
[09:36] <wgrant> Wait.
[09:36] <wgrant> Hmmm.
[09:36] <wgrant> That's the sampledata, isn't it?
[09:36] <beuno> yes
[09:43] <siretart> Rinchen: pong
[09:43] <Rinchen> hi siretart
[09:43] <Rinchen> siretart, what's the process to request something packaged in universe?
[09:43] <Rinchen> siretart, I need a particular program which exists on sourceforge (as a .deb no less) to be in Universe.
[09:44] <siretart> Rinchen: there is currently a discussion about involving brainstorm for that on the ubuntu-mailing list
[09:44] <siretart> Rinchen: the current process is to file a bug in launchpad and tag it 'needs-packaging'
[09:44] <siretart> Rinchen: .deb no less? this means without source?
[09:48] <Rinchen> siretart, source is available
[09:48]  * wgrant notes that upstream packaging rarely helps :(
[09:49] <Rinchen> http://sourceforge.net/project/showfiles.php?group_id=199315
[09:49] <Rinchen> it's under a funky license though
[09:49] <Rinchen> well, not really funky
[09:49] <Rinchen> http://projity.com/license/index.html
[09:49] <siretart> Rinchen: in any case, I'd suggest filing such a needs-packaging bug, and start a discussion about the license and who is going to package it there
[09:49] <philn> hi
[09:50] <Rinchen> ok siretart thanks.
[09:50] <philn> i have a "basic" LP subscription.. my project is using private bzr branches fine but i'd like bugs to be private as well
[09:51] <ace> hi there
[09:51] <philn> oh bac replied my mail ;)
[09:51] <ace> is there a list of the next features available in lp?
[09:51] <beuno> ace, you mean like a roadmap?
[09:51] <ace> yes
[09:51] <ace> or just a wishlist
[09:52] <beuno> well, bugs and blueprints
[09:52] <ace> for example, will a wiki be available in lp?
[09:52] <beuno> and we have milestones: https://edge.launchpad.net/launchpad-project
[09:52] <persia> bugs and blueprints are more of a set of trail blazes than a roadmap per se.
[09:53] <beuno> ace, wikis have been talked about, yes. But there's no ETA for them yet
[09:53] <ace> where do you talk about this? in a blueprint?
[09:53] <beuno> you can see what's being targeted for the next release in: https://edge.launchpad.net/launchpad-project/+milestone/2.1.11
[09:53] <ace> ok
[09:53] <beuno> there is no roadmap, yet
[09:53] <Rinchen> thanks siretart. I'll contact the package owners since I can't find the source. Once I get the data I'll file the packaging request bug
[09:54] <beuno> I suspect there will be something similar soon-ish
[09:55] <siretart> Rinchen: feel free to advertise that bug on the #ubuntu-motu channel, though
[09:55] <ace> perhaps i miss something, but is there something to write doc in lp?
[09:56] <beuno> ace, no, there's no feature available to write it in Launchpad
[09:56] <ace> i say that because when i click on "read full spec" on a blueprint , it goes to a documentation with close access
[09:57] <ace> for example: https://launchpad.canonical.com/Translations/Licensing#remove-translations-by
[09:57] <beuno> well, in other projects, you can link to public wikis instead
[09:57] <beuno> so that would work
[09:57] <ace> ok
[09:57] <beuno> Launchpad currently uses a private wiki, but that may change as well
[09:57] <ace> ok i see
[09:58] <beuno> blueprints ar emore for tracking then the actual content of the spec
[09:58] <beuno> so you can target it to a release, assign it to people, etc
[09:58] <ace> ok like a little post-it
[09:58] <beuno> a clickable post-it!   :)
[09:59] <ace> do you think LP and sourceforge have the same goal? they compete in the same category?
[09:59] <beuno> I don't think so, but I really wouldn't know
[10:00] <ace> i m looking at where i ll put my project
[10:00] <beuno> well, Launchpad has more features, that's for sure
[10:00] <ace> there are info about how many ppl and project on LP?
[10:01] <beuno> you have a nice tour at: https://launchpad.net/+tour/index
[10:01] <wgrant> SF is slightly more flexible for some uses.
[10:01] <wgrant> But LP wins everywhere else.
[10:01] <ace> SF is damn slow too
[10:01] <beuno> ace, https://launchpad.net/projects and https://launchpad.net/people
[10:02] <ace> ok only 9k projects
[10:02] <ace> i thought it was more used
[10:03] <beuno> well, Ubuntu uses it
[10:03] <beuno> so you have a massive amount of packages
[10:03] <beuno> which aren't projects per-se
[10:03] <davidfraser> I got a PPA upload rejected with this message: Unable to identify file gimp_2.6.1.orig.tar.bz2 (graphics) in changes.
[10:04] <ace> ubuntu use it but not for the code hosting
[10:04] <beuno> ace, they will very soon
[10:04] <ace> ah ok
[10:04] <ace> nice
[10:04] <wgrant> davidfraser: You must use a tar.gz.
[10:04] <davidfraser> The previous original file was gimp_2.6.0.orig.tar.gz
[10:04] <davidfraser> What do I need to do to fix this?
[10:05] <ace> i find that LP is really close the ubuntu community, but will it work for a windows opensource project or we ll be bashed :)
[10:05] <beuno> as long as it's open source, it sure won't be bashed
[10:06] <Ng> ace: see https://launchpad.net/windows-ssh-server :)
[10:06] <ace> ah yes :)
[10:06] <ace> a one man project :)
[10:07] <philn> bac: hi, the bug contact was set ;)
[10:08] <davidfraser> wgrant: So if the upstream software only releases .tar.bz2, I must extract and recompress it...
[10:10] <wgrant> davidfraser: Yes. That's the normal practice in Debian and Ubuntu.
[10:10] <davidfraser> OK, Thanks
[10:10] <wgrant> But I think Soyuz (and thus Launchpad's PPA service) is meant to be growing support for bz2 tarballs in the next couple of months.
[10:10] <ace> what is the best way to create a sandbox project?
[10:11] <cprov> wgrant: that true, but don't expect it live in the next cycle :(
[10:12] <wgrant> cprov: We've been waiting a while, so I'm sure we can wait a bit longer.
[10:12] <davidfraser> wgrant: Great. It was just a slightly cryptic error message
[10:19] <ace> funny, i don't find the link to create a new LP project
[10:20] <wgrant> ace: https://launchpad.net/, Open Source Projects, Register a project
[10:22] <ace> lol ok
[10:22] <ace> thank you
[10:22] <dholbach> Rinchen: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[10:23] <Rinchen> thanks dholbach
[10:29] <ace> LP doesn't use subversion?
[10:29] <rockstar> ace, no.  bzr is the future.  :)
[10:30] <ace> of course :)
[10:30] <ace> launchpad too
[10:30] <wgrant> rockstar: And the present.
[10:30] <rockstar> wgrant, well, only because we have a time machine.
[10:30] <wgrant> rockstar: True
[10:34] <kiko> ace, we can import svn of course (maybe somebody else has said that already)
[10:34] <ace> yes i read that
[10:34] <kiko> cool
[10:35] <ace> but there  a big lack in the GUI client
[10:35] <wgrant> olive isn't bad for bzr.
[10:35] <ace> for windows :)
[10:35] <wgrant> Not entirely fully-featured, I guess.
[10:35] <wgrant> Ah.
[10:35] <ace> tortoiseBazaar
[10:36] <ace> http://bazaar-vcs.org/TortoiseBzr
[10:36] <ace> ahaha it exists
[10:36] <wgrant> I wonder if it's still alive...
[10:36] <wgrant> Oh, it is
[10:37] <beuno> yes, there's someone working on it quite a lot
[10:37] <ace> "3  commits by 1  person in the last month "
[10:37] <beuno> Mark Hammond
[10:37] <Hobbsee> beuno: um, what? (#287935)
[10:37] <kiko> that's not just "someone" it's "the one"
[10:37] <ace> :)
[10:38] <ace> the One
[10:38] <beuno> Hobbsee, click the link on the top, takes you to the right place
[10:39] <beuno> top right that is
[10:39] <Hobbsee> beuno: yes.  and?
[10:39] <beuno> uhm, that's why it's there..........
[10:39] <wgrant> I'd imagine it'd be useful for getting to a valid context if you arrive at one in which the bug doesn't exist.
[10:40] <wgrant> Is that your point, beuno?
[10:40] <beuno> yes
[10:40] <wgrant> That is obscure but useful.
[10:41] <Hobbsee> right, so i'ts useful when you're not already at that page.
[10:41] <beuno> yes
[10:41] <rockstar> wgrant, tortoise bzr is actively maintained.
[10:41] <beuno> and
[10:41] <Hobbsee> i guess for consistency's sake,it should always be there, whether it's just actually useful or not
[10:41] <beuno> to give people a link
[10:42] <beuno> yeap
[10:42] <wgrant> rockstar: So beuno said. I just hadn't heard much about it.
[10:42] <beuno> Hobbsee, so, I propose we mark it as a suplicate of the other bug, which should be easy to fix this way now
[10:42] <beuno> just to put pressure  :)
[10:43] <Hobbsee> beuno: except for the fact that it's a bug about the fix of that bug.
[10:43] <beuno> Hobbsee, well, sure. But there is a relevant comment
[10:43] <beuno> otherwise it's just invalid
[10:43] <beuno> so, whatever makes you happier
[10:44] <Hobbsee> well, if you're into marking A a dupe of notA...it's probably best to mark it invalid.
[10:45] <beuno> right, so it's one or the other
[10:46] <beuno> if you don't feel it's a dupe, we'll just mark it as invalid and I'll move on to try and get that ported to the sibgle-comment page
[10:46] <persia> Is it not possible to show the link iff the context differs from the current page (as mpt suggests)?
[10:46] <persia> That makes the presence of the link a useful indicator as to whether you are on the correct page.
[10:46] <beuno> I like consistancy
[10:47] <mpt> eh, why are you still talking about marking it as a duplicate?
[10:47] <Hobbsee> persia: well, i would have thought that.
[10:47] <mpt> They're completely different bugs
[10:47] <beuno> and, that's a link to the bug which will always do the right thing
[10:47] <persia> I guess.  I think you're losing information.  I think mpt has a very good point.
[10:47] <ace> why they didn't use Git?
[10:47] <Hobbsee> mpt: i've got NFI - and i've no idea how the comments on the bug actually relates toeither of the other comments, either.
[10:48] <mpt> it's not invalid, either
[10:48] <wgrant> It could be Won't Fix.
[10:49] <Hobbsee> mpt: more won'tfix, but i'm unconvinced that beuno has actually read the bug sufficiently to grasp what's being said, tbh.
[10:49] <wgrant> But it's not Invalid.
[10:49] <Hobbsee> maybe i was unclear to start with, i'm not sure
[10:49] <beuno> Hobbsee, I'm here, explain!  :)
[10:50] <mpt> beuno, ever since people stopped using Netscape 4 for Mac, no browser has made it easy to copy text inside a link.
[10:50] <mpt> So, copying a bug number from inside a "Bug 12345" link is difficult.
[10:50] <persia> beuno, It breaks a current use case, but does not add value when the bug is in the correct context.
[10:50] <mpt> which is 99.99% of the time.
[10:51] <mpt> And the other 0.01% could be handled better another way.
[10:51] <mpt> (All percentages approximate.)
[10:51] <Hobbsee> mpt++
[10:52] <persia> mpt, Well, I'm not sure about "could be handled better another way".  When out of context, having a link to return to proper context is nice.
[10:53] <persia> Mind you, the link as currently constructed doesn't do that well for multitask bugs.
[10:53] <Hobbsee> persia: I was wondering about that.  Doesn't really help you there anyway
[10:53] <persia> Having such a link be unobtrusively in the upper left isn't bad.
[10:53] <mpt> persia, the other way being, making it imspossible to not be in the proper context.
[10:53] <persia> mpt, Except I routinely abuse the context to work around the ACLs.
[10:53] <beuno> yes
[10:54] <mpt> Which would also have the benefit that each bug report would no longer have ~100000 possible URLs.
[10:54] <beuno> the reason is there, is because so many people URL hack around
[10:54] <mpt> persia, what do you mean by ACLs?
[10:54] <wgrant> Do you make it not exist, or redirect to /bugs/432432423432523?
[10:54] <persia> Well, it's arguable that the fact one can abuse the model is a bug : perhaps it ought detect the right context and redirect when e.g. changing the bug number.
[10:54] <mpt> wgrant, redirect.
[10:55] <persia> Then use URLrewriting to feed the browser the correct context anyway.
[10:55] <mpt> persia, Answers already does that, so it's perfectly possible for Bugs to do it too.
[10:55] <wgrant> So it does.
[10:55] <wgrant> Forgot that.
[10:55] <persia> mpt, Yep.
[10:56] <beuno> so I think it's unobtrusive, and sovles a few problems
[10:56] <beuno> it's possible, just harder
[10:57] <beuno> I opened a bug to do a redirect
[10:57] <beuno> so this was a middle ground
[10:57] <beuno> I approved the UI change, but opened a bug to do redirects in the future
[10:57] <beuno> it's hard to do redirects because it can be linked to multiple projects
[10:57] <persia> beuno, but it breaks use cases.  Can it be reverted in the meantime?  I've yet to see any user comment positively on it.
[10:57] <beuno> and, as it's said, mayne people URL hack
[10:57]  * persia doesn't personally care about it, but it generated more traffic than most commits
[10:58] <beuno> persia, revert the link?
[10:58] <persia> Yes, but generally when URL hacking, we want to be in the "wrong" context.
[10:58] <persia> I think it would make more people happy than sad to revert the link.
[10:58] <persia> I think the bug you want to fix is a valid and useful one, but I think your redirect bug is a better solution.
[10:59] <beuno> I fail to see why it makes anyone unhappy
[10:59] <beuno> like, a real workflow =breaker
[10:59] <beuno> so, reverting involves a lot of steps
[10:59] <persia> Copy & Paste.  Three users (kirkland, mpt, Hobbsee) have complained about it.  Nobody has said anything good.
[10:59] <beuno> you have the bug # on the url
[10:59] <beuno> it takes much less precision to copy it from the url
[11:00] <persia> Not that can be reliably copied in many browsers.
[11:00] <persia> e.g. firefox does DnD for the URLbar unless you are very careful.
[11:01] <persia> beuno, I don't disagree with any of your statements : I'm just not seeing any positive reaction from any of the users, and I see some negative reaction.  Since you seem to agree there exists a more elegant solution, I don't see the benefit of not maintaining the status quo until it is resolved.
[11:02] <persia> (and it doesn't break my use case, so I probably shouldn't even care much)
[11:02] <beuno> persia, the time needed to revert
[11:03] <beuno> so, if we're going to invest time in that, we need some sort of benefit
[11:03] <beuno> clear benefit
[11:03] <persia> happy users?  Lack of complaint?  Lower sense of unresponsiveness of LP to user requests?
[11:03] <beuno> I can see that it's a bit annoying if you're used to copy n pasting from that place
[11:03] <beuno> well, people who are happy with the change are usually less vocal  ;)
[11:04] <beuno> the link is different than the URL
[11:04] <beuno> so it's useful in some cases
[11:04] <persia> OK.  I'm just judging by channel traffic.  Not worth further argument.
[11:05] <beuno> why should we make those users unhappy, that can't find that URL otherwise?
[11:05] <beuno> there was a bug reported about it, which triggered that work
[11:05] <beuno> (can't find it now)
[11:05] <beuno> so a few people where unhappy, that now are happy
[11:05] <beuno> it's hard to please everyone!
[11:05] <jml> beuno: impossible even
[11:06] <persia> Oh, certainly.  It's impossible to please anyone.
[11:06] <jml> o.O
[11:07] <persia> I just don't think it's useful to go from one bad state to another bad state.  If edge is so far down the development pipeline that it's hard to revert, I think the process needs help, but that's entirely separate.
[11:07] <persia> (and there are plenty of other bugs that need work, so clearly spending a lot of time to revert something isn't ideal)
[11:08] <beuno> :)
[11:25]  * Hobbsee eyes the above discussion
[11:27] <jml> it's an interesting problem in general though.
[11:28] <jml> a particular layout has a bunch of implicit benefits
[11:28] <jml> which are only made explicit when it changes.
[11:29] <wgrant> Indeed.
[11:29] <Flimm> Hello, I've tried uploading a source package to my ppa, but I get this error:
[11:29] <Flimm> Already uploaded to ppa.launchpad.net
[11:29] <Flimm> However, I can't find any uploaded packages at http://launchpad.net/~flimm/+archive
[11:30] <Hobbsee> beuno: could you define "not blocking anyone else" please?
[11:31] <wgrant> It's quite clearly not blocking anybody because Launchpad bugs can't block anything. No bug dependencies.
[11:31] <wgrant> For no particularly good reason.
[11:34] <Hobbsee> beuno: in particular, how you can "not block anyone" while breaking use cases.
[11:54] <Flimm> I get a 404 error when I try to visit  http://ppa.launchpad.net/flimm/ubuntu
[11:55] <Flimm> I have enabled my PPA though: https://launchpad.net/~flimm/+archive
[11:55] <bigjools> nothing will be there until the first upload is processed successfully
[11:56] <Flimm> That's strange, bigjools, dholbach's PPA (for example) is empty, but you don't get a 404 error when visiting http://ppa.launchpad.net/dholbach/ubuntu
[11:57] <bigjools> he probably used to have something and deleted it
[11:57] <bigjools> trust me, you need to upload something
[11:57] <Flimm> I have, I've been waiting for half an hour already, bigjools
[11:57] <bigjools> you get any emails back?
[11:58] <Flimm> No emails
[11:58] <Flimm> Oh wait, I did just get one
[11:58] <kiko> Flimm, and your gpg key is registered?
[11:58] <Flimm> Yes, gpg keys are registered
[11:58] <bigjools> no emails means either you didn't sign the upload or you signed with a key not in LP
[11:58] <bigjools> otherwise the email will tell you what you did wrong
[11:59] <Flimm> Thank you, that's very helpful
[11:59] <Hobbsee> bigjools: or the uploader borked again?
[11:59] <bigjools> welcome
[11:59] <Flimm> I just got an email: epidermis_0.1b-10ubuntu1_i386.changes rejected
[11:59] <Hobbsee> Flimm: that'll be why.  You needt o upload a *source* changes.
[11:59] <Flimm> I had tried to upload an unsigned package a few hours ago, I didn't get any error messages
[11:59] <wgrant> bigjools: Malformed Changed-By or Maintainer addresses will generate error mails now? They always used to be silently dropped.
[12:00] <bigjools> umm dunno, I'd need to check
[12:00] <Flimm> And when I tried to upload it again, it told me I had already uploaded it
[12:00] <Hobbsee> Flimm: see https://help.launchpad.net/Packaging/PPA?action=show&redirect=PPA#Building
[12:00] <Flimm> So I had to up the version one.
[12:00] <wgrant> Flimm: That's just dput being silly locally. Pass -f to it to convince it to upload again.
[12:00] <Flimm> Thanks wgrant!
[12:01] <wgrant> np
[12:01] <Flimm> I've been using dpkg-buildpackage , which is supposed to build both source and binary packages, can I use that?
[12:02] <wgrant> We generally use debuild, and you must pass -S in either case.
[12:02] <wgrant> Launchpad does not accept binaries.
[12:04] <Flimm> I'm going to try dpkg-buildpackage -S first, as I'm unfamiliar with debuild
[12:04] <Hobbsee> Flimm: debuild is a wrapper around dpkg-buildpackage.
[12:04] <Hobbsee> (so most of the options arethe same)
[12:05] <Flimm> Oh... I am learning a lot today
[12:06] <Flimm> Well, the dpkg-buildpackage -S seems to have worked
[12:12] <Flimm> How long will it take roughly to build?
[12:16] <Flimm> It's built
[12:16] <Flimm> That was ten minutes long
[12:21] <kiko> heh
[12:21] <kiko> yeah, it's usually less than 10 mins in fact
[12:22] <wgrant> But then you have to wait for up to 20 minutes or hack URLs to get to the binaries :(
[12:23] <beuno> no, it's usually under 10 minutes
[12:23] <beuno> it *may* take longer, like anything....
[12:24] <wgrant> Doesn't the PPA publisher run on */20?
[13:12] <bac> philn: ok, great. thanks.
[14:36] <pecisk> people, what means current and packaged in translations? How it could be that packaged is something different than current, but currrent is older than packaged
[14:36] <pecisk> that is in LP Rosetta
[14:39] <kiko> I think current reflects what's current in LP
[14:39] <kiko> danilos will know though
[14:41] <danilos> pecisk: that's right, packaged is what was "active" in a package (usually upstream), current is what is going to be active for Ubuntu when new language pack is released
[14:41] <pecisk> danilos: in this case it is debian-installer. It is non-lang-pack, afaik
[14:42] <pecisk> I did changes in July
[14:42] <pecisk> but it still insist to use wrong version
[14:43] <danilos> pecisk: ah, that's a completely separate question, they are manually updated, check with cjwatson on #ubuntu (or wherever he hangs around :)
[14:46] <pecisk> cjwatson: ping? :)
[14:53] <kirkland> persia: thanks for making our case.
[14:53] <kirkland> beuno: would it be possible to print the bug number *somewhere* on the bug page, without hyperlinking it?
[14:53] <beuno> kirkland, sure, I'll revise the UI
[14:54] <beuno> do you want to re-phrase the bug and re-open it?
[14:54] <persia> kirkland, Always happy to make a case, although I'm not always successful in pursuing them.
[14:54] <kirkland> beuno: all we really need is some place on the page that we can easily double-click to highlight (without sending to another page), and put on the copy buffer
[14:54] <beuno> assign it to me, I'll take care of it
[14:54] <kirkland> beuno: thanks
[14:56] <soren> bzr says a branch on launchpad is locked, and suggests I run this to fix it: bzr break-lock lp-46042832:///~ubuntu-virt/vmbuilder/trunk/.bzr/branch/lock
[14:56] <soren> However, when I try that, I get: bzr: ERROR: Unsupported protocol for url "lp-46042832:///~ubuntu-virt/vmbuilder/trunk/.bzr/branch/lock"
[14:56] <soren> Removing -46042832 fixes it.
[14:58] <cjwatson> pecisk: I did a by-hand update of the translations in d-i not very long ago. Which language are you interested in?
[14:58] <pecisk> cjwatson: Latvian
[14:58] <cjwatson> pecisk: however, you should know that many of the translations in d-i are *never* updated from Launchpad
[14:59] <cjwatson> pecisk: I am not interested in being man-in-the-middle for different translation groups any time I merge d-i from upstream
[14:59] <cjwatson> pecisk: so, for strings that exist in Debian too, I refer people to Debian for translating d-i
[14:59] <cjwatson> pecisk: the strings I update from LP are just those that are new in Ubuntu
[14:59] <pecisk> ahhh, that explains a lot
[15:00] <pecisk> ok, it should be noted somewhere, otherwise I think LP has bug or something :)
[15:02] <ace> is it possible to add some hook in LP?
[15:02] <ace> like in svn to display commits in irc for example
[15:03] <cjwatson> pecisk: I thought it was, but I don't really know where translators would be looking
[15:04] <pecisk> cjwatson: so, next time you will take d-i translations from Debian, you will take from lenny, right? And it will be for 9.04?
[15:04] <cjwatson> pecisk: I merge updated packages from unstable, which include translations
[15:04] <fantix> jtv: ping?
[15:04] <cjwatson> pecisk: they don't necessarily correspond exactly to lenny or anything
[15:04] <pecisk> ok, I see
[15:04] <pecisk> thanks for info
[15:04] <cjwatson> pecisk: and yes, I'm not anticipating any more translation changes for 8.10 at this point
[15:05] <pecisk> I know
[15:05] <pecisk> it is too late already
[15:05] <fantix> excuse me, but is jtv around please?
[15:11] <fantix> got a question here. :) my first pot uploaded with bad name was approved and renamed inside LP, and does my second pot with the new name still need manual review? thanks
[15:18] <philn> bac: can you confirm me by mail when i'll be able to file private bugs on my project? not that i'm tired to fill stoopid test bugs ;)
[15:21] <bac> philn: it is done now.
[15:31] <exarkun> I uploaded a new translation template, but I guess I must have done something wrong, since it ended up in the import queue.
[15:31] <exarkun> Can anyone tell me what I did wrong?
[15:31] <exarkun> https://translations.launchpad.net/twisted
[16:30] <ace> do you really prefer the mailing list against forums?
[16:34] <cjwatson> it's a legitimate preference
[17:16] <cjwatson> mwhudson: I don't suppose there's been any movement on bug 112327?
[17:17] <mwhudson> cjwatson: nope
[17:17] <mwhudson> (sorry)
[17:17] <cjwatson> whom do I have to bribe? :)
[17:21] <cjwatson> danilos: wow, the import queue is not exactly proceeding quickly :-(
[17:24] <Rinchen> cjwatson, rockstar
[17:24] <Rinchen> cjwatson, for the bribe ;-)
[17:25] <cjwatson> rockstar: I'm in London next week. What booze do you like? :-)
[17:25]  * cjwatson <- fed up of using CVS for OpenSSH ...
[17:25] <rockstar> cjwatson, I actually don't drink, but there are other ways to bribe me.  :)
[17:26] <rockstar> cjwatson, unfortunately, that bug is not even on my radar.
[17:26] <rockstar> Er, wasn't until just now.
[17:26] <rockstar> I'll take a look at it, and if it's not a big deal, I may work on it tonight.
[17:27] <cjwatson> cool, thanks!
[17:27] <rockstar> cjwatson, Ooh, a patch!
[17:27] <cjwatson> well, I'm in the Millbank office next week, so if I manage to make it over to Paddington or vice versa ...
[17:28] <rockstar> cjwatson, just because you submitted a patch, I'll make sure it gets done this weekend, even if I have to mess with it.
[17:28] <cjwatson> cool, thanks a lot
[17:28]  * rockstar believes in rewarding patches.
[17:29] <cjwatson> just for that I might get round to 256050 as well
[17:29] <cjwatson> I like producing patches to make my pet projects work. :)
[17:30] <Rinchen> cjwatson, we have this pet project.... it's called Launchpad. Maybe you've heard of it? :-)
[17:30] <cjwatson> I have, but I have another pet project called Ubuntu which may be familiar to you ;-)
[17:31] <Rinchen> touche`
[17:41] <rockstar> cjwatson, there is also this neat thing called bzr that even works WITH launchpad.  It makes patch management and merging WAY easy.  :)
[17:43] <exarkun> I uploaded a new translation template, but I guess I must have done something wrong, since it ended up in the import queue.  Can anyone tell me what I did wrong?  https://translations.launchpad.net/twisted
[17:49] <hlh> So how does one unsubscribe someone to a bug in LP?
[17:49] <hlh> fyi, I'm the project owner
[18:16] <danilos> exarkun: that's the correct behaviour: someone needs to review it
[18:16] <danilos> cjwatson: unfortunately, we haven't optimized the import of completely new files when we did previous rounds of import optimizations, because they are a minority of cases (but now, with this set of KDE data, they are all new files) :(
[18:31] <krish> hey hi. I am not able to upgrade my branch bazaar version
[18:33] <krish> [krish@lappie timepass-devel]$ bzr upgrade bzr+ssh://srikrishna@bazaar.launchpad.net/~timepass/timepass/timepass-devel
[18:33] <krish> Format <RepositoryFormatKnit1> for lp-46042832:///~timepass/timepass/timepass-devel/.bzr is deprecated - please use 'bzr upgrade' to get better performance
[18:33] <krish> bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format.
[18:35] <krish> spiv:
[18:52] <exarkun> danilos: Last time I uploaded something, someone told me it wouldn't need to be reviewed next time.
[18:52] <danilos> exarkun: ah, then it needs to wait for auto-approval process to finish, it may take a few hours for that to happen
[18:53] <danilos> exarkun: if not, please file a question on answers.launchpad.net/rosetta/ and we'll look at it
[18:53] <danilos> sorry, have to go now
[18:53] <exarkun> okay.  thanks.
[19:11] <fantix> exarkun: thanks! :) gotta sleep, 2am here
[19:27] <nelson_mtkwan> hi there. I am a newbie in ubuntu. I have just setup the automounting of my partition by the 1st method on https://help.ubuntu.com/community/AutomaticallyMountPartitions, which containing Chinese file name. Everything goes rights except those Chinese file name. They all became question marks!!! Can anybody here help me?
[20:00] <psusi> I can't seem to log into staging... is there anything special you have to do for that?
[21:01] <Jazzva> hello... I'm experiencing a problem with bzr and launchpad. I keep getting "User timeout caused connection failure" message on the branch page when I try to push changes. I have tried it at least 4 or 5 times.
[21:01] <Jazzva> here is the branch address https://code.edge.launchpad.net/~jazzva/app-install-data-ubuntu/ubuntu.xul-extensions
[21:03] <Jazzva> Deleting the branch and then pushing all the changes didn't help.
[21:07] <LarstiQ> Jazzva: hmm
[21:07] <LarstiQ> Jazzva: is this a mirrored branch perchance?
[21:07] <LarstiQ> hello Ursinha
[21:08] <Ursinha> hi LarstiQ
[21:08] <Jazzva> LarstiQ, mirrored? I don't think so. I push changes from my local branch on my computer.
[21:08] <LarstiQ> Jazzva: ok
[21:08] <LarstiQ> Ursinha: do you have the power to see what is causing the timeout on https://code.edge.launchpad.net/~jazzva/app-install-data-ubuntu/ubuntu.xul-extensions ?
[21:09] <Ursinha> LarstiQ, are you getting any oopses?
[21:09] <LarstiQ> Ursinha: no, it looks like the branch puller to me
[21:09] <Ursinha> User timeout caused connection failure.
[21:09] <Ursinha> urgh, what's that
[21:10] <LarstiQ> not sure :)
[21:10] <Ursinha> :)
[21:10] <Ursinha> well
[21:10] <Ursinha> let me dig
[21:12] <Ursinha> hey beuno, what's up :)
[21:13] <Ursinha> LarstiQ, by timeout you mean that yellow box with that connection failure message?
[21:13] <LarstiQ> Ursinha: I do
[21:13] <Ursinha> LarstiQ, ok
[21:13] <LarstiQ> not an oops timeout, sorry for the confusion
[21:19] <Ursinha> LarstiQ, no problem at all :)
[21:22] <LarstiQ> Ursinha: pfew :)
[21:42] <Ursinha> LarstiQ, didn't forget you, trying to understand the error
[21:48] <beuno> hey hey Ursinha
[21:48] <Flimm> Hey everyone, I just submitted a blog post about my experiences with Launchpad:
[21:48] <Flimm> http://epidermis.tuxfamily.org/?q=node/34
[21:49] <Ursinha> beuno, how long :P
[21:50] <beuno> Ursinha, yeah, it's been a while!
[21:50] <beuno> where di you have dinner?
[21:50] <Ursinha> beuno, went to salisbury and bought some fruits and so :)
[21:50] <Ursinha> salisbury local
[21:50] <Flimm> Well, that's it folks, you don't have to read it if you don't want to, I just wanted the right people to read it. Good night
[21:50] <beuno> oh, they have very good food
[21:51] <beuno> I bought food there last night
[21:51] <Ursinha> beuno, oh, cool :) thought i was the only one to go dinner in the supermarket :P
[21:52] <beuno> Ursinha, ha, no. It's cheap and good, what more would you want?
[21:53] <Ursinha> beuno, maybe take a walk in london :)
[21:54] <beuno> Rinchen, url above ^
[21:56] <Rinchen> er huh?
[21:56] <Rinchen> ah
[21:56] <Rinchen> epidermis!
[21:57] <Rinchen> I wish this hotel AP didn't block connections.
[21:57] <Rinchen> can't use avahi
[21:59] <beuno> I see people in bonjour just fine
[22:00] <Rinchen> beuno, yeah but try to msg them
[22:00] <Rinchen> beuno, connection cannot be completed
[22:00] <Rinchen> we could do it on the cisco Ubuntu router in the classroom
[22:00] <Rinchen> but not on the hotel's router
[22:01] <beuno> ah
[22:01] <beuno> right
[22:01] <awilkins> Does it let 22 out? I use my router to bounce things off via SOCKS
[22:01] <beuno> we can't con nect to each other
[22:01] <beuno> in any port
[22:03] <bigjools> Sainsbury
[22:03] <Rinchen> 92.54.156.162
[22:03] <Ursinha> bigjools, yes yes
[22:03] <Ursinha> :)
[22:03] <bigjools> :)
[22:04] <Ursinha> sorry about the typo
[22:05] <bigjools> and sorry for stealing your food earlier :)
[22:05] <awilkins> Howdoes/can one become a Launchpad dev if you are not employed by Canonical?
[22:06] <lifeless> awilkins: at the moment its pretty rarely done
[22:06] <lifeless> awilkins: but the technical side of the process is an NDA
[22:06] <lifeless> awilkins: once its open sourced it will be a lot easier :)
[22:06] <Ursinha> hahaha! bigjools, I don't even remember anymore :)
[22:07] <bigjools> and then you refused my two offerings, which meant that I had to eat them, so it's all your fault if I get fat ;)
[22:07] <awilkins> I just have a requirement to investigate project/stuff tracking for my org so my thoughts naturally turned to Launchpad
[22:08] <awilkins> They want to be tracking rather more bits'n'bobs than just issues and code, but maybe we can learn stuff from each other
[22:08] <Ursinha> bigjools, hahaha :)
[22:08] <awilkins> (usual craptastic lack of well-defined requirements at present)
[22:08] <awilkins> lifeless: Any idea when that open-sourcing will happen (as if!)
[22:09] <awilkins> (any schedule would be stuck to ,etc!)
[22:09] <beuno> awilkins, july-ish next year
[22:10] <wgrant> Will it be an all-at-once, drown-everyone-in-code effort?
[22:10] <awilkins> Could be a bit of a wait... would being "the NHS" make it any more or less likely that you'd trust an NDA in my hands :-)  ?
[22:13] <lifeless> awilkins: whats your email address; I'd be delighted to mail you & kiko to get a discussion rolling
[22:15] <beuno> wgrant, we don't know. There will be quite a few things happening in between
[22:17] <wgrant> Will the roadmap be public when it's done?
[22:17] <beuno> yeap
[22:18] <beuno> probably before
[22:18] <wgrant> Great.
[22:22] <wgrant> It's good to see this finally happening... we've been waiting a while.
[23:04] <RAOF> Has anyone had a chance to look at bug #270031?  It's been a while, and it's got a fairly wide impact on PPAs.