[05:28] <dholbach> good morning
[05:29] <itchydog> good evening :)
[05:29] <dholbach> hi itchydog
[05:29] <itchydog> hello
[05:37] <itchydog> dholbach: have a good day,bye
[08:20] <thekorn> good morning
[08:22] <maco> thekorn: hello
[08:22] <thekorn> hi maco
[08:38] <thekorn> ara: hi, I'm about to add the hugday tool to ubuuntu-qa-tools,
[08:38] <thekorn> but lp:~ubuntu-bugcontrol/ubuntu-qa-tools/packaging is missing debian/ from you packaging branch
[08:38] <thekorn> can you please update this branch?
[08:39] <ara> thekorn: sure, will do
[08:39] <ara> thekorn: I didn't notice it was missing... weird
[08:41] <ara> thekorn: this one is the one: https://code.edge.launchpad.net/~apulido/ubuntu-qa-tools/packaging
[08:42] <thekorn> ok, I will use this one,
[08:42] <thekorn> and file a merge request for this one
[08:42] <ara> thekorn: ok, thanks
[09:33] <askand> Is there a need to file bugs about upgrading software in repos to the newest version in Jaunty?
[10:14] <ccooke> Is there, anywhere, some actual information about how to *do* things in Launchpad?
[10:14] <thekorn> ara: pushed my changes to lp:~thekorn/ubuntu-qa-tools/add_hugday, will do a test build and create the merge request this evening
[10:14] <ccooke> Not *what* to do or *when* to do it, just the actual mechanics of how you accomplish various tasks.
[10:15] <ccooke> For instance, correctly linking a bug to various types of project.
[10:15] <jpds> ccooke: help.launchpad.net ?
[10:16] <ccooke> jpds: I'm there
[10:16] <ara> thekorn: cool! thanks! I will review it tomorrow morning and ask for sponsorship accordingly
[10:16] <ccooke> not finding what I'm after :-/
[10:16] <ccooke> I see lots of stuff about what you *can* do
[10:17] <thekorn> ara: gracias
[10:17] <ccooke> ... uh. Oh. So you have to link a branch *to* a bug report. You can't link a bug report to a branch?!
[10:18] <dholbach> thekorn: maybe we should move hugdaylist into ubuntu-qa-tools now that it's there :)
[10:19] <jpds> ccooke: Maybe https://wiki.ubuntu.com/Bugs and subpages?
[10:20] <jpds> ccooke: https://wiki.ubuntu.com/BugSquad ?
[10:20] <ccooke> jpds: tried there, too :-)
[10:20] <thekorn> dholbach: yes, makes sense, where is this tool now?
[10:20] <ccooke> again, it's full of the when and the what, but very short on the how!
[10:21] <dholbach> thekorn: ubuntu-dev-tools
[10:21] <ccooke> the specific example: There's a bug that looks like a bash completion bug. I'm trying to link it to there - but I got the upstream, which apparently isn't used. And try as I might - although I've found the Ubuntu bash-completion project - I can't create a link to it!
[10:23] <jpds> ccooke: I see a +choose-affected-project link under the bug status info.
[10:23] <thekorn> dholbach: ok, u-qa-tools sounds like a better place,
[10:23] <thekorn> will also look at it later today
[10:24] <dholbach> thekorn: there's a bunch of bug tools in ubuntu-dev-tools that could probably move :)
[10:25] <ccooke> jpds: ... I don't. There's an "Also affects project" link... which has worked before... but the only bash-completion it lists is the upstream
[10:25] <ccooke> ... Ah, but there *is* a field for "package".
[10:26] <ccooke> bah.
[10:26] <ccooke> Except that's related to the thing it was *ioriginally* filed under.
[10:26] <ccooke> you can't *add* another package while keeping the current one.
[10:26] <jpds> ccooke: Which bug #?
[10:27] <ccooke> 327452
[10:27] <ccooke> (well, I'm sure you *can*. I'm just not seeing *how*)
[10:29] <jpds> ccooke: So we should like it to the ubuntu source package?
[10:29] <ccooke> well, it's a regression in Jaunty.
[10:29] <jpds> link*
[10:29] <ccooke> Sounds like something to link, yes
[10:30] <thekorn> dholbach: apropos scrips, you showed me a script to create source packages for multible versions of ubuntu at once and sign it, what's the name of this script and where can I find it?
[10:31] <jpds> ccooke: changed package assignment: Ubuntu --> bash-completion (Ubuntu)
[10:31] <ccooke> right. Noticed that. But you didn't actually add project/package
[10:32] <jpds> Yes, I just changed from distro to package.
[10:32] <ccooke> as I said, I (just :-) saw how to change the package, but can't see how to add one
[10:32] <ccooke> and it seems that the "usual" behaviour I've seen in bugs other people have worked on is to add the new package and leave the old one as invalid
[10:34] <ccooke> Right. Thanks anyway.
[10:35] <ccooke> Before I go fiel a bug against Launchpad's documentation... *is* there any documentaion on actual processes in there?
[10:35] <ccooke> I still can't see any.
[10:45] <dholbach> thekorn: daniels-machine-in-berlin:~daniel/bin/build-sources :-)
[10:45] <dholbach> http://people.ubuntu.com/~dholbach/build-sources
[10:45] <dholbach> but there's a nicer script somewhere, let me try to find it
[10:46] <thekorn> hehe, thanks
[10:46] <dholbach> https://launchpad.net/autoppa I think does something similar
[10:48] <thekorn> dholbach: thanks, but it looks more complicated ;)
[10:50] <dholbach> thekorn: the unstoppable james_w might have a more authoritative, cleverer and saner method too :)
[10:50] <dholbach> ... and better documented :)
[11:03] <ccooke> anyone: Is there any action on Launchpad you've had trouble finding the right way to accomplish?
[11:04] <ccooke> I'm filing a bug report on their documentation and trying to give some good examples of things that would help new users
[11:05] <james_w> I have nothing, sorry
[11:06] <ccooke> this is the problem with people who already know how to do things :-)
[15:06] <bddebian> Boo
[15:13] <BUGabundo> foo
[15:17] <Pici> bar
[15:17] <BUGabundo> crock
[16:39] <ubuntujenkins> Hi I am a newbie so hope someone can help. On the new bug reports page if there is a report such as https://bugs.launchpad.net/ubuntu/+bug/263561 . Is this a bug? It appears not to be a bug so can I some how remove it from the list or assign it to something else? If so what can it be assigned to?
[16:40] <ubuntujenkins> indeed
[16:42] <bdmurray> ubuntujenkins: it is a request for a new package and while not technically a bug report the best place for it is the bug tracking system
[16:42] <bdmurray> ubuntujenkins: you can learn more about them at https://wiki.ubuntu.com/Bugs/HowToTriage#Needs%20Packaging%20Bugs
[16:45] <ubuntujenkins> bdmurray: Thank you for that makes sense and appears to be easy. Should be able to sit and clear a few from the list.
[18:20] <EagleScreen> how can i add a tag to a bug?
[18:21] <bdmurray> EagleScreen: edit the description
[18:23] <EagleScreen> patch tag must be used when a patch is provided?
[18:24] <bdmurray> EagleScreen: no, what bug are you looking at?
[18:24] <EagleScreen> Bug #327333
[18:25] <EagleScreen> then what is the usage of patch tag?
[18:26] <bdmurray> EagleScreen: you could add it but it is kind of redundant.  You've already flagged the attachment as a patch which will make it appear in some Launchpad searches.
[18:26] <bdmurray> You can learn more about patches at http://wiki.ubuntu.com/Bugs/Patches
[18:27] <EagleScreen> thanks, but, with the patch already attached, must I do something else?
[18:29] <EagleScreen> ok i am reading
[19:43] <maco> i have a question about the Popularity Report
[19:43] <maco> can packages that mysteriously disappeared after Hardy and are not in sid be on that list?
[19:47] <bdmurray> if there is a needs-packaging bug about it yeah
[19:49] <maco> bdmurray: nvm, i'm being told in -motu that the maintainer went away and a better piece of software that's DFSG-free exists anyway
[23:40] <xlukasx> lol i guess its good if it's quiet here!