-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Lintian failure on Debian 10 #48573
Comments
Pinging @elastic/es-core-infra (:Core/Infra/Packaging) |
cc @atorok |
Build failure: https://gradle-enterprise.elastic.co/s/izjgwzn5rolaq |
We are getting all kinds of nasty errors and warning related to issues setting the default locale on Debian 10. I think I've tracked down the problem. I've opened https://github.com/elastic/infra/issues/15670 to have this addressed. |
I don't think the locale errors are causing this.
|
I think the root cause is
which is indicative of a a bug in lintian. Also of note:
According to https://packages.debian.org/search?keywords=lintian that's the version in testing, debian 10 should have Running We have a miss configured source
|
Relates to elastic#48573 and intended as a work around to stop the CI failures until we fix the image.
* Work around incorrect lintian version on debian 10 Relates to #48573 and intended as a work around to stop the CI failures until we fix the image. * Need to pass --allow-downgrades
* Work around incorrect lintian version on debian 10 Relates to #48573 and intended as a work around to stop the CI failures until we fix the image. * Need to pass --allow-downgrades
* Work around incorrect lintian version on debian 10 Relates to #48573 and intended as a work around to stop the CI failures until we fix the image. * Need to pass --allow-downgrades
The workaround was merged to stop the CI failures, will keep the issue open to track removing it once the image is fixed. |
Different Lintian versions check different things, that's why this was particular to Debian 10. |
We added Debian 10 to the packaging tests for #44657. Now those tests are failing, as below.
The text was updated successfully, but these errors were encountered: