Josef, On Wed, Jun 18, 2014 at 07:30:47PM +0200, Josef Wolf wrote:
On Wed, Jun 18, 2014 at 04:23:02PM +0200, Lars Müller wrote:
On Wed, Jun 18, 2014 at 09:24:54AM +0200, Josef Wolf wrote:
On Fri, Jun 13, 2014 at 10:55:45PM +0200, Lars Müller wrote:
... when you file the issue/ report via https://github.com/ Also be this nice to report the issue ID as a clickable URL back to this thread.
Github.com don't seem to recognize my account and "forgot password" says, it can't find my email address.
Have you ever created one at the github.com? That's nothing that happens automatically if you have an account for bugzilla or openSUSE.
But bugzilla seems to work from a different computer. Here's the link to the bug:
https://bugzilla.novell.com/show_bug.cgi?id=883260
I could not find out how to assign to aaa_base, though.
As aaa_base is a package it not possible to assign the bug to it. Packages are maintained by one person or a group. The individual(s) responsible for a package you get by calling: osc maintainer aaa_base -e I expect the bug is assigned to the bugzilla screening team at the moment. And it will stay there till they find the time to move it to a responsible person. With the help of the the osc maintainer sub command the community is enabled to accelerate the process a lot. It would be a nice hackweek or student summer of code project to get this more automated/ better integrated on the bugzilla side. Might be worth to file a issue at github or a feature request if there is none. Unfortunately we had this discussion before. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany