Re: action needed for python-lamson and rubygem-cloudservers

Hi On Fri, May 30, 2014 at 6:39 PM, Till Maas wrote: > > The process is described here: > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life > Is this what you wanted? The message can be specified on the command > line with fedpkg retire. It is not possible to do this via a we

Re: action needed for python-lamson and rubygem-cloudservers

On Fri, May 30, 2014 at 06:22:09PM -0400, Rahul Sundaram wrote: > On Fri, May 30, 2014 at 5:51 PM, Till Maas wrote: > > Thank you for the information. I retired it together with lastuser, the > > third dependent package. Btw. it is helpful to specify such details in > > the dead.package file. >

Re: action needed for python-lamson and rubygem-cloudservers

Hi On Fri, May 30, 2014 at 5:51 PM, Till Maas wrote: > > > Thank you for the information. I retired it together with lastuser, the > third dependent package. Btw. it is helpful to specify such details in > the dead.package file. > I was

Re: action needed for python-lamson and rubygem-cloudservers

On Fri, May 30, 2014 at 03:22:43PM -0400, Rahul Sundaram wrote: > On Fri, May 30, 2014 at 8:11 AM, Till Maas wrote: > For the record, lamson was dropped due to > > https://bugzilla.redhat.com/show_bug.cgi?id=972251 > > Lamson was originally packaged for askbot which powers > http://ask.fedora

Re: action needed for python-lamson and rubygem-cloudservers

Hi On Fri, May 30, 2014 at 8:11 AM, Till Maas wrote: > Hi, > > rubygem-cloudservers is currently retired in packagedb but not blocked > in koji/dead-packaged. python-lamson is dead-packaged but not retired > or blocked. Both packages are dependencies for other packages and > therefore cannot b

action needed for python-lamson and rubygem-cloudservers

Hi, rubygem-cloudservers is currently retired in packagedb but not blocked in koji/dead-packaged. python-lamson is dead-packaged but not retired or blocked. Both packages are dependencies for other packages and therefore cannot be just completely retired. FYI: If you got this e-mail directly, you