[03:45] <dhastha> danilos, I want to do Full Launchpad Translation API project for gsoc. Are you available for mentor?
[03:48] <wgrant> dhastha: He's more likely to be around during the European working day.
[03:52] <dhastha> wgrant, thank you.
[03:55] <dhastha> wgrant, If u don mind, can you clear my doubt?
[03:58] <wgrant> dhastha: What do you want to know?
[03:59] <dhastha> wgrant, How many API 's are available in launchpad, like launchpadlib?
[04:00] <wgrant> dhastha: See https://launchpad.net/+apidoc
[04:01] <wgrant> I don't really think that a full Translations API is a sufficiently large project for GSoC, but Danilo may have bigger ideas.
[04:06] <dhastha> wgrant, This project interesting to me. Because most of application only available in english. If we translate in our own language the uses of Ubuntu will be increase. Isnt it?
[04:07] <dhastha> wgrant, i like danilo idea. I am looking forward to work with him.
[04:09] <dhastha> wgrant, can u visit this page? https://wiki.ubuntu.com/GoogleSoC2010/Dhasthagheer              and tell me your suggestion
[06:42] <humphreybc> hi guys, we need some help sorting out some branches in our project
[06:42] <humphreybc> should I ask in here or #bzr ?
[06:43] <lifeless> depends on what you need
[06:43] <lifeless> if you need administrative stuff done, ask here or a question on answers.launchpad.net/launchpad
[06:46] <wgrant> If you're unsure, give us more details here and we can direct you to the right place if required.
[06:48] <humphreybc> godbyk will explain some more
[06:48] <humphreybc> basically we need to duplicate some branches for launchpad.net/ubuntu-manual
[06:48] <humphreybc> but we're not sure how to do it without destroying the translations
[06:49] <wgrant> Why do you want to do this?
[06:50] <godbyk> we've been doing all our work in the main branch. But now we'd like to split off a copy of the branch so translators have a stable set of strings to translate while we continue working on new content.
[06:50] <wgrant> So you'd basically like to create and freeze a 10.04 release branch?
[06:51] <godbyk> wgrant: yes.
[06:51] <wgrant> While keeping development going in trunk for 10.10?
[06:51] <godbyk> translators have already started translating what's in the main branch, and I want to make sure I don't screw up their work.
[06:51] <godbyk> Precisely.
[06:53] <wgrant> I'm no Launchpad Translations expert. The Translations developers should be around in an hour or two; I'd recommend asking then.
[06:54] <lifeless> so
[06:54] <godbyk> wgrant: fair enough.  thanks!
[06:54] <lifeless> yes, get a translation dev to comment
[06:54] <lifeless> I'd be guessing
[06:54] <wgrant> With message sharng it should be pretty easy.
[06:55] <wgrant> Since unchanged strings will have their translations shared across all series.
[06:55] <godbyk> that's good to know.
[06:55] <godbyk> my fear is that if we want translators to use the new (stable) branch, rosetta will still be applying their work to the (new) dev focus branch.
[06:56] <wgrant> You can set the translation focus series -- that will be shown to translators as the series that should be translated.
[06:56] <wgrant> How much do you know about Launchpad's series model?
[06:56] <godbyk> wgrant: Absolutely nothing.
[06:57] <godbyk> wgrant: Feel free to point me at enlightening documentation if you have some.  I haven't even looked yet.
[06:57] <wgrant> godbyk: Have a look at https://help.launchpad.net/Projects/SeriesMilestonesReleases
[06:57] <godbyk> humphreybc just dumped this in my lap. :)
[06:57] <wgrant> So, I imagine you'll create a new 10.04 series.
[06:57] <wgrant> Then create a 10.04 branch of trunk, push it up to LP, and link it to the new series.
[06:57] <wgrant> It will be called lp:ubuntu-manual/10.04.
[06:58] <wgrant> Then you can continue your normal development in lp:ubuntu-manual.
[06:58] <wgrant> But you also need som Translations magic in there, which the developers will be able to advise yon on.
[06:58] <wgrant> s/yon/you/
[06:58] <godbyk> Sounds easy enough.
[06:59] <godbyk> Can you ping me when you've spotted a translation dev shows up?
[06:59] <humphreybc> and then all hell breaks out
[06:59] <wgrant> Sure.
[06:59] <humphreybc> thanks wgrant
[07:00] <godbyk> wgrant: thanks!
[07:44] <fradeve> hi all, how can I solve the #1024 bug on LP? I've installed the firefox addon/953 but it seems does nothing... :(
[07:45] <wgrant> The #1024 bug?
[07:45] <lifeless> bug 1024
[07:45] <lifeless> \o/
[07:45] <fradeve> https://answers.edge.launchpad.net/launchpad/+faq/1024
[07:46] <wgrant> fradeve: Firefox doesn't filter the header by default. You have an existing setting or plugin which is causing the problem.
[07:46] <wgrant> You do not need to install another to fix it.
[07:48] <fradeve> wgrant: yeah, so... where's the problem?
[07:48] <fradeve> wgrant: this is the first time I see that kind of problem on my ubuntubox
[07:48] <fradeve> wgrant: I've always used firefox :|
[07:49] <wgrant> fradeve: You have at some point configured Firefox or an extension to avoid sending a Referer header.
[07:50] <fradeve> wgrant: mmmm I'm checking
[07:50] <wgrant> You need to disable that filtering, or add an exception for launchpad.net.
[07:52] <fradeve> wgrant: I couldn't imagine where this kind of setting should be in Firefox, I've searched, but nothing...
[07:53] <wgrant> fradeve: Checked the network.http.sendRefererHeader setting in about:config?
[07:54] <wgrant> (the default value appears to be '2'.)
[07:56] <fradeve> It was "0" in my about:config; I've changed it to 2, but nothing :|
[07:56] <fradeve> will try to restart firefox
[07:57] <dhastha> danilos, visit this page https://wiki.ubuntu.com/GoogleSoC2010/Dhasthagheer
[07:59] <fradeve> wgrant: quick hint: after restarting firefox, the network.http.sendRefererHeader setting returned to "0"... about:config settings are saved simply closing the page?
[08:00] <wgrant> fradeve: Yes. One of your extensions is probably resetting it.
[08:00] <fradeve> wgrant: damn
[08:02] <wgrant> jtv, henninge: Can one of you please help humphreybc and godbyk? They need to create a 10.04 series for ubuntu-manual, and need guidance on the Translations issues.
[08:03] <henninge> wgrant, humphreybc, godbyk : Sure, what is the problem?
[08:03]  * jtv is emphatically Not Here.
[08:04] <godbyk> henninge: Currently we've been writing all our code in a single branch.
[08:04] <godbyk> We've just created a couple of new series.
[08:04] <fradeve> wgrant: solved, you roule, it was one of my extensions ;) I apologies for not trying that from beginning ;) thanks ;)
[08:04] <godbyk> We'd like all the translations to happen on the stable series (which has strings frozen).
[08:04] <godbyk> but up 'til now, they've been translating the main branch.
[08:05] <godbyk> can I somehow safely move the translation work to another series without disrupting everyone?
[08:05] <henninge> godbyk: will "everyeone" will have to know they have to continue work on the other series.
[08:06] <henninge> godbyk: but apart from that, it should be save.
[08:06] <wgrant> godbyk: Hm, it would be conventional to have a 'lucid' series with two milestones, rather than 'lucid-e1' and 'lucid-e2'.
[08:06] <henninge> godbyk: let me look at the series a bit more closely
[08:06] <henninge> godbyk: yes, I was about to ask about the meaning
[08:06] <godbyk> wgrant: well, the e1 and e2 will be two releases.  does that fit the milestones paradigm?
[08:07] <wgrant> godbyk: Yes. Releases are just special milestones.
[08:07] <godbyk> wgrant: cool. I'll fix that, then.
[08:09] <godbyk> Just so I'm clear on the semantics: a series would be, say, per Ubuntu release whereas a milestone could be associated with an edition of the manual.
[08:09] <godbyk> So the 10.04 manual that has two editions would have (at least) two milestones in the lucid series.
[08:09] <godbyk> And the 10.10 manual would be in the 10.10 series.
[08:09] <wgrant> godbyk: The Ubuntu 10.04 series has Alpha 1, Alpha 2, Alpha 3, Beta 1, Beta 2, 10.04, 10.04.1, 10.04.2, 10.04.3, 10.04.4.
[08:10] <wgrant> Er, add RC in there as well.
[08:10] <wgrant> You maintain multiple series so you can have parallel lines of development.
[08:10] <wgrant> So, yes, one for 10.04, one for 10.10, etc.
[08:10] <godbyk> Theh first and second edition of our manual will be developed in parallel, somewhat.
[08:11] <wgrant> Hmm.
[08:11] <godbyk> The first edition is being translated and I'll be tweaking it a bit. Meanwhile, the second edition is being written.
[08:11] <wgrant> I see. So maybe two series is a good idea.
[08:11] <godbyk> Okay.
[08:12] <godbyk> I'd like the translators to only worry about the 10.04 first edition.
[08:12] <godbyk> Up to this point, they've been translating on the main branch (we've only had the one branch/series).
[08:12] <godbyk> Can I seamlessly pull them off the main branch and have them continue working on the 10.04 first edition series?
[08:13] <godbyk> (I think they're all using Launchpad/Rosetta.)
[08:15] <henninge> godbyk: they way to go is this:
[08:16] <henninge> godbyk: upload the two templates in their current state (download them from Launchpad first) to the new series, using the exact same template names.
[08:16] <henninge> godbyk: oh, just realised you are using bzr sync .... ;-)
[08:17] <godbyk> I haven't set up the sync on the new series yet.
[08:17] <henninge> godbyk: does the new series have its own branch?
[08:17] <godbyk> henninge: yes.
[08:18] <henninge> godbyk: and it starts out as an identical copy of main?
[08:18] <godbyk> henninge: yes, precisely.
[08:18] <godbyk> they're currently pristine copies of main.
[08:19] <henninge> godbyk: so just set it up to have translation templates imported from that branch into the new series.
[08:19] <henninge> godbyk: once that has happened you will see that all the translations are instantly available in the new series's templates, too.
[08:20] <godbyk> Well, the lucid-e1 branch (for instance) has a copy of the .pot file from main.
[08:20] <godbyk> So do I want it to import that copy or something else?
[08:27] <henninge> godbyk: that copy, yes
[08:27] <henninge> godbyk: but you really just need to import the template, not the translations.
[08:28] <godbyk> henninge: do I want to upload the .pot file from the main branch or tell it (somewhere) to pull it (just once) from the main branch?
[08:29] <henninge> godbyk: do you not expect changes on the template?
[08:29] <henninge> in the future?
[08:29] <godbyk> henninge: Not for the lucid-e1 series/branch. It's in string-freeze mode so the translators can do their thing in peace.
[08:30] <godbyk> Further work will carry on in the other series' branches.
[08:30] <henninge> godbyk: but if it has a code branch that contains the template, it would be easiest (and clearest) to just import from there.
[08:31] <godbyk> henninge: the lucid-1e branch does have its own template, yes.
[08:31] <godbyk> henninge: if I import that template, will the existing translations find their way there as well or is that a separate operation?
[08:32] <henninge> godbyk: that will be automatically and instantly.
[08:32] <henninge> godbyk: it goes by the name of the template
[08:32] <godbyk> henninge: okay, I'll do that, then.
[08:32] <wgrant> Is that message sharing coming into play?
[08:32] <henninge> wgrant: yes
[08:32] <godbyk> henninge: when translates hit translations.launchpad.net/ubuntu-manual, how can I have their future translations directed at the lucid-1e series (for now)?
[08:32] <henninge> that's exactly what it was meant for
[08:32] <henninge> easy start of new series.
[08:33] <dhastha> wgrant, sorry to disturb you. Mentor for Full Launchpad translation API Mr. Danilos is not available. How do i contact him?
[08:33] <wgrant> godbyk: https://translations.launchpad.net/ubuntu-manual/+settings
[08:33] <wgrant> godbyk: You can set the translation focus series there.
[08:33] <henninge> godbyk: exactly
[08:34] <henninge> godbyk: also, on going work will always be reflected in both series, due to message sharing.
[08:34] <godbyk> wgrant: ah, perfect.  also, is there a way I can add some text to the top of our project's translation page?  (say, directing translators to our style guide)
[08:34] <henninge> godbyk: so even if somebody did a translation in main, it would show up in lucid-e1 if that string exists there, too.
[08:35] <jtv> dhastha: hang on, I'm checking.
[08:35] <godbyk> henninge: so if the series/branches share a common string, and that string is translated in one branch/series, the translation will appear automatically in the other branch/series?  sweet!
[08:35] <jtv> dhastha: I think he should be around in a few hours.
[08:36] <henninge> godbyk: yup, exactly. took some effort to get that working properly .... ;-)
[08:36] <godbyk> heh, I can imagine!
[08:36] <dhastha> jtv, thank you
[08:36] <godbyk> henninge: are you who I should pester about fuzzy strings in rosetta?
[08:37] <henninge> godbyk: what's there to pester? ;-)
[08:37] <henninge> godbyk: fuzzy translations are simply dropped on import, AFAIK.
[08:37] <jtv> yes they are
[08:38] <henninge> AFAIR
[08:38] <godbyk> henninge: we have a lot of long strings to be translated (as we're writing a manual). when I fix a spelling error, the whole paragraph must be retranslated because rosetta doesn't show the previous (similar) translations.
[08:38] <jtv> we used to keep them, but they only made things worse
[08:38] <godbyk> henninge: ah, well, that dropping of fuzzy translations is my complaint, then. :)
[08:38] <jtv> They were wrong a lot more often than they were right, leading to all sorts of wrong translations.
[08:39] <henninge> godbyk: I see the problem.
[08:39] <godbyk> jtv, henninge: any suggestions on how we should handle our long strings?
[08:39] <godbyk> We're using po4a and LaTeX.  I think po4a dumps in the strings one paragraph at a time.
[08:39] <jtv> godbyk: you could export the old translations, replace the English there, and re-import.
[08:41] <godbyk> jtv: That would work if we've just fixed an English spelling error (and the translators translated it correctly regardless).  But doesn't help if we, say, add an \index{add this word to the index} command, for instance.
[08:41] <godbyk> If the entire string is the same, save for that added bit of text, the translation is still okay, but just needs that \index command added to match.
[08:43] <jtv> godbyk: so you either change both the English and the translation, or you change only the English and treat the rest as translation of the English string.
[08:44] <godbyk> jtv: As a translator, when the English author has added an \index command (or comma or whatever), Rosetta asks me to re-translate the entire paragraph.  Can Rosetta at least tell me what the previous translation looked like?
[08:45] <godbyk> I guess it'd have to do some fuzzy string matching (diff) on the English source to pull that off.
[08:45] <jtv> godbyk: if you update the English string in the PO files like I said, you'll still have the old translation active.
[08:45] <jtv> That was the whole point.
[08:46] <jtv> It's annoying, but it's a fundamental problem that the software can't tell whether an English string is "the same" as a previously existing one, from our human point of view.
[08:46] <godbyk> jtv: Ah, I see what you're saying.  I should handle that on my end and have the translations autosync with the po files in the branch (along with the branch's pot file)?
[08:46] <henninge> godbyk: but be aware that the template needs to be updated, too.
[08:46] <jtv> We wish we had a better solution for that; unfortunately "fuzzy" just wasn't good enough.
[08:47] <jtv> godbyk: you could do it that way, but there are risks with automatic two-way synchronization.
[08:48] <henninge> jtv: I don't think he meant two-way, though.
[08:48] <henninge> just importing templates and translations
[08:48] <godbyk> jtv: If it's not pulling the po files from the branch, then what good does changing the English strings in the po files do me?
[08:48] <henninge> (which I think is the current setting anyway)
[08:49] <jtv> godbyk: it's also possible to upload manually, e.g. as a single tarball.
[08:49] <jtv> We don't recommend it for general usage anymore, since it's more tedious and more error-prone than branch synchronization, but it's possible for those one-offs.
[08:49] <godbyk> Ah, I should've clarified that.  Currently, we're letting launchpad import the template and translations.  But we manually pull a tarball from launchpad and dump it into the bzr repository.
[08:49] <jtv> And as Henning points out, if you're not also exporting translations to the same branch, there's really nothing against importing both templates and PO files from your branch.
[08:50] <godbyk> So our auto-sync is one-way (into LP only).
[08:50] <henninge> godbyk: "Exporting translations to branch:  lp:~jshholland/ubuntu-manual/manual-trans"
[08:51] <godbyk> So I'd need to write a tool that handles the English string comparison and updates the English strings in the po files (to match the new pot file strings).  Correct?
[08:51] <henninge> godbyk: so are you saying that because that's not the same branch as the import branch?
[08:51] <henninge> godbyk: yes, that sounds like it. ;)
[08:52] <godbyk> henninge: Correct.  jshholland's branch is separate.
[08:52] <godbyk> henninge: Fair enough. :)
[08:52] <wgrant> Won't that tool result in the translators not being notified that they need to update the translations?
[08:52] <jtv> godbyk: I guess... but you'd have to tell the tool what string you're changing to what, otherwise you're trying to solve the same problem that gettext's "fuzzy" handling didn't do well enough.  :-)
[08:52] <godbyk> I don't s'pose you guys are interested in showing diffs between the previous string and the current string, are you?  So the translators can easily see what was added/changed/removed so they can update their translation accordingly.
[08:53] <godbyk> jtv: Are there more details on the problems you had with gettext's fuzzy handling?  Do you think it'd work better (or worse) with our longer strings?
[08:53] <henninge> godbyk: the problem is that rosetta does not have that concept
[08:53] <jtv> wgrant: well this is for cases where the old and new strings are "the same" from a human pov, so this wouldn't be done in cases where translators need notification.
[08:54] <henninge> godbyk: a changed English string will be stored as a new string.
[08:54] <jtv> There is no "change," only an old string and a new string that *we humans* may feel are "identical."  Or not.
[08:54] <godbyk> I see.
[08:54] <godbyk> Well, that'd be a handy concept to introduce!
[08:55] <jtv> Yes and no.  It also means that humans are invited to keep the translations the same when there may be small but significant changes in the English.
[08:57] <godbyk> jtv: Possibly.  But it'd be easier to click on a suggestion, make the minor edits, and accept it than to have to retranslate the whole paragraph from scratch.
[08:58] <jtv> godbyk: definitely.  And I think we'll probably want build something along those lines at some point...  the real problem is, we have more things we want to program than we have engineers!
[08:58] <godbyk> jtv: I hear you there!
[08:59] <jtv> BTW Launchpad is available under the GPL now, hint hint  ;-)
[08:59] <henninge> godbyk: what I could imagine would be a sperate "search for similar English string" feature, that the translator can invoke.
[08:59] <godbyk> LOL.  Well, it wouldn't be the first time we jumped in to fix some bug that was in our way (or wrote an entirely new piece of software to make our lives easier).
[09:00] <henninge> it could search for similar strings and list the available translation(s) for it.
[09:00] <jtv> Or a "we once had this other English string in the same place, here's how it was translated" suggestion...  just figuring out what is the best thing to do is hard work.  :-)(
[09:01] <godbyk> That might work.  Basically, I'd like it to say, 'here's the original string and here's a diff showing what's changed. Here's your original translation; fix it.'
[09:02] <jtv> A diff is a really nice idea...  the nasty part is always that these nice ideas make the feature harder to build, making it less likely to be built.  :/
[09:03] <godbyk> jtv: Certainly true.
[09:04] <godbyk> I'll sleep on it and see if any brilliant solutions come to me. :)
[09:04] <godbyk> jtv, henninge: Thanks a lot for your help. I really appreciate it!
[09:04]  * persia notes that "diff" on a "string" tends to be tricky, especially for short strings.
[09:04] <persia> Err, UI-tricky
[09:04] <godbyk> persia: We're looking at a paragraph at a time.
[09:05] <henninge> godbyk: pleasure
[09:05] <henninge> jtv: turn off the computer now. ;)
[09:05] <jtv> henninge: good idea.  :-)
[09:08]  * godbyk has the feeling that the translator devs will never speak to him again. ;-)
[09:40] <hakaishi> Hi! Is there something wrong with launchpad? - My builds are awaiting publication since about 7 hours (see https://launchpad.net/~hakaishi/+archive/qshutdown/+packages)
[09:44] <hakaishi> Hello?
[09:45] <wgrant> hakaishi: Something is wrong, possibly only with your PPA.
[09:46] <hakaishi> wgrant: why do you think it could be my PPA?
[09:47] <wgrant> hakaishi: Because some other PPAs I've checked seem to be happier than yours.
[09:48] <wgrant> I'm having a deeper look now.
[09:48] <hakaishi> wgrant: okay, thank you ^^
[10:05] <hakaishi> wgrant: anything found yet?
[10:06] <wgrant> hakaishi: I have a suspicion, but I don't have access to verify that suspicion, and it seems that no real member of the relevant team is around at the moment.
[10:07] <hakaishi> wgrant: Would it be solved if I just upload with a new upstream version number?
[10:08] <wgrant> hakaishi: Probably not.
[10:08] <hakaishi> -.-
[10:09] <wgrant> Try not to fix it until someone has further examined it; it probably won't fix it, might destroy evidence, and might break things further.
[10:09] <hakaishi> wgrant: Okay, then I'll just wait...
[10:11] <edakiri> If I register a PGP key, will LaunchPad use it when it sends me bug e-mails?
[10:13] <tumbleweed> edakiri: no
[10:13] <hakaishi> edakiri: I don't think so. The PGP key should be for uploading to your PPA.
[10:13] <BlindFreakazoid> hi there, I wanted to import a subversion branch from sourceforge to launchpad but says "Pending Review" for 2 weeks :( Who needs to review it? Me? (as the project owner)
[10:13] <BlindFreakazoid> https://code.launchpad.net/pidgin-birthday-reminder
[10:14] <tumbleweed> BlindFreakazoid: a launchpad admin has to review it, it can take a while, yes
[10:15] <BlindFreakazoid> okay
[10:15] <BlindFreakazoid> thank you
[10:15] <sheymann> Hello guys, I'm a maintainer of Gephi software. We use LP a lot and it's great, thanks! Now we want to use the translations features, but our import queue is blocked and no one can approuve the templates. Could someone help me fixing it?
[10:15] <BlindFreakazoid> then I am just waiting :> I just wondered if I missed something that I had to do
[10:34] <Charlie_X> Hi, I'm looking for a bit of help using the Launchpad API. I'm new to Rest stuff so my mistakes probably arise as much from not understanding how to apply that to documentation
[10:45] <wgrant> Charlie_X: Ask your question -- someone will answer if they know.
[10:48] <Charlie_X> Thanks. I just need to know how to get the bugs for a particular project. I'm using launchpadlib but can't seem to work out how to get the bugs for a particular project. launchpad.bugtrackers[projectname] doesn't work
[10:49] <Charlie_X> There is a method .getByName(**kw) but I don't quite understand the parameters
[10:49] <wgrant> Charlie_X: Have a look at the searchTasks method.
[10:49] <wgrant> On https://launchpad.dev/+apidoc.
[10:49] <wgrant> Er.
[10:49] <wgrant> https://launchpad.net/+apidoc
[10:50] <Charlie_X> Yes, I'm reading that but .getByName(ws.op='getByName', name=projectname) is a syntax error
[10:50] <wgrant> Charlie_X: ws.op is sent automatically by launchpadlib. Omit it.
[10:51] <Charlie_X> ah, so it's like "self" in class methods?
[10:53] <waschtl> Hi all
[10:54] <wgrant> Charlie_X: Sort of.
[10:54] <wgrant> Charlie_X: +apidoc describes the raw REST API.
[10:54] <wgrant> launchpadlib is a wrapper around it.
[10:54] <waschtl> I'm stumped about reporting bugs on launchpad. I no longer get the input form, but instead instructions about the GUI bug reporter.
[10:55] <wgrant> waschtl: Have you read the instructions?
[10:55] <Charlie_X> neither getByName(name="zope3" nor queryByBaseURL(
[10:55] <Charlie_X>                     base_url="https://bugs.launchpad.net/zope3") return anything
[10:55] <wgrant> Charlie_X: Why not just use lp.projects['zope3'?
[10:55] <wgrant> Er, with a ']' as well.
[10:55] <waschtl> wgrant: I don't have a GUI on my server, which is the subject of the bug report.
[10:55] <Charlie_X> I tried that but that has no bugtracker_link
[10:56] <wgrant> waschtl: Continue reading the document; it describes what to do in that circumstance.
[10:56] <wgrant> Charlie_X: Why do you want the bugtracker_link? That's just for pointing to a non-Launchpad bug tracker.
[10:56] <waschtl> wgrant: all right -- maybe it could be made to stand out more, so that it would be seen while skimming over all the GUI stuff.
[10:56] <waschtl> wgrant: thanks
[10:57] <wgrant> waschtl: That is probably better discussed in #ubuntu-bugs; Launchpad does not control that page.
[10:57] <waschtl> wgrant: ah, allright, will do -- thanks again
[10:58] <wgrant> Charlie_X: Try the searchTasks method on the project to get the Launchpad bugs involving it.
[10:59] <Charlie_X> Thanks - I was just about to ask which method I should look at.
[11:05] <danilos> sheymann, hi, did you get any help with your translations problems already? (if not, perhaps I can help)
[11:15] <danilos> sheymann, hey (let's keep the discussion public so someone else can jump in if I can't help)
[11:15] <sheymann> all right
[11:16] <sheymann> I previously asked the french translation team for help, but he couldn't do more than redirecting here after adding me to the team.
[11:16] <sheymann> this is out import queue: https://translations.launchpad.net/gephi/0.7/+imports?start=225&batch=75
[11:16] <danilos> sheymann, are you using branch imports?
[11:16] <sheymann> yes
[11:19] <danilos> sheymann, I see you have a big number of files named "template.pot": that doesn't make approval easier
[11:19] <danilos> sheymann, usually, what you should do is have them named after the actual context, i.e. ClusteringAPI/src/org/gephi/clustering/api/template.pot should probably be ClusteringAPI/src/org/gephi/clustering/api/clustering-api.pot
[11:19] <danilos> sheymann, if you name them like that and use bazaar branch integration, then it will all be automatically approved few minutes after you push the branch up
[11:20] <danilos> sheymann, so, I see you are using a branch already, so that's good
[11:20] <danilos> sheymann, automatic approver can't name these templates because they are using the identical POT file names, so just change that and it should be approved
[11:20] <danilos> sheymann, if that doesn't happen soon after the rename, just stop by here and we'll take a look
[11:21] <danilos> sheymann, there's more help up on https://help.launchpad.net/Translations/YourProject/ImportingTemplates
[11:22] <sheymann> all right, I'll try it and back to tell if it resolved the problem. Thanks!
[11:22] <hakaishi> wgrant: anyone online yet who could help me, about my PPA publication pending?
[11:23] <danilos> sheymann, you are welcome
[11:33] <cyberix> What should I mark a bug when the bug continues to disturb users, but is not a bug in the application, and thus needs to be fixed elsewhere?
[11:34] <cyberix> Is there a way to mark bug as "inherited" or something like that
[11:34] <maxb> Open a bugtask on the actual part which needs to be fixed, and set as "Invalid" the bugtask on your project?
[11:36] <cyberix> maxb: I guess that works. I was just hoping it would be easy to see that it is still a problem.
[11:36] <cyberix> I mean
[11:37] <cyberix> a bug could be seriously invalid
[11:37] <cyberix> and calling something that constantly disturbs users invalid may sound like the project wouldn't care
[11:39] <cyberix> also
[11:39] <cyberix> there should be a way for the library provider to see, how many projects are bugged by the upstream bug
[11:39] <cyberix> this would make it easier to see how big the problem really is
[11:49] <hakaishi> Hi, anyone there who could help me? - My builds are waiting for publication since over 11 hours...
[11:54] <hakaishi> anyone?
[11:57] <persia> hakaishi: It's still being investigated: you're still in "wait" mode.
[11:57] <hakaishi> persia: ah, okay, thank you.
[12:00] <Charlie_X> wgrant: thanx
[12:09] <Charlie_X> Is it possible to pass in a list of values for a parameter in project.searchTasks()?
[12:10] <wgrant> Charlie_X: For some (such as status and importance), sure.
[12:10] <wgrant> The best way to find out is to try, probably.
[12:10] <wgrant> (or read the docs)
[12:12] <Charlie_X> The docs make no reference to multiple values
[12:13] <Charlie_X> But passing in a tuple works
[13:38] <maxb> leonardr: Hi,
[13:38] <maxb> oops, pressed enter too soon
[13:38] <leonardr> hi maxb
[13:39] <maxb> I don't suppose you'd be processing code import approvals today?
[13:39] <leonardr> maxb: oops, i forgot to take my name off the irc channel
[13:40] <maxb> ah, fair enough
[13:40] <leonardr> maxb: tell me which project you need an import for
[13:40] <maxb> https://code.edge.launchpad.net/~maxb/guice/trunk
[13:42] <leonardr> maxb, approved
[13:42] <maxb> thanks
[13:43] <maxb> I feel a bit bad about jumping the queue, there was someone on here earlier noting they had one pending review since 2 weeks ago
[14:00] <askhl_> Hi, I've had some translations stuck in the import queue (in 'approved' state) for several days, https://translations.launchpad.net/~askhl/+imports .  This is an error, isn't it?
[14:04] <leonardr> ashkhl_, it's human error. i'm working through the import queue now
[14:04] <wgrant> leonardr: Not the translations queue, surely?
[14:05] <askhl_> leonardr: thank you very much
[14:05] <leonardr> wgrant: oops, yeah
[14:05] <leonardr> askhl_: actually, sorry, i'm working on the _code_ import queue. i don't know about the translation queue
[14:05] <askhl_> One of them is an 'import' and one of them is an 'upload', I believe.
[14:07] <askhl_> (The import is because I wanted to merge with upstream as soon as possible in case there were version differences to resolve in LP.  The other one is meant to override some 'changed in launchpad', i.e. some discrepancies with upstream)
[14:07] <danilos> askhl_, don't you want to upload these into ubuntu packages instead?
[14:08] <askhl_> danilos: They are in ubuntu lucid packages.  I don't think there is another way, is there?
[14:08] <danilos> askhl_, it seems someone has registered these as projects and set-up translations imports, however that's the wrong thing to do
[14:09] <danilos> askhl_, so, you tried doing it in gedit project, where you should have done it in ubuntu gedit sourcepackage
[14:10] <askhl_> danilos: actually I didn't do anything in the gedit project.  I have no clue why there are other imports happening.  I assume it is because I am the translator of upstream for these projects, and someone else did an import
[14:10] <askhl_> danilos: ...but now I realize that it doesn't make all that much sense perhaps
[14:10] <askhl_> danilos: the only two imports I have made myself are those that are 'approved'
[14:10] <danilos> askhl_, oh, it actually does because someone has also ticked the box to set up imports
[14:11] <danilos> askhl_, right, that makes sense (fwiw, we are currently working on implementing direct imports from upstream, so that's why the other bits make sense as well :)
[14:11] <askhl_> just a question, how fast will the direct imports be?  I mean the latency
[14:11] <danilos> askhl_, ok, so we've got some 4-6k files to import, it may take a while (few hours) for all of them to be imported
[14:12] <danilos> askhl_, we expect it to be less than 1 day since they are committed upstream
[14:12] <askhl_> danilos: that's excellent
[14:13] <danilos> askhl_, let's see how it goes, it's probably going to be available post-Lucid (we are hoping to get it done by June)
[14:13] <askhl_> I have to get some work done now, but I may pop back in later if I have time, as I didn't understand all the stuff about someone 'also ticking the box to set up imports'
[14:13] <askhl_> Thanks, danilos and leonardr
[14:14] <danilos> askhl_, yeah, don't worry about it, it's about setting upstream imports (which won't fully work anyway)
[14:38] <rdb> Is there a way to claim a username? Someone else has a username that I'd really like to have, he/she has never used launchpad yet, and doesn't reply to my e-mails.
[14:39] <danilos> rdb, you should probably file a request at https://answers.launchpad.net/launchpad and admins will rename that account and let you rename yours if the previous one was never really used
[14:40] <rdb> It was really never used: https://launchpad.net/~rdb
[14:40] <rdb> But thanks, I'll do that.
[14:42] <wgrant> A question was asked by that user.
[14:42] <wgrant> But that's it.
[14:44] <rdb> https://answers.launchpad.net/launchpad/+question/106620
[14:44] <rdb> There we go. Thanks for your help. =)
[15:07] <joaopinto> hello
[15:08] <joaopinto> I am getting a lot of spam on an LP team ML, doesn't it use some integrated spam removal tool ?
[15:19] <Drakeson> how can I notify a relevant user (whose email is @ubuntu.com) not currently on the subscribers list of a bug?
[15:19] <Drakeson> oops
[15:19] <Drakeson> nevermine
[15:22] <Drakeson> if I add someone to the subscribers list, do they get all the messages, or the messages posted on the bug from then on?
[15:23] <dhastha_> need help: Unable to install launchpad-developer-dependencies.
[15:23] <joaopinto> the messages posted from then on
[15:23] <Drakeson> joaopinto: thanks. I guess I have to find them on irc then.
[15:27] <psusi> as a member of ubuntu-dmraid and ubuntu-bugsquad, I used to be able to change the Importance of bugs in the dmraid package when it was in universe... it has been moved to main and now shows ubuntu-dev as the maintainer and I can not set the Importance... could this be fixed somehow?
[15:29] <james_w> psusi: you need to be in ubuntu-bugcontrol to change the importance. I'm not sure what has changed, but that doesn't matter if the package is in main or universe.
[15:30] <psusi> james_w: I was thinking the maintainer changed from ubuntu-dmraid to ubuntu-dev
[15:31] <psusi> but I could be confusing ubuntu-bugsquad and ubuntu-bugcontrol... maybe I used to be in both and my membership expired in bugcontrol...
[15:33] <psusi> yea... I think that's what happened.... though that would let me work on all bugs in ubuntu... would it be possible to set ubuntu-dmraid to be able to manage just the bugs in the dmraid package?
[15:34] <james_w> that's not currently possible AIUI
[15:37] <psusi> oh well... guess I need to renew my membership in bugcontrol then... yea... just checked my mailbox and it expired on 5/8/2009 ;)
[15:43] <lfaraone> Hi, somehow https://code.launchpad.net/~sugarteam/turtleart/debian  got stacked on lp:turtleart. Now, when I try to branch /debian, I get "bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~lfaraone/turtleart/trunk/"."
[15:43] <lfaraone> How can I unstack the /debian branch? (it's not based on turtleart at all)
[15:49] <ricotz> hello, is there a timeframe for fixing the ppa package publishing
[15:51]  * Drakeson wishes there was also possible to report that a bug does NOT affect some other distribution, such as debian.
[15:54] <maxb> lfaraone: I think the problem is not what it is stacked on, but rather that according to the LP db, /debian is stacked on ~sugarteam/turtleart/trunk, whereas according to bzr, it's stacked on ~lfaraone/turtleart/trunk
[15:56] <maxb> Download this script of mine: http://j.maxb.eu/~maxb/bits/bzr-set-stacked-url.py
[15:56] <maxb> And run ./bzr-set-stacked-url.py lp:~sugarteam/turtleart/debian lp:sugarteam
[16:05] <lfaraone> maxb: okay, will do.
[16:06] <lfaraone> maxb: you mean "./bzr-set-stacked-url.py lp:~sugarteam/turtleart/debian lp:turtleart"
[16:06] <lfaraone> maxb: right?
[16:06] <maxb> oh
[16:06] <maxb> Yes :-)
[16:06] <lfaraone> maxb: ideally I don't want /debian stacked on anything :)
[16:07] <maxb> lfaraone: The fact that it's needlessly stacked shouldn't hurt anything, but once you've fixed the current inconsistency, you should be able to use `bzr reconfigure --unstacked` on it
[16:34] <hakaishi> Hi, I'm still there to wait for a solution for the "publication pending" problem in https://launchpad.net/~hakaishi/+archive/qshutdown/+packages . Anything found yet? - Can't I just delete the package and make a new upload?
[16:40] <persia> You may be able to, but it depends.
[16:40] <persia> I haven't seen any traffic about it since near the time you last asked, at which point it was blocked on finding someone with access to the logs to hunt down the issue.
[16:44] <hakaishi> persia: If I have to wait all day, I'll just try to delete it and make a new upload... - It could be that this problem was caused by uploading a newer version right after I uploaded another one. The second one was accepted before the first one...
[16:45] <smoser> is there a way to un-attach an "also affects distribution" link on a bug ?
[16:46] <smoser> someone incorrectly linked a debian bug to bug 523148 .  I'd like to avoid the confusion that that may cause.
[16:48] <maxb> There's no way to delete a bugtask. You have to settle for status=Invalid
[16:53] <persia> smoser: You can also unlink it from a specific bug, or change to which bug it's linked.
[16:54] <smoser> thanks.
[17:08] <chrisccoulson> is there anything wrong with PPA's at the moment? I uploaded some packages to https://edge.launchpad.net/~tracker-team/+archive/tracker last night, and they built 14 hours ago but aren't published yet
[17:09] <hakaishi> Aha! there is someone else with the same problems I have^^
[17:11] <ripps> some packages in the gmpc-trunk/gmpc-stable ppa have been stuck in pending publication for around 24 hours, what's up? I need those packages published before I can build some other ones
[17:11] <ripps> Looks like a number of people are having my problem
[17:12] <persia> Excellent.  More folk having the problem increases the chances the logs can be made available to someone who can interpret them.
[17:12] <persia> I'd recommend that one of you files a question, and the others "Add information" with more details.
[17:13] <persia> This saves the mess of hanging around on IRC asking every few hours, and 3 is enough folk that there's probably going to be good information to debug it.
[17:14] <hakaishi> I just tried removing my package and reupload. While two of three builds finished the publication wasn't a Problem, but after the last one finished there now is "pending publication" again....
[17:15] <persia> Best leave it so the bug can really be fixed, rather than fussing with it.
[17:26] <hakaishi> I've found something similar: https://answers.launchpad.net/soyuz/+question/105345
[17:27] <persia> hakaishi: Does the same solution work for you?
[17:27] <persia> If not, it deserves a new question.
[17:28] <hakaishi> persia: I'm looking into it
[17:29] <hakaishi> No, this is somthing different... That person forgot the hook at .../+archive/somePackage/+edit
[17:33] <hakaishi> Okay, I'll create that question at "Launchpad itself"
[17:39] <hakaishi> https://answers.launchpad.net/launchpad/+question/106631
[18:02] <hakaishi> persia, ripps, chrisccoulson: I've filed the question at https://answers.launchpad.net/launchpad/+question/106631
[18:03] <persia> I think flacoste is working on it already, based on the /topic change.
[18:03] <flacoste> persia: yes, the soyuz team is investigating the issue
[18:11] <hakaishi> ok...
[18:45] <nikm> How can I change my password?
[19:26] <pmjdebruijn> lo
[19:26] <pmjdebruijn> right... KNOWN ISSUE :)
[19:26]  * pmjdebruijn confirms the KNOWN ISSUE :)
[19:26] <pmjdebruijn> byebye
[20:20] <psusi> there is no way in lp to releate bugs other than duplicate?
[20:20] <psusi> what do you do when one bug depends on another bug for instance?
[20:21] <jpds> psusi: No, you can't do that.
[20:21] <jpds> psusi: There's a bug for that feature somewhere.
[20:21] <psusi> heh
[20:24] <jpds> bug #95419
[20:46] <qense> Maintenance mode? Where did that come from?
[20:47] <cody-somerville> qense, what do you mean?
[20:47] <qense> cody-somerville: Briefly a message appeared on Launchpad that it was read-only and in maintenance mode, which is in accordance with the fact that I don't seem to be able to make changes to LP-data
[21:02] <Kangarooo> hello. i posted bug 30min ago in launchpad about LP search. but now i wanted to add one possible solution and in my people page in bugs that bug is not showing. maybe it was deleted or wasnt saved? i clicked save and i saw all page.
[21:03] <qense> the data did change, don't know why I couldn't see it
[21:03] <ubott2> Launchpad bug 30 in malone "comments on bugs require subjects" [Medium,Fix released] https://launchpad.net/bugs/30
[21:51] <tekknokrat> hi, i just try to dput a package to my repo again, but it is rejected!
[21:52] <tekknokrat> File fsvs_1.2.2-0karmic0.diff.gz already exists in ... , but uploaded version has different contents.
[21:53] <tekknokrat> how can i upload the package again?
[21:57] <geser> bump the version number of the package, e.g. to 1.2.2-0karmic1
[22:18] <jtimberman> Does the topic change mean publications are working again? Will pending publications happen automatically or do the packages need to be re-uploaded/rebuilt?
[22:40] <bdrung> hi, can a member of ~vcs-imports remove https://code.launchpad.net/~vcs-imports/dvdbackup/trunk? i want to bazaar for development now and do not need the vcs import any more.
[22:50] <beuno> bdrung, gone!
[22:51] <beuno> (kinda, it timed out)
[22:52] <bdrung> beuno: thanks
[23:09] <Talidan> hi there, i'm trying to configure Bazaar Explorer with launchpad, but cant figure out how to setup authentification
[23:10] <Talidan> i've generated a public key, added it to launchpad, but cant see how to do it in bazaar explorer
[23:14] <Talidan> whatever happened to username and passwords :P