package sa-compile 3.4.1-3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 25

Bug #1547801 reported by MAUGER Pierre II
34
This bug affects 6 people
Affects Status Importance Assigned to Milestone
spamassassin (Ubuntu)
Expired
High
Unassigned

Bug Description

after an upgrade of 14.04 to 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sa-compile 3.4.1-3
ProcVersionSignature: Ubuntu 3.13.0-78.122-generic 3.13.11-ckt33
Uname: Linux 3.13.0-78-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Sat Feb 20 09:18:26 2016
DuplicateSignature: package:sa-compile:3.4.1-3:le sous-processus script post-installation installé a retourné une erreur de sortie d'état 25
ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 25
InstallationDate: Installed on 2015-06-10 (254 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt 1.2.3
SourcePackage: spamassassin
Title: package sa-compile 3.4.1-3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 25
UpgradeStatus: Upgraded to xenial on 2016-02-19 (0 days ago)

Revision history for this message
MAUGER Pierre II (pierremauger586) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in spamassassin (Ubuntu):
status: New → Confirmed
Revision history for this message
Vincent Fortier (th0ma7) wrote :

same issue for me when upgrading from 16.04 to 16.10 beta

Changed in spamassassin (Ubuntu):
importance: Undecided → High
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi and thank you for your bug report to make Ubuntu better.

It seems that on the upgrade it calls sa-compile again to refresh your rules.

In the log I've found:
Paramétrage de sa-compile (3.4.1-3) ...
Running sa-compile (may take a long time)
x86_64-linux-gnu-gcc: error: unrecognized command line option ‘-fstack-protector-strong’
make: *** [blib/arch/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.so] Erreur 1
command 'make >>/tmp/.spamassassin5175d5McLJtmp/log' failed: exit 2

That seems odd, as that clearly is a supported option of gcc for quite a while.

Do you have any extra info that you can share about your setup regarding your spamassassin, but also your compiler setup that could explain this and help us understand/reproduce?

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Dupped another bug onto that - I hope that with the combined details we can identify more of a root cause.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Setting the state to incomplete, since we are waiting on extra info to assist repro and debugging

Changed in spamassassin (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Vincent Fortier (th0ma7) wrote :

If I can add, in my case I have no setup for spamassassin. It just got installed as per dependencies and I never configured it. Still, I had that exact same issue while upgrading from 16.04 to 16.10 beta.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for spamassassin (Ubuntu) because there has been no activity for 60 days.]

Changed in spamassassin (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.