Bug 970016 - Mantainer has been absent for more than 4 years
Summary: Mantainer has been absent for more than 4 years
Alias: None
Product: Fedora
Classification: Fedora
Component: bacula (Show other bugs)
(Show other bugs)
Version: rawhide
Hardware: All All
Target Milestone: ---
Assignee: Simone Caronni
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-06-03 10:33 UTC by Simone Caronni
Modified: 2013-06-06 15:54 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-06-06 15:54:44 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Simone Caronni 2013-06-03 10:33:00 UTC
The bacula package had the mantainer missing since 1st December 2008:


No package updates were committed, no commits in the git repositories; no bugs were resolved since that date.

This request is to start the missing package mantainer process [1]; I'm already a co-mantainer of the package and most of the work in the past years has been done by myself.

[1] https://fedoraproject.org/wiki/Package_maintainer_policy#What_to_do_if_a_maintainer_is_absent

Comment 1 Andreas Thienemann 2013-06-03 10:39:06 UTC
Huh? Mind explaining what exactly the problem is?

Comment 2 Simone Caronni 2013-06-03 10:43:07 UTC
Ehm, there has been no activity from you on the package in the past years. Do you have any plan to come back to it?

Comment 3 Simone Caronni 2013-06-03 10:45:49 UTC
Can we at least make a switch (i.e. owner for me and co-mantainer for you) so that I don't need to reassign the bugs to myself all the time?

Please read also I mail I sent to the Fedora devel list 2 weeks ago:



Comment 4 Fedora Admin XMLRPC Client 2013-06-05 18:55:42 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Note You need to log in before you can comment on or make changes to this bug.