Am 15.02.2013 um 12:50 schrieb Johnny Hughes johnny@centos.org:

On 02/15/2013 05:28 AM, Tilman Schmidt wrote:

...

Every time I go to http://bugs.centos.org/my_view_page.php I am shown, under "Reported by me", three problems with the CentOS Bacula packages which I reported in 2011, complete with proposed fix, but which never got any love (status still "new"):

0005271 missing dependency mt-st bacula - 2011-11-28 12:44 0005261 make_catalog_backup.pl creates .my.cnf with bad mode bacula - 2011-11-24 11:19 0005260 bad symlink /usr/sbin/dbcheck bacula - 2011-11-24 11:08

As I have since switched to Simone Caronni's better maintained Bacula packages I would prefer not to be constantly reminded of that useless effort anymore. So I'd like to close them as "nobody cares" or something like that to get them off my radar.

Any hints how I can do that?

All these are package maintainer (Red Hat), not CentOS issues. CentOS is bug for bug compliant on purpose.

I will submit these to the upstream bugzilla if they are not already there.

Also, please remember that we depend on the community to answer questions in the bugs database and take actions there as well ...

https://bugzilla.redhat.com/show_bug.cgi?id=651780

-- LF

Am 15.02.2013 12:50, schrieb Johnny Hughes:

On 02/15/2013 05:28 AM, Tilman Schmidt wrote:

...

Every time I go to http://bugs.centos.org/my_view_page.php I am shown, under "Reported by me", three problems with the CentOS Bacula packages which I reported in 2011, complete with proposed fix, but which never got any love (status still "new"):

0005271 missing dependency mt-st bacula - 2011-11-28 12:44 0005261 make_catalog_backup.pl creates .my.cnf with bad mode bacula - 2011-11-24 11:19 0005260 bad symlink /usr/sbin/dbcheck bacula - 2011-11-24 11:08

As I have since switched to Simone Caronni's better maintained Bacula packages I would prefer not to be constantly reminded of that useless effort anymore. So I'd like to close them as "nobody cares" or something like that to get them off my radar.

Any hints how I can do that?

All these are package maintainer (Red Hat), not CentOS issues. CentOS is bug for bug compliant on purpose.

Well, yes, sure, I understand why CentOS cannot fix these. But that doesn't answer my question.

I will submit these to the upstream bugzilla if they are not already there.

Thanks. That'll surely help those who still use those packages. But again, it doesn't address my problem. I have switched to a different build and would just like not to be bothered by my misguided reports to bugs.centos.org anymore.

Also, please remember that we depend on the community to answer questions in the bugs database and take actions there as well ...

I actually tried to do that, by isolating the source of the problems and proposing solutions as best I could. But I never found a way to get those solutions through to anyone who would have been able to actually get them into the affected packages. That was of course my own fault for not looking in the right places. But all this is long past. Today I just want to get rid of these old reports.

Thanks, Tilman

On 02/15/2013 06:07 PM, Tilman Schmidt wrote:

Am 15.02.2013 12:50, schrieb Johnny Hughes:

...

On 02/15/2013 05:28 AM, Tilman Schmidt wrote:

...

Every time I go to http://bugs.centos.org/my_view_page.php I am shown, under "Reported by me", three problems with the CentOS Bacula packages which I reported in 2011, complete with proposed fix, but which never got any love (status still "new"):

0005271 missing dependency mt-st bacula - 2011-11-28 12:44 0005261 make_catalog_backup.pl creates .my.cnf with bad mode bacula - 2011-11-24 11:19 0005260 bad symlink /usr/sbin/dbcheck bacula - 2011-11-24 11:08

As I have since switched to Simone Caronni's better maintained Bacula packages I would prefer not to be constantly reminded of that useless effort anymore. So I'd like to close them as "nobody cares" or something like that to get them off my radar.

Any hints how I can do that?

All these are package maintainer (Red Hat), not CentOS issues. CentOS is bug for bug compliant on purpose.

Well, yes, sure, I understand why CentOS cannot fix these. But that doesn't answer my question.

...

I will submit these to the upstream bugzilla if they are not already there.

Thanks. That'll surely help those who still use those packages. But again, it doesn't address my problem. I have switched to a different build and would just like not to be bothered by my misguided reports to bugs.centos.org anymore.

...

Also, please remember that we depend on the community to answer questions in the bugs database and take actions there as well ...

I actually tried to do that, by isolating the source of the problems and proposing solutions as best I could. But I never found a way to get those solutions through to anyone who would have been able to actually get them into the affected packages. That was of course my own fault for not looking in the right places. But all this is long past. Today I just want to get rid of these old reports.

Thanks, Tilman

I do not see any way that a user can do that ... if you insist, I will mark them closed. We don't delete them and I am not entirely sure what making them closed would do for you in particular.

I understand that you are not happy that it took so long to get updated, but these are now actually valid items. If you would like me to close them, then let me know ... however, I have just actually reported them upstream so they should probably stay open.