On Sun, Oct 08, 2006 at 11:05:45PM +0200, Matthias Andree wrote: > It cannot be a drop-in, since the hash function for Message-IDs is > different (making message.id/NNN/ assume a different layout), internal > file formats change and some filenames of internal book-keeping files > have also changed. That all comes under the sort of thing I'd really expect a package to take care of for the user. Someone using a Leafnode package via NNTP shouldn't see any of that. > At the very least, the downgrade way should be blocked and require a Debian doesn't support downgrades at all but yes, warning about this is possibly a good idea. > purge first (telling users this in the leafnode-2 preinstall that > they're on a path with no return), and several updating procedures such > as "texpire -r" (perhaps more, make update or something perhaps -- I'm There's "fetchnews -f --" to update the active file, as mentioned in the upgrade notes. > Which is intentional BTW. No need wasting everybody else's time if I can > help it. I've done this before with the chmod fiddling for the > out.going/ files between 1.9.23 and 1.9.33 and it was a pain for the > users. Yes, and much appreciated. -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
Attachment:
signature.asc
Description: Digital signature
-- _______________________________________________ leafnode-list mailing list leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx https://www.dt.e-technik.uni-dortmund.de/mailman/listinfo/leafnode-list http://leafnode.sourceforge.net/