On Sat, Jun 18, 2011 at 02:20:12AM +0300, Marius Cirsta <[email protected]> wrote: > It wasn't my intention to blame him at all, on the contrary, I think > he's doing a great job. Just recently he pointed to a mistake that I > made.
OK, fine. :) > Still, rare as these problems are, this is debatable. Maybe there > should be something to protect against this. It was a very strange > error and it could be very hard for some people to figure it out. At > least a helpful message or something would be nice. > I remember I kept trying to download the package over and over again > because it said it was corrupted which wasn't exactly right... It's > not that I can't solve this problem now but for a new user it might be > hard and it might make a bad impression when you can't even get the > package manager to install a package. > I'm not sure I understood this correctly but if I did then a possible > solution would be to generate a file when a corrupted archive is found > with the name of that archive. Any other tries to install it should > then default to pacman -Syy. Upon success the file would be deleted. > This is just an idea, I don't know pacman internals .... There are two problems here: 1) When the sha1 of an fpm is corrupted in the fdb. - This is part of the testsuite and in case there is such a corruption, we're notified. 2) When we fix the sha1 without pkgrel++ then pacman -Sy won't notice it, just pacman -Syy. One could argue that then we need to make -Syy the default, but that's slow, we don't want that. A solution I see is to teach pacman to read fdb files directly (via libarchive). AFAIK the original pacman project implemented this in the meantime, so cherry-picking that feature (with proper attribution) should not be too hard. (Right now I'm busy with 1.5pre2 release stuff, so can't do it myself, I may do it in the future, and anybody else with C knowledge is also welcome to help.) Thanks.
pgpFmwQpRVT2u.pgp
Description: PGP signature
_______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
