| 1 |
Monday 29 May 2006 00:51 skrev Hemmann, Volker Armin: |
| 2 |
> > The digest still changed so it would have to be a mirror that the devs |
| 3 |
> > who created the digests used.. |
| 4 |
> |
| 5 |
> what? |
| 6 |
> |
| 7 |
> I am talking about the problem, that mirrors might corrupt files and that |
| 8 |
> this is why making a new digest may not be a good idea. Also, it might be |
| 9 |
> possible, that someone hacked the file on the mirror. |
| 10 |
> |
| 11 |
> And what are you talking about? |
| 12 |
> |
| 13 |
> *confused* |
| 14 |
|
| 15 |
Like I stated in my previous mail I installed this a couple of weeks ago with |
| 16 |
the older, smaller version of the tar file. At that time there was no digest |
| 17 |
verification error which means that the digest fitted that tar file. |
| 18 |
|
| 19 |
When I reinstalled yesterday (after the ebuild had been bumped to -r1) but |
| 20 |
with the name of the tar file unchanged I ran into a digest verification |
| 21 |
error because the digest had changed to fit the newer, bigger tar file with |
| 22 |
the same name. Since the name was unchanged I had to delete the file to have |
| 23 |
the newer version downloaded which fitted the new digest... |
| 24 |
|
| 25 |
Note that the ebuilds of 1.03 and 1.03-r1 are identical. You get exactly the |
| 26 |
same software no matter which one of them you install. But since the tar file |
| 27 |
has changed you do not get the same as 2 weeks ago when I originally |
| 28 |
installed 1.03. I have exactly run a diff on those tar files so I can't tell |
| 29 |
if the difference is important... |
| 30 |
|
| 31 |
Please read the previous mail I sent 75 minutes ago. I hope I am more clear |
| 32 |
now.. |
| 33 |
|
| 34 |
-- |
| 35 |
Bo Andresen |
Archives