-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JAMES-2558 Tests should rely on SpamAssassin 3.4.2 #1793
Conversation
Packaging not yet available exception? |
The container inherit Debian Stretch from the postgres container https://github.com/docker-library/postgres/blob/3f585c58df93e93b730c09a13e8904b96fa20c58/10/Dockerfile But stretch is only 3.4.1 based cf https://packages.debian.org/fr/spamassassin Switching to testing or unstable do not seem wize. Maybe we should curl + dpkg some trusted 3.4.2 package over the internet (or update our APT lists) |
This should be done in the following days : https://tracker.debian.org/pkg/spamassassin We can monitor progress here... |
test this please |
|
Yes no need to relaunch it, the debian package is not yet available |
test this please (just to have a failing build report instead of an inapropriate pending build report, packaging is still not yet available...) |
here you are
|
test this please |
|
test this please |
still
|
One minute is a little too low to build successfully a Dockerfile |
still
test this please... |
@@ -52,7 +52,7 @@ public void waitUntilReady(WaitStrategyTarget waitStrategyTarget) { | |||
return spamAssassinContainer | |||
.execInContainer("spamassassin", "-V") | |||
.getStdout() | |||
.contains("SpamAssassin version 3.4.1"); | |||
.contains("SpamAssassin version 3.4.2"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
haha!
third-party/spamassassin/src/test/java/org/apache/james/spamassassin/SpamAssassinExtension.java
Show resolved
Hide resolved
Merged |
Fixes CVE-2017-15705, CVE-2016-1238, CVE-2018-11780 & CVE-2018-11781