Bug 675408 - Non-responsive Maintainer Process - Please respond.
Summary: Non-responsive Maintainer Process - Please respond.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Authen-Krb5
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Simon Wilkinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-05 13:38 UTC by Steve Traylen
Modified: 2011-02-08 10:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-08 10:55:06 UTC
Type: ---


Attachments (Terms of Use)

Description Steve Traylen 2011-02-05 13:38:58 UTC
Hi

Following the procedure outlined here

http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers

I'm am commencing this procedure for fedora user id: sxw

The last build by sxw was in July 2008.

http://koji.fedoraproject.org/koji/userinfo?userID=598

Bug #673472 for perl-Authen-Krb5 is a recent submission but has gone
            unanswered since it was submitted 28th January 2011.

Bug #474311 for remctl was submitted on 3rd December 2008 and has
            not been commented on or has it been resolved since then, remctl
            is still at version 2.11.

 Packages owned by swx:

(Name, Current in F14, Current Upstream)

(kstart, 3.11, 3.16)
(perl-Authen-Krb5, 1.7,  1.9)
(perl-Catalyst-Model-LDAP, 0.16, 0.17)  
(perl-Catalyst-Plugin-StackTrace, 0.10, 0.11)
(perl-Catalyst-View-JSON, 0.30, 0.32)
(perl-HTML-Prototype, 1.48, 1.48)
(perl-Task-Weaken, 1.02, 1.03)
(remctl, 2.11, 2.16)

Please respond to this bug.

If there is no response to this bug the next step will be another comment
in this ticket in 7 days time.
Many Thanks
Steve.

Comment 1 Simon Wilkinson 2011-02-08 10:55:06 UTC
Hi,

Sorry about the delay in responding to 673472 - the real world has got in the way somewhat recently. I'll take a look at pushing some new builds out.

Cheers,

Simon.


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