the state of yank

The yank package: * is orphaned (bug#374129), * has been maintained by NMUs for 3 years, * has several potential replacements in the archive, * is buggy according to its own description, * is probably the last one to use GConf 1. Should I ask for its removal? (please

Re: the state of yank

reassign 374129 ftp.debian.org retitle 374129 RM: yank -- unmaintained, buggy, old, has replacements thanks * Josselin Mouette <[EMAIL PROTECTED]> [2006-08-01 11:56]: > The yank package: > * is orphaned (bug#374129), > * has been maintained by NMUs for 3 years, > * has several po

Re: Bug#357020: dict-wn: could not be installed when runningalternative for dictd

* Andreas Tille <[EMAIL PROTECTED]> [2006-08-01 08:53]: > Thanks for CCing these people. What would you regard as reasonable > time to wait for them? ... > What would you think about stop building the dict-wn package? Well, I'd really like for Bob Hilliard to comment given that he maintains dict.

advanced features.

databases including crop trade through Cornell keyword too. popular requested Freedom Act Food spews garbage nothing Thing Complaint esteem silly problem. train finest technical support planet common errors. erroneous system settings youll messages Alaska Arizona Arkansas Colorado D

RM: zope-zshell -- RoQA; orphaned, not packaged for current Zope

retitle 361018 RM: zope-zshell -- RoQA; orphaned, not packaged for current Zope reassign 361018 ftp.debian.org thanks I think we should remove zope-shell. * Orphaned for 3 months. * Not certain whether it works with Zope 2.9 or 3.x; it is currently packaged for Zope 2.8. * Last upstream

Re: RM: zope-zshell -- RoQA; orphaned, not packaged for current Zope

When I was asked about my MIA status and orphaning my packages, I said that it made sense to remove zope-zshell from the archive. Upstream, a very good developer and a nice guy, is very busy, and has not updated it in a long time. It uses some gory corners of python to do some of its work. It i

Renaming jaxml to python-jaxml

retitle 380848 Python transition (#2): misnamed package with public modules thanks jaxml is a bit of an anomaly: it used a single package to provide a public module for Python 2.1, 2.2, and 2.3. It's not a stand-alone application, so it should really, really be called python-jaxml. There are two

Re: Renaming jaxml to python-jaxml

Le mar 1 août 2006 22:42, Matej Vela a écrit : > retitle 380848 Python transition (#2): misnamed package with public > modules thanks > > jaxml is a bit of an anomaly: it used a single package to provide a > public module for Python 2.1, 2.2, and 2.3. It's not a stand-alone > application, so it sh

Re: Renaming jaxml to python-jaxml

Pierre Habouzit <[EMAIL PROTECTED]> writes: > Le mar 1 août 2006 22:42, Matej Vela a écrit : >[...] >> Victor, as the maintainer of scanerrlog, would you like to adopt >> jaxml? >> >> And QA folks: can we go ahead and remove jaxml immediately? If it's >> adopted and renamed, it'll have to go thro

Re: Renaming jaxml to python-jaxml

Le mar 1 août 2006 23:45, Matej Vela a écrit : > Pierre Habouzit <[EMAIL PROTECTED]> writes: > > Le mar 1 août 2006 22:42, Matej Vela a écrit : > >[...] > > > >> Victor, as the maintainer of scanerrlog, would you like to adopt > >> jaxml? > >> > >> And QA folks: can we go ahead and remove jaxml imm

RM: xcircuit -- RoQA; orphaned, RC buggy

retitle 323678 RM: xcircuit -- RoQA; orphaned, RC buggy reassign 323678 ftp.debian.org thanks I think we should remove xcircuit. * Orphaned for 11 months. * 2 RC bugs, plus a soon-to-become-RC bug for the Python transition. * Already removed from testing. * popcon: 277 installs, 35 votes.

RM: eroaster -- RoQA; orphaned, RC buggy

retitle 364280 RM: eroaster -- RoQA; orphaned, RC buggy reassign 364280 ftp.debian.org thanks I think we should remove eroaster. * Orphaned for 3 months. * 1 RC bug. * The previous maintainer says: "It is not maintained upstream, buggy, and closely dependent on cdrtools. I'd suggest tha