You are not logged in.
Pages: 1
Hi all,
in the release file:
http://pkgmaster.devuan.org/devuan/dists/stable/Release
it says:
f79ea6e9c962b7b4021a216c0a49d847993303b743773995458ac448d59ebdb0 74077 main/installer-amd64/current/images/SHA256SUMS
but if i check:
http://pkgmaster.devuan.org/devuan/dist … SHA256SUMS
i get b14f1d9375dad1394ff8e5026c272076c51b1bf76464ff556445d49c91cbb103 SHA256SUM
am i missing something here ?
thanks in advance..
Offline
Not sure what you are wanting to do.
Yes, I can see f79ea6e9c962b7b4021a216c0a49d847993303b743773995458ac448d59ebdb0 at the url you post.
But when I visit https://pkgmaster.devuan.org/devuan/dis … SHA256SUMS, I do not find any:
b14f1d9375dad1394ff8e5026c272076c51b1bf76464ff556445d49c91cbb103
Anyway, normally you download an iso and then use the SHASUM process to verify that the download occurred without error.
You download this to get the SHA256 hash number for whatever you are downloading (mirror site used):
https://mirror.leaseweb.com/devuan/devu … SHA256SUMS
Then after you download your desired iso file, you then run sha256sum <iso file>(for example for netinst.iso):
sha256sum devuan_ascii_2.0.0_amd64_netinst.iso
c16bebdeecdf452188ae4bb823cd5f1c0d2ed3a7a568332508943ce16f7e5c71 devuan_ascii_2.0.0_amd64_netinst.iso
And you will find an exact match of this cryptic number in file SHA256SUMS, if the download completed without error. If the numbers do not match, the downloaded ISO file is invalid.
Offline
thanks for your reply. i am setting up an pxe boot and would only need the pxe file from here not an iso...
the release file is gpg signed and fine:
http://pkgmaster.devuan.org/devuan/dists/stable/Release
in this one it says:
f79ea6e9c962b7b4021a216c0a49d847993303b743773995458ac448d59ebdb0 74077 main/installer-amd64/current/images/SHA256SUMS
until now all is fine.
now when i do :
sha256sum https://pkgmaster.devuan.org/devuan/dis … SHA256SUMS
which is what the release file above is pointing to
i would expect: f79ea6e9c962b7b4021a216c0a49d847993303b743773995458ac448d59ebdb0 (from the release file)
but i get : b14f1d9375dad1394ff8e5026c272076c51b1bf76464ff556445d49c91cbb103
something is wrong here...
Offline
I "think" maybe its because the file at:
https://pkgmaster.devuan.org/devuan/dis … SHA256SUMS
is the latest/current file.
Note the sha you are referring to :
f79ea6e9c962b7b4021a216c0a49d847993303b743773995458ac448d59ebdb0 74077 main/installer-amd64/20181213+devuan1/images/SHA256SUMS
Has a date in the name (20181213).
Then note that the sha that was returned by your check, is listed on line:
b14f1d9375dad1394ff8e5026c272076c51b1bf76464ff556445d49c91cbb103 74077 main/installer-amd64/20190228+devuan1/images/SHA256SUMS
Note the date difference.
Does this make sense? I can hardly follow this myself!
Offline
thanks for your reply, but i checked always the "current" file (see my first post)
anyway now it is working because the release file was newly build:
6th line of : https://pkgmaster.devuan.org/devuan/dis … le/Release
Date: Thu, 28 Feb 2019 02:27:17 UTC
as this issue is now solved , i am having problems to understand how any "apt" action could have worked as the shasum was obviously wrong for a couple of days ..
Offline
Pages: 1