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 are a affected (co)maintainer.
Package (co)maintainers ======================================================================= python-lamson kumarpraveen, kumarpraveen, pjp, ralph, sundaram rubygem-cloudservers orphan
The following packages require above mentioned packages: Depending on: python-lamson lastuser (maintained by: sundaram, kumarpraveen, pjp, sundaram) lastuser-0.1-5.20110724gitf41a49.fc18.src requires python-lamson = 1.3.4-1.fc20
python-flask-mail (maintained by: sundaram, kumarpraveen, pjp, sundaram, tflink) python-flask-mail-0.6.1-5.fc20.src requires python-lamson = 1.3.4-1.fc20
funnel (maintained by: sundaram, kumarpraveen, pjp, sundaram) funnel-0.0-5.20110803git66922b.fc20.src requires lastuser = 0.1-5.20110724gitf41a49.fc18
Depending on: rubygem-cloudservers deltacloud-core (maintained by: mfojtik, clalance, mfojtik) deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudservers) = 0.4.2
condor-cloud (maintained by: imain, imain) condor-cloud-0.1-7.fc20.noarch requires deltacloud-core = 1.1.3-1.fc20
Affected (co)maintainers clalance: rubygem-cloudservers imain: rubygem-cloudservers kumarpraveen: python-lamson mfojtik: rubygem-cloudservers pjp: python-lamson ralph: python-lamson sundaram: python-lamson tflink: python-lamson
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 be just completely retired. FYI: If you got this e-mail directly, you are a affected (co)maintainer.
Package (co)maintainers======================================================================= python-lamson kumarpraveen, kumarpraveen, pjp, ralph, sundaram
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.fedoraproject.org but it is a optional dependency for a functionality we don't use in Fedora infrastructure. I have now retired the dependent packages as well. It might be feasible to replace it with a fork
https://pypi.python.org/pypi/salmon-mail/0
If anyone is interested, you are very welcome to do that. fedpkg retire threw up the following similar error for the two dependent packages but seems to have done the process anyway
No collection found by the name of devel Could not retire package: Command '['pkgdb-cli', 'orphan', '--retire', 'funnel', 'devel']' returned non-zero exit status 8
Rahul
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.fedoraproject.org but it is a optional dependency for a functionality we don't use in Fedora infrastructure. I have now retired the dependent packages as well. It might be feasible to replace it with a fork
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.
No collection found by the name of devel Could not retire package: Command '['pkgdb-cli', 'orphan', '--retire', 'funnel', 'devel']' returned non-zero exit status 8
There are patches in the queue to fix this.
Regards Till
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. https://admin.fedoraproject.org/mailman/listinfo/devel
I was wondering about that. What is the best practice for this? Is it detailed anywhere? Also, can you do this via the web UI?
Rahul
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.
I was wondering about that. What is the best practice for this? Is it detailed anywhere? Also, can you do this via the web UI?
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 web UI.
Regards Till
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 web UI.
Ah, I missed the description at the end of it. Noted for future retirements. Thanks
Rahul
-
Rahul Sundaram -
Till Maas