Hi,

since I have managed to destroy my fpc and/or lazarus installation and have to install fresh ones, i wondered:

Are there chechsums available anywhere for the needed downloads - fpc, fpc sources, lazarus?

I would feel mauch better, if so.

Thanks in advance,
Marc

I am not aware of them being separately published (except for the ones on sourceforge, which are calculated by sourceforge).

As for the win installers, here are the checksums from the original installers (the local copies I kept after the build).

MD5 SHA-1
-------------------------------------------------------------------------fc90c4a3f0e34fecec9026be5b7a96bf 610f535bfd3c6ea1addcdf019d21fc2c14edadb1
1.4.2\lazarus-1.4.2-fpc-2.6.4-cross-x86_64-win64-win32.exe f177f00cbb16a87f044efc8cd7c90789
77b0a6914a9b4b5416b4cb4d14e867cbfa89c635
1.4.2\lazarus-1.4.2-fpc-2.6.4-win32.exe 28d8cd24dfb443ca48f8abec84d251a0 3b2a389fc5746ce7ea2d59125bd02b707528ba9e
1.4.2\lazarus-1.4.2-fpc-2.6.4-cross-arm-wince-win32.exe fd1f7ddc01762a9c86b742c607b33319
34e89dd020e302414f1aa546b4318d104fee3ed1
1.4.2\w64\lazarus-1.4.2-fpc-2.6.4-cross-i386-win32-win64.exe b4d4b91854915e6ca0a5772f2a27013b
88b537a1ef50ae321c0323adc627cdf600e6e43f
1.4.2\w64\lazarus-1.4.2-fpc-2.6.4-win64.exe

Sourceforrge is (as of today) still showing the same checksums (so it seems their recent downtime, has not led to modifications). Though of course that is, if the checksums shown today by sourceforge actually matches the files online today.
I have not downloaded todays files to check if they indeed have the checksum that SF claims.

Trust your mail program to mess up the text....

MD5 SHA-1

-------------------------------------------------------------------------

fc90c4a3f0e34fecec9026be5b7a96bf
610f535bfd3c6ea1addcdf019d21fc2c14edadb1
1.4.2\lazarus-1.4.2-fpc-2.6.4-cross-x86_64-win64-win32.exe

f177f00cbb16a87f044efc8cd7c90789
77b0a6914a9b4b5416b4cb4d14e867cbfa89c635
1.4.2\lazarus-1.4.2-fpc-2.6.4-win32.exe

28d8cd24dfb443ca48f8abec84d251a0
3b2a389fc5746ce7ea2d59125bd02b707528ba9e
1.4.2\lazarus-1.4.2-fpc-2.6.4-cross-arm-wince-win32.exe

fd1f7ddc01762a9c86b742c607b33319
34e89dd020e302414f1aa546b4318d104fee3ed1
1.4.2\w64\lazarus-1.4.2-fpc-2.6.4-cross-i386-win32-win64.exe

b4d4b91854915e6ca0a5772f2a27013b
88b537a1ef50ae321c0323adc627cdf600e6e43f
1.4.2\w64\lazarus-1.4.2-fpc-2.6.4-win64.exe

I think it may be only little effort to publish those sums on the website or put a file mdsums.txt aside wioth the downloads.

As for the win installers, here are the checksums from the original installers (the local copies I kept after the build).

Many thanks, but I'm using FreeBSD (8 and 9).

Your're right, the text is a bit messy but usable.

How do you manage to see checksums on Sourceforge? That would be a start.

ideally there would be one md5sum file for each individual file available for download... this way, one can check the remote checksum file with a local one to see if the file has been updated since the checksums would be different... we use this for automated update mechanisms...

Indeed, you're right. And then it would even better to have the archives signed with a gpg key of the developer(s) tracable to the root cert. But I wanted to keep things simple, not demanding too much. ;)

Marc Santhoff wrote

Many thanks, but I'm using FreeBSD (8 and 9).

I am only doing the windows builds..

How do you manage to see checksums on Sourceforge? That would be a start.

Click on the (i) symbol behind the entry. You may have to scroll down, after you clicked, because sometimes the info (in-side popup) is displayed a bit far down.

Martin Frb wrote

Trust your mail program to mess up the text....

Suggested email program settings to improve the matter (some more than others). Some email client are just too broken to work correctly.

https://www.kernel.org/doc/Documentation/email-clients.txt

Regards,
- Graeme -