Control: fixed -1 python-stdnum/1.13-1 Control: forwarded -1 https://github.com/arthurdejong/python-stdnum/issues/182 Control: tags -1 + fixed-upstream
On Tue, 2020-03-03 at 14:57 +0100, Harald Welte wrote: > The problem is that from January 1st, Dutch BTW (VAT) numbers can > have two valid formats, and python stdnum < 1.13 only understands the > old format. This creates various failures in downstream application > software that relies on stdnum.nl.btw accepting all valid VAT > numbers. This has been fixed in 1.13-1 which is available in unstable and testing. There are a few possibilities for addressing this: * introducing a backport package of 1.13-1 (for buster and stretch) * uploading fixes to proposed-updates so they will be part of the next point release Which pages in Debian does this break for you? I know that Tryton has a dependency on python-stdnum and I know that at least Odoo used to use the packages that were shipped by the distribution (I think recent versions use a virtualenv though). Due to the nature of the numbers that are supported by python-stdnum there will always be a the possibility that the implementation will lag behind legislative or other changes. The easiest work-around for third-party or other software not shipped as part of Debian is to use a virtualenv to install a recent version of python-stdnum. Please let me know what you think should be the correct cause of action. Kind regards, -- -- arthur - [email protected] - https://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
