=== LewisCawte is now known as Lcawte|Away | ||
=== yofel_ is now known as yofel | ||
=== Lcawte|Away is now known as LewisCawte | ||
=== LewisCawte is now known as Lcawte|Away | ||
=== Lcawte|Away is now known as Lcawte | ||
sao | hey guys. I was trying to create a recipe for a bzr branch following the instruction on https://help.launchpad.net/Packaging/SourceBuilds/GettingStarted. When coming to "Setting up the recipe in Launchpad" I was looking for the link "Create packaging recipe" on my bazaar branch page but cannot find it. Could it be that this link has moved somewhere else or do I need to enable it somewhere? | 22:34 |
---|---|---|
karni | Well well, you get +25 karma for asking porn-related question ;) haha | 22:35 |
karni | https://answers.launchpad.net/ubuntuone-storage-common/+question/139455 | 22:35 |
karni | https://launchpad.net/~lewowpard/+karma | 22:35 |
WasserDragoon | hello everyone, is it possible to open bugs in a team? because there's no report a bug link at the top right: https://bugs.launchpad.net/~apache-zeta-components | 22:38 |
karni | WasserDragoon: I don't think so. You should report bugs against software projects. | 22:39 |
WasserDragoon | karni: but why there's a menu item "bugs" then? | 22:40 |
sao | k just found the answer to my question ;) (https://answers.launchpad.net/launchpad/+question/124741) | 22:40 |
radix | WasserDragoon: those are bugs that are assigned or owned by the team | 22:40 |
karni | WasserDragoon: interesting. they don't drive any projects https://launchpad.net/~apache-zeta-components/+related-software | 22:40 |
radix | (or any of those things on the top-right) | 22:41 |
karni | WasserDragoon: that's kinda strage. | 22:41 |
radix | WasserDragoon: bugs can be assigned to a team, for example | 22:41 |
WasserDragoon | radix: how to assign bugs to a team? | 22:41 |
radix | WasserDragoon: when you report the bug, you can determine who to assign it to. | 22:42 |
WasserDragoon | on https://launchpad.net/ubuntu/+filebug ? | 22:42 |
radix | WasserDragoon: but bugs are about software, not people, so you have to report them on a project. | 22:42 |
WasserDragoon | radix: ok i registered a project, how to connect the project to the team, now? | 22:50 |
radix | WasserDragoon: well, you can make the team the "bug supervisor" by clicking "configure bug tracker" | 22:54 |
radix | but that's not strictly necessary -- you can just file bugs against that project, and then in the bug itself, assign it to the team. | 22:55 |
WasserDragoon | radix: ok thanks a lot | 22:56 |
WasserDragoon | radix: i selected, that i wont be the maintainer of the project because i'm not a developer of this project, just a packager. now i can't configure the bug tracking stuff https://bugs.launchpad.net/zeta | 22:58 |
WasserDragoon | i can't file a bug here https://launchpad.net/zeta/+filebug | 23:13 |
maxb | WasserDragoon: Yes, and that page tells you why: "Apache Zeta Components does not use Launchpad as its bug tracker. " | 23:15 |
WasserDragoon | maxb: okay, but i can't set it as its bug tracker, because i selected that i wont be the maintainer | 23:16 |
WasserDragoon | so how to set now? | 23:16 |
maxb | If you are not associated with the project, it would be misleading to start a bugtracker in Launchpad that the main dev team do not know about | 23:16 |
=== TheUni is now known as theuni | ||
=== theuni is now known as TheUni | ||
WasserDragoon | maxb i created the project | 23:18 |
maxb | At this point, you'll need a member of Launchpad staff to give the project ownership back to you | 23:19 |
maxb | I agree that that checkbox during project registration really ought to make the implications of disowning the project clearer | 23:19 |
WasserDragoon | maxb: thats why i checked the box | 23:20 |
WasserDragoon | i didn't knew that i'm not the admin anymore | 23:20 |
maxb | Although, based on "< WasserDragoon> radix: i selected, that i wont be the maintainer of the project because i'm not a developer of this project, just a packager.", it seems to me that you really should not be starting an independent bugtracker | 23:20 |
maxb | At least, not under the upstream project record | 23:20 |
WasserDragoon | i just need a packaging bug tracker, if there are some bugs in the deb packages itself | 23:21 |
maxb | In that case, you should not establish it under https://launchpad.net/zeta, which should have its bugtracking settings set to point to https://issues.apache.org/jira/browse/ZETACOMP | 23:22 |
maxb | You are making PPA packages for this? | 23:22 |
WasserDragoon | maxb: right | 23:22 |
maxb | Launchpad currently lacks a sensible way to handle bugs filings against a PPA. It only has the concept of bugs against a project or distribution source package | 23:23 |
maxb | Is this package going to go into Ubuntu eventually? | 23:24 |
WasserDragoon | maxb: i don't know | 23:25 |
maxb | ~> | 23:28 |
maxb | The only option for a bugtracker in Launchpad for PPA only packages that I can think of is to create a separate project, i.e. https://launchpad/net/apache-zeta-components-ppa | 23:29 |
WasserDragoon | maxb that's what i tried, but i think your name is better :-) i'll do that now, thanks | 23:31 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!