Your message dated Thu, 23 May 2024 13:32:55 +0200
with message-id <a491a6f5-623f-4e55-9718-6062821b8...@debian.org>
and subject line Re: Bug#1022311: python-stdnum: FTBFS: AssertionError: Failed
doctest test for test_no_fodselsnummer.doctest
has caused the Debian Bug report #1022311,
regarding python-stdnum: FTBFS: AssertionError: Failed doctest test for
test_no_fodselsnummer.doctest
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 ow...@bugs.debian.org
immediately.)
--
1022311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-stdnum
Version: 1.17-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_test -- --system=custom --test-args='TZ=Europe/Amsterdam
> {interpreter} setup.py nosetests'
> I: pybuild base:240: TZ=Europe/Amsterdam python3.10 setup.py nosetests
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508:
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use
> license_files instead.
> warnings.warn(msg, warning_class)
> running nosetests
> running egg_info
> writing python_stdnum.egg-info/PKG-INFO
> writing dependency_links to python_stdnum.egg-info/dependency_links.txt
> writing requirements to python_stdnum.egg-info/requires.txt
> writing top-level names to python_stdnum.egg-info/top_level.txt
> reading manifest file 'python_stdnum.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'COPYING'
> writing manifest file 'python_stdnum.egg-info/SOURCES.txt'
> nose.plugins.cover: ERROR: Coverage not available: unable to import coverage
> module
> .................................................................................................................................................................................................................................S................S....S.S.SS...........SS...........................................F................................
> ======================================================================
> FAIL: Doctest: test_no_fodselsnummer.doctest
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/usr/lib/python3.10/doctest.py", line 2221, in runTest
> raise self.failureException(self.format_failure(new.getvalue()))
> AssertionError: Failed doctest test for test_no_fodselsnummer.doctest
> File "/<<PKGBUILDDIR>>/tests/test_no_fodselsnummer.doctest", line 0
>
> ----------------------------------------------------------------------
> File "/<<PKGBUILDDIR>>/tests/test_no_fodselsnummer.doctest", line 94, in
> test_no_fodselsnummer.doctest
> Failed example:
> fodselsnummer.validate('19102270846')
> Expected:
> Traceback (most recent call last):
> ...
> InvalidComponent: The birth date information is valid, but this person
> has not been born yet.
> Got:
> '19102270846'
>
>
> ----------------------------------------------------------------------
> Ran 342 tests in 1.408s
>
> FAILED (SKIP=8, failures=1)
> E: pybuild pybuild:379: test: plugin custom failed with: exit code=1:
> TZ=Europe/Amsterdam python3.10 setup.py nosetests
> dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.10
> --system=custom "--test-args=TZ=Europe/Amsterdam {interpreter} setup.py
> nosetests" returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2022/10/23/python-stdnum_1.17-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20221023&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
El 23/5/24 a las 12:39, Petter Reinholdtsen escribió:
Is there still any reason to keep this RC BTS report open?
It's not actually RC for trixie because version tracking says trixie is not
affected.
However, I'm closing the bug so that people who insist on following version
tracking strictly
do not complain about it being still open.
In theory, bullseye is still oldstable and it's still a supported distribution.
If I were the maintainer, I would try to fix this in bullseye, for posterity.
In fact, I am a member of python team, so in theory I could fix this myself
(via team upload). But what would be the proper fix in bullseye?
Thanks.
--- End Message ---
