---------- Forwarded message ---------- From: François BIOT <[email protected]> Date: Sat, Jun 18, 2011 at 1:33 PM Subject: Re: [Frugalware-devel] corrupted archive To: Marius Cirsta <[email protected]>
Hi every one IMHO just modifying the pacman error message will be enough. Instead of package corrupted, the message could be 'package corrupted, you can try -Syy'. The problem occurs approximately once per 6 months for me, and each time, I just don't remember the -Syy flag :-) The message could be also enhanced with 'You can try another repository' ? Sometime the package is corrupted only on one ftp server, I've already fix this error by changing to another ftp.frugalware site. When the archive is really corrupted, I agree with Vajna (or Miklos sorry ...), this is so rare that there is no need (imho) to do more. Thanks to all of you for your great work. 2011/6/18 Marius Cirsta <[email protected]> > > On Sat, Jun 18, 2011 at 2:01 AM, Miklos Vajna <[email protected]> wrote: > > On Fri, Jun 17, 2011 at 09:29:18AM -0600, Marius Cirsta <[email protected]> > > wrote: > >> Wouldn't it be possible to somehow impose an increase of either the > >> pkgver or pkgrel ? I mean if you do update a package you should > >> probably increase one of these. Maybe the build machine could check > >> this ? Or maybe on commit but I'm not sure .... > > > > Given how rare such problems are, I would not force such a check. Just > > think about for example a description correction of the kernel package. > > If you force pkgrel++, then you need to rebuild all external modules as > > well - while currently we have the option to say "this is a minor > > change, it's enough if it'll be included in the next build". > > > > Again, to have this problem, a developer has to intentionally upload the > > same package release two times with different contents, that's rare. I'm > > sure Melko already learned he won't do this next time, no need to blame > > him, he's a great guy. :) > > > > _______________________________________________ > > Frugalware-devel mailing list > > [email protected] > > http://frugalware.org/mailman/listinfo/frugalware-devel > > > > > > 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. > > 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 .... > _______________________________________________ > Frugalware-devel mailing list > [email protected] > http://frugalware.org/mailman/listinfo/frugalware-devel -- Francois Biot Responsable R&D AuchanDirect Grosbill Tel: 01 56 70 51 36 Forwarded the message. There's a problem when you hit reply in gmail with this ( and other ) mailing lists. _______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
