Bug 1044029 - EasyTAG co-maintenance request
Summary: EasyTAG co-maintenance request
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: easytag
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Saou
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-17 16:27 UTC by David King
Modified: 2014-01-09 12:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-09 12:04:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description David King 2013-12-17 16:27:18 UTC
Following the policy at:

https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers

I am filing a bug to request a response from the easytag package maintainer.

There are several open bugs, which would be fixed by updating the easytag package to 2.1.8, as noted in bug 951265. I have posted a spec file and SRPM for EasyTAG 2.1.8 in that bug. At least bug 548833, bug 925288 and bug 954121 would be fixed by the update. It is likely that several other open bugs would also be fixed with the update.

I have requested commit permissions for master (rawhide) and f20 branches in the pkgdb:

https://admin.fedoraproject.org/pkgdb/acls/name/easytag

Please respond so that the update can be pushed.

Comment 1 David King 2013-12-24 16:28:28 UTC
Hi, it has been a week without a response. I would still like to be a co-maintainer of the package, and get the remaining package bugs fixed. Please respond.

Comment 2 David King 2014-01-01 13:14:06 UTC
Hi, it has been another week without a response. I posted to the devel mailing list to try to elicit a response:

https://lists.fedoraproject.org/pipermail/devel/2014-January/193301.html

Comment 3 David King 2014-01-09 12:04:48 UTC
All resolved now:

https://lists.fedoraproject.org/pipermail/devel/2014-January/193654.html


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