[00:30] <poolie> launchpad now shows the merge proposal diffs inline in gmail, well done! :)
[00:55] <poolie> thumper: are you changing all those bugs by hand? or by a script?
[00:58] <thumper> poolie: which bugs :)
[00:58] <thumper> changing
[00:58] <thumper> I read chasing
[00:58] <thumper> that was by hand
[00:58] <thumper> I've been meaning to write a script for a while
[00:58] <thumper> but I can never be arsed
[01:02] <poolie> :/ we should just have Fixed
[01:10] <mwhudson> fix verified!
[01:20] <spiv> More Fixerated!
[01:20] <spiv> Hmm, I guess the pattern is "Fix Verbed"
[01:21] <spiv> Fix Verbed II: Fixed Harder With A Vengance.
[03:34] <days_of_ruin> Unable to obtain lock lp-46119120:///~freshapplepy/rssn/main/.bzr/branch/lock
[03:34] <days_of_ruin> held by codehost@crowberry on host crowberry [process #21552]
[03:34] <days_of_ruin> locked 23 hours, 3 minutes ago
[03:34] <days_of_ruin> Will continue to try until 03:33:45, unless you press Ctrl-C
[03:34] <days_of_ruin> If you're sure that it's not being modified, use bzr break-lock lp-46119120:///~freshapplepy/rssn/main/.bzr/branch/lock
[03:34] <days_of_ruin> bzr: ERROR: Could not acquire lock "(remote lock)"
[03:34] <days_of_ruin> ;_;
[03:36] <mwhudson> days_of_ruin: the suggested url is wrong (known bug)
[03:36] <mwhudson> days_of_ruin: try 'bzr break-lock lp:~freshapplepy/rssn/main'
[03:38] <thumper> mwhudson: not being updated by translations is it?
[03:38] <thumper> just a thing to think about now
[03:38] <thumper> that we commit to user branches internally
[03:38] <mwhudson> thumper: true
[03:38] <wgrant> For 24 hours?
[03:38] <thumper> well, no
[03:38] <mwhudson> yeah, not for 24 hours i hope
[03:38] <thumper> that'd indicate some screwage
[03:39] <wgrant> Doesn't it normally give a more informative username?
[03:41] <sladen> I can't see Launchpad for all the yellow circles
[03:41] <thumper> wgrant: no
[03:41] <thumper> wgrant: I don't think so
[03:42] <thumper> ...
[03:42]  * thumper can't remember
[03:43] <wgrant> I know it used to.
[03:43] <wgrant> But maybe that was back in the good old days before bzr+ssh.
[03:46] <wgrant> held by<EMAIL_ADDRESS>on host crowberry [process #1080]
[03:46] <wgrant> I wonder if that *was* translations.
[03:48] <wgrant> THat branch does have translation updates enabled.
[03:48] <wgrant> So there is some screwage! Yay.
[03:48] <mwhudson> codehost@ could well be translations actually
[03:49] <wgrant> That is the email address that it uses in commits.
[03:49] <wgrant> So... oh dear.
[03:54] <mwhudson> the translation user?
[03:54] <wgrant> Translation commits are by "held by<EMAIL_ADDRESS>on host crowberry [process #1080]
[03:54] <wgrant> Er/
[03:54] <wgrant> Not that.
[03:54] <wgrant> Launchpad Code Hosting <codehost@crowberry>
[03:55] <days_of_ruin> mwhudson, That worked thanks.
[04:10] <johnf> Architecture: all packages build on i386 builders for PPA, right?
[04:11] <johnf> Can anyone think of a reason not to build the on i386 instead. Considering it's queue always seems to be shorter https://launchpad.net/builders
[04:13] <lifeless> I think you mean 'not on' or something
[04:13] <lifeless> but yes, all->i386
[04:13] <lifeless> there is a Grand Plan
[04:13] <lifeless> in the meantime, tough luck said the kitty
[04:14] <ScottK> lifeless: Would it perhaps make sense to drop the lpia PPA builders and recycle them for i386/amd64 in the meantime.  It'd give more throughput and I think it's reasonably official that no one cares about lpia anymore.
[04:15] <johnf> hmm lp:bzr.dev doesn't have a 2.0.0 tag
[04:15] <lifeless> ScottK: no comment on lpia [I have no info]
[04:15] <lifeless> johnf: lp:~bzr-pqm/bzr/2.0.0
[04:16] <lifeless> johnf: it hasn't been merged back to 2.0, and thence to bzr.dev yet
[04:16] <ScottK> lifeless: Ubuntu dropped the atmo specific gcc patches for lpian in Karmic, so it's just a clone of i386.
[04:16] <ScottK> atmo/atom
[04:37] <RenatoSilva> error when deleting milestones (several times along the day): (Error ID: OOPS-1364C714)
[04:44] <wgrant> johnf: The i386 PPA build queue is longer just because arch-indep packages build there.
[04:44] <wgrant> Most of the current i386 queue is the archive rebuild, which is well behind any PPA builds.
[04:45] <johnf> wgrant: then maybe all should be allocated to the Arch which currently has the shortest Q or similar
[04:47] <lifeless> johnf: its not a policy thing atm, AFAIK, rather its code.
[04:47] <RenatoSilva> guys can't delete milestones
[04:48] <wgrant> johnf: The intention is to eventually pool all of the x86 (i386/amd64/lpia) buildds, but the queue algorithm is hard.
[04:49] <lifeless> wgrant: perfect. Good. ENEMIES4EVA
[04:49] <wgrant> lifeless: Huh?
[04:50] <johnf> wgrant: sounds good
[04:50] <wgrant> johnf: How far is your i386 build behind the rest?
[04:51] <wgrant> It shouldn't be too bad, although there are lots of buildds missing today.
[04:52] <johnf> wgrant: they've manage to finish while I've been whinging :) This morning was a bit worse though. Took about an hour. I suppose I'm just used to thing usually building straight away
[04:52] <wgrant> Hmmm.
[04:52] <wgrant> Does lawrencium show up on /builders for other people?
[04:53] <wgrant> It's disabled, but /builders still shows it building for me.
[04:53] <wgrant> Ah, that's better.
[07:03] <asabil> hi all
[07:03] <asabil> when trying to setup launchpad, I end up with the following error:
[07:03] <asabil> ImportError: No module named _pythonpath
[07:06] <spm> asabil: best bet is to try #launchpad-dev
[07:07] <asabil> ok will do that later, gtg now to work :)
[07:07] <asabil> thanks spm
[07:07] <asabil> ttyl
[10:35] <resolve> hi folks. i have 'people can ask questions in launchpad answers' turned off, but I was still able to post a question. is that only because I'm an admin?
[10:36] <resolve> I wish unused features/pages like answers could be removed from the top menu :-(
[11:03] <james_w> OOPS-1364ED613
[11:08] <james_w> what are the other pages like +activereviews?
[11:08] <james_w> that only shows reviews I can do, not ones that I have bumped to needs-fixing and the like
[11:08] <james_w> I'm getting timeouts going to the listing page that would have the links at the top
[11:12] <james_w> ah, if I go to my +activereviews then I see them
[11:15] <hanska> hello people
[11:15] <hanska> is there any way to control a project's bugs by email?
[11:15] <hanska> (like DBTS does, that is, with<EMAIL_ADDRESS>[11:17] <LarstiQ> hanska: yes
[11:17] <LarstiQ> hanska: https://help.launchpad.net/Bugs/EmailInterface
[11:18] <hanska> LarstiQ: great! Is that a new thing? :)
[11:18] <LarstiQ> hanska: no, been active for years now
[11:18] <hanska> uh, I totally missed that, really.
[11:19] <hanska> I'm going to write a git post-receive hook then (hoping that github allows them)
[11:19] <hanska> LarstiQ: maybe I missed this too.. LP still doesn't have git, right?
[11:19] <wgrant> I probably first used it four years ago. It has been there a while.
[11:19] <LarstiQ> hanska: it can do imports using bzr-git
[11:20]  * LarstiQ hasn't been paying attention to the development on that front
[11:20] <LarstiQ> hanska: do note you'll need to gpg sign the email
[11:21] <hanska> LarstiQ: uhm. That would be difficult, but I'll try to hack something.
[11:21] <hanska> Thank you!
[11:35] <asabil> hi all
[11:35] <asabil> is there any documentation about how to deploy lp for production ?
[11:35] <Fly-Man-> asabil: try #launchpad-dev
[11:36] <asabil> ok thanks
[12:07] <rowinggolfer_> greetings.
[12:07] <rowinggolfer_> my project uses launchpad for bugs.
[12:07] <rowinggolfer_> and I would like to make it as easy as possible for end-users to file bugs.
[12:08] <rowinggolfer_> presumably I can do this with the launchpad api?
[12:09] <rowinggolfer_> or perhaps I simply call apport?
[12:11] <rowinggolfer_> this is useful (another of mrevell's wonderful howto's)
[12:11] <rowinggolfer_> https://help.launchpad.net/Bugs/PluginAPISpec#report_bug():%20File%20a%20new%20bug
[12:11] <rowinggolfer_> grr... url fail.
[12:11] <mrevell> rowinggolfer_: Why, thank you but the credit for that page must go to gmb :)
[12:12] <wgrant> rowinggolfer_: I don't think that does what you want.
[12:12] <mrevell> gmb: who can probably answer your question better than me, too
[12:12] <wgrant> rowinggolfer_: That's for Launchpad to create bugs on remote bug trackers.
[12:12] <rowinggolfer_> mrevell - sorry, you are down as the last editee. my bad
[12:12] <rowinggolfer_> wgrant - any suggestions?
[12:12] <rowinggolfer_> are there any projects out there already doing this?
[12:12] <wgrant> rowinggolfer_: https://help.launchpad.net/API
[12:13] <wgrant> What exactly do you want to do?
[12:13] <rowinggolfer_> my users are totally non-savvy.
[12:13] <rowinggolfer_> wgrant - ok... suppose my app runs into a non-critical exception...
[12:13] <rowinggolfer_> something like a database schema update failing.
[12:14] <wgrant> It's difficult, because Launchpad bug filing requires that the user has an account.
[12:14] <rowinggolfer_> I would like to compile the information I need, and offer the user the opportunity to file it.
[12:14] <rowinggolfer_> wgrant - ah.. ok.
[12:14] <rowinggolfer_> could I register a user for the application itself?
[12:14] <wgrant> You could, but that sounds more than slightly crazy.
[12:15] <rowinggolfer_> why?
[12:15] <rowinggolfer_> and perhaps I am :(
[12:15] <wgrant> Because then users cannot receive notifications about updates to the bug, they cannot provide more information, they can do bad things with the account...
[12:16] <rowinggolfer_> ok.
[12:16] <rowinggolfer_> bug the bug report could include contact details for them.
[12:17] <rowinggolfer_> and TBH - I may have to encrypt the information sent occasionally.
[12:17] <rowinggolfer_> I was thinking about public/private key crypto there.
[12:17] <rowinggolfer_> but, I am just at the planning stage TBH.
[12:19] <rowinggolfer_> but I am "community building"... I want these bugs published.
[12:19] <rowinggolfer_> otherwise my co-developers have nothing to do :(
[14:26] <Lukas> hi there. could anybody help with translations feature in launchpad? I'm stuck
[14:27] <beuno> maybe dpm_ is around?
[14:27] <dpm> Lukas: please, just ask your question :-)
[14:28] <dpm> and then we can try to give you a hand
[14:28] <Lukas> I'm trying to force launchpad to load my POT file which I pushed into repository but no success
[14:28] <dpm> Lukas: which project is it?
[14:28] <Lukas> i anebled it in "Automatic synchronization" but it still says "This project is currently not using any synchronization with bazaar branches."
[14:29] <Lukas> https://translations.launchpad.net/timesheets/1.x
[14:30] <dpm> danilos: jtv was telling me this morning that due to the auto-approver problem imports had been disabled, do you think the problem he is having ^ is caused by that?
[14:38] <dpm> Lukas: independently of the problem there might be with imports, I would recommend you changing the name of the generated template to something more descriptive than messages.pot. I'm guessing that you are using 'messages' as the translation domain as well, which is the default domain gettext looks for when loading translations (http://www.gnu.org/s/libc/manual/html_node/Locating-gettext-catalog.html)
[14:39] <dpm> Lukas: I'd recommend using 'timesheets' as the translation domain in the application and timesheets.pot as the template name
[14:46] <Lukas> dpm: ok, will change it
[14:48] <Lukas> dpm: one more thing? What exactly does this message say and can it be the cause of my problem? "This series does not have an official Bazaar branch. Set it now!"
[14:58] <dpm> Lukas: let me have a look...
[14:58] <froud> Hi, when I do bzr push to launchpad I get bzr: ERROR: Transport operation not possible: http does not support mkdir()". What am I missing?
[15:01] <dpm> Lukas: you probably have to link your branch to the 1.x series. I believe you can just go to https://launchpad.net/timesheets/1.x/+linkbranch and enter your bzr branch there
[15:02] <james_w> froud: what command are you using to push?
[15:05] <dpm> Lukas: also remember that you can also have translations automatically committed to a bzr branch of your choice (see 'Export translations to branch' in https://translations.edge.launchpad.net/timesheets/1.x/+translations-settings)
[15:07] <dpm> Lukas: this -> http://blog.launchpad.net/translations/screencast-exporting-translations-to-a-bazaar-branch and this -> http://blog.launchpad.net/translations/screencast-importing-translation-templates-from-a-bazaar-branch might also be useful
[15:08] <froud> james_w: bzr push lp:
[15:08] <james_w> froud: what does "bzr lp-login" say?
[15:09] <froud> james_w: bzr push lp:~development-prepaidmeters/utiliflex/trunk
[15:13] <froud> james_w: okay fixed have to configure bazaar with launchpad id
[15:22] <lxp> hi
[15:23] <mvo> hello! is there a way to rename a project from http://launchad.net/foo to http://launchpad.net/bar ?
[15:24] <beuno> mvo, you need to file a question, and an admin will do it
[15:24] <lxp> i have forgotten my launchpad password
[15:24] <mvo> beuno: cool, many thanks
[15:24] <lxp> but the passwort recovery asisstent always says "Your account details have not been found. Please check your subscription email address and try again."
[15:25] <mvo> beuno: a question against launchpad -general? or a specific component of it?
[15:25] <lxp> launchpad general
[15:25] <mvo> thanks again
[15:25] <lxp> if i try to reregister i get "The email address<EMAIL_ADDRESS>is already registered"
[15:34] <Lukas> dpm: i changed the domain to "timesheets" Now I should place the timesheets.pot to /timesheets folder? (/timesheets/timesheets.pot)
[15:35] <dpm> Lukas: it doesn't actually matter what the name of the folder containing the template is (in GNOME and GNU projects it is customary to use po/templatename.pot) timesheets/timesheets.pot is fine
[15:50] <Lukas> dpm: now, everything should be commited and set up correctly. what if no record appears in the queue in upcoming 15 miutes?
[15:51] <Lukas> do you have an idea whether the functionality works or not at the moment?
[15:51] <Lukas> dpm: do you have an idea whether the functionality works or not at the moment?
[15:53] <dpm> danilos, henninge or Ursinha: are imports active again? ^
[15:53] <henninge> I thought they were ...
[15:55] <dpm> Lukas: then wait for some minutes and if nothing has happened just ping us again (henninge: how long do roughly bzr pot imports take to appear in the queue after commit?)
[15:56] <danilos> dpm: jtv said he was going to re-enable them, but only later today after we rollout a fix
[15:56] <Lukas> dpm: i asked my college to assign a series to a branch and now the settings states "Translations are imported with every update from branch lp:timesheets. "   Hope that this will solve the problem. Thanks for your tips.
[15:56] <danilos> dpm: oh, imports should be running for everything but ubuntu, if I understood the situation correctly
[15:57] <dpm> danilos: ah, then it might not have been a problem at all in that particular project. He's committed a new template and I guess he should just wait a bit for it to appear in the imports queue
[15:58] <henninge> dpm, Lukas: commit-to-queue time should be no longer than 30 to 60 minutes.
[16:00] <dpm> thanks henninge
[16:04] <dpm> Lukas: the template has just appeared in the imports queue -> https://translations.edge.launchpad.net/timesheets/1.x/+imports , but the path is not timesheets/timesheets.pot as you mentioned, but messages/fr/LC_MESSAGES/timesheets.pot. Could you fix that? Or is there anything in your project or your build system that needs the path to be like that?
[16:07] <Lukas> dpm: yes it's there, finally. This path is required by PHP implementation of gettext. At least it works when the .mo file is under this path and I wanted to keep the .pot file with .po, .mo files. Is it a problem?
[16:11] <dpm> Lukas: it is not a problem in Launchpad (the template has just been imported), but only a recommendation for good practice :-). The template really doesn't belong to the fr/LC_MESSAGES folder, since it is not a French translation. And I think you won't be able to keep the POT file with the MO files, since for other languages they will be installed in xx/LC_MESSAGES/timesheets.mo
[16:13] <Lukas> yeah, you
[16:14] <Lukas> dpm: yeah you're right, it should be /messages/timesheets.pot instead of /messages/fr/LC_MESSAGES/timesheets.pot
[16:15] <Lukas> dpm: if I move it and commit it again and import it again what should I do with the old template having been already imported?
[16:18] <dpm> I'm afraid I'll have to ask someone else :) henninge, what's the best thing to do in these cases? ^^ (bzr commit of template to a wrong path, import - now would like to change the path and re-import)
[16:19] <Lukas> dpm: i should perhaps set status to Deleted and import the new one..
[16:21] <dpm> Lukas: let's wait a few minutes if Henning can give us an answer ^
[16:29] <henninge> dpm, Lukas: just do "bzr mv" and push the file. If the template name stays the same, the path is updated in Launchpad.
[16:30] <Lukas> henninge: cool, thanks
[16:30] <henninge> Lukas: yeah, if it's "brz mv messages/fr/LC_MESSAGES/timesheets.pot messages/timesheets.pot" the template name is unchanged and it will pick up on the new path.
[16:37] <Lukas> thanks all, have a good day/night :-) bye
[16:56] <zul> how do you disable the redirection for edge testing?
[16:56] <beuno> zul, it lets you do so on the bottom of the page
[16:56] <zul> thanks
[17:00] <pro-rsoft> I've just uploaded a package using dput, but it doesnt appear on my ppa page.
[17:00] <pro-rsoft> what could be the problem?
[17:00] <bigjools> pro-rsoft: did you sign the upload with a key in your Launchpad account?
[17:01] <pro-rsoft> uhm, the key might not be in my lp account
[17:01] <pro-rsoft> will it appear when I do add it?
[17:01] <bigjools> Launchpad doesn't email if it doesn't know the key, to save the spam
[17:01] <bigjools> pro-rsoft: you need to add the gpg key and re-upload
[17:02] <bigjools> dput -f, as dput will think you already uploaded it
[17:04] <pro-rsoft> kay, thanks
[17:11] <froud> When I try bzr lp-login I always get No Launchpad user ID configured. despite having done bzr lp-login my-id
[17:12] <froud> But when I run bzr lp-login my-id it returns
[17:12] <froud> bzr: ERROR: https://launchpad.net/%7ESean/%2Bsshkeys is permanently redirected to https://launchpad.net/~sean/+sshkeys
[17:13] <pro-rsoft> bigjools, okay, I added my gpg key and reuploaded the package, but it still doesnt appear on my ppa page
[17:13] <froud> I uploaded the public key to lp
[17:13] <bigjools> pro-rsoft: how long ago did you upload?  it can take a few minutes to appear
[17:13] <pro-rsoft> just yet
[17:14] <pro-rsoft> or do I need to sign the CoC too?
[17:14] <bigjools> you'll get a rejection email if there's any problem, and your gpg key is good
[17:15] <pro-rsoft> okay
[17:16] <pro-rsoft> Ah, I got a reject mail indeed. thanks
[17:16] <bigjools> great, CoC?
[17:17] <pro-rsoft> naw, an error in my changelog file
[17:21] <pro-rsoft> How do I create a package for multiple distros?
[17:21] <pro-rsoft> should I create multiple changelog files, one for jaunty, karmic, etc?
[17:35] <pro-rsoft> is there support for building on ARM?
[17:37] <bigjools> pro-rsoft: for multi series, you can either upload different versions for each, or upload for the oldest series and once it's build you can "copy" it (promote it) to the new series
[17:37] <bigjools> no ARM support, it's i386, amd64 and lpia
[17:38] <pro-rsoft> ah, okay. thanks
[17:38] <pro-rsoft> looks like my package got accepted now
[17:40] <pro-rsoft> say, if I wanted to have a package in the official ubuntu repos, and it got accepted, how would that work? would I add it to my ppa, and would it then be promoted or so?
[17:41] <bigjools> you would need to get a MOTU to sponsor you, PPAs don't help much in that regard.
[17:41] <pro-rsoft> oh, ok.
[18:03] <froud> anyone around who can give commercial customer support for launchpad
[18:03] <beuno> froud, maybe bac is still around
[18:03] <beuno> froud, are you an existing customer?
[18:03] <bac> here i am
[18:04] <bac> what's up froud?
[18:04] <froud> bac: yes
[18:04] <froud> been so since +7 hrs and cannot get baz setup
[18:04] <froud> maybe I'm having a bland day
[18:05] <froud> s/bland/blond
[18:05] <bac> froud: what is the project name in LP?
[18:06] <froud> Utiliflex
[18:07]  * froud is asking bac for DCC
[18:10] <RenatoSilva> https://launchpad.net/moin-solenoid/+milestone/rc-2009.6.3/+delete
[18:10] <RenatoSilva> Error ^: (Error ID: OOPS-1364A2948)
[18:13] <RenatoSilva> Currently I don't maintain any old versions of my project, because new versions don't behave that much different. I apply bug fixes to new versions, and the recommendation is to update to the latest version.
[18:13] <RenatoSilva> So the question is: should I leave old versions available for download?
[18:14] <RenatoSilva> I want to remove old versions, so what do I do? a) remove download file b) remove release from milestone 3) remove milestone??
[18:30] <pro-rsoft> What does this lintian error mean?
[18:30] <pro-rsoft> E: squish source: version-substvar-for-external-package libsquish-dev -> squish
[18:31] <pro-rsoft> oops, my bad. please hit me with the largest object you can find.
[18:31]  * beuno goes find a desk
[19:17] <kfogel> james_w: got a sec to chat about launchpadlib packaging?
[19:17] <james_w> I do
[19:18] <kfogel> james_w: You probably saw my thread from a while back about the madness of trying to use bleeding-edge launchpadlib :-).  I guess I want to start with a very open-ended question: what's our state of the onion right now?  How far behind is latest-released launchpadlib from trunk-launchpadlib, and how hard is it to run trunk if someone wants to?
[19:18] <james_w> kfogel: I believe it is "not very far"
[19:18] <james_w> I may be wrong though
[19:18] <kfogel> james_w: not very far behind?
[19:18] <james_w> I think the trunk switched as so I'm not subscribed any more
[19:18] <james_w> yeah
[19:19] <hax404> where can i change my E-Mailadress in my launchpad-account?
[19:19] <james_w> let me dig up your thread
[19:19] <kfogel> james_w: bac was telling me today that login stuff had been moved into launchpadlib, but that version hasn't been released (or at least not packaged) yet.
[19:19] <james_w> login stuff?
[19:21] <bac> hax404:  go to https://launchpad.net/people/+me
[19:21] <bac> hax404: click on the yellow 'edit' icon next to the 'Email' heading
[19:21] <kfogel> james_w: I should confess I'm not a big launchpadlib expert -- I'm not keeping up with latest (partly because I can't :-) ).
[19:21] <kfogel> james_w: bac might know more, and he's right here.  bac?
[19:22] <james_w> that's ok, I'm going straight to the source
[19:22] <bac> james_w: a new method called 'login_with' was added to the Launchpad class.  it makes it easier to manage credentials
[19:22] <james_w> oh, that was a couple of months ago wasn't it?
[19:22] <bac> james_w:  a lot of the scripts we want to distribute use this method
[19:22] <bac> james_w: yes, it has been a pretty long time
[19:22] <james_w> we're missing the last 4 revisions of lp:launchpadlib in karmic
[19:23] <james_w> that's PROD_SERVICE_ROOT or whatever it is called
[19:23] <james_w> contents on the API documentation
[19:23] <james_w> "move samples -> contrib and add pertinent scripts from lp-dev-utils to that directory"
[19:23] <james_w> "Add contrib/lp-bug-ifier.py"
[19:23] <james_w> so only one little bit of API missing it seems
[19:25] <james_w> kfogel: do you have a subject for your thread?
[19:25] <james_w> I can't seem to find it
[19:25] <bac> james_w: r37 are the good bits
[19:25] <james_w> yeah, that's in karmic
[19:25] <bac> james_w: excellent
[19:25] <kfogel> james_w: one sec
[19:26] <james_w> I'm asking as I think the problem you had is now fixed, which should make things easier
[19:26] <bac> Solving the launchpadlib packaging mess.
[19:27] <bac> 8/14/09 on the internal list
[19:27] <kfogel> james_w: "Solving the launchpadlib packaging mess."
[19:27] <kfogel> oh
[19:27] <kfogel> bac was there ahead ofme
[19:27] <james_w> ah
[19:27] <james_w> I'm not on that list
[19:27] <james_w> I think we discussed it on IRC though
[19:28] <bac> kfogel: i'm going afk for an hour.  let me know if you need me to follow up on this
[19:28] <kfogel> bac: thanks.
[19:29] <kfogel> james_w: I'll give you a URL, one sec
[19:30] <kfogel> james_w: https://lists.ubuntu.com/mailman/private/canonical-launchpad/2009-August/thread.html
[19:30] <kfogel> james_w: frankly it could have been a public thread, I don't know why I didn't post out here.
[19:30] <james_w> no dice
[19:30] <kfogel> james_w: no password?
[19:31] <james_w> correct
[19:31] <james_w> https://pastebin.canonical.com/20826/
[19:31] <james_w> grep to the rescue
[19:31] <kfogel> heh
[19:31] <james_w> http://irclogs.ubuntu.com/2009/08/05/%23launchpad.html
[19:31] <kfogel> let's just get you the thread, that's what's really needed here
[19:31] <kfogel> one sec
[19:32] <james_w> so yes, that immediate error is no more
[19:32] <james_w> so you should at least be able to install from source now
[19:39] <kfogel> james_w: if one can install latest source now, that is a HUGE win.
[19:39] <james_w> so, I share your misgivings about installing from source (unsurprisingly)
[19:39] <kfogel> james_w: I'll try it.  And I'm on a debian box at the moment, as it happens (usually am on Ubuntu), so this will be a good test.
[19:39] <james_w> but the recent fixes should at least make it possible
[19:40] <kfogel> james_w: Oh, I have no objection to installing from source for myself.  I just don't think it's a reasonable mass distribution strategy :-).
[19:40] <james_w> if it doesn't then I consider it a python tool issue
[19:40] <james_w> but if the packaging gets in the way somehow I can look at fixing it
[19:40] <james_w> as for packaging in Ubuntu
[19:40] <james_w> I will update to new releases each cycle
[19:41] <james_w> we can SRU critical fixes in to old releases
[19:41] <kfogel> james_w: Are we good for Karmic?
[19:41] <james_w> and we could look at backports if you want a supported option for "new version on old release"
[19:41] <james_w> yeah, karmic is good, we have the latest released version
[19:42] <james_w> if you think we should have a newer version then you haven't indicated that by actually, you know, releasing it
[19:42] <james_w> though someone asked me about cherry picking in the stable service_root change to make it easier to run scripts against production
[19:42] <james_w> which I may pursue after beta
[19:43] <james_w> we could also set up a "launchpadlib" PPA for distribution to interested Ubuntu users
[19:43] <CarlFK> is there a way to search lp ppa's ? like i am looking for ffmpeg
[19:43] <beuno> CarlFK, https://launchpad.net/ubuntu/+ppas
[19:43] <james_w> and a automated tip PPA to make it easier to run trunk
[19:44] <james_w> but for the issue of wanting to use new features that some people don't have, it's not a new issue
[19:44] <CarlFK> beuno: yay.  thanks.
[19:44] <james_w> so, suck it up, and don't use new features unless you have to
[19:44] <james_w> does that make sense?
[19:44] <bigjools> CarlFK: also visit https://launchpad.net/ubuntu/+source/ffmpeg and click the green expander at the bottom of the page
[19:45] <CarlFK> beuno: woah... very nice.
[19:45] <bigjools> beuno: talking of which, can you see the problem with the 2-column dl on that page?
[19:46] <beuno> bigjools, that make seems to need to use a different template?
[19:46] <beuno> to use up the whole page?
[19:46] <CarlFK> fantastic:  4:0.5+svn20090924-0ubuntu0~ppa2   (22 hours ago)
[19:47] <bigjools> beuno: I don't understand you
[19:47] <bigjools> beuno: I am talking about the package information section
[19:48] <bigjools> if the <dd> at the top left has a slightly larger than normal icon it seems to push the <dd> below it down
[19:48] <beuno> bigjools, ah
[19:48] <beuno> I see
[19:48] <beuno> it needs to format this differently
[19:48] <bigjools> I've seen it on a few pages, not just the DSP
[19:49] <beuno> yeah
[19:49] <beuno> sinzui just enlightened me
[19:49] <bigjools> oh good job getting rid of the disgusting grey background on the sidebar BTW
[19:50] <beuno> :)
[19:50] <beuno> it was all thanks to jml's wierd color settings that I saw it
[19:51] <bigjools> ah jml is weird for sure
[19:56] <fabrice_sp> Hi. With the new interface, how is it possible to see the log of changes made in a bug report?
[20:03] <maxb> urgh
[20:03] <maxb> fabrice_sp is right - where's the link to /+activity gone?!
[20:03] <pro-rsoft> my package build had a build error, so I tried to dput a fixed version of the source package. But it keeps getting rejected. What should I do?
[20:04] <maxb> What is the rejection reason?
[20:06] <pro-rsoft> already existed
[20:06] <pro-rsoft> "file X already exists in Y, but uploaded version has different contents"
[20:08] <RenatoSilva> when I create a bug based on a question, will the reporter be who asks or me?
[20:08] <maxb> pro-rsoft: It is not possible to reupload different contents for the *same* version. You must increase the version.
[20:09] <maxb> I have filed bug 436818 on fabrice_sp's observation
[20:09] <pro-rsoft> maxb, ok, thanks
[20:46] <quentusrex> keyserver.ubuntu.com down???
[21:07] <resolve> hi folks. I have a problem - http://pastebin.com/m48f97c4a
[21:07] <resolve> is crowberry supposed to hang on to the lock for that long?
[21:07] <resolve> and why can't I break it?
[21:08] <resolve> to answer my second question, replacing the text with 'lp:projname' seems to break the lock
[21:43] <jbuncher> Anyone here?  Launchpad seems broken, I can't report a bug.  Clicking on "report a bug" takes me to https://help.ubuntu.com/community/ReportingBugs  Is anyone else experiencing this?
[21:46] <ScottK> jbuncher: If it's an Ubuntu bug you are trying to report, that's on purpose.  The page tells you the preferred way to report bugs.
[21:49] <jbuncher> ScottK:  that's fairly maddening, but ok.  Plenty of bugs/wishlist items don't have apps that are running, and using ubuntu-bug seems like overkill.
[21:51] <jbuncher> ScottK:  What would be your recommended action for filing a but/wishlist agaist a package that no longer exists in karmic?  (libstdc++5 to be specific, plenty of proprietary binaries still depend on it, so it'd be nice if it was at least available in universe so that it wouldn't prevent upgrades to karmic)
[21:54] <jbuncher> Ok, I'm attempting to file it using "ubuntu-bug libstdc++6", but it won't load firefox and is crashing with some kind of window error.
[22:19] <ScottK> jbuncher: I've no idea.  I'm not a proponent of this change, just an observer.  I'd ask in #ubuntu-bugs.
[22:20] <czajkowski> any idea who i can ask about the uds spoonsorship page submitted but getting message waiting for login.launchpad.net transgering from summit.ubuntu.com
[22:20] <czajkowski> i think it's submitted
[22:20] <czajkowski> but not sure
[22:20] <czajkowski> *transfering
[22:20] <ScottK> czajkowski: PM jacastro and ask him to check.
[22:20] <czajkowski> ScottK: thanks
[22:20] <ScottK> Generally it's OK, but he can make sure (known bug)
[22:20] <ScottK> You're welcome.
[22:21] <jbuncher> ScottK:  Thanks for the info.
[22:21] <ScottK> jbuncher: You're welcome.
[22:22] <czajkowski> ScottK: that's a special bug
[22:29] <kfogel> beuno: I'm trying to update the description for bug #436888, but after I hit the green checkmark to submit my edits, it spins forever and I get a pink rectangle around the text field, with this message in tiny font at the bottom:
[22:29] <kfogel> Linking a branch to a bug report doesn't show the new link until you refresh the branch page.
[22:29] <kfogel> CancelOk
[22:29] <kfogel>    1. Launchpad itself
[22:29] <kfogel>    2. Bugs
[22:29] <kfogel>    3. Bug #436888
[22:29] <kfogel> Affects 	Status 	Importance 	Assigned to 	Milestone
[22:29] <kfogel>
[22:29] <kfogel> Launchpad itself Edit
[22:29] <kfogel>
[22:29] <kfogel> New
[22:29] <kfogel>
[22:29] <kfogel> Undecided
[22:30] <kfogel>
[22:30] <kfogel> Unassigned Edit
[22:30] <kfogel>
[22:30] <kfogel> Affecting: 	Launchpad itself
[22:30] <kfogel> Filed here by: 	Karl Fogel
[22:30] <kfogel> When: 	15 minutes ago
[22:30] <kfogel> Project
[22:30] <kfogel> (Choose…)
[22:30] <kfogel> Status 	Importance 	Milestone
[22:30] <kfogel>
[22:30] <kfogel>
[22:30] <kfogel> Assigned to
[22:30] <kfogel> 	Nobody
[22:30] <kfogel> 	Me
[22:30] <kfogel>
[22:30] <kfogel> (Choose…)
[22:30] <kfogel> Comment on this change (optional)
[22:30] <kfogel> Also affects project Also affects distribution Target to release
[22:30] <kfogel> This bug affects me too Edit This bug affects me too Edit
[22:30] <kfogel>
[22:30] <kfogel> Bug Description
[22:30] <kfogel> I was on this branch page:
[22:30] <kfogel>   https://code.edge.launchpad.net/~kfogel/launchpadlib/426323-apidoc-html-title-attrs
[22:30] <kfogel> and clicked "Link to a bug report" to link it to bug #426323. After I entered the bug number and hit Return, I was left at the branch page, and the link now said "Link to another bug report" -- however, the actual link to the bug, which should have been right above that, was not present! Only after I reloaded the branch page did that link show up (the one with the bug icon next to it and the summary of the bug as the link text).
[22:30] <kfogel> I don't know if it's important that this was the first time this branch had been linked to any bug report. I'll test by linking that same branch to *this* bug after I submit, and linking a fresh branch to this bug. More in a moment.
[22:31] <kfogel>  CancelOk
[22:31] <kfogel> Entity-body was not a well-formed JSON document.
[22:31] <kfogel> aaaaaaaaaaaaaaaaaaargh
[22:31] <kfogel> beuno: let me try that again:
[22:31] <kfogel> beuno: I'm trying to update the description for bug #436888, but after I hit the green checkmark to submit my edits, it spins forever and I get a pink rectangle around the text field, with this message in tiny font at the bottom:
[22:31] <kfogel> "Entity-body was not a well-formed JSON document."
[22:31] <ScottK> kfogel: Known issue
[22:31] <ScottK> kfogel: Add /+edit to the url to get the non-ajax edit form.
[22:31] <kfogel> ScottK: the unable-to-edit-a-bug-description is a known issue?
[22:31] <ScottK> Yep.
[22:31] <kfogel> ScottK: thanks
[22:31] <ScottK> Apparently that's not a critical feature for a release.
[22:42] <kfogel> ScottK: sheesh.  I went to link a branch to a bug, and ran across *three* bugs in that process of doing that, one of which (the edit description bug) was already known.  The other two are now filed.
[22:43] <ScottK> Don't get me started.
[22:55] <solrize> suddenly filebug-advanced doesn't work any more, it always goes to the kiddie interface now.  what happened???
[22:56] <gmb> solrize: We removed +filebug-advanced; you can now do anythign you could do thorough that page on the main page, provided you have the right permissions.
[22:57] <solrize> huh?  how?  thanks
[22:58] <gmb> solrize: There's an "Extra options" section of the page that drops down, just about the submit button (on the second page). In there you can set importance, status, assignee and tags, depending on the permissions you ahve. You can also add an attachment.
[23:00] <solrize> i'm trying to figure out how to get to that screen without going through the search step
[23:02] <gmb> solrize: You have to go through the search step.
[23:02] <gmb> solrize: (We're working on making the search results load asynchronously, which will reduce your load times and stop timeouts from being as much of an issue.
[23:04] <solrize> gmb, the search step is a useless pain in the neck, i'm one of the maintainers of this program, i get email notifications of every bug, lots of times i file bugs against features that i implemented 5 minutes ago and i KNOW there will be no useful search hits
[23:05] <solrize> can the bypass url please be put back pleeeease?
[23:05] <gmb> solrize: No.
[23:05] <gmb> solrize: But
[23:05] <gmb> You can just put a meaningless term in the search box on the first step
[23:05] <gmb> And then correct it.
[23:05] <gmb> On the second step.
[23:05] <solrize> gaaah.
[23:05] <solrize> is there a bug filing API so i can bypass the web interface completely?
[23:06] <gmb> solrize: Yes. https://help.launchpad.net/API
[23:06] <solrize> thanks
[23:55] <uni4dfx> why does launchpad redirect me to the wiki when i try to report a bug?
[23:55] <ScottK> uni4dfx: Because of the reasons explained on the wiki page.
[23:56] <uni4dfx> i have an account, i just don't wanna use the ubuntu-bug thing
[23:59] <uni4dfx> fine, i won't report any more bugs


[16:14] <bac> jcsackett: ping
[16:16] <bac> jujugui can someone near jcsackett poke him?
[18:06] <lazyPower> jcsackett: I'm silly. I pulled my workspace from home and re-deployed and I must have remembered incorrectly. I saw the same behavior peter demonstrated.
[18:06] <lazyPower> so, apologies for the false positive.
[18:31] <jcsackett> lazyPower: all good. i'm actually a little relieved that it doesn't work, since that at least comports with my notion of reality. :p
[20:56] <bac> jcsackett: cw review? https://code.launchpad.net/~bac/charmworld/add-annotations-back/+merge/217823  old school.
[20:57] <jcsackett> hiya.
[21:01] <jcsackett> bac: lgtm, with one idea for a slightly cleaner approach to checking extra_data.
[21:16] <bac> thanks jcsackett. nice suggestion
[21:20] <jcsackett> yw
[22:16] <bac> jcsackett: https://docs.google.com/a/canonical.com/document/d/1BenQuD_mN-OotNE84_Axt_mWuCS76no1EsuFwvuZE-M/edit#


[07:38] <davidcalle> Morning o/
[07:43] <popey> yo
[14:55] <popey> pleia2: knome have asked IS to re-use https://launchpad.net/~ubuntu-community-wiki-editors (given it already exists and has knome as an admin) for wiki editorship. We can add admins to that as appropriate.
[14:55] <popey> Made sense to re-use that as it's already used for that purpose, rather than make a whole other team
[15:37] <pleia2> popey: please don't, that's a special team that the documentation team has a process for joining
[15:38] <pleia2> it allows rename and delete, which are admin tasks that we don't grant to everyone
[15:39] <pleia2> edits aren't recoverable, so we really, really need to trust the folks we give that admin power to
[15:40] <pleia2> s/edits/deletes
[15:41] <popey> ah
[15:41] <popey> bum
[15:42] <popey> sorry
[15:42] <pleia2> it's ok, I guess I was unclear, I thought we had discussed creating a new team
[15:42] <popey> will let them know
[15:42] <pleia2> thanks
[15:42] <popey> we did, and i requested that, but they found that one and it seemed good, no worries, we'll get there  😃
[15:44] <pleia2> if you read the description of that launchpad team it links to joining criteria, which we've been pretty strict about (which is why there are only 7 members :))
[15:45] <pleia2> and now, off to work!
[15:45] <popey> o/
[16:25] <knome> popey, what exactly would be the criteria to join this new group?
[16:27] <knome> people have suggested that the requirement level would be something between the ubuntu membership and the ubuntu-etherpad team membership, and that sounds about right, but leaves a lot of space for interpretations
[16:27] <popey> I think we can work that out, but basically someone who is looking to become a member (because this blocks them) or someone who has some obvious track record of contribution
[16:27] <popey> yes
[16:27] <popey> +100
[16:30] <knome> what we should do is to get as many sensibly moderated contributor teams as subteams...
[16:30] <knome> for example, the xubuntu team very moderated, and there's no reason why everybody there shouldn't get the edit permissions
[16:31] <knome> and by adding subteams we ultimately help ourselves with individual moderation
[16:31] <knome> but of course, this can't be "every team there is" as it would again open up a lot of possibilities for spammers to be included
[16:40] <popey> I would be exceptionally cautious of adding _any_ team at all to this one.
[16:41] <popey> At least to start.
[16:41] <popey> Given ~ubuntumembers and ~canonical are on it.
[16:42] <knome> my gut feeling says any team that grants upload permissions to the archive should be safe to include at least...
[16:43] <popey> Perhaps. Some careful thought needed. Maybe we should make an etherpad with a list we think might be useful.
[16:43] <popey> Need to be super careful that they're all teams that people can't self-join or coerce people to join
[16:43] <popey> I agree ones like core dev which are quite nailed down seem like good candidates
[16:43] <knome> indeed, all the teams included should be moderated
[16:44] <knome> and not only moderated technically, but socially too
[17:25] <pleia2> czajkowski: glad I'm not the only one doing two talks about ubucon eu :)
[17:25] <pleia2> s/about/at
[17:37] <tsimonq2> pleia2: you are going to UbuCon Europe? \o/
[17:39] <pleia2> tsimonq2: yes :)
[17:39] <tsimonq2> pleia2: I hope to be there too :)
[17:39] <pleia2> great
[17:46] <popey> yay
[17:53] <popey> Looking forward to that, a bunch of people are going
[17:53] <popey> a bunch of /cool/ people are going
[17:53] <popey> and me!
[17:54] <pleia2> haha popey <3
[17:55] <popey> might get an opportunity to go out for one of those beers I saw photos of in your stream recently pleia2 :)
[17:56] <pleia2> \o/
[17:56] <pleia2> the only time I've been to germany I was on schedule to get my gallbladder removed so I couldn't drink D:
[17:57] <Kilos> ouch
[17:57] <pleia2> it was indeed sad
[17:57] <pleia2> but I did learn that darmstadt had a booming in house root beer brewing trend, so that was nice :)
[17:57] <Kilos> hehe
[17:59] <popey> ooooooo
[17:59] <popey> i looooove root beer
[18:02] <wxl> i quit alcohol but i adore a good handcrafted soda
[18:02] <wxl> i got this caramel cola the other day that was sublime
[18:03] <pleia2> that does sound interesting
[18:04] <wxl> http://www.amazon.com/Retro-Brownie-Caramel-Cream-Root/dp/B009YN8BQO%3FSubscriptionId%3DAKIAILSHYYTFIVPWUY6Q%26tag%3Dduckduckgo-d-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3DB009YN8BQO
[18:05] <wxl> ugh come on amazon
[18:32] <popey> oooh
[18:38] <popey> There's a few people in the Ubuntu community who are fans of boutique colas. ikonia and directhex spring to mind
[18:40]  * wxl creates ~ubuntu-soda-jerks
[18:40] <wxl> (not really)
[19:18] <tsimonq2> XD
[19:18] <tsimonq2> wxl: ever have bacon soda?
[21:01] <tsimonq2> popey: could somebody with access clarify http://community.ubuntu.com/contribute/support/irc/ to indicate that #ubuntu-us isn't used pretty much at all anymore?
[21:07] <popey> probably someone in the US should confirm that
[21:08] <knome> pleia2?
[21:09] <tsimonq2> wxl: can you confirm the above?
[21:10] <popey> I would imagine a brief look at the logs would reveal that :)
[21:11] <popey> (if it was logged)
[21:11] <knome> but it isn't :P
[21:11] <tsimonq2> I have logs
[21:11] <wxl> i didn't even know it was a thing
[21:11] <tsimonq2> wxl: yeah, I thought the US team was one thing at one point?
[21:12] <wxl> yeah well so were a lot of things :)
[21:12] <tsimonq2> :)
[21:12] <tsimonq2> wxl: so would it be safe to say that we should NOT recommend it?
[21:13] <tsimonq2> like on http://community.ubuntu.com/contribute/support/irc/
[21:13] <wxl> i think it might be wise, but i don't know
[21:41] <pleia2> knome: people come by about twice a year to ask for help with their state-based loco, so I keep it open and lurk in there, but the project itself isn't proactively doing work anymore
[21:41] <pleia2> and it's not a general support channel, it's specific to loco work
[21:51] <knome> mhm
[21:51] <knome> isn't the idea of loco support a different language anyway
[21:51] <knome> well, mostly..
[21:57] <popey> not really
[21:57] <knome> the support aspect of it
[21:57] <popey> the uk loco is mostly offtopic, and a bunch of support from known people and randoms
[21:58] <popey> for some reason international people find the uk loco channel very easily and get support there
[21:58] <popey> we often point them at #ubuntu of course
[21:58] <popey> but our loco does a fair amount of support
[21:58] <knome> i understand that there are some potential local(e) issues, but for the most part, it's just normal questions in the local language
[21:59] <popey> i guess uk is different because en_gb..
[21:59] <knome> sure; what i mean that the main reason to point people to say #ubuntu-fr is the support in french
[21:59] <knome> so if somebody comes asking for help in #ubuntu in english, there is no real need to point them to the UK channel even if they are from the uk...
[22:00] <popey> indeed
[22:00] <knome> so that's probably why #ubuntu-us isn't high traffic :)
[22:00] <knome> at least partly...
[22:00] <knome> especially as there are those state channels
[22:01] <knome> it's kind of similar to #ubuntu-nordic... which is REALLY quiet