=== eMxyzptlk is now known as eMxyzptlk[away] [02:32] $ bzr branch lp:hwtest [02:32] bzr: ERROR: Revision {david.murphy@canonical.com-20080417161838-a2tfnk26kx1q7vjf} not present in "revisions.kndx". [02:33] 'bzr co --lightweight' works (but not just 'bzr co'). [02:46] hmm [02:48] bimberi: what happens if you do 'bzr branch http://bazaar.launchpad.net/~hardware-certification/hwtest/trunk'? [02:58] bimberi: I appear to get the same error. At a guess, I'd say that the branch needs to be fixed by someone who has a copy [03:00] jml: your command worked [03:00] *interesting* [03:02] bimberi: are you a member of the hardware-certification team? [03:05] I thought they said that they fixed all of those branches. [03:05] After they broke them a few weeks ago. [03:05] jml: no (sorry so unresponsove, frequently afk atm) [03:05] (they being lp-bzr people) [03:05] wgrant: I am they. [03:06] jml: I always forget which team you're in, sorry. [03:06] wgrant: np :) [03:06] Too many LP people. [03:07] wgrant: when we fixed up the branches that the LP bug corrupted, we noticed other corrupted branches that were not caused by us. [03:07] I've seen corrupt branches on launchpad that were user errors... [03:07] right. [03:08] or bzr client errors. [03:08] * jml tries fetching the branch over sftp [03:09] if it works there, then it's probably a bazaar bug. [03:09] * bimberi retries lp:hwtest - same error. Now retrying http://... [03:16] "Branched 300 revision(s)." [03:16] So yes it worked. [03:16] But that'll be an outdated version. [03:18] wgrant, why would it be outdated? [03:19] do you guys know about this? [03:19] Sorry, there was a problem connecting to the Launchpad server. [03:19] anilm: what URL were you connecting to? [03:19] jml: http://bazaar.launchpad.net/~amakhijani/survv/blog/files [03:20] anilm: I've also had problems connecting to the code browsing service. [03:20] rockstar: If the branch is broken on SFTP, won't it not have been pushed to HTTP for a while? [03:20] jml: ahh ok [03:21] jml would know authoritatively, but I think not. [03:21] wgrant: if you don't have write access, you should get the same version of the branch no matter what protocol you use. [03:22] jml: Ah. [03:23] * jml can get the branch via sftp, but not via bzr+ssh [03:24] I'm guessing this is a Bazaar bug. [03:24] afaict, the version of the branch that I've got (as a non-team-member) is the latest. [03:26] I can't see any relevant errors in the logs I've got on hand. [03:26] I'll chase it up with the Bazaar guys tomorrow. [04:17] not being able to connect to bazaar in LP, is that known yet? [04:18] give me the "try reloading in a few" message [04:18] nixternal, Loggerhead? as in "view revisions/code"? [04:18] yes [04:18] well, it's been misbehaving for a few days now [04:19] k, it was working perfectly earlier, as it was flying allowing me to steal, I mean research, other's code :) [04:19] heheh [04:19] k, I will try again later then...thanks beuno [04:20] I think the devs are aware, and, AFAIK, a new version is being rolled out on wednsday, which should make it work much better [04:20] groovy [05:19] beuno: generally any misbheaviour is considered a severe problem and should be escalated, for future reference [05:20] lifeless, ah, alright. Since jml was notified above, and it has been the case for the past days, I didn't think it was worth bothering anyone. I'll make sure to be more annoying next time :) [05:21] beuno: uhm, I think he interpreted it as a branch specific thing [05:21] lifeless: no I didn't. [05:21] oh [05:21] I interpreted it as an intermittent thing. [05:22] well, I'm chasing it [05:22] thanks. [05:34] its up and running [05:35] thanks lifeless :) [08:57] hi, I've a question not close related to Launchpad : I'm an Ubuntu Member with an @ubuntu.com alias mail which I use mainly into the free software world mailing-list, I recently change to a new domain name my email server, and @ubuntu.com alias alway forward mails to the old one [08:58] I just changed my default e-mail contact in my launchpad account [08:58] (to my new zic@newdomain.org) [08:58] It should change automatically within a few days. [08:58] How long Launchpad "rehash" email alias ? [08:58] few days ? thanks for your help :) [08:59] Might be nightly, I forget. [09:00] can you confirm that Launchpad use the e-mail contact defined in accounts ? because, after my migration, I use my @ubuntu.com alias for e-mail contact on Launchpad [09:00] I just changed it to my newdomain, because I thought Launchpad use the contact adress to do the alias forward [09:01] I believe that setting your ubuntu.com alias as your primary Launchpad address will cause problems. [09:01] But IANALPD, I've just heard it happen to people. [09:01] yes, I believe it too, it's why I set it to my new email adress [09:15] doesn't LP use the first non @ubuntu.com email address for mail forwarding anymore? === asac_ is now known as asac === Spads_ is now known as Spads [11:46] geser: That matches my experience, but the tales of those who manipulate accounts with primary set to @ubuntu.com are legion: likely best to set something else primary before any adjustment, and once complete, maybe set back @ubuntu.com [14:13] Please give me a feature that helps me keep track about the Ubuntu packages I have been working with. [14:13] cyberix: What do you mean by "keep track"? [14:13] My use case is as follows [14:13] 1) I'm working on a new Ubuntu package [14:13] 2) Someone points out a bug in my packaging [14:14] 3) I realize I did the same error on all my previous packages [14:14] 4) I try to remember all the packages I created [14:14] 5) Look at https://launchpad.net/people/+me/+packages. [14:14] 6) ??? [14:14] 7) Profit. [14:14] Hello. There seems to be a lock stuck on one of my project's bzr branches. [14:15] wgrant: Thank you. That is just what I'm looking for. [14:15] Matt-W: Use bzr break-lock on it, if it says it's held by you. [14:15] wgrant: unfortunately it's held by somebody else [14:16] for 951 hours and counting [14:16] Matt-W: Who supposedly has it held? [14:16] held by jamesbrashko@bazaar.launchpad.net on host vostok [process #25147] [14:16] locked 951 hours, 31 minutes ago [14:16] he's the other person with commit access to the branch [14:17] You can probably safely break it - I doubt he's still doing anything with it after 40 days [14:17] It's highly unlikely that they've actually been doing a commit for the last 951 hours :) [14:17] What happens to translations that people contribute for Ubuntu? [14:17] he's not been able to commit at all this may explain it [14:17] cyberix: They go into the next language pack update. [14:17] The language pack then overwrites the translations that I ship? [14:18] the ones that are included in my original package [14:18] woo, a successful commit [14:18] Thanks [14:19] cyberix: Those translations aren't in your package if said package is in main. [14:19] cyberix: If your package is in universe or multiverse, it is not translated in Launchpad at this time. [14:19] Oh [14:19] Interresting [14:20] Ofcourse it makes sense to atleast have them separate [14:20] otherwise the task of translating Ubuntu would grow insanely big [14:20] It's actually largely due to technical issues with getting the universe translations to end users, I believe. [14:22] I'm having trouble with creating a process to handle Launchpad translations for a piece of software I wrote [14:22] I change one letter in the original software [14:22] then I have to create a new translation template [14:22] which makes all translations go fuzzy [14:22] and as, my software is not very common, no-one will check those [14:24] I'm currently "just including" all the translations I get from Launchpad [14:24] but I've understood that this leads to broken user experience [14:25] Also I'm not sure, if I'd like to do new releases all the time because some translation was updated. [14:27] I should find myself some guide for managing this [14:27] It is just that most guides concentrate on the technical issues [14:40] hi all, if a bug affects two versions of Ubuntu, say Intrepid as well as Hardy, how can I show that? [14:41] I have seen those kind of bugs but don't know how people affected that change. [14:41] nominate for release? [14:42] shirish: If you've tested against both, and you think it's important enough to get fixed as a stable release update, you can Nominate it for hardy. [14:44] persia the bug I've bug #240191 affects both hardy and intrepid, its a merge request of a package from debian [14:44] Launchpad bug 240191 in postr "Please merge postr 0.12.1-1 (universe) from Debian unstable (main)" [Undecided,In progress] https://launchpad.net/bugs/240191 [14:45] that doesn't affect hardy. [14:45] as in, hardy doesn't get 'merges' [14:46] Hobbsee: ah ok, it should be called a sync then or what, somebody else reported it, I just added stuff. [14:46] Also, #ubuntu-bugs is a better place for this sort of discussion. [14:46] ah ok, sorry guys [14:46] it should be caleld a stable release update, adn only the critical changes should be pushed into hardy. [14:46] or the entire thing backported. [14:46] neither of which is a merge. [14:47] true, so the description needs to be changed. [14:48] no, it shouldnt, as it's valid for intrepid. [14:48] which is what hte bug was first for. [14:48] before you attempted to sidetracker. [14:48] er, side track it. [14:50] ok I would be just happy when I get the updated package, that's about it [15:42] Are watch-files parsed on PPA? [15:44] phobie: parsed how? [15:45] show me if my package is up to date [15:45] like uscan or on debian.net [15:45] ppas do not have internet access, so, no [15:46] (beyond the mirror, anyway) [15:47] http://dehs.alioth.debian.org/maintainer.php?name=eric [18:13] hi guys, is there anyone here who can delete the series located here for me [18:13] https://launchpad.net/crunchbang-tips/random/ [18:15] ? === ubuntu-laptop is now known as gnomefreak === meepix is now known as meepix^away === eMxyzptlk[away] is now known as eMxyzptlk === mwhudson_ is now known as mwhudson === eMxyzptlk is now known as eMxyzptlk[away] === damdam is now known as meepix [23:52] bimberi: btw, I filed https://bugs.edge.launchpad.net/bzr/+bug/242232 as a followup to our conversation over the weekend. [23:52] Launchpad bug 242232 in bzr "Branch accessible via file, sftp & http, but not bzr+ssh" [Undecided,New]