Short circuiting is fine here since maintainer was @redhat and mail bounces and user didn't update their FAS acct and no other contact method is known. This counts as a +1 from a FESCo member, sorry for the top post, I'm out right now. On 10/23/08, Michael Schwendt <mschwendt@xxxxxxxxx> wrote: > On Thu, 23 Oct 2008 14:51:23 -0700, Toshio Kuratomi wrote: > >> >> https://admin.fedoraproject.org/pkgdb/packages/name/pguiman >> >> >> >> Maintainer "odvorace" gives "user unknown" at Red Hat. >> >> Pkg ACLs are locked down. >> > >> > Who takes care of issues like this? >> > Is it necessary to follow the lengthy AWOL procedure? >> > https://bugzilla.redhat.com/468160 >> > >> I've opened the acl. >> >> Would FESCo like to short circuit the NonResponsiveMaintainers policy in >> this case? It seems like most of the steps in the procedure have been >> followed except that the opening of the bugzilla bug was done last >> instead of first. > > I didn't start any formal process. This is only one of a few packages > where I stumbled into locked ACLs while fixing lots of unowned > directories. Mailing the owner then failed. > > There's another open ticket which is unanswered for several months. > The app crashes and possibly doesn't work much, given that it's only > 0.0.1. > > The missing packager is also the upstream developer. > > -- > fedora-devel-list mailing list > fedora-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-devel-list > -- Sent from my mobile device Jon Stanley Fedora Bug Wrangler jstanley@xxxxxxxxxxxxxxxxx -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
