Hi mika,
I tried to submit a bts to grml Bug Tracking System submit@bugs.grml.org yesterday. I made 3 attemps (across 7 hours), but today when I check, my bts is still not in the system.
I cc you @ mika@grml.org in my last 2 attemps. Could you check for me what I'm doing wrong please?
thanks
* T o n g mlist4suntong@yahoo.com [20080908 15:23]:
I tried to submit a bts to grml Bug Tracking System submit@bugs.grml.org yesterday. I made 3 attemps (across 7 hours), but today when I check, my bts is still not in the system.
submit (at) bugs.grml.org is the wrong mail address for the BTS, it's bts (at) bts.grml.org instead.
I've added your mail to the BTS:
http://bts.grml.org/grml/issue523
I just noticed that http://wiki.grml.org/doku.php?id=bugs is horrible out of date, sorry. :(
Small notice: please try to split up bug reports into small parts so every single feature/wish/... is in a separate bugreport. This makes it much easier to track and work on. Thanks! :)
PS: I'll reply to issue523 as soon as I can, I just came back from the FAI developer meeting in Spain and have to catch up some stuff...
regards, -mika-
On Mon, 08 Sep 2008 15:49:45 +0200, Michael Prokop wrote:
submit (at) bugs.grml.org is the wrong mail address for the BTS, it's bts (at) bts.grml.org instead.
Oh, sorry, I was using an old version of reportbug. Erh, wait a second, having upgraded reportbug to the latest version, I can't find the grml bts option any more. I.e., previously 'reportbug --bts help' contains the grml entry but now it doesn't.
Small notice: please try to split up bug reports into small parts so every single feature/wish/... is in a separate bugreport. This makes it much easier to track and work on. Thanks! :)
OK, I'll remember it next time. This time it is a little special that the two options are closely related with each other -- description of the 2nd depends on the 1st...
cheers
On Mon, Sep 08, 2008 at 02:49:14PM +0000, T o n g wrote:
On Mon, 08 Sep 2008 15:49:45 +0200, Michael Prokop wrote:
submit (at) bugs.grml.org is the wrong mail address for the BTS, it's bts (at) bts.grml.org instead.
Oh, sorry, I was using an old version of reportbug. Erh, wait a second, having upgraded reportbug to the latest version, I can't find the grml bts option any more. I.e., previously 'reportbug --bts help' contains the grml entry but now it doesn't.
It was removed from "reportbug" when we migrated to the new bugtracking system (reportbug only works with debian-style bts).
greets Jimmy
On Mon, 08 Sep 2008 17:38:51 +0200, Andreas Gredler wrote:
having upgraded reportbug to the latest version, I can't find the grml bts option any more. I.e., previously 'reportbug --bts help' contains the grml entry but now it doesn't.
It was removed from "reportbug" when we migrated to the new bugtracking system (reportbug only works with debian-style bts).
Maybe it is now a good time to update the wiki on how to report bugs now, since new devel releases are available now, and people might start to report bugs.
thanks
* T o n g mlist4suntong@yahoo.com [20080930 06:19]:
On Mon, 08 Sep 2008 17:38:51 +0200, Andreas Gredler wrote:
It was removed from "reportbug" when we migrated to the new bugtracking system (reportbug only works with debian-style bts).
Maybe it is now a good time to update the wiki on how to report bugs now, since new devel releases are available now, and people might start to report bugs.
Thanks for the hint, did that:
http://wiki.grml.org/doku.php?id=bugs
If something is unclear please let me know, and feel free to correct my german-english wording. ;)
I also added links pointing to it from http://grml.org/bugs/ and http://wiki.grml.org/
regards, -mika-
Thanks mika, and for posting the debconf-get-selections.txt too.
On Tue, 30 Sep 2008 11:40:01 +0200, Michael Prokop wrote:
to submit bug report by email. is the format the same as that prepared by reportbug?
How about priorities, seems to me that grml current bts priorities are different than that of Debian.
Further, how to comment on a bts issue by email?
thanks
* T o n g mlist4suntong@yahoo.com [20080930 22:40]:
Thanks mika, and for posting the debconf-get-selections.txt too.
On Tue, 30 Sep 2008 11:40:01 +0200, Michael Prokop wrote:
to submit bug report by email. is the format the same as that prepared by reportbug?
Just send a mail, no special layout. A meaningful subject and more details in the body of the mail. :)
How about priorities, seems to me that grml current bts priorities are different than that of Debian.
That's stuff we (the developers) adjust according to our needs, no need to deal with it.
Further, how to comment on a bts issue by email?
If you have an account in the BTS you can login and just write stuff directly at the according bts issue. Ok, should be mentined at the bugs webpage in the grml wiki, thanks for the hint.
regards, -mika-
Thanks mika,
On Tue, 30 Sep 2008 22:46:11 +0200, Michael Prokop wrote:
to submit bug report by email. is the format the same as that prepared by reportbug?
Just send a mail, no special layout. A meaningful subject and more details in the body of the mail. :)
so there is no automatic linking of the bug report and the reported package. moreover, when would I get a confirmation message with an issue number then?
How about priorities, seems to me that grml current bts priorities are different than that of Debian.
. . .
Further, how to comment on a bts issue by email?
If you have an account in the BTS you can login and just write stuff directly at the according bts issue.
So there is no email address associated with each bts, as debian does, and use can't close a bts by email either.
hmm..., seems less automated than reportbug and more human intervention to me. I'm curious why we give up reportbug. Anyway, I believe the ease is on the administration side, not the end user side.
Thanks.
* T o n g mlist4suntong@yahoo.com [20081001 00:07]:
On Tue, 30 Sep 2008 22:46:11 +0200, Michael Prokop wrote:
to submit bug report by email. is the format the same as that prepared by reportbug?
Just send a mail, no special layout. A meaningful subject and more details in the body of the mail. :)
so there is no automatic linking of the bug report and the reported package. moreover, when would I get a confirmation message with an issue number then?
Each report gets its own issue id. You'll get a confirmation message as soon as anyone replies to the issue.
Further, how to comment on a bts issue by email?
If you have an account in the BTS you can login and just write stuff directly at the according bts issue.
So there is no email address associated with each bts, as debian does, and use can't close a bts by email either.
The email address identifies the person, if you want to *edit* stuff inside the BTS itself you have to login with an account.
You can use the BTS via mail as well: http://bts.grml.org/ -> "Roundup docs" -> http://roundup.sourceforge.net/doc-1.0/user_guide.html#e-mail-gateway
hmm..., seems less automated than reportbug and more human intervention to me. I'm curious why we give up reportbug. Anyway, I believe the ease is on the administration side, not the end user side.
It works better than reportbug because too many *users* of grml either didn't know about reportbug or are afraid of it at all (yeah, not a joke - that's really not uncommon). It works just fine for the administration side as well, that's why we switched from reportbug to roundup.
regards, -mika-
participants (3)
-
Andreas Gredler -
Michael Prokop -
T o n g