[00:11]  * sladen drums fingers
[00:15] <sladen> sinzui: could you advise what summary title should be used for bug #449092 such that it can be progressed?
[00:15] <elmo> james_w: hmm, unfortunately, I can't see any obvious problems this time round
[00:17] <james_w> elmo: seems to have fixed itself in the meantime, thanks for looking
[00:20] <elmo> I think it may be LP buildbot DOS-ing the ssh service.  but I may just want it to be that because of the irony.  I'll keep an eye on it for a while anyway
[01:09] <sinzui> sladen: it is not a bug, it is a question. I will use the Convert to question link to ask a LOSA to add an alias for the old project name. I image a Question was used the first time to rename the project
[01:20] <sladen> sinzui: questions have a '?' question mark.  Why does this (bug report) not have a question mark?
[01:21] <sladen> sinzui: how does "ask[ing] a LOSA to add an alias" fix the Launchpad codebase?
[01:23] <sladen> sinzui: if you let me the know the magic phrase that covers the root cause, I can (re-)file a bug report covering that
[01:23] <sinzui> sladen: There is nothing wrong in the code, because in many operations we do not want an alias. We only want an alias if the project asks for one
[01:25] <sladen> sinzui: what phrase succinctly identifies that such an offer should be automatic and by default
[01:28] <sinzui> sladen: we do not support user renaming projects because it is very danger. The screen that allows an admin to rename a project also has a alias field. The admin uses it when someone asks a question
[01:28] <sinzui> sladen: So we are discussing a process where two people must engage each other and talk
[01:31] <sladen> sinzui: is the alias pre-filled with the previous proejct name.  If not, how do I phrase that it should be pre-filled by default in order to prevent previously published URLs rotting
[01:32] <sinzui> It is not, because that is NOT the default behaviour. Most cases to reanme a project is because someone want the name being given up.
[01:33] <sladen> sinzui: how do I phrase that the default behaviour (link breakage) is non-ideal?
[01:37] <sinzui> sladen: I do not see how you. can There is no right answer. We favour this approach because of the most common use case. The example we are using in the bug/question is still one of user communication
[01:40] <sladen> sinzui: so to confirm.  During a rename, the requestee is not explicitly asked if a redirect is required.  Because few requestees explicitly ask for a redirect, the common-case is not to provide one; and therefore the common-case is set as the default?
[01:41] <sinzui> sladen: and the admin did not confirm that an alias was not wanted
[01:42]  * sladen staggers in belief.
[01:42] <sladen> diselief
[01:42] <sinzui> The common case is someone is squating on a name or the name is given to a project group!
[01:43] <sinzui> Renaming a project for other reason is rare and is the reason launchpad supports aliases. gaim's rename to pidgin was the driving need as I recall
[01:44] <sinzui> The problem with automatically aliasing is that the squating is still happening, so the admin has more work to fix the issue
[01:48] <sladen> sinzui: sounds like two separate use-cases.  (a) Projects changing name.  (b) Tackling squatters/vandalism. ; the difference being whether the $old_name is cause of the admin actions, or whether $new_name is the initiator
[01:48] <sinzui> It's the same screen
[01:49] <sinzui> And I do not think malicious is the drive for squating. There is a tremendous amount of ignorance in the pool of launchpad registrants
[01:50] <sinzui> giving users a test to verify they are qualified to be a project maintain seem to be out the question though :(
[01:50] <sladen> so the problem is one of overloading.  A low-impact action performed frequently is masking a high-impact action performed infrequently (Quantity masking Quality)
[01:51] <sinzui> Do you want to fix this? I can review a code change. We do not have much code for workflows so we resort to simple screens
[01:52] <sinzui> This issue is not a priority because we are not inundated with reports of the problem
[01:53] <sladen> sinzui: so, can be agree upon  Confirmed,Wishlist (and a summary of your choosing) over Invalid?
[01:55] <sinzui> I will move the bug launchpad-registry. it will be Triaged,Low We do not used wishlist because that does not indicate when and how it will be fixed
[01:55] <sladen> sinzui: Low would be even better
[01:56] <sinzui> I will report a new bug actually because there is a question tied to the old one
[01:56] <sinzui> Low is just clear. It will be fix opportunistically when an engineer volunteers to work on it
[07:53] <highvoltage> hi launchpadders!
[07:53] <highvoltage> I have a list problem, when I visit https://launchpad.net/~ubuntu-ngo/+mailinglist-moderate there are 5 messages for moderation
[07:54] <highvoltage> when I click on Moderate, I get a message that says "Unexpected form data"
[07:54] <wgrant> highvoltage: Are you using Chromium?
[07:54] <highvoltage> wgrant: I am indeed, is it a browser issue?
[07:55] <highvoltage> wgrant: well, it worked fine in firefox. thanks
[07:58] <wgrant> highvoltage: It's fixed in recent Chromiums, apparently.
[08:22] <Peng> bazzar.launchpad.net is read-only right now. Trying to take out a right-lock fails, saying it's a read-only transport.
[08:22] <spiv> Any losa around?  There are some reports on #bzr of users getting readonly errors when they try to push to their own branches via bzr+ssh
[08:22] <Peng> Hehe.
[08:22] <Peng> Err, write-lock*
[08:45] <Peng> I just realized I screwed up my test: I tried to lock a mirrored branch. I just tried a normal branch, and it worked.
[08:45] <Peng> So, it looks like this might be luks-only.
[08:46] <Peng> Same with the branch the other user was having a problem with.
[08:46] <Peng> So, no disaster. :D
[08:48] <spiv> For losas checking backlog: false alarm.  phew.  thanks.
[11:55] <szpuni> hi
[11:56] <szpuni> did anybody had any problem with karmic hanging when typing in shell??
[11:57] <spiv> szpuni: #launchpad isn't really the place to ask that.  At a guess #ubuntu is a better venue.
[12:42] <slytherin> Can anyone who is not on vacation help with porting bugs from sourceforge.net to launchpad.net?
[13:12] <slytherin> jamesh: Around? Can you help with bug migration from sourceforge?
[13:46] <sladen> sinzui: do you have the new bug# for "<sinzui> I will report a new bug actually because there is a question tied to the old one"
[14:41] <sinzui> sladen: bug 501525
[15:26] <RenatoSilva> someone please expire bug 452034
[15:26] <RenatoSilva> sorry, not this, but bug 452069
[15:27] <sinzui> RenatoSilva: Auto expiration is not turned on. When bugs reach 60 days on incomplete, I change the bug to invalid myself
[15:28] <RenatoSilva> is just that what the expiration job does?
[15:28] <sinzui> Yes
[15:28] <RenatoSilva> oh
[15:36] <RenatoSilva> thanks, happy new year
[17:33] <ripps> Hello, the developer of a set of programs I supply daily packages for in the gmpc-trunk ppa's wants to know If it's possible to build arm packages in the ppa?
[17:41] <elmo> ripps: unfortunately it's not, no.  (PPAs require virtualization support for security reasons that arm's don't have)
[17:41] <ripps> elmo: I know that some ppa's have an exemption from that rule
[17:42] <elmo> ripps: only internal Canonical ones, AFAIK
[18:24] <EagleScreen> hello
[18:24] <EagleScreen> i try to push/upload a project code to bazaar in my Launchpad account
[18:25] <EagleScreen> i obtain this warning, is it safe to continue? -> http://pastebin.com/d5055968d
[18:25] <EagleScreen> why this warning?
[18:34] <sinzui> EagleScreen: Have you ever connected to bazaar.launchpad.net before. That is the message commonly shown when you first try to connect to an unknown host.
[18:49] <frangor> hi
[18:52] <EagleScreen> thanks sinzui, it was the first time