| ubotu | New bug: #176641 in launchpad "SanDisk SD Memory Card doesn't work in card reader, Ubuntu Gutsy Gibbon" [Undecided,New] https://launchpad.net/bugs/176641 | 00:41 |
|---|---|---|
| ubotu | New bug: #176643 in launchpad "SoundBlater 5.1 digital soundcard doesn't work all the time" [Undecided,New] https://launchpad.net/bugs/176643 | 01:25 |
| * Fujitsu sighs. | 01:28 | |
| ubotu | New bug: #176644 in malone "Blueprint icon in bug listings should be more descriptive and linkified" [Undecided,New] https://launchpad.net/bugs/176644 | 01:31 |
| Nafallo | hmm | 01:32 |
| Fujitsu | lamont: I'm liking the steep look of the hppa line. | 03:00 |
| ubotu | New bug: #176656 in launchpad "Concord Eye Q Duo 2000 USB Digital Camera Doesn't Work in Ubuntu 7.10" [Undecided,New] https://launchpad.net/bugs/176656 | 03:40 |
| jml | d'oh. | 03:43 |
| Fujitsu | Not another one. | 03:49 |
| Fujitsu | I bet it was the same person. | 03:49 |
| Fujitsu | Indeed it was. | 03:49 |
| * Fujitsu deals with it similarly. | 03:49 | |
| Fujitsu | Maybe they'll realise it's the wrong thing to do after I've corrected it some 3 times. | 03:50 |
| jml | Fujitsu: I was really hoping that the "Launchpad itself" rename was going to prevent that sort of thing | 04:06 |
| Fujitsu | jml: That's what I would have hoped, yep. | 04:08 |
| Fujitsu | As it appears not to help, maybe we can have sanity restored again and rename it back! | 04:11 |
| mariocesar_bo | Hi all, How works the download action on the translations ... I am waiting two days to launchpad send me the .po file. | 15:20 |
| === Ubulette_ is now known as Ubulette | ||
| ubotu | New bug: #176729 in launchpad "launchpad blueprints not available for peer review" [Undecided,New] https://launchpad.net/bugs/176729 | 17:55 |
| outsidecontext | hi | 19:05 |
| outsidecontext | does anybody know if it is possible to purge the PPA or at least to remove wrongly uploaded packages? | 19:06 |
| === oojah_ is now known as oojah | ||
| thumper | morning | 19:58 |
| somerville32 | thumper, Any updates on closing bugs via bzr commits? :] | 20:26 |
| thumper | somerville32: not really | 20:28 |
| thumper | somerville32: in the upcomming release we have the first step of using the --fixes on the bzr commit to link bugs to branches | 20:28 |
| thumper | somerville32: the next step is to modify the associated task | 20:29 |
| thumper | somerville32: the interesting bit is how do you really determine that a bug is to be closed | 20:29 |
| thumper | somerville32: the current thinking goes something like this: | 20:29 |
| thumper | When a revision is found on the main-line history for a branch that says it fixes a bug, the branch should be linked to the bug and set as in-progress | 20:30 |
| thumper | once that revision finds its way into the ancestry for the development focus branch, then it is fix committed | 20:30 |
| thumper | however the automatic closing "fix released" is somewhat harder to determine | 20:30 |
| somerville32 | search for "closes lp: #xxx" ? | 20:31 |
| thumper | we don't scan the message, we check the associated revision properties | 20:31 |
| thumper | it is a little more difficult given the distributed nature of the bazaar branche | 20:32 |
| thumper | s | 20:32 |
| thumper | somerville32: just because a given branch has a revision that says it fixes a bug, doesn't mean that the bug fix has been released | 20:33 |
| somerville32 | Right | 20:33 |
| somerville32 | Maybe set it as fix committed? | 20:33 |
| thumper | right, and that is the plan | 20:33 |
| somerville32 | And then make it so you can connect a branch to a release? | 20:33 |
| somerville32 | And when that occurs, all bugs set as fix committed are upgraded to fix released | 20:34 |
| thumper | that would be pretty cool | 20:34 |
| mantiena-baltix | Hi all | 20:35 |
| * thumper tries to remember how we define a release | 20:35 | |
| thumper | morning mantiena-baltix | 20:35 |
| mantiena-baltix | thumper: evening thumper ;) | 20:35 |
| mantiena-baltix | it seems po export doesn't work in launchpad, at least for me :( | 20:36 |
| mantiena-baltix | I choosed to download gnome-volume-manager po file from rosetta but didn't get an email for about 3 or 4 hours | 20:36 |
| thumper | mantiena-baltix: sorry, don't know much about po exports | 20:37 |
| mantiena-baltix | :( | 20:43 |
| thumper | somerville32: here's an idea | 20:45 |
| thumper | somerville32: since series can have associated branches, and the releases are attached to a series | 20:46 |
| thumper | somerville32: perhaps we could have it so --fixes on the development focus branches get "fix committed", and --fixes on other series branches get "fix released"? | 20:46 |
| thumper | somerville32: that way when you cut a release branch (or merge into an existing release branch) the bug tasks could be closed out | 20:47 |
| somerville32 | hmm | 20:48 |
| thumper | somerville32: however this does give us a problem of reversability, that is setting the wrong branch as a release branch, having it update a whole pile of bug tasks, and then going "oops" | 20:48 |
| somerville32 | Maybe bug updates will have to be manually approved by the driver? | 20:49 |
| somerville32 | Or maybe have a threshold | 20:50 |
| thumper | perhaps we could have a page that shows all the bugs "fixed" by a branch that aren't yet marked as fixed | 20:50 |
| thumper | and have a "yep, these are released" button | 20:50 |
| * somerville32 nods | 20:50 | |
| thumper | that could be cool | 20:50 |
| thumper | hi BjornT | 20:50 |
| thumper | was just talking about bugs | 20:51 |
| BjornT | hi thumper | 20:51 |
| mantiena-baltix | BjornT: hi, maybe you know, why po export doesn't work in launchpad, at least for me :( | 20:52 |
| mantiena-baltix | I choosed to download gnome-volume-manager po file from rosetta but didn't get an email for about 3 or 4 hours | 20:52 |
| BjornT | mantiena-baltix: hmm. it seems like the export is broken at the moment. nothing i can do about it, though, i'll make sure the relevant people get notified about it. | 20:56 |
| mantiena-baltix | BjornT: thank you very much | 21:08 |
| MattCampbell | I'm not sure I understand the purpose of Launchpad. Can it be used as the primary host for an open-source project, like SourceForge but with Bazaar for version control? | 21:27 |
| MattCampbell | I ask because the title of the project registration page says "upstream". | 21:28 |
| thumper | MattCampbell: yes it can | 21:29 |
| thumper | MattCampbell: "upstream" I believe is used in relation to a package | 21:29 |
| thumper | MattCampbell: so "upstream" is the unadulterated source code | 21:30 |
| MattCampbell | No, I mean the title of the project registration page says "Register an upstream open-source project". To me that implied that the project's primary home should be somewhere else. | 21:30 |
| thumper | MattCampbell: I think that is just badly worded | 21:31 |
| MattCampbell | Also, is there any requirement that the project run on GNU/Linux or a free OS in general? | 21:32 |
| MattCampbell | For my first project, I want to release some Windows API bindings for hte Lua programming language, under the MIT/X license. | 21:32 |
| MattCampbell | And I like Bazaar, so Launchpad seemed to be the natural choice. | 21:33 |
| radix | There aren't any restrictions on what OSes the code must run on. | 21:33 |
| MattCampbell | I ask primarily because I know Launchpad was created originally for packages in Ubuntu. | 21:34 |
| MattCampbell | At least that's how it appears from my point of view. | 21:34 |
| thumper | MattCampbell: that was how it was originally, but it has moved on from just that | 21:35 |
| MattCampbell | And since Canonical is providing this free of charge, I certainly want to respect their wishes. | 21:35 |
| thumper | MattCampbell: Canonical doesn't care about which platform your project targets | 21:36 |
| MattCampbell | Why does Launchpad put the branch author's short username (e.g. username-basedomain) in the branch URL? | 22:11 |
| Fujitsu | MattCampbell: Why wouldn't it? It shows the ownership, potentially the reputability, and resolves namespace clashes. | 22:12 |
| MattCampbell | So should I leave the branch author field blank for the main branch? | 22:12 |
| Fujitsu | That won't work. You should create a team if multiple people will be working on it. | 22:13 |
| Fujitsu | If you set it as the trunk branch afterwards, people should be able to branch from https://code.launchpad.net/project or lp:project anyway. | 22:13 |
| Fujitsu | So the owner for the trunk branch probably won't be seen much. | 22:13 |
| jml | Fujitsu: that's a good answer, btw. | 22:19 |
| jml | re why show username. | 22:19 |
| Fujitsu | jml: Really? That's good. | 22:22 |
| MattCampbell | In this case, I'm releasing code that I wrote for my employer, with my employer's permission. It's possible that in the future, someone else working for the same company may work on this code. So I set up the company as a team and will make it the owner of the trunk. | 22:22 |
| Fujitsu | That would probably work. | 22:22 |
| Fujitsu | You can easily transfer ownership at any later stage, though it can get messy if people have existing checkouts. | 22:23 |
| MattCampbell | I'll use my own Launchpad account to commit to the branch, correct? | 22:24 |
| MattCampbell | even though the owner is a team | 22:24 |
| MattCampbell | I mean author | 22:24 |
| Fujitsu | Correct. | 22:24 |
| MattCampbell | Any Launchpad admins here? | 22:30 |
| MattCampbell | I just set up a team called "serotek" with a newly created email address "dev@serotek.com" as the contact email. I haven't yet received the confirmation message at that address. So I'm wondering if it's stuck at our spam/virus filtering service. | 22:31 |
| jml | MattCampbell: All of the LP admins that I know of are asleep or enjoying a lazy sunday afternoon :) | 22:33 |
| MattCampbell | Fair enough, I'll wait a while. | 22:34 |
| jml | MattCampbell: can you not check with your filtering service? | 22:34 |
| MattCampbell | Fujitsu: Thanks for the help earlier. | 22:34 |
| Fujitsu | MattCampbell: No problem. | 22:35 |
| MattCampbell | jml: Any tech support people at MailRoute (our filtering service) are probably doing the same thing as the LP admins. :) | 22:38 |
| MattCampbell | I can wait. | 22:39 |
| MattCampbell | I'm sure the confirmation message is just being held by greylisting. | 22:41 |
| somerville32 | What is the format for poll dates? | 22:46 |
| somerville32 | Ok | 22:54 |
| somerville32 | What a waste :/ | 22:54 |
| SWAT | are there any rules about creating teams in launchpad? Are teams like ubuntu-de-events allowed? | 23:10 |
| thumper | SWAT: I don't think there are rules... | 23:28 |
| SWAT | thumper, is it OK to use launchpad as a group management tool? (because I think that's happening). I just want to be sure of it | 23:32 |
| SWAT | A extra 'team' shouldn't be a huge load, but I don't know if it's frowned upon | 23:32 |
| thumper | SWAT: I believe so | 23:32 |
| SWAT | thumper, in that case, thanks for the info. | 23:32 |
| === oojah_ is now known as oojah | ||
| cyberix | I've been developing some software in a Launchpad hosted Bazaar branch and now I'm planning to do the first release. Am I supposed to create a web page for the software at some external site, or can I somehow use Launchpad to publish tar.gz archives? | 23:36 |
| spiv | cyberix: you can host the tar.gz files on Launchpad | 23:39 |
| spiv | cyberix: there's a "Download project files" action link on your project's overview page. | 23:41 |
| cyberix | So how do I upload project files then? | 23:43 |
| thumper | cyberix: I think there is a link on the download files page to upload files if you have permission to do so (as a project Driver) | 23:57 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!