On Thu, 2018-10-25 at 15:23 +0100, Dominic Raferd wrote: > > > On Thu, 25 Oct 2018 at 15:16, RW <rwmailli...@googlemail.com> wrote: > > On Thu, 25 Oct 2018 16:07:02 +0200 > > Matus UHLAR - fantomas wrote: > > > > > >On Thu, 25 Oct 2018 08:37:45 -0400 Alexander Lieflander wrote: > > > >> As a side-note, it seems like the error message returned by > > dpkg > > > >> (and thus SpamAssassin, I guess) is incorrect. Where it > > mentions > > > >> “sa-compile”, it should really be mentioning “sa-update”, as > > the > > > >> man page for sa-update contains the “--nogpg” option, and the > > man > > > >> page for sa-compile does not. > > > > > > where did it say sa-compile? > > > > It failed when sa-compile was being installed > > > > > nothing with sa-compile. > > > > > > On 25.10.18 14:37, RW wrote: > > > >This is a consequence of Ubuntu (or Debian) splitting off sa- > > compile > > > >into a separate package. The error occurred while checking > > > >sa-compile's dependency, the spamassassin package. > > > > > > this should not happen at all. when sa-compile is installed, > > > spamassassin (and sa-update) should be installed and configured. > > > > I would guess that there was no problem when spamassassin was > > installed > > and sa-compile was installed later. > > I am using SA on Ubuntu 18.04 without any such problems. Looking at > the package changelogs for SA 3.4.1-8 under Debian/Ubuntu they are > identical except that, for Ubuntu 18.04, SA was rebuilt > against openssl1.1. The only sadness is that Ubuntu 18.04 is > currently stuck with 3.4.1 (3.4.2 is available on 18.10).
FWIW back on 9 Oct I submitted a bug report regarding 3.4.2 for 18.04 https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1796863 I'm hoping that it will be available soon. Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 08:23:12 up 3 days, 16:37, 1 user, load average: 1.08, 0.96, 0.75 Description: Ubuntu 18.04.1 LTS, kernel 4.15.0-38-generic
signature.asc
Description: This is a digitally signed message part
