[Bug 1860588] Re: Spamassassin FTBFS in focal

2020-01-23 Thread Bryce Harrington
Rebuilding sa-exim did indeed clear the blockage, and allowed exim4 to migrate successfully. ** Changed in: spamassassin (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1860588] Re: Spamassassin FTBFS in focal

2020-01-22 Thread Bryce Harrington
sa-exim generates its requirements via: binary-arch: build ... echo "exim:Depends=exim4-localscanapi-`exim4-localscan-plugin-config --localscan-apiversion`" \ >> debian/sa-exim.substvars dh_gencontrol So, looks like rebuilding sa-exim should correct the mis-dependency.

[Bug 1860588] Re: Spamassassin FTBFS in focal

2020-01-22 Thread Bryce Harrington
apt shows sa-exim depends on exim4-localscanapi-2.1, $ apt-cache depends sa-exim sa-exim Depends: Depends: spamc Depends: libc6 |Depends: debconf Depends: cdebconf debconf Depends: libnetaddr-ip-perl Recommends: perl Suggests: spamassassin However its control file doesn't

[Bug 1860588] Re: Spamassassin FTBFS in focal

2020-01-22 Thread Bryce Harrington
>From update-excuses.txt: trying: exim4 skipped: exim4 (177, 181, 1) got: 95+0: a-20:a-18:a-18:i-2:p-19:s-18 * ppc64el: sa-exim It doesn't seem to be showing exim4 failing on other platforms though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1860588] Re: Spamassassin FTBFS in focal

2020-01-22 Thread Bryce Harrington
In the CI PPA, spamassassin was failing to build on amd64: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/3902/+packages However, with a simple rebuild it seems now to be passing (it's in the publication step). Perhaps the issue was just a network related glitch, and lack of

[Bug 1860588] Re: Spamassassin FTBFS in focal

2020-01-22 Thread Bryce Harrington
On first glance at the build log, it looks like the spamd daemon is not starting up spam_pid not found: Sleeping 2 - Retry # 30 ... spamd start failed - Could not find a valid PID. It's not immediately evident from the log output why it did not start up. There are a number of warnings about

[Bug 1860588] Re: Spamassassin FTBFS in focal

2020-01-22 Thread Bryce Harrington
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860588 Title: Spamassassin FTBFS in focal To manage notifications about this bug go to:

[Bug 1860588] Re: Spamassassin FTBFS in focal

2020-01-22 Thread Bryce Harrington
** Changed in: spamassassin (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860588 Title: Spamassassin FTBFS in focal To manage