Only two days ago, another package was accepted into unstable from NEW under the name of 'rush'. Thus the name 'rush' must now be considered as taken, which influences this RFP.
The other package also has an upstream 'rush', which made my sponsor change the 'gnurush' suggestion for my package to be 'rush'. It was only as my package entered NEW that the name collision came to our attention. Since the Ruby-kin shell, asked for in this thread, has not seen any activity since March 2009, whereas I have been refining my package since February 2010, one could argue that the more active package, now in the unstable branch, has earned the priority. This message is written in order to signal 'rush' as a taken name for a binary executable, for a binary package, as well as for a source package. The situation is unfortunate, but that is the path a chain of events happened to follow. Regards, Mats Erik Andersson, DM -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org