reopen 1022311
found 1022311 1.16-1
found 1022311 1.17-1
fixed 1022311 1.18-1
thanks
El 13/11/22 a las 22:45, Arthur de Jong escribió:
If this ever needs to be backported for some reason the fix is trivial:
https://arthurdejong.org/git/python-stdnum/commit/?id=1003033fa0e97726d92f47231f96cf02fb35869a
Hi. I'm reopening this bug because it also happens in bullseye (exactly as
described by Lucas),
and packages in stable must build in stable.
I attach a proposal to fix this in bullseye, in the form of debdiff against
version 1.16-1, the current version in bullseye.
(Fortunately, since you pointed at the exact commit fixing it, producing this
debdiff was trivial)
If you have never made an upload for stable, the procedure is explained here:
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions
Thanks.
diff -Nru python-stdnum-1.16/debian/changelog
python-stdnum-1.16/debian/changelog
--- python-stdnum-1.16/debian/changelog 2021-02-06 17:52:07.000000000 +0100
+++ python-stdnum-1.16/debian/changelog 2023-01-08 22:39:00.000000000 +0100
@@ -1,3 +1,9 @@
+python-stdnum (1.16-1+deb11u1) bullseye; urgency=medium
+
+ * Update Fødselsnummer test case for date in future. Closes: #1022311.
+
+ -- Arthur de Jong <adej...@debian.org> Sun, 08 Jan 2023 22:39:00 +0100
+
python-stdnum (1.16-1) unstable; urgency=medium
* New upstream release:
diff -Nru python-stdnum-1.16/debian/patches/series
python-stdnum-1.16/debian/patches/series
--- python-stdnum-1.16/debian/patches/series 1970-01-01 01:00:00.000000000
+0100
+++ python-stdnum-1.16/debian/patches/series 2023-01-08 22:36:43.000000000
+0100
@@ -0,0 +1 @@
+the-future-was-now.patch
diff -Nru python-stdnum-1.16/debian/patches/the-future-was-now.patch
python-stdnum-1.16/debian/patches/the-future-was-now.patch
--- python-stdnum-1.16/debian/patches/the-future-was-now.patch 1970-01-01
01:00:00.000000000 +0100
+++ python-stdnum-1.16/debian/patches/the-future-was-now.patch 2023-01-08
22:36:43.000000000 +0100
@@ -0,0 +1,28 @@
+From 1003033fa0e97726d92f47231f96cf02fb35869a Mon Sep 17 00:00:00 2001
+From: Arthur de Jong <art...@arthurdejong.org>
+Date: Wed, 19 Oct 2022 21:06:27 +0200
+Subject: =?UTF-8?q?Update=20F=C3=B8dselsnummer=20test=20case=20for=20date?=
+ =?UTF-8?q?=20in=20future?=
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+The future was now. This problem was pushed forwards to October 2039.
+---
+ tests/test_no_fodselsnummer.doctest | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+--- a/tests/test_no_fodselsnummer.doctest
++++ b/tests/test_no_fodselsnummer.doctest
+@@ -91,9 +91,9 @@
+ Traceback (most recent call last):
+ ...
+ InvalidComponent: This number is an FH-number, and does not contain birth
date information by design.
+->>> fodselsnummer.validate('19102270846')
++>>> fodselsnummer.validate('18103970861')
+ Traceback (most recent call last):
+- ...
++ ...
+ InvalidComponent: The birth date information is valid, but this person has
not been born yet.
+
+
