[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#758231: rsyslog: is priority important, depends on packages with priority extra



unmerge 758231
retitle 758231 rsyslog: is priority important, depends on packages with priority extra
reassign 758231 rsyslog 8.2.2-3
severity 758231 serious
retitle 758233 cron: is priority important, depends on package with priority extra
reassign 758233 cron 3.0pl1-124.2
severity 758233 serious
quit


15:34:45 bug#758229 filed against nfacct
15:47:02 bug#758231 filed against rsyslog
15:52:19 bug#758233 filed against cron
15:57:05 1st followup from rsyslog maintainer, ironic
15:59:55 bug#758231 re-assing to ftp.debian.org, merged with #758233,
         severity set to normal, retitle by ftpmaster
16:10:24 cross-post to two lists from rsyslog maintainer, intends to
         re-assign to policy
16:17:07 bug#758231, 758233 re-assign to policy
16:21:10 bug#758234 filed against policy, asking to remove MUST in
         policy by ftpmaster
16:31:42 cross-post to three mailing lists from rsyslog maintainer, FUD


Heck, I was preparing a mail to debian-qa to give some explanation
about my reasoning and suggestions on how to improve the situation.
Don't you have other things to do?  If not, how about thinking a bit
about what the concerns of the bug submitter could be?

In another area I work, this is called the
 jumping-on-bugs-anti-pattern

I really don't think this is the way bugs filed by a Debian developer,
who is with Debian since more than 13 years, should be handled.
Actually no matter who filed the bugs.

I filed bugs, raised my concerns, and stand by this.

> forcemerge 758231 758233
> retitle 758233 override: init-system-helpers: admin/important

This is not the bug I reported, but "rsyslog: is priority important,
depends on packages with priority extra" and a list of four packages,
not one.

For reasoning, see
 https://lists.debian.org/debian-policy/2014/08/msg00033.html
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758234#35


Reply to: