[00:04] The OED cites Romany as "early 19th century". But I think Romani is the preferred spelling nowadays, and LP should probably use that. [00:05] (Though preferably with a bit more verification than me at 1am) [00:09] https://translations.launchpad.net/ubuntu/dapper/+source/kde-systemsettings/+pots/systemsettings/nb/7/+translate to find the original misspelling of innstillinger "instillinger" the suggestions just point at each other. [00:09] Result, a misspelling can never be corrected, and shows up everywhere [00:16] comradekingu: Looks like https://bugs.launchpad.net/launchpad/+bug/52805 [00:16] Launchpad bug 52805 in Launchpad itself "Remove wrong suggestions like typos etc." [Low,Triaged] [00:19] ok, ty === hloeung is now known as Guest79884 === Guest79884 is now known as hloeung === jamesh_ is now known as jamesh [10:37] How does one report a spamming account? Or should I just mark the bug as invalid? [10:41] rbasak: What's the username? [10:41] wgrant: https://launchpad.net/~tsnwv https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1313599 [10:41] But usually https://answers.launchpad.net/launchpad/+addquestion [10:41] Launchpad bug 1313599 in puppet (Ubuntu) "What Is the Healthiest Slimming Diet in the World?" [Undecided,New] [10:41] Oh, them again. [10:41] grar. [10:41] +addquestion - noted, thanks. === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === lazypower-travel is now known as lazyPower [18:07] <[MT]> So... what's causing this to fail now? https://code.launchpad.net/~nginx/nginx/debian the repo is perfectly fine as far as I can tell. [18:10] [MT]: the error seems pretty clear to me, but i can't tell you why the sha is invalid [18:15] <[MT]> dobey: I guess I'm more concerned with fixing it, but it seems like an issue on the LP side, not in the repo itself [18:16] [MT]: maybe bzr-git is being too strict, or has a bug [18:17] i don't think there's anything in launchpad itself we can do for that error, beyond getting bzr-git updated on the server if the bug is fixed [18:19] <[MT]> Should I just file a bug against bzr-git? [18:19] or launchpad if you wish; seems like the best place to start with that [18:20] then again, it could be a bug in git where the sha actually is broken and git is just going on anyway instead of failing [18:20] and bzr is doing the "right [18:20] err [18:20] and bzr-git is doign the "right" thing there [18:20] but i don't know for certain. just pointing out what i see :) [18:21] <[MT]> If it actually were broken, I'd expect to see that when doing git clone. [18:23] <[MT]> thanks for the info and taking a look [18:25] [MT]: right, unless there's a bug in git that is not failing when it should (which is why i menteiond that). git isn't without bugs either. could have a goto fail in it too ;) [18:26] <[MT]> git has no flaws! [18:26] <[MT]> ya, could be the case. I'll try to do some reading on git so see if I can find anything wrong in this repo. [18:27] it is the word, and the word is it? [18:27] <[MT]> that went over my head [18:28] heh. common retort from bible thumpers when flaws are pointed out to them. "it is the word of god, and the word is god." [18:28] aka rhetorical avoidance :) [18:29] <[MT]> ooh [18:29] circular logic