On 01 Dec 2005 00:48:52 +0100, Matthieu Moy wrote: > > I have a cron job using tla running on the SourceForge compilation > farm. This cron job breaks each time there is an important upgrade of > the servers (and since their email notification seems broken, it's a > silent failure for me). > > I didn't find a satisfying solution to this problem, but at least in > my precise case, automatically removing the revlib entries for which > inode signature fails would have been a solution
I would not try to automatically "fix" revlib revisions by default. Think about incompatible revlib formats as something related (tla 1.2.1 creates revlib in the format unknown for tla 1.2). I prefer to get an error of possible corruption, with suggestion to run library-remove bad--revision. > (a better solution for this would have been a second signature, based > on a hash, that would survive backup/restore and rebuild the inode > signature on demand). I support this solution. Still, I'd like to get a warning when inode signatures are recalculated, as a signal of a possibly larger problem. Additionally, I support having ~/.arch-params options that override these defaults, i.e. allow automatical recreation of corrupted revlib trees, or maybe suppress warnings when recalculating inode signatures. Regards, Mikhael. _______________________________________________ Gnu-arch-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/
