Need help with revelation
Hello debian-python, I have been maintaining revelation in the past, a GNOME2 Password manager. I will most likely orphan this package because: - I no longer use revelation - I don't have a sponsor right now - Upstream is discontinued since, Tuesday 16. January 2007 11:44 There are a couple of bugs left, for some of them I do have an upload ready, which you can dget from: http://bc-bd.org/www/revelation/revelation_0.4.11-4.dsc Please note that the above release does not include a NMU, 0.4.11-3.1, which is currently in sid and lenny. Simply removing the package may be a bad idea, as people who are using revelation will then no longer be able to access their password lists. Additionally upstream is looking for someone to take over the stable branch development, aka. bug fixing etc. Maybe somebody on this list wants to take over maintaining revelation, or even better, maintaining upstream. Regards Stefan PS: please CC me, as I am not on this list. -- A man was reading The Canterbury Tales one Saturday morning, when his wife asked "What have you got there?" Replied he, "Just my cup and Chaucer." -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Need help with revelation
On Mon, Dec 22, 2008 at 05:22:09PM -0500, Scott Kitterman wrote: > On Mon, 22 Dec 2008 21:00:40 + b...@bc-bd.org wrote: > >... > >Simply removing the package may be a bad idea, as people who are using > >revelation will then no longer be able to access their password lists. > >... > > Removing the package from the archive won't remove it from installed > systems. > > If it's dead upstreamam then I'd suggest it ought to go. You are right that removing it from the archive will not uninstall it on systems directly, but revelation pulls in a lot of dependencies (directly and indirectly) and in the past it has happen more than once that revelation was uninstalled due to library incompatibilities. So what might happen, is that revelation gets removed from a system because some dependency changes. IMHO we should provide uses with some kind of exist strategy, perhaps a popup dialog saying something like "This program is dead upstream, it may be removed from the next stable release without further notice, we recommend that you migrate your password information to another application". Regards Stefan -- BOFH excuse #416: We're out of slots on the server -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
