[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1031920: marked as done (upstream-ontologist and lintian-brush need hinting into testing)



Your message dated Sat, 25 Feb 2023 13:53:27 +0100
with message-id <Y/oEx8IB8b2aPcge@ramacher.at>
and subject line Re: Bug#1031920: upstream-ontologist and lintian-brush need hinting into testing
has caused the Debian Bug report #1031920,
regarding upstream-ontologist and lintian-brush need hinting into testing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1031920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031920
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal

Mixing of testing/unstable upstream-ontologist/lintian-brush in either
direction gives a test-only failure due to a test adapted to changed output.


lintian-brush/unstable with upstream-ontologist/testing:

https://ci.debian.net/data/autopkgtest/testing/amd64/l/lintian-brush/31658430/log.gz

...
FAIL: fixer test: configure for upstream-metadata-file
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.c3g0u400/downtmp/build.QVr/src/lintian_brush/tests/fixers.py", line 153, in runTest
    self.assertEqual(stdout.decode().strip(), f.read().strip())
AssertionError: 'Set [89 chars]nty: certain\nFixed-Lintian-Tags: upstream-met[17 chars]sing' != 'Set [89 chars]nty: possible\nFixed-Lintian-Tags: upstream-me[18 chars]sing'
  Set upstream metadata fields: Bug-Submit (from ./configure), Name (from ./configure).
- Certainty: certain
+ Certainty: possible
  Fixed-Lintian-Tags: upstream-metadata-file-is-missing
...


lintian-brush/testing with upstream-ontologist/unstable:

https://ci.debian.net/data/autopkgtest/testing/amd64/l/lintian-brush/31650963/log.gz

...
FAIL: fixer test: configure for upstream-metadata-file
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.o1uoy7bm/downtmp/build.8P4/src/lintian_brush/tests/fixers.py", line 153, in runTest
    self.assertEqual(stdout.decode().strip(), f.read().strip())
AssertionError: 'Set [89 chars]nty: possible\nFixed-Lintian-Tags: upstream-me[18 chars]sing' != 'Set [89 chars]nty: certain\nFixed-Lintian-Tags: upstream-met[17 chars]sing'
  Set upstream metadata fields: Bug-Submit (from ./configure), Name (from ./configure).
- Certainty: possible
+ Certainty: certain
  Fixed-Lintian-Tags: upstream-metadata-file-is-missing
...


Unstable autopkgtest is all green:
https://ci.debian.net/packages/l/lintian-brush/

Updating both in testing is also green:
https://ci.debian.net/packages/l/lintian-brush/testing/i386/

--- End Message ---
--- Begin Message ---
On 2023-02-25 13:03:46 +0200, Adrian Bunk wrote:
> Package: release.debian.org
> Severity: normal
> 
> Mixing of testing/unstable upstream-ontologist/lintian-brush in either
> direction gives a test-only failure due to a test adapted to changed output.
> 
> 
> lintian-brush/unstable with upstream-ontologist/testing:
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/l/lintian-brush/31658430/log.gz
> 
> ...
> FAIL: fixer test: configure for upstream-metadata-file
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/tmp/autopkgtest-lxc.c3g0u400/downtmp/build.QVr/src/lintian_brush/tests/fixers.py", line 153, in runTest
>     self.assertEqual(stdout.decode().strip(), f.read().strip())
> AssertionError: 'Set [89 chars]nty: certain\nFixed-Lintian-Tags: upstream-met[17 chars]sing' != 'Set [89 chars]nty: possible\nFixed-Lintian-Tags: upstream-me[18 chars]sing'
>   Set upstream metadata fields: Bug-Submit (from ./configure), Name (from ./configure).
> - Certainty: certain
> + Certainty: possible
>   Fixed-Lintian-Tags: upstream-metadata-file-is-missing
> ...
> 
> 
> lintian-brush/testing with upstream-ontologist/unstable:
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/l/lintian-brush/31650963/log.gz
> 
> ...
> FAIL: fixer test: configure for upstream-metadata-file
> ----------------------------------------------------------------------
> Traceback (most recent call last):
>   File "/tmp/autopkgtest-lxc.o1uoy7bm/downtmp/build.8P4/src/lintian_brush/tests/fixers.py", line 153, in runTest
>     self.assertEqual(stdout.decode().strip(), f.read().strip())
> AssertionError: 'Set [89 chars]nty: possible\nFixed-Lintian-Tags: upstream-me[18 chars]sing' != 'Set [89 chars]nty: certain\nFixed-Lintian-Tags: upstream-met[17 chars]sing'
>   Set upstream metadata fields: Bug-Submit (from ./configure), Name (from ./configure).
> - Certainty: possible
> + Certainty: certain
>   Fixed-Lintian-Tags: upstream-metadata-file-is-missing
> ...
> 
> 
> Unstable autopkgtest is all green:
> https://ci.debian.net/packages/l/lintian-brush/
> 
> Updating both in testing is also green:
> https://ci.debian.net/packages/l/lintian-brush/testing/i386/

Hint added.

Cheers
-- 
Sebastian Ramacher

--- End Message ---

Reply to: