Hash Sun mismatch

David6FEO · 2019-11-28 12:58:34

I've just found Devuan and I'm very pleased with it, it just loads without trouble.

Now I've come to add Apache2, PHP and SSMTP I've got the dreaded Hash Sum mismatch issue.

I've tried all the usual 'fixes' without success.

Is it possible to 'bypass' the Hash Sum checking of apt?

Thank you,

David.

HevyDevy · 2019-11-28 14:32:26

How did you add Apache2, PHP and SSMTP ?

What are the "usual fixes" ?

Last edited by HevyDevy (2019-11-28 14:32:58)

bgstack15 · 2019-11-28 14:56:54

My usual fixes involve double-checking the sources.list to make sure it points to:

deb http://packages.devuan.org/merged ceres main contrib non-free
deb-src http://packages.devuan.org/merged ceres main contrib non-free

And clearing out /var/lib/apt/lists/*:

rm /var/lib/apt/lists/*

David6FEO · 2019-11-29 04:17:17

Sorry I should have been more specific in the original post.

Apache2, PHP and SSMTP were added using the 'apt-get install' command.

The usual fixes I tried were any commands I could find using the apt feature.

I have looked at the sources.list and neither of the ones listed were there, I've added them, but hashed out the original entries, not sure if that's the correct thing to do.

I've got some screen grabs to show what I've done, but I can't see a method of posting them.

David.

rolfie · 2019-11-29 20:24:53

Which release do you intend to use? ASCII = stable, Beowulf = testing, ceres = unstable/experimental?

Check if changing the sources to

deb http://deb.devuan.org/merged ascii

helps. This is the official notification, refer to https://devuan.org/os/etc/apt/sources.list.

golinux · 2019-11-29 20:32:32

Posting for clarity that in Devuan we advise not to use the Suite designations because doing so can cause unexpected "breakage". Here's why:

Codenames or suites?
The release codenames or suite designations in /etc/apt/sources.list indicate which release will be used when updating and upgrading packages. Note that the suite names stable and testing will refer to different releases over time.
As of this writing, stable refers to Devuan ASCII (Debian Stretch) and testing refers to Devuan Beowulf (Debian Buster). Once Beowulf is officially released, stable will refer to Beowulf and testing will refer to the next release in development, Chimaera (Debian Bullseye).
However, if your ASCII sources.list refers to the release codename ascii you will remain on ASCII until you change your sources.list. That means that you will have more control over when the upgrade happens. And if you are using beowulf in your sources.list you will move seamlessly to the new stable version of Beowulf when it is released.
To avoid the possibility of mixing two potentially incompatible repositories, Devuan recommends using release codenames in sources.list.
Source: https://devuan.org/os/releases

David6FEO · 2019-12-01 06:55:22

Thank you for the reply.

I'm using ASCII and I've followed the link at the end of your message about sources and changed my settings accordingly.

Looking at the reports on my screen after trying apt autoremove I am told that libgdk-pixbuf2.0-0:i386 depends on shared-mime-info: however Package shared-mime-info is not configured yet.

Is this the problem?

Would I benefit from using the Country Code in the sources.list?

David.

golinux · 2019-12-01 07:29:48

David6FEO wrote:

Would I benefit from using the Country Code in the sources.list?

deb.devuan.org is recommended but you can also choose a mirror from the list of available mirrors that might suit you better.

The officially official Devuan Forum!

#1 2019-11-28 12:58:34

Hash Sun mismatch

#2 2019-11-28 14:32:26

Re: Hash Sun mismatch

#3 2019-11-28 14:56:54

Re: Hash Sun mismatch

#4 2019-11-29 04:17:17

Re: Hash Sun mismatch

#5 2019-11-29 20:24:53

Re: Hash Sun mismatch

#6 2019-11-29 20:32:32

Re: Hash Sun mismatch

#7 2019-12-01 06:55:22

Re: Hash Sun mismatch

#8 2019-12-01 07:29:48

Re: Hash Sun mismatch

Board footer