[02:29] <RenatoSilva> Asking again: how about a GPL project with a lot of copyright holders using LP for translations?
[02:30] <RenatoSilva> in current policy, ALL of them need to deliver their translations under BSD, when importing the translations to LP
[02:30] <RenatoSilva> why not lock these imported msgstrs to only GPL-compatible projects
[02:32] <RenatoSilva> why make everything BSD? this makes projects like the example not be able to use LP
[02:35] <spiv> RenatoSilva: perhaps try the launchpad-users mailing list?  I'm no sure if any of the translations people are around in this timezone.
[02:44]  * RenatoSilva lazy
[02:45] <spiv> RenatoSilva: :)
[02:45] <spiv> RenatoSilva: well, so long as you're patient as well as lazy, I'm sure it'll work out :)
[02:54]  * RenatoSilva goes watch LOST
[04:30] <crimsun> OOPS-1473C388
[04:38] <spiv> crimsun: ouch, death by thousand cuts^WSQL queries.
[04:38] <spiv> (well, almost)
[04:38] <spiv> No single really obvious culprit from a 5 second glance :/
[08:58] <aquarius> I have many, many small projects; no more than a half-dozen files of HTML+JavaScript or Python or whatever. I'd like to keep these in source control. I used to use svn for this. I'd like to use LP instead, but setting up a project is a big pain. Is there some easily-taken middle ground?
[08:59] <aquarius> I don't really want to push the branches as +junk -- the projects aren't junk, they're just small.
[09:00] <ronny> make a single project, just push to branches below that?
[09:00] <adeuring> aquarius: I'm afraid that we don't have anything smaller than projects.
[09:01] <wgrant> aquarius: Why is setting up a project a pain?
[09:01] <aquarius> ronny, I thought about that. Isn't it likely to be a bit confusing for people? Also, won't LP keep complaining at me about not having set a main branch for the project?
[09:01] <adeuring> aquarius: I think ronny is right (assuming that your projects are at least slightly related)
[09:02] <aquarius> wgrant, fill in a long page, pick a description, nominate a branch as trunk
[09:02] <aquarius> svn experience of "creating a new project": svn mkdir http://svn.kryogenix.org/svn/projectname; svn co !$ .; svn add *; svn commit -m "first checkin"
[09:03] <wgrant> You should just need to fill in the name, summary, description and license.
[09:03] <aquarius> these projects don't rate their own description pages, talks about what they are, that sort of thing; they're just a way to get the code online.
[09:03] <aquarius> so maybe the answer is: write a launchpadlib script that creates a minimal project
[09:04] <aquarius> wgrant, if I don't nominate a trunk branch, though, it's confusing for someone who goes to launchpad.net/projectname, because they will say: where do I get the code from?
[09:05] <wgrant> aquarius: Right. So nominate a trunk branch.
[09:05] <aquarius> and, realistically, the only question I expect people to ask about these projects is "where do I get the code from"? If that's in any way hard or confusing then it's a deal breaker for this use :-)
[09:05] <wgrant> That takes about two seconds.
[09:06] <aquarius> adeuring, the projects are totally, totally unrelated, unless "I wrote them" counts as a relation ;)
[09:06] <aquarius> so it sounds like you guys are suggesting that I create a new LP project for each thing, and I just have to live with LP requiring more metadata?
[09:07] <adeuring> aquarius: well, i think it depends on how much of the LP features you want to use aside from code hosting
[09:07] <adeuring> aquarius: the more things you want to use, the more hassles you'll get if you have just one project
[09:08] <aquarius> adeuring, yeah, so the one-project-to-rule-them-all idea is probably a bad one.
[09:09] <adeuring> aquarius: probably. Anyway, how many projects are you talking about? (plain curiosity ;)
[09:09] <aquarius> http://svn.kryogenix.org/svn/ has 41
[09:10] <adeuring> aquarius: I see. OK, needs some quite boring work to create these projects on LP...
[09:11] <aquarius> yep.
[09:11] <aquarius> looks like I need to write a launchpadlib script, which is annoying because it solves the problem for *me* but doesn't solve it for anyone else.
[09:12] <aquarius> so everyone else will look at lp and think: blimey, setting up projects is a pain, by comparison with {my svn server, github, etc} :(
[09:12] <aquarius> hm, making it a bzr plugin would be good
[09:12] <aquarius> bzr new-lp-project
[09:15] <adeuring> aquarius: If/when you set up these 41 projects, it might help us if you send a short notice to feedback@launchpad.net. We are monitoring the creation of new projects to avoid "spamming" of Launchpad with unused or bogus projects. Just mention the existing SVN repository so that the reviewer can see that there is some real code for these projects.
[09:20] <aquarius> adeuring, cheers for that tip :)
[09:20] <adeuring> aquarius: welcome ;)
[09:22]  * adeuring thinks it would be really frustrating if you set up all these 41 projects and the out reviewers suspects that somebody did not know what he was doing and disables all these projects....
[09:24] <aquarius> you are entirely correct :)
[09:25] <aquarius> right, time to go talk to the bzr people about extending their launchpad plugin. :)
[09:51] <aquarius> weird. https://help.launchpad.net/API/launchpadlib says to use launchpad = Launchpad.login_with('just testing', 'staging', cachedir), which says lazr.uri._uri.InvalidURIError: "staging" is not a valid URI.
[09:51] <aquarius> Does it need to be "https://staging.launchpad.net" rather than "staging"?
[09:51] <aquarius> (i.e., is this a doc bug)
[09:52] <aquarius> indeed yes, it looks like a doc bug
[09:52] <aquarius> er!
[09:53] <aquarius> and now I get an undefined entity &nbsp; traceback when authorizing.
[09:54] <spiv> aquarius: I would guess you should use launchpadlib.launchpad.STAGING_SERVICE_ROOT
[09:54] <spiv> But that's a wild guess considering I haven't even looked at that doc link :P
[09:55] <aquarius> and that also fixes the second bug, too :)
[09:55] <spiv> aquarius: maybe look at bzrlib/plugins/launchpad/lp_api.py?
[09:55]  * aquarius files a doc bug
[10:01] <aquarius> hm. So...if I know that there's a REST method available (to create new projects, in this case), how do I know how what launchpadlib calls it?
[10:07] <maxb> launchpad.net/+apidoc
[10:07] <maxb> though I'd be surprised if something as complex and usually guided as project creation had an API method
[10:11] <aquarius> https://edge.launchpad.net/+apidoc/#projects-new-project
[10:11] <aquarius> I know there's a REST method for it. What I don't know is how to call that using launchpadlib.
[10:18] <adeuring> aquarius: I think the call is lp.projects.new_project(...9
[10:20] <aquarius> adeuring, aha, that exists. got it; launchpad.<section name>.<rest method name>
[10:20] <aquarius> that's useful :)
[10:21] <adeuring> aquarius: right. If you are confused by the API doc, it often helps to take a look at the webservice tests. In this case, I looked in lib/lp/registry/stories/webservice/xx-project-registry.txt of the LP source code.
[10:21] <aquarius> adeuring, can't imagine why I didn't think to look there ;-)
[10:21] <adeuring> (line 658)
[10:21] <aquarius> that's handy, though; now I'll know where to look next time :)
[10:22] <adeuring> aquarius: well, for perfcet documentation, that shouldn't be necessary ;) But we are humans and haven't yet figured out how to write perfect dics ;)
[10:22] <adeuring> ...perfect docs...
[10:27]  * aquarius creates a project on staging from launchpadlib. Nice.
[10:28] <persia> aquarius: Was that standalone, or with bzr lp new-project?
[10:28] <aquarius> persia, lp new-project already exists??
[10:28] <persia> Not to my knowledge.  I thought you were adding it.
[10:29] <aquarius> oh right, OK, I see what you mean. No, not from a bzr plugin yet; direct with launchpadlib. I'm experimenting to see how to do it before I start writing code
[10:42] <komputes> Is there a page on Launchpad that shows, overall, what bugs affect the most users. (A tally sheet of 'affectsmetoo').
[10:56] <komputes> Also is there a way to list the user a bug affects?
[10:58] <adeuring> komputes: there is an API method bug.users_affected_collection_link
[10:58] <adeuring> (for you latter question)
[10:58] <adeuring> komputes: regarding your first question: I don't hink that we have such a page
[10:58] <komputes> adeuring: not sure how I can use that> in combinating with launchpad scripts (like what bdmurray does?)
[10:59] <persia> Could one use the collection_link to get a countable list of users to get the affected count?
[10:59] <komputes> adeuring: how hard would it be to hack one together quickly (or would it kill the db)?
[11:00] <persia> komputes: Note that making staging thrash would probably have less effect on most users.  The data is a bit outdated, but it would be close to what you seek.
[11:00] <adeuring> komputes: (1) load an launchpadlib bug object; (2) iterate over bug.users_affected
[11:01] <adeuring> persia: tehre is also the API property bug.users_affected_count
[11:01] <persia> nifty :)
[11:01] <persia> SO it's just query all open bugs, and then sort by that property.  Handy nice list.
[11:01] <komputes> adeuring: need some help with 1 & 2, sorry, I use launchpad a lot, but think is a little outside my comfort zone. Can any user do this or special permissions are needed?
[11:02] <adeuring> persia: yes
[11:02] <persia> komputes: Try installing launchpadlib and reading the docs.  It mostly needs a bit of python.
[11:02] <komputes> persia: okidok
[11:03] <komputes> python-launchpadlib
[11:03] <persia> komputes: Also https://help.launchpad.net/API/launchpadlib
[11:03]  * komputes is checking it out
[11:03] <adeuring> komputes: as persia says: should be easy to do. See https://help.launchpad.net/API/ and https://help.launchpad.net/API/Uses to find examples.
[11:04] <mwhudson> iterating over all open bugs doesn't sound like a small amount of data
[11:04]  * komputes grrrs to himself, no man page ;)
[11:05] <adeuring> komputes: There are lots of methods to find bugs; if you already know which bug or bugs you are interested in, simply call lp.load(https://api.edge.launchpad.net/beta/bugs/<id>) to get the bug object.
[11:07] <adeuring> And you can get the string "https://api.edge.launchpad.net/beta" as launchpadlib.launchpad.EGDE_SERVICE_ROOT (similar for staging)
[11:13] <marchino> can i download a tar package of a project which does not provide any download files?
[11:14] <marchino> (...from lauchpad, it was implicit)
[11:14] <marchino> launchpad*
[11:16] <mwhudson> marchino: you mean, can you download the current branch tip as a tarball?
[11:17] <marchino> mwhudson: yep
[11:17] <mwhudson> then no, that's not implemented yet
[11:17] <spiv> There's always "bzr export project.tar.gz lp:project"
[11:18] <mwhudson> you can do bzr export lp:foo foo.tar.gz, but most of the work is on your side in that case
[11:18] <spiv> Probably not amazingly efficient.
[11:18] <spiv> (But shouldn't be completely terrible either)
[11:19] <marchino> i haven't clone the project
[11:19] <marchino> i think i must do it
[13:38] <nad> g.m.
[14:48] <Peng> Why does Launchpad like to change a couple of my Experimental branches to Development?
[14:54] <ripps> Does anybody have any idea when launchpad ppa download counters are going to show up?
[15:03] <bdmurray> komputes: disregarding the formatting of the page - http://qa.ubuntu.com/reports/launchpad-database/bugs-with-most-users-affected.html
[15:05] <komputes> bdmurray: exactly what I was looking for, thanks
[15:06] <komputes> bdmurray: by the way I wanted to chat with you about a few things (private?)
[15:10] <komputes> bdmurray: that is, ping me when you have some free time
[16:12] <gnomefreak> anyone here that can remove/suspend a users LP account. Please see bug 505092
[16:19] <adeuring> gnomefreak: thanks for the notice!
[16:19] <gnomefreak> adeuring: np
[16:19] <RenatoSilva> anyone from translation/licenses here?
[16:22] <adeuring> RenatoSilva: for license question, ping bac; for trnaslations, henninge or danilos
[16:23] <bac> hi RenatoSilva -- what sort of licensing issues are you referring to?
[16:24] <RenatoSilva> bac: imagine a project like MoinMoin which has its own system of translation, but wants to use LP now
[16:25] <RenatoSilva> bac: so they have to import current translations into LP, and the start new translations at Launchpad
[16:25] <bac> RenatoSilva: if you are asking specifically about licensing of translations then you need to talk to henninge or danilos.
[16:25] <RenatoSilva> henninge: ^
[16:25] <RenatoSilva> danilos: ^
[16:26] <RenatoSilva> but afaik when you import translations in LP, they become available for all LP users under BSD license...
[16:26] <henninge> RenatoSilva: AFAIUI, All new translations done in LP will be BSD-licensed, the imported strings will remain whatever they are.
[16:27] <henninge> RenatoSilva: no, imported strings keep their license.
[16:27] <RenatoSilva> henninge: that's unclear in the wiki docs anyway, but how LP manages that, it has a flag for each msgstr standing whether it's from LP or external?
[16:28] <henninge> RenatoSilva: yes.
[16:28] <RenatoSilva> is it recent? because it seems the docs weren't clarified about that
[16:29] <RenatoSilva> henninge: you know MoinMoin right? So this all means that Thomas can start using LP for translations without worrying about copyright violation?
[16:31] <RenatoSilva> henninge: I have presented LP to Thomas and sugegsted him to use LP at least for translations, but he didn't because of license, he would have to ask each contributor to convert the msgstrs to BSD, now this is not needed, great
[16:33] <henninge_> RenatoSilva: Yes, of course ... ;-)
[16:33] <RenatoSilva> henninge: btw, if you could look into this issue, I'd thank you: https://bugs.launchpad.net/rosetta/+bug/478902
[16:33] <henninge_> RenatoSilva: But what kind of violations are you expecting?
[16:34] <RenatoSilva> henninge_: you mean what Thomas was afraid of?
[16:34] <henninge_> RenatoSilva: Simple strings like "File", "Submit", etc. are too common to be protected.
[16:34] <henninge_> RenatoSilva: yes
[16:35] <henninge_> RenatoSilva: More complex strings are usually too specific to the project that their translations could not be used elswhere unless used with a fork of the software.
[16:35] <henninge_> and that fork would be under the license of the software anyway.
[16:35] <henninge_> GPL, I assume.
[16:36] <RenatoSilva> henninge_: at that moment a few months ago, we understood that all imported stuff wo9uld be available to LP users under BSD, which means a license change because Moin translations are GPL. And license change can be done only by copyright owners which are a LOT of people, and even unknown
[16:37] <henninge_> RenatoSilva: exactly, that is why we didn't even start on that for LP translations ... ;-)
[16:37] <henninge_> RenatoSilva: BSD is most permissive.
[16:37] <d1b> public domain...:P
[16:37] <henninge_> RenatoSilva: Basically, the feat would be that GPL'ed translations end up in non-free software.
[16:38] <henninge_> s/feat/fear/
[16:38] <RenatoSilva> henninge_: the problem was not use BSD, it was change the license with permission of ALL authors
[16:38] <henninge_> Yes, bug a change from BSD to GPL for example is possible without any permission from any author, that's why it is the easier base.
[16:38] <henninge_> s/bug/but/
[16:38] <henninge_> pardon my typing.
[16:39] <RenatoSilva> henninge_: this is the current fear, for NEW translations done in LP, but for the imported, we thought in the past that we needed to contact every translation contributor to ask "may we import all current stuff into LP and change the license to BSD?"
[16:39] <henninge_> RenatoSilva: no need to do that, no.
[16:39] <RenatoSilva> henninge_: we misunderstood it in the past, or was it really that way some time ago?
[16:40] <henninge_> RenatoSilva: not really
[16:40] <RenatoSilva> so we misunderstood, ok
[16:40] <henninge_> RenatoSilva: We used to have two contradicting statements, one in the wiki, one in LP, I think.
[16:41] <henninge_> RenatoSilva: Then at one point we clarified that to be BSD and had every LP translator agree with that or remove his/her translations.
[16:41] <RenatoSilva> I think the wiki is at least unclear, *still*
[16:41] <henninge_> about a year ago
[16:41] <henninge_> possibly ... ;)
[16:41]  * henninge_ looks at bog
[16:41] <henninge_> bug
[16:42] <RenatoSilva> bug 478902 summarizes one thing I think is unclear
[16:43] <RenatoSilva> in a nutshell, making translations BSD require to add the BSD text in original and derived works
[16:44] <RenatoSilva> but when you download a po, you don't get the BSD notice with the list of copyright owners, and I don't think developers pay attention on this and add mannually the BSD text in their softwares
[16:45] <RenatoSilva> I think a possible solution is to change the licensing from "I give this to you as BSD" to "I give this to you as any BSD-compatible license you wish"
[16:46] <RenatoSilva> this would eliminate the need of adding the BSD text in projects using these translations
[16:47] <d1b> is the gpl compatible with the bsd...
[16:55] <RenatoSilva> bsd -> gpl yes, gpl -> bsd no
[17:14] <RenatoSilva> henninge: http://pastie.org/775085
[17:17] <RenatoSilva> [15:17] <RenatoSilva> ThomasWaldmann: sorry, it does NOT need to be rather "this po file is BSD", it MAY be "the same as project", however I think the BSD *text* should be exported together, either attached or inside the po body
[17:20] <henninge> RenatoSilva: thanks for the suggestions.
[17:20] <henninge> RenatoSilva: I will have to discuss this with the other's on the team to see what we can do here.
[17:24] <danilos> RenatoSilva, fwiw, exported PO file is not BSD licensed, and it can't be, because it's a derivative work
[17:24] <RenatoSilva> henninge: ok thanks. Improvements in the docs and procedures are welcome, as Thomas is still a bit worried
[17:25] <danilos> RenatoSilva, what is BSD licensed are translations provided through LP; in general, current copyright law doesn't really cope with the way translations of free software happen, and that's the biggest problem
[17:26] <danilos> RenatoSilva, when these BSD-licensed individual translations end up in a PO file, copyright law would usually make them whatever-parent-project-is-licensed-under since almost all licenses are "stricter" than BSD
[17:28] <danilos> RenatoSilva, the point we should probably try to clarify is that licensing applies strictly to the translation texts when they are used (i.e. integrated elsewhere)
[17:29] <danilos> RenatoSilva, like being integrated into certain project PO files, when the entire "collection of works" is distributed under the strictest license of all the works
[17:30] <RenatoSilva> exported PO file is not BSD licensed, and it can't be, because it's a derivative work???
[17:31] <RenatoSilva> works derived from BSD works canNOT be BSD still?
[17:31] <danilos> RenatoSilva, so, if you need to add BSD licensing information that would be completely correct, you could say something like: "for translations of messages 'blah', 'foo' and 'bar', you can also use those translations under BSD license"
[17:31] <danilos> RenatoSilva, PO file is not licensed under BSD because it's a derivative work of a POT file coming from a project (GPL in your case, I guess), some GPL translations (that you imported into Launchpad) and some BSD translations
[17:32] <RenatoSilva> what is BSD licensed are translations provided through LP ---> but exported po files may be made of these translations, fully or partially
[17:32] <danilos> RenatoSilva, such derivative work as a whole is basically GPL licensed; if you really want to be completely specific, you would have to say that some of the translations are available under looser terms of BSD, and you could list them
[17:33]  * RenatoSilva reading above, sorry...
[17:34] <danilos> RenatoSilva, basically, your full PO file can't be under BSD because it's a combination of works under GPL and BSD; for some parts of it, you can apply BSD to them; but for the whole file, you can only distribute it under GPL
[17:34] <danilos> that's why we chose BSD in the first place, because it can be embedded in any combined work (i.e. BSD is compatible with all free software licenses)
[17:35] <danilos> alternative is to do as TranslationProject did and ask for public domain translations, but we'd rather if people keep their copyright
[17:37] <RenatoSilva> danilos: I understand danilos
[17:37] <RenatoSilva> danilos: however the BSD text stands that it must be included in derived works, which doesn't happen when you get an exported .po file
[17:38] <RenatoSilva> danilos: the BSD text should go along with the .po when exporting from LP, and/or developers should be warned about the need of including the BSD text with copyright owners in their software
[17:39] <danilos> RenatoSilva, right, it's a tricky issue, since with GPL, you're probably fulfilling all the conditions anyway
[17:40] <RenatoSilva> danilos: I'm not sure, but don't we need the *exact* BSD text?
[17:40] <RenatoSilva> let me read it again
[17:40] <danilos> RenatoSilva, well, the thing is that Launchpad is a development tool; insisting on BSD license being included is like insisting that a source code browser which displays a single source file must also display the license on the same web page
[17:41] <danilos> RenatoSilva, you can eg. use bzr or svn or cvs (I know you can use cvs like this, don't think others can) to check-out a single file from the repository without getting the license file; and getting a single PO file is like this
[17:41] <ronny> RenatoSilva: btw, does any of the moinmoin guys actually agree on pushing the translations to lp?
[17:44] <RenatoSilva> I'm not sure if the GPL text itself (except for copyright list of course) is a "copy" or "implementation" of the BSD text, is it?
[17:44] <danilos> RenatoSilva, on reading it, it would still have to be included yes... so perhaps that was a bad choice on our part of the license
[17:45] <danilos> RenatoSilva, so, your source code distribution would probably have to include a copy of BSD if you want to be fully certain of being legal, but IANAL :)
[17:46] <RenatoSilva> ronny: please go to #moin if you can, but yes they seem friendly about using LP, jsut worried with licensing
[17:47] <RenatoSilva> IANAL? is there any irc dict command? :)
[17:47] <RenatoSilva> danilos: sorry but did you read that bug I pasted here? it's about this
[17:48] <RenatoSilva> danilos: my suggestion is: when some user translates something in LP, he's not giving his work to all the other LP users *under BSD*, but under *any BSD-compatible license*
[17:49] <RenatoSilva> danilos: it's like "changing the license early" (because developers using these translations will do that anyway)
[17:49] <RenatoSilva> danilos: the advantage is that there's no need to add the BSD text anymore
[17:50] <danilos> RenatoSilva, oh, haven't gotten to it yet, that sounds as a good idea, it's just a shame we haven't done it earlier because today...
[17:50] <danilos> RenatoSilva, today it would mean having everybody re-license their work *again*
[17:51] <danilos> RenatoSilva, also, I think nobody feels comfortable in lawyer offices with such blank statements (i.e. if we don't list what those licenses are, they're probably going to say that it's not legally binding)
[17:52] <RenatoSilva> how about each user having in its preferences what licenses he gives his translations under?
[17:52] <danilos> RenatoSilva, that would be impossible to track, and we'd have to implement per-message license checking which is exactly what we wanted to avoid
[17:52] <RenatoSilva> ok
[17:54] <danilos> RenatoSilva, i.e. we show translations from different projects as suggestions for identical strings, and if we introduce different licenses, we'd have to do license checks for each of the messages which would make code unreasonably complex
[17:54] <RenatoSilva> there isn't any legal meaning for "BSD-compatible"? For example, a legally acceptable list of compatible licenses, or even a clear way to determine in court whether a license X is compatible or not?
[17:55] <danilos> RenatoSilva, I don't think there is, "GPL-compatible" is a term defined by FSF and which talks only about licenses they wouldn't sue people over if they combined it with GPL work; others might still sue people if they have different interpretations of license compatibility
[17:57] <RenatoSilva> about everybody re-license their work, I can't get it. If you can change the license of current translations done in LP (can you?), then why users would need any re-licensed?
[17:57] <danilos> RenatoSilva, we can't change license of anything in LP, that's the whole thing
[17:57] <RenatoSilva> *re-licensing
[17:57] <RenatoSilva> danilos: so how you did in the past to change to BSD?
[17:58] <danilos> RenatoSilva, I've joined #moin, let's discuss it there
[17:58] <RenatoSilva> danilos: or are translations done in LP BSD since beginning??
[17:58] <danilos> RenatoSilva, we've asked people to consent to the change with a form which stopped them from doing any work before they either agreed or disagreed with it
[17:58] <RenatoSilva> danilos: ok
[17:58] <danilos> RenatoSilva, later we removed all translations for those who disagreed
[19:30] <jblount> Is there a way to trigger a 500 on launchpad so I can see the oops page?
[19:31] <jblount> Alternatively what is the template that has the oops page?
[19:33] <mars> jblount, append ++oops++ to the url (see https://dev.launchpad.net/Debugging)
[19:33]  * jblount high-fives mars
[19:34] <mars> np
[19:34] <matsubara> jblount, that won't give you the oops template page though
[19:35] <jblount> mars: Actually, I'm looking for the template, so I can look at the phrasing for inspiration for Ubuntu One
[19:35] <mars> ah
[19:35] <matsubara> jblount, the template for the oops page is oops.pt (lib/canonical/launchpad/templates/oops.pt)
[19:36] <mars> well, a round-about way to do it is to view an OOPs, pick a unique string, grep-find :)
[19:36] <beuno> jblount, our oops template is pretty broken atm
[19:37] <jblount> matsubara: Thanks (also mars & beuno)
[19:37] <matsubara> beuno, jblount: i just filed https://bugs.edge.launchpad.net/launchpad-foundations/+bug/506581 for the brokeness while QA'ing one of salgado's changes
[19:37] <beuno> mars, great, thanks
[19:38] <mars> matsubara, ^
[19:40] <matsubara> you're welcome :-)
[20:48] <otto_sange> hi, I have a Launchpad/Bzr branching question.
[20:49] <otto_sange> One of my friends published a branch with code, that is intended to be a part of a bigger project.
[20:49] <otto_sange> Now when I've written the bigger project and I'd like to include my friends code into it, what is the best way to do it?
[20:50] <otto_sange> Simply copying my friends code in a folder and then committing it does not sound good.
[20:51] <otto_sange> Should I do some kind of merger with two Bazaar branches, even though their content is completely different?
[20:52] <beuno> otto_sange, this ir more of a question for #bzr
[20:52] <beuno> (not an easy one)
[20:53] <otto_sange> Would the correct way be to first branch my friends code so that I have a local copy, then with bzr mv move all files into one folder caller "plugin", push it back into Launchpad as a new branch and finally merge my two own branches?
[20:53] <otto_sange> And what about access rights? How can my friend continue to commit to his code inside my bigger project?
[20:58] <RenatoSilva> your friend will maintain a plugin for your project?
[20:59] <otto_sange> RenatoSilva: yes, although it is not a plugin, rather a sub part
[21:00] <RenatoSilva> afaik at least LP has no support for commit permissions in parts of a branch
[21:01] <RenatoSilva> otto_sange: it seems you may want a build process
[21:01] <RenatoSilva> otto_sange: that process would bzr branch all required branches to set up a ready-to-use instance of your application
[21:02] <RenatoSilva> otto_sange: you could write a build.sh or so, and include that file itself in version control :)
[21:03] <otto_sange> RenatoSilva: ok, then the process to install the app is 1. branch my project 2. run build.sh which branches more projects as sub folders ..?
[21:04] <RenatoSilva> your friend could also branch the whole project, and work only in his subsystem, and *you* merge that work once in a while
[21:04] <otto_sange> RenatoSilva: ok
[21:05] <RenatoSilva> and he merges your changes which would not give any conflict as long as *you* don't touch *his* subsystem in the *main* branch
[21:06] <otto_sange> RenatoSilva: what about the series and milestones things in Launchpad. Are they of any use in this case?
[21:07] <RenatoSilva> for build.sh, maybe I would separate the result in another dir, targeted only for using, while current dir is targeted only for code commits. So I would not branch to a subdir.
[21:08] <otto_sange> RenatoSilva: apparently I could just register my friends branch as an independent series, so that it is visible in the code overview of my project, but that's it?
[21:08] <RenatoSilva> I would do somehting like zip required files to a /dist subdir, where that zip is already a download package ready for distribution, not just for testing while developing
[21:09] <RenatoSilva> that zip would be created with the files in the current main branch, plus the ones from you friend's branch, which would be bzr branched at the time of build to a /tmp or so
[21:10] <otto_sange> ok
[21:10] <RenatoSilva> otto_sange: I don't think series is suitable in your case
[21:11] <RenatoSilva> otto_sange: series is when you want to keep more than one big version
[21:12] <RenatoSilva> otto_sange: for example, bzr2 is an update of bzr1 with new features, but people still can use bzr1, which still receives security fixes etc
[21:13] <RenatoSilva> otto_sange: I have a project which is single-seried, that is, even when I add new features or change behavior of the software widely, that new version is pushed to end-users
[21:14] <RenatoSilva> they don't have the choice of using the old version, because I stop maintaing it immediatelly
[21:15] <RenatoSilva> if the users want important fixes, they need to move to the new version even if they don't like
[21:17] <otto_sange> ok, I was thinking about that too, but now when you confirmed it I feel much more confident in using bzr/Launchpad. Thanks for your help!
[21:35] <amondo> is there launchpad support personnel?
[21:36] <jpds> amondo: Not at the moment, see /topic.
[21:36] <amondo> okay thanks
[21:39] <jpds> amondo: But if you have a problem we can try and help you.
[21:40] <amondo> jpds: thanks... i am getting ubuntu bug reports to my launchpad project. my project has nothing to do with ubuntu. so i am trying to edit these user's bug reports and change the project that it affects to ubuntu or something. but searching for ubuntu in project list gives "too many projects" and then "undefined". no wonder the users are too pissed off to report the bugs to the right package. and its frustrating for me too because i h
[21:40] <amondo> ave to deal with all these bugs.
[21:41] <amondo> how do i put these bugs in the ubuntu bug queue?
[21:42] <RAOF> amondo: Your project is packaged in Ubuntu, and you're getting bugs which should be going to the Ubuntu package against your project?
[21:42] <amondo> no, there is no connection to ubuntu at all. started project called lucid back in 2007 or so and now i am getting ubuntu lucid bug reports
[21:43] <amondo> i even named my project "Lucid Editor NOT UBUNTU"
[21:43] <RAOF> Oh, whoops!
[21:44] <amondo> yeah, but you know, when users search for "ubuntu" in the package to report. they got nothing.
[21:44] <amondo> when they search for lucid, they at least get a hit.
[21:48] <jpds> amondo: Searching for "ubuntu" on bugs.launchpad.net brings up the Ubuntu project, but I can see your problem with lucid...
[21:49] <jpds> amondo: On bug #506445 - if you click "Also affects distro", you can mark it as an Ubuntu bug.
[21:49] <amondo> jpds: yes, it does.. i mean in a particular bug report, when you choose the "package name". it won't let you leave it blank.
[21:49] <amondo> oh i see... let me try
[21:49] <jpds> amondo: No, you can leave it blank, I just did that...
[21:50] <jpds> amondo: Then you'll have to mark your projects task as invalid, I'm afraid...
[21:50] <amondo> okay, so it still shows up in my bug list
[21:51] <amondo> jpds: marked it invalid now
[21:51] <jpds> Once Invalid, it shouldn't.
[21:51] <amondo> jpds: so that's all? should i repeat for other similar bugs?
[21:51] <jpds> Hmm, yeah...
[21:51] <amondo> jpds: thanks, will get on that shortly
[21:52] <jpds> amondo: And maybe have a template comment you can copy and paste into a comment explaining why you've done that.
[22:59] <highvoltage> hi, I need some LP support
[22:59] <highvoltage> how do I change the list of packages that's listed on https://bugs.edge.launchpad.net/~edubuntu-bugs/+packagebugs ?
[23:03] <amondo> is the list derived from the actual bugs?
[23:06] <amondo> highvoltage: no support person here atm, see topic
[23:08] <highvoltage> amondo: I'm not sure how it's derived
[23:08] <highvoltage> amondo: I guess I'll have to hang around for a while then :)
[23:10] <amondo> highvoltage: yeah, hang around... but i suspect the page lists aggregated data based on individual bugs. so if you ubsubscribe from individual bugs, you won't have an entry in the projects page. for example, if you unsubscribe from Bug #177287, then you won't have an entry for "tuxpaint-stamps in ubuntu"
[23:11] <amondo> it won't be zero, it just will not appear on the page at all
[23:11] <amondo> you can always test it out in staging.launchpad.net
[23:12] <micahg> highvoltage: you need to subscribe the team to the packages in question
[23:12] <micahg> highvoltage: that should probably be discussed with your team
[23:12] <amondo> micahg: i think he's trying to unsubscribe them, to remove entries from the package list
[23:13] <micahg> amondo: same thing
[23:13] <amondo> yeah
[23:13] <spiv> amondo: it's packages that ~edubuntu-bugs are subscribed to.  e.g. look at https://edge.launchpad.net/ubuntu/+source/denemo, under the "Bug subscriptions" heading in the sidebar.
[23:15] <amondo> spiv: yeah i see now
[23:16] <amondo> spiv: maybe "ubuntu development team" control the subscriptions
[23:16] <micahg> amondo: the team itself can control whether or not they are subscribed
[23:24] <highvoltage> I'm members of those teams but I don't see anywhere where I can unsubscribe ~edubuntu-bugs from those packages/bugs
[23:24] <maxb> highvoltage: I believe only team admins can subscribe/unsubscribe the team
[23:26] <micahg> ah, yeah, that's correct...it even says it on the page!
[23:27] <micahg> highvoltage: so it would have to be someone on the edubuntu council to do it
[23:29] <highvoltage> micahg: which I am on as well :)
[23:30] <micahg> indeed
[23:30] <micahg> highvoltage: on this page you should see a checkbox for Edubuntu Bugsquad: https://bugs.edge.launchpad.net/ubuntu/+source/atomix/+subscribe
[23:35] <highvoltage> micahg: ah, d'oh, I see now. I have to click on the "Subscribe" link in order to unsubscribe, that wasn't too obvious to me, thanks for your patience
[23:35] <micahg> highvoltage: np
[23:35] <highvoltage> (especially since there's a plus sign next to 'subscribe')
[23:35]  * micahg thought there was a bug to change that...
[23:37] <micahg> bug 273192
[23:37] <micahg> highvoltage: ^^
[23:37] <highvoltage> cool