[00:06] <maxb> extended downtime :-(
[00:06] <wgrant> lpnet is OOPSing constantly, too. But edge is OK.
[00:12] <maxb> The read only mode has an interesting side effect. "Max Bowsher does not use Launchpad", apparently
[00:13] <wgrant> Yeah, that happened last time too.
[00:13] <wgrant> But not the time before.
[00:34] <Cleo> hmm, the new Launchpad bug viewing page renders funny for me, the right sidebar is forced all the way to the bottom, below comments, although still on the right
[00:36] <CarlFK> Cleo: I saw that too, yesterday
[00:36] <Cleo> I see it has been reported as bug #497209
[00:38] <poolie> did launchpad go down again?
[00:38]  * poolie looks
[00:38] <poolie> oh, r/o rollouts
[00:42] <sproaty> is translations email down? been waiting 20 mins
[00:52] <vadi2> Why do I have to re-upload my sources for each Ubuntu release I want to build in my PPA?
[00:59] <xnox> Because all binaries are stored in one APT pool (one directory) and they would have the same name then and hence next build would override the results of the previous one
[01:03] <persia> Reading backscroll, I notice that bug 497209 is a duplicate of 493518.  Unfortunately, I don't seem to be able to mark it as such.  Anyone with permission want to fix that?
[01:04] <spm> persia: done
[01:04] <maxb> What permissions would that require?
[01:05] <spm> no idea; but I have rubber ducky :-)
[01:05] <spm> probably part of the bug team contacts whatsit
[01:06] <maxb> yeah, I'm just wondering whether this would be a bug - I thought anyone could dup/undup bugs that they can see
[01:06] <wgrant> Anyone can...
[01:06] <spm> oh I see. unknown to me unf. it's actually a pain in that respect - as there are no barriers for most things I do; I'm not aware of when there are for others. :-/
[01:07] <wgrant> persia: Sure you're logged in?
[01:07] <xnox> So did bzr-svn for branch imports landed with this new release?
[01:07] <spm> mwhudson: ^^
[01:08] <persia> wgrant: Ah, that was it.  Thanks for finding my issue before I'd even investigated it :)
[01:12] <maxb> "A username may not be specified in the URI." Boo
[01:12] <maxb> I was hoping the bzr-svn importer would let me import branches that require guest:guest@
[01:13] <wgrant> Have you considered asking whoever runs that repository to remove that pointless requirement/
[01:15] <maxb> tigris.org. Lame project hosting site
[01:16] <wgrant> But... don't they host svn itself?
[01:16] <wgrant> Or am I misremembering from my svn days...
[01:22] <xnox> Will existing imports use bzr-svn from now on?
[01:23] <xnox> Or do I need to request a new one?
[01:25] <wgrant> xnox: The latter. bzr-svn branches are incompatible with those produced by cscvs (the old method)/
[01:26] <xnox> Ok thanks =) I'll request new ones then. Horay!
[01:26] <xnox> Thank you to everyone who works on launchpad yet another release with hot stuff
[01:26] <xnox> can't wait for the blog entry about bzr-svn imports
[01:31] <thumper> xnox: you'll have to make sure that the urls of the old ones are changed
[01:32] <xnox> thumper: what do you mean?
[01:32] <thumper> xnox: as we check that the same url isn't imported multiple times
[01:32] <thumper> xnox: two import svn branches can't point to the same place
[01:32] <mwhudson> xnox: yes
[01:32] <xnox> oh that's fine =) i did realise that
[01:33] <xnox> the new import is created under my namespace
[01:33] <xnox> that's quite cool
[01:33] <xnox> instead of ~vcs-imports
[01:35] <xnox> Anywho submitted mine =) it's xiphos and libsword
[01:35] <xnox> lp:~dmitrij.ledkov/xiphos/trunk and lp;~dmitrij.ledkov/libsword/trunk
[01:35] <xnox> Hopefully they will be up and running soon ;-)
[01:35]  * xnox has some chocolates for bribes
[01:37] <dhillon-v10> hi all, how's everyone doing, I am one of the answer contacts for Ubuntu so I answer questions everyday, but my karma isn't updating why is that so, it also didn't record the karma from the last 3 days (not that I do it for karma, but its nice to have it)
[01:40] <mwhudson> who wants to write me an xchat plugin that makes lp: urls clickable?
[01:40]  * persia  
[01:40] <thumper> mwhudson: paste it into a code review comment, bug comment or answer comment :)
[01:40] <mwhudson> thumper: possibly a little abusive :)
[01:40] <thumper> mwhudson: perhaps we should have auto approval of bzr-svn imports?
[01:40] <xnox> mwhudson: THANK YOU =)
[01:40] <mwhudson> xnox: :)
[01:41] <mwhudson> thumper: maybe yeah
[01:41] <xnox> where shall I send chocolates to?
[01:41] <thumper> xnox: where are they coming from?
[01:41] <xnox> UK =)
[01:42] <xnox> to canonical HQ? does mwhudson work there?
[01:42] <mwhudson> nah, i'm in nz (as is thumper)
[01:42] <xnox> Right =) do you go to ubuntu UDS?
[01:42] <xnox> I'll send them there then ;-)
[01:42] <xnox> Or I'll send them to NZ if you give me address
[01:42] <xnox> for both of you to share ;-)
[01:49] <onox> how do I sign bzr revisions with a particular key?
[01:49] <mwhudson> onox: spiv tried to answer you in #bzr
[01:50] <mwhudson> onox: i think i once created a shell wrapper that did gpg -u $UID $@ and pointed gpg_signging_command at that
[01:55] <maxb> Why do code imports require approval, anyway? Would we really have a problem if they were all allowed to try?
[01:55] <mwhudson> maxb: well, apparently back in the mists of time, someone typed "svn.debian.org" into the form
[01:56] <mwhudson> maxb: and there was much unhappiness
[01:56] <maxb> Ah
[01:56] <mwhudson> maxb: also, people get it wrong a lot of the time, possibly because of the wording on the form
[01:56] <mwhudson> which i guess we should change, now we have bzr-svn
[01:58] <thumper> there was also the non-mergability of two cscvs imports of the same location
[02:01] <wgrant> Are you going to relax the trunk restriction now?
[02:01] <thumper> wgrant: for svn, yes
[02:02] <wgrant> thumper: And just hope that CVS quietly dies eventually?
[02:04] <onox> mwhudson: thx, a shell wrapper did the trick
[02:04] <mwhudson> wgrant: got a better idea?
[02:05] <wgrant> mwhudson: nope.
[02:09] <mwhudson> good
[02:09] <mwhudson> this one seems to be working ok...
[02:14] <emezeta> hi chan
[02:15] <emezeta> I'd like to do some changes on name and uri of a project
[02:16] <emezeta> Is there anybody who can help me on this?
[02:16] <emezeta> is it possible?
[02:19] <dhillon-v10> thumper, hi :D I have a lot of deactivated pgp keys, I didn't know we could export keys out so I just made a new one everytime, so now I have 4 keys in the keyserver, is it possible to remove them
[02:20] <thumper> dhillon-v10: I have no idea
[02:21] <wgrant> dhillon-v10: You can't remove them.
[02:21] <thumper> emezeta: yes, ask a question on the launchpad project
[02:21] <dhillon-v10> wgrant, so what happens now
[02:22] <wgrant> dhillon-v10: Use your revocation certificates to revoke the keys, if you have not already.
[02:22] <wgrant> That is all you can really do.
[02:22] <wgrant> You cannot remove them.
[02:23] <dhillon-v10> wgrant, I didn't make any revocation certificates sorry :) I guess I'll just live with it them
[02:23] <dhillon-v10> * then
[02:24] <emezeta> thumper: tks
[03:01] <xnox> wgrant: does soyuz now accept DebSrc3.0?
[03:01] <wgrant> xnox: The code does, the buildds do, but some machines still haven't been upgraded, so it's not enabled yet.
[03:02] <xnox> =) ok cool
[03:02] <wgrant> I don't know when those upgrades will happen.
[03:44] <persia> I've just gotten my first LP bzr merge proposal.  Can I automate the merge with LP, or do I need to grab branches and merge manually and push?
[03:45] <spiv> persia: the latter
[03:45] <persia> Will that automatically update anything in LP, or do I need to update the UI there (or do email) as well?
[03:46] <jml> persia, once you've pushed, lp will take care of it.
[03:46] <spiv> Launchpad will notice when the branch has been merged and update the merge proposal accordingly.
[03:46] <persia> Nifty.  Thanks for the explanations.
[03:46] <spiv> (And also hide the branch from default views as it will no longer have any changes outstanding)
[03:47] <spiv> (Well, assuming there are no changes outstanding vs. the development focus, but that's the usual scenario)
[03:48] <persia> I'm not sure there is a "development focus" branch.
[03:49] <persia> Do you know if there are any plans to make it so people *don't* have to pull a branch to merge?
[03:50] <mwhudson> persia: there have been plans for that since well before i started at canonical :-)
[03:50] <mwhudson> persia: too much to do....
[03:50] <mwhudson> persia: i take it you mean a "merge it!" button that you can press in the ui?
[03:50] <persia> mwhudson: That there are plans is enough.  That they aren't implemented yet is a minor detail.
[03:50] <mwhudson> (if you have edit permisssions on the target branch etc)
[03:50] <persia> Something like that.
[03:50] <mwhudson> yeah
[03:50] <mwhudson> "planned, not implemented"
[03:51] <mwhudson> well, about 15% implemented
[03:51] <persia> heh :)
[03:51] <persia> So, at that rate, another 17 years or so?
[03:53] <mwhudson> persia: sounds about right
[03:54] <persia> Likely not such a huge issue though: I imagine that most bzr merge approvers are likely to have local branches of code.
[03:55] <spiv> Right.
[03:55] <persia> And, except in corner coses, would want to download *something* to test anyway.
[03:56] <spiv> Right.
[03:56] <mwhudson> i can see how udd would have more of a use case for this
[03:56] <spiv> For bzr, we actually delegate the merging and running of tests to PQM.
[03:56] <persia> Perhaps, although for the medium terms, we can cheat with dget and dput
[03:56] <persia> And, again, except in corner cases, we'd want something local to test anyway.
[04:10] <bjsnider> i think i've got an unusual situation here
[04:11] <bjsnider> i think one of these ppa builds is just going around in circles endlessly
[04:11] <bjsnider> never seen this before, but it's been building for 3 hours
[04:11] <wgrant> Which?
[04:11] <wgrant> Maybe it's just bohrium again.
[04:12] <bjsnider> it's on shipova
[04:12] <bjsnider> https://launchpad.net/~nvidia-vdpau/+archive/testing-ppa/+build/1401374
[04:13] <bjsnider> it was building when the launchpad upgrade was applied
[04:39] <Sam-I-Am> bjsnider: heh, i had one hose up a few nights ago
[04:39] <Sam-I-Am> just kinda sat there for a few hours
[04:43] <bjsnider> did it fix itself?
[04:43] <bjsnider> did it build eventually?
[04:45] <Sam-I-Am> it finally finished
[04:45] <Sam-I-Am> took a good long time tho
[04:45] <Sam-I-Am> the machine was bohrium... as noted above... i had talked with wgrant about my issue.
[04:46] <Sam-I-Am> i didnt have to do anything tho...
[04:53] <wgrant> Sam-I-Am: "finally finished" might just mean that a sysadmin noticed and reset the builder.
[04:54] <Sam-I-Am> wgrant: also possible... although everything built fine, no failures.
[04:54] <wgrant> Sam-I-Am: When a builder disappears, the build is transparently retried without failure notification.
[04:54] <Sam-I-Am> oh, thats nice.
[04:57] <Sam-I-Am> currently rolling openldap 2.4.21 release candidate locally... testing for the openldap folks on hardy and karmic.
[04:57] <Sam-I-Am> one of these days i need to figure out how to get involved in the official backports system
[05:40] <slangasek> wgrant: ping, re: v3 source support
[05:41] <slangasek> wgrant: we seem to still not have a version of dpkg on cocoplum that works for this; is that a known outstanding item?
[05:49] <AnAnt> Hello,  a project already has a bzr branch, but I want to either create a new branch (for that project) which imports from git, or just sync from git in the current bzr branch, how can I do so ?
[05:54] <wgrant> slangasek: Before the new source formats can be enabled, dpkg needs to be upgraded on cocoplum, germanium, iron, and whichever machine generates package diffs. This is the last blocker. I do not know which of those have been upgraded, nor do I know when they will be upgraded, nor do I have access to RT to find out.
[05:56] <wgrant> slangasek: Once those are upgraded, a LOSA justs needs to fire off the SQL or Python to enable the new formats in Lucid, and then everything will work.
[05:56] <slangasek> wgrant: do you have an RT# that I can track myself? :)
[05:56] <wgrant> slangasek: I don't.
[05:57] <wgrant> Maybe spm does?
[05:57] <slangasek> wgrant: found it at the top of the queue, heh
[05:57] <spm> who sent it in?
[05:57] <wgrant> slangasek: Ah, handy.
[05:58] <slangasek> spm: bigjools; ticket #36873
[06:00] <spm> haha. sent in ~ 5 hours ago. nice. :-)
[06:00] <wgrant> Oh :(
[06:01] <spm> in any event; it's not something I can do; I'll have to leave that for when the GSAs are around.
[06:03] <AnAnt> does the launchpad translations export to branch feature work ?
[06:03] <wgrant> AnAnt: Yes.
[06:04] <AnAnt> wgrant: I select a branch to export to, yet I get an error every time I do this
[06:04] <wgrant> AnAnt: "an error"?
[06:04] <wgrant> You need to select a branch that *you*, not a team, own.
[06:04] <AnAnt> it says: invalid value
[06:04] <AnAnt> ah, ok
[06:05] <AnAnt> why is that ?
[06:05] <wgrant> I don't know.
[06:07] <jml> that's lame.
[06:08] <jml> I bet it's because it should be checking that you have launchpad.Edit permissions, and instead it's checking for equality, or something like that.
[06:14] <AnAnt> sorry, I asked a question earlier and left for a couple of mins (I thought that I would find the answer on irclogs, but found that it isn't updated yet)a project already has a bzr branch, but I want to either create a new branch (for that project) which imports from git, or just sync from
[06:14] <AnAnt> git in the current bzr branch, how can I do so ?
[06:25] <spiv> AnAnt: IIRC you can just register a new import
[06:25] <spiv> AnAnt: it doesn't matter if the project already exists and has branches.
[06:31] <AnAnt> spiv: I don't understand
[06:31] <AnAnt> spiv: there is another project where I registered a new import
[06:33] <spiv> AnAnt: ok?  I don't understand the problem then?
[06:33] <spiv> AnAnt: is it that the import is registered against the wrong project?
[06:34] <AnAnt> spiv: well, the project is called monajat, I can't register new imports there
[06:34] <AnAnt> spiv: while for another project that I added 2 days ago, I was able to register an import from Git
[06:35] <spiv> Oh, you can't simply put 'monajat' into the form at https://code.launchpad.net/+code-imports/+new ?
[06:35] <AnAnt> I'll try that
[06:37] <AnAnt> spiv: that worked, thanks
[06:39] <spiv> Cool.  I honestly have no idea what other way there is that you were trying, though!
[06:42] <AnAnt> spiv: I went to code.launchpad.net/monajat, and didn't find an import button, that was my problem
[06:43] <spiv> Ah, you should have tried just code.launchpad.net :)
[08:17] <toobaz> Hello. I have a package for "unstable" that I correctly uploaded to my ppa for Karmic thanks to suggestion in https://help.launchpad.net/Packaging/PPA/Uploading. However, it doesn't work for Lucid or Jaunty.
[08:17] <toobaz> I get "The source gpapers - 0+svn20090122-3 is already accepted in ubuntu/karmic"
[08:18] <toobaz> should the PPA somehow be enabled for other releases?
[08:18] <wgrant> You cannot upload the same version number more than once in a single PPA, regardless of the release.
[08:19] <wgrant> You should append something like ~jaunty1 to the version.
[08:20] <persia> That works for jaunty, but +lucid1 is probably required for lucid
[08:20] <persia> (to preserve jaunty >> karmic >> lucid)
[08:28] <toobaz> ok, thanks
[08:53] <mac_v> hi... if i change my openID name , will i still have access to my branches?
[08:53] <mac_v> and other projects I'm working in?
[08:54] <wgrant> Yes, but your branches will be renamed.
[08:54] <wgrant> And sites other than Launchpad may no longer recognize you.
[08:55] <mac_v> wgrant: other sites are not a problem , my concern is more about the teams/projects i'm involved in.. so it wont affect those permissions?
[08:56] <wgrant> mac_v: Correct.
[08:56] <mac_v> thanks :)
[11:54] <EsatYuce>  i am member of one Launchpad's teams, i want to learn when the package released?
[13:26] <persia> Does anyone happen to know how Soyuz handles two source packages in Ubuntu that build a binary package with the same name?
[13:29] <noodles775> Hi persia - I'm not sure, my guess would be a conflict, but I'll have a look and see.
[13:29] <persia> noodles775: Seems both binaries end up on archive.ubuntu.com
[13:30] <noodles775> persia: different versions then? What's an example?
[13:31] <bigjools> I think this usually gets solved with an transitional meta-package
[13:31] <persia> Sources: squashfs, squashfs-tools; Binary: squashfs-tools
[13:32] <persia> bigjools: Well, that won't help Soyuz: that's just an end-user system issue.
[13:32] <bigjools> exactly
[13:32] <bigjools> I don't know how this has been handled before
[13:32] <bigjools> someone in distro may know
[13:32] <persia> Like me :)
[13:33] <bigjools> well, foundations :)
[13:33] <persia> I know how to handle it so the right thing happens for end-users.
[13:33] <persia> What I don't know is what Soyuz does with it.
[13:33] <bigjools> see if Colin knows, would be my best suggestion
[13:33] <persia> They manage those bits of Soyuz?
[13:34] <bigjools> the archive admins et al, yes
[13:34] <persia> Ah, that makes sense.  Thanks.
[13:34] <bigjools> I think stuff gets manually superseded, but check.
[13:35] <persia> Yeah, it looks like it ends up being manual.
[13:36] <persia> And that the Package file generation just selects an arbitrary binary package based on version number comparison.
[13:37] <persia> Anyway, thanks.  I'll go chase an archive-admin :)
[13:39] <maxb> persia: A binary package can only ever increase in version, so it depends on which way around the versions of the sources are
[13:39] <maxb> If a higher versioned source builds a binary formerly built by a different source, it takes it over
[13:39] <persia> maxb: Well, kinda.  Depends on context.
[13:40] <maxb> If a lower versioned source tries the same, that build will result in a "Failed to upload" error
[13:40]  * persia looks harder
[13:40] <persia> maxb: Except https://launchpad.net/ubuntu/+source/squashfs/1:4.0-3ubuntu1/+build/1391240 doesn't appear to have that error.
[13:41] <maxb> What is the other source package involved?
[13:41] <persia> squashfs-tools
[13:43] <maxb> persia: That is because of the order in which they built
[13:43] <maxb> squashfs 1:4.0-3ubuntu1 built first, and produced binary squashfs-tools 1:4.0-3ubuntu1
[13:44] <maxb> then, squashfs-tools 1:4.0-6 built, and produced binary squashfs-tools 1:4.0-6
[13:44] <maxb> the version number was an increase, so the upload was allowed
[13:45] <persia> Aha!, and I was misled by the dates of source modification vs. dates of build.
[13:45] <persia> Thanks for explaining the details.
[14:44] <ulysses__> what has happened with launchpad? I can't open any page
[14:45] <persia> ulysses__: Works fine here.
[14:45] <persia> (well, rather, no more than normally slow and with known bugs)
[14:45] <ulysses__> hm, then Firefox stucked
[14:46] <ulysses__> okay, it was pebkac:P
[14:47] <ulysses__> bye
[14:47] <persia> ulysses__: That's the best kind of bug: easy to solve and you don't even need to prepare a patch :)
[14:50] <KLondenberg> Hi all ..
[14:50] <KLondenberg> Short question: I'm currently trying to get my private copy auf Launchpad working, including Codehosting and so on. Everything except codehosting seems to work fine. But when I try to push to alp://dev/ repository, the repository gets created in the root folder (/) of the server launchpad is running on. It fails, even, if this is not done with root rights (for obvious reasons). Any clue...
[14:51] <KLondenberg> 	...what might be wrong, or where I should start looking into ?
[14:51] <KLondenberg> Apart from that, pushes to that repository don't get picked up by the webapp, even if I "make sync_branches"
[15:29] <aleksander_m> hi all... working with my projects in lauchpad, I usually do a bzr branch of the published branch as a local mirror, and then merge different local branches into that mirror, and then make a bzr push back to launchpad
[15:30] <aleksander_m> but one of my friends is also doing the same in the same project, and we end up with the revisions in launchpad wrong
[15:31] <aleksander_m> I mean, I pushed yesterday new revisions 15 and 16, and today he did a pull and push and we ended up with my revisions disappeared and new revisions 15 and 16 made by him
[15:31] <aleksander_m> what are we doing wrong?
[15:31] <tsimpson> probably better to ask in #bzr
[15:32] <persia> aleksander_m: You're forgetting to pull again before pushing, or you're using push --overwrite.  You ought to get an error.
[15:57] <AnAnt> Hello, launchpad translations help says that I can export translations to a bzr branch owned by a team of which I am a member, yet when I tried this, it didn't work !
[15:59] <AnAnt> or actually I got an "Invalid value| error when setting the team branch as the export branch
[15:59] <dpm> AnAnt, looking at https://help.launchpad.net/Translations/YourProject/Exports, it states that "At the moment, team-owned branches don't work as expected. To work around this, make yourself the owner of the branch, set it as the translations branch, and then make the team the owner of the branch again."
[15:59] <AnAnt> dpm: ah, I didn't see that, thanks
[15:59] <AnAnt> dpm: but won't the  URL of the branch change when I change the owner ?
[15:59] <dpm> AnAnt, you're welcome :). So you'll need to do this one-time workaround due to the current bug
[16:00] <AnAnt> dpm: the branch is now: lp:~<username>/....
[16:01] <dpm> AnAnt, perhaps danilos or henninge can better help on this (I'm not a LP dev :) )
[16:02] <dpm> AnAnt, but I would guess that when you make the team the owner of the branch again as suggested, the URL would go back to the original
[16:05] <henninge> AnAnt: and the link is not via the branch url but the internal database id of the branch.
[16:06] <AnAnt> hmm, lemme see that
[16:07] <AnAnt> henninge: yeah, that's right, thanks !
[16:23] <AnAnt> can I export translations to a newly created branch (that haven't been pushed to yet) ?
[16:23] <AnAnt> s/can I/can Rosetta/
[16:25] <henninge> AnAnt: I think so. AFAIK Rosetta does the same thing you would do when pushing.
[16:25] <AnAnt> ok
[16:33] <micahg> can LP link to flyspray yet?
[17:23] <rdb> are there any issues with soyuz right now?
[17:23] <rdb> I dputted some source archives an hour or so ago, still didn't get an email
[17:24] <al-maisan> rdb: where did you upload to?
[17:24] <bigjools> did you sign them with a key in your LP account?
[17:24] <rdb> al-maisan, to my PPA
[17:24] <rdb> let me check if the key is in the LP account
[17:25] <rdb> Oops, it wasn't. you were right
[17:25] <rdb> so will I need to reupload my stufF?
[17:25] <al-maisan> rdb: is the key in place now?
[17:26] <al-maisan> rdb: what is your ppa?
[17:26] <rdb> al-maisan, not yet, I I found out that I didnt even send it to the keyserver yet. gotta wait until its pushed
[17:27] <al-maisan> ah, I see.
[17:29] <rdb> al-maisan, ok, validated. PPA is https://launchpad.net/~panda3d/+archive/ppa
[17:30] <rdb> do I need to reupload, or wait?
[17:30] <al-maisan> rdb: reupload please
[17:30] <rdb> ok
[17:36] <rdb> al-maisan, yay, the upload appeared to have worked. Thanks for your help!
[17:36] <al-maisan> rdb: great!
[17:37] <al-maisan> rdb: thank bigjools :)
[17:37] <rdb> thanks bigjools :-)
[17:37] <bigjools> welcome :)
[18:18] <sproaty> https://launchpad.net/whyteboard/+download  - is this the right way to manage releases? every release has 5 files, so if I do a 0.39.1, 0.39.2, 0.39.3, 0.39.4 that's 20 files into one release if I just stick them under 0.39
[18:18] <sproaty> I want to keep up old ones just for a download total tally
[19:33] <jkakar> It would be cool if the 'Tags' portlet on bugs pages was a list of tags insteads of a cloud.  The cloud is hard to navigate/understand.
[19:36] <deryck> jkakar, I'm largely in agreement at this point.  It should be switched back to the way it was before, I think.
[19:36] <deryck> I still feel our handling of tags is not quite what it could be with either approach, though.
[19:38] <persia> I'm not sure "back to the way it was before" would be entirely ideal.
[19:38] <persia> Automated sorting would be nice, for example.
[19:42] <jkakar> deryck: I'm attempting to use tags to track work items.  A work item may involve many bugs (and by association branches).
[19:42] <jkakar> deryck: Having an alphabetized list of tags would basically give me a list of work items in Launchpad.
[19:43] <deryck> jkakar, ah, interesting that you would like it alphabetized.  It used to be descending order by number of bugs tagged.
[19:49] <jkakar> deryck: I would prefer alphabetization because then the order will always be predictable, making it faster/easier to use.
[19:53] <bjsnider> shipova is doing that thing where it endlessly builds a package again
[19:53] <bjsnider> just like last night
[19:54] <maxb> Is bazaar.lp.net totally dead?
[19:55] <maxb> intellectronica: Can you locate us a LOSA? Codehosting go boom!
[19:56] <Chex> maxb: hi, we are aware of the codehost problem and are working on it now
[19:56] <maxb> Thanks
[19:56] <mbarnett> maxb: yeah, we are loooking into it.  thanks
[19:57] <mbarnett> what chex said!
[20:02] <fta> build times are broken in lp. the page says "Finished 4 minutes ago (took 3 hours, 38 minutes, 31.8 seconds)", the log says "Build needed 03:04:37"
[20:02] <dhillon-v10> mrevell, hi :D how are you, I have been writing a lot of docs. so I wanted to join launchpad-docs and write some more docs for launchpad, what the criteria for joining
[20:03] <fta> another build (arm): "took 9 hours, 43 minutes, 23.6 seconds" vs "Build needed 21:39:16"
[20:03] <fta> and indeed, it tools ~22h
[20:03] <fta> took
[20:04] <bjsnider> why are builds taking so long though?
[20:04] <bjsnider> what could possibly take that long to build?
[20:05] <bjsnider> fta, were those long builds i386?
[20:06] <fta> 22h is armel, not i386
[20:07] <Adys> Hello - I'm trying to push one of my repos to a branch I just created (bzr push lp:~adys/+junk/main), but it's just hanging without any feedback whatsoever. Am I doing something wrong?
[20:07] <bjsnider> topic says bazaar is down
[20:08] <Adys> Oh
[20:08] <fta> bjsnider, the thing that takes 3h on amd64 is chromium, which i build in less than 1h locally, exact same package, but more memory / cores
[20:08] <Adys> was surprised by the lack of timeout message
[20:08] <bjsnider> that could potentially cause a problem i think
[20:08] <bjsnider> fta, i've been waiting hours for mplayer to build on i386 here. the other two arches built in i dunno 15 minutes or something
[20:09] <bjsnider> happened last night too
[20:10] <bjsnider> mplayer shouldn't take 5 hours to build on i386
[20:10] <fta> i'm not talking about the time spent in queue waiting for a slot, but actual build time
[20:12] <bjsnider> fta, me too. it's actually been building for 5 hours and counting
[20:12] <fta> iirc, mplayer is quite fast to build, i've built it hundreds of times since 2001
[20:13] <wgrant> fta: Do you have links to those builds?
[20:14] <fta> wgrant, https://edge.launchpad.net/~chromium-daily/+archive/ppa/+build/1402388 & https://edge.launchpad.net/~ubuntu-mozilla-security/+archive/nss3.12.3/+build/1377663
[20:14] <wgrant> fta: Note that anything that finished building during the LP upgrade or while buildd-manager was down will have a longer than expected time inside LP.
[20:14] <wgrant> But shorter? That seems really odd.
[20:14] <fta> wgrant, it's not new, it's been wrong for a while
[20:14] <wgrant> Oh. That's ages ago.
[20:14] <wgrant> Anything recent?
[20:15] <wgrant> Preferably less than 24 hours old.
[20:15] <fta> wgrant, the 1st one is from today
[20:15] <fta> 4h ago
[20:15] <james2432> is  bazaar down?
[20:15] <bjsnider> yes
[20:16] <fta> wgrant, ^^, the 2nd is just a few days old
[20:16] <ScottK> james2432: See /topic
[20:16] <james2432> mk that's what i though
[20:16]  * james2432 facepalm should have checked topic
[20:16] <bjsnider> indeed you should
[20:16] <wgrant> fta: Ah, so it is.
[20:18] <fta> wgrant, afaics, all build times are wrong, the armel ones are just worse than the other arches
[20:18] <bigjools> there's a bug about it, it represents the lag between the build itself, and the scanner collecting it
[20:19] <bigjools> and we've had a load of problems with the scanner lately
[20:19] <wgrant> bigjools: But 40 minutes?
[20:19] <bigjools> yes
[20:19] <wgrant> Just a couple of hours ago?
[20:20] <bigjools> yes
[20:20] <wgrant> Ah.
[20:20] <wgrant> sproaty: 0.39.1, 0.39.2 etc. should be separate releases in the 0.39 series.
[20:20] <bigjools> scanner was down
[20:20]  * bigjools needs beer
[20:22]  * james2432 hand bigjools a beer
[20:22] <cody-somerville> bazaar.launchpad.net doesn't seem down to me :(
[20:22] <cody-somerville> *:)
[20:22] <Adys> cody-somerville: at least here pushing to it doesnt work
[20:22] <james2432> up 4 me
[20:22] <james2432> I just pushed
[20:22] <Adys> ah
[20:22] <Adys> yeah its up now
[20:23] <james2432> yay
[20:23] <A4Tech1> hi all
[20:23]  * bigjools thanks james2432
[20:23] <Adys> which reminds me if theres a bazaar dev around, it would be nice to add a timeout
[20:24] <A4Tech1> http://paste.ubuntu.com/343669/
[20:24] <A4Tech1> Why am I not working push (bazaar)
[20:32] <jpds> A4Tech1: See /topic.
[20:33] <A4Tech1> oh
[20:33] <A4Tech1> thx)
[20:40] <jldupont> help, please, I get the following error: " Error while executing push  RemoteRepository(bzr+ssh://bazaar.launchpad.net/~jldupont/erljld/trunk/.bzr/) is not compatible with CHKInventoryRepository('file:///home/jldupont/workspace/erljld/.bzr/repository/') different rich-root support"
[20:40] <jldupont> with a bzr push command
[20:42] <maxb> It means your local repository is in a format which is incompatible with the one you are trying to push into
[20:42] <maxb> Most likely you have been bitten by the fact that bzr 2.x creates rich-root repositories by default
[20:43] <maxb> Unfortunately, revisions committed to such a repository cannot be pushed into a non-rich-root repository
[20:44] <jldupont> @maxb: what are my options here?
[20:46] <maxb> jldupont: Obtain a non-rich-root local copy of the remote, then port your changes across to that, potentially using bzr merge
[20:46] <jldupont> @maxb: how do I do that??
[20:47] <maxb> Presumably you ran 'bzr init-repo' at some point when starting work?
[20:47] <wgrant> Or think about upgrading the remote side, after considering all of the issues.
[20:47] <jldupont> remote side is Launchpad... I have no idea how to do this.
[20:47] <lifeless> maxb: pushing preserves format
[20:47] <Adys> Ergh
[20:47] <jldupont> I use the Bazaar plugin under Eclipse.
[20:47] <Adys> how do I add someone on a launchpad branch? Allowing them to commit
[20:48] <maxb> lifeless: I don't understand what you're saying?
[20:48] <lifeless> jldupont: run bzr upgrade bzr+ssh://bazaar.launchpad.net/~jldupont/erljld/trunk
[20:48] <jldupont> @lifeless: trying out...
[20:48] <thumper> Adys: you need to make the branch owned by a team whose members all have commit access
[20:48] <lifeless> maxb: I'm probably incoherent; was a late night
[20:48] <wgrant> lifeless: That seems like it might be a bad idea.
[20:48] <maxb> lifeless: Shouldn't he first check there's no branches stacked on it?
[20:48] <wgrant> lifeless: eg. it'll break stacking
[20:49] <lifeless> see, I shouldn't be giving advice until awake.
[20:50] <lifeless> more of an issue is that the remote branch might be stacked itself
[20:50] <wgrant> It's trunk so that seems less likely.
[20:51] <lifeless> wgrant: trunk != series, but we'll find out :P
[20:51] <Adys> thumper: confusing - where do I create a team?
[20:51] <wgrant> lifeless: Is there not some big document in the bzr docs explaining the issue and how to resolve it?
[20:52] <thumper> Adys: I'm pretty sure there is a link off the homepage
[20:52] <wgrant> Adys: https://launchpad.net/people/+newteam
[20:52] <wgrant> But yes, there is a link on the front page.
[20:57] <maxb> Is there full documentation for the merge@code.launchpad.net email anywhere? For example, can I send it a bundle, or must the code already be pushed?
[21:00] <jpds> maxb: The branch and MP are automatically created by the patch bundle.
[21:02] <maxb> Well.... I got an OOPS
[21:02] <maxb> So apparently I did something it didn't like :-)
[21:03] <maxb> Also, is it possible to use 'editor' as the MUA, but still fit the GPG signing in somehow?
[21:08] <jpds> maxb: https://dev.launchpad.net/Code/BzrSend
[21:08] <persia> maxb: $(VISUAL) mail.txt && gpg -s mail.txt && /usr/lib/sendmail < mail.txt
[21:14] <maxb> Hmm... that wiki page claims you can use 'editor' as a mail client, but how is the gpg signing going to happen then?
[22:15] <EsatYuce> who knows about GPG key?
[22:17] <RAOF> Almost everyone here knows _something_ about GPG keys, I'd wager.  What particularly are you after?
[22:20] <EsatYuce> i got one GPG key to use some commant in terminal, then one e-mail came me, i need to solve tihs e-mail than pasted it to Launchpad's fingerprint. How can i open this e-mail?
[22:22] <RAOF> EsatYuce: I'm not entirely sure what you're trying to do.  I am having trouble understanding you.  Are you trying to sign the Ubuntu code of conduct on launchpad?
[22:23] <EsatYuce> Raof: exactly, you are right
[22:34] <RAOF> EsatYuce: Sorry, I killed my computer trying 3D on the nouveau drivers.
[22:34] <RAOF> EsatYuce: If I remember correctly, what you get is a text file containing the code of conduct, correct?
[22:35] <EsatYuce> right
[22:35] <EsatYuce> there are many letters on e-mail
[22:35] <EsatYuce> but they are randomly
[22:36] <poolie> spm: any news or just "bazaar.launchpad.net is down due to hardware failure, we're working on it"
[22:36] <spm> poolie: apparently it's OOM'ing. from what little I can see it's thrashing heavily (or rather feels like that)
[22:36] <spm> one of the GSAs is about to stab
[22:38] <persia> EsatYuce: https://help.launchpad.net/ReadingOpenPgpMail
[22:39] <EsatYuce> persia, : i did it already,
[22:40] <EsatYuce> but i cant get e-mal from firefox to Evolition
[23:04] <poolie> spm: are we back upright?
[23:04] <poolie> if so can we update the status?
[23:04] <spm> poolie: yes; ta; fixing
[23:05] <poolie> thumper: hey, how about a chat?
[23:06] <thumper> poolie: yeah, ok
[23:07] <EsatYuce> İ created one key, then pasted it to Launchpad's fingerprint, then clicked import key button, then one e-mail came to my box. it is randomly text, i need to describe it. How?
[23:08] <wgrant> EsatYuce: Use a proper email client, or run 'gpg' in a terminal, paste the encrypted content into that window, press Control+D, and enter your passphrase when prompted.
[23:08] <EsatYuce> wgrant, : ok i m trying
[23:14] <EsatYuce> wgrant: i tried it, but i cant
[23:15] <wgrant> EsatYuce: "cant"? Why not?
[23:15] <EsatYuce> wgrant, : i typed what you said me to Terminal
[23:16] <EsatYuce> it said me "Go ahead and type your message", then i pasted the message, but it did nothing
[23:17] <wgrant> EsatYuce: Did you then press Ctrl+D?
[23:17] <EsatYuce> when i press ctrl+d my terminal exit
[23:17] <wgrant> Also, did you paste in the ----- BEGIN [...] lines?
[23:17] <EsatYuce> no
[23:17] <wgrant> You need to.
[23:17] <EsatYuce> ok
[23:20] <EsatYuce> wrang: can yuo send me private message
[23:20] <EsatYuce> i will send you the results
[23:21] <EsatYuce> wgrant,
[23:24] <wgrant> EsatYuce: Done.
[23:25] <gagita> hy guys how can I upload my offline translation to LAUNCHPAD?
[23:47] <EsatYuce> wgrant, : i sent you
[23:50] <wgrant> EsatYuce: Enter your passphrase.
[23:51] <EsatYuce> in Terminal?
[23:52] <EsatYuce> wgrant, : did you read my private message
[23:56] <wgrant> EsatYuce: I did. Once you paste the message, it should ask you for your passphrase. Enter it.
[23:57] <EsatYuce> already, but it said me You need a passphrase to unlock the secret key for
[23:59] <EsatYuce> wgrant: Could you please help me : i am trying again