Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1270462 > unrolled thread

Bug#1117402: golang-github-gonvenience-neat: FTBFS: FAIL github.com/gonvenience/neat

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1117402: golang-github-gonvenience-neat: FTBFS: FAIL github.com/gonvenience/neat Otto Kekäläinen <otto@debian.org> - 2025-11-17 01:50 +0100
    Bug#1117402: golang-github-gonvenience-neat: FTBFS: FAIL github.com/gonvenience/neat Santiago Vila <sanvila@debian.org> - 2025-11-17 02:40 +0100
    Bug#1117402: golang-github-gonvenience-neat: FTBFS: FAIL github.com/gonvenience/neat Santiago Vila <sanvila@debian.org> - 2025-11-17 03:00 +0100

#1270462 — Bug#1117402: golang-github-gonvenience-neat: FTBFS: FAIL github.com/gonvenience/neat

Control: severity -1 important

Hi!

This is a failure in the post-build test suite. Downgrading severity
as removing the package from Debian seems a bit too harsh. The
existing binary already in Debian works and will continue to work.

[toc] | [next] | [standalone]

#1270464

severity 1117402 serious
thanks

On Sun, Nov 16, 2025 at 04:44:11PM -0800, Otto Kekäläinen wrote:

> This is a failure in the post-build test suite. Downgrading severity
> as removing the package from Debian seems a bit too harsh. The
> existing binary already in Debian works and will continue to work.

Please don't do that.

Packages must build from source, where "build" usually means zero exit
status from dpkg-buildpackage, which of course includes the build-time
tests.

The existing binary which "works" may not be generated anymore from
the source package (because the build fails), and that makes the issue
to be a DFSG violation (packages in forky must build in forky).

That's why we make build failures to be RC, even if only it's the
build time tests the thing which fails.

Normally one would forward the issue upstream and wait for their
reply. If there are reasons why this can't be done and you prefer to
ignore the test errors, then please at least do it deliberately, not
cheating with severities.

The way to do it deliberately would be to add the following line
to debian/rules:

override_dh_auto_test:

which makes it to be a no-op. A better option would be to run the test
and ignore the outcome, like this:

override_dh_auto_test:
	dh_auto_test || true

but even doing that would be a bad fix and would be considered sloppy,
because we usually want to run the tests and fail the build if the
tests fail, to avoid regressions.

If we absolutely need to ignore the test error, we would skip the test
which fails, and only the one that fails.

Anyway, I've used debbisect to know when exactly this started to fail
and this was the outcome:

bisection finished successfully
  last good timestamp: 20250919T022738Z
  first bad timestamp: 20250919T084327Z
only one package differs: golang-github-gonvenience-wrap-dev 1.1.2-2 -> 1.2.2-1

Most probably this is the information that the author needs to be able
to understand the problem ("package golang-github-gonvenience-neat does
not work anymore with golang-github-gonvenience-wrap-dev version 1.2.2").

Thanks.

[toc] | [prev] | [next] | [standalone]

#1270466

Hello.

I explained Otto why we can't just downgrade the severity, but I
completely forgot that there was a newer version in experimental.

Could any of the usual uploaders please upload golang-github-gonvenience-neat
for unstable to see if it fixes this bug?

Or maybe there is some reason why this should not be done, like
starting an unwanted transition or alike?.

(With some luck, it could be the case that we dont even need to
forward this upstream).

Thanks.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web