Bug#1005044: python3-subnettree: package completely broken, module won't load

2022-11-03 Thread Scott Kitterman
On Wed, 9 Feb 2022 17:12:27 -0500 Michael Stone wrote: > On Wed, Feb 09, 2022 at 04:32:43PM -0500, Scott Kitterman wrote: > >On Sat, 5 Feb 2022 17:28:04 -0500 Michael Stone wrote: > >> It seems to be some kind of incompatibility in swig. Upstream .cc files > >> are built with swig 3, debian has s

Bug#1005044: python3-subnettree: package completely broken, module won't load

2022-02-09 Thread Michael Stone
On Wed, Feb 09, 2022 at 04:32:43PM -0500, Scott Kitterman wrote: On Sat, 5 Feb 2022 17:28:04 -0500 Michael Stone wrote: It seems to be some kind of incompatibility in swig. Upstream .cc files are built with swig 3, debian has swig 4. If the package is built with the upstream .cc files (ditching

Bug#1005044: python3-subnettree: package completely broken, module won't load

2022-02-09 Thread Scott Kitterman
On Sat, 5 Feb 2022 17:28:04 -0500 Michael Stone wrote: > It seems to be some kind of incompatibility in swig. Upstream .cc files > are built with swig 3, debian has swig 4. If the package is built with > the upstream .cc files (ditching the associated lines in debian/rules) > it seems to work f

Bug#1005044: python3-subnettree: package completely broken, module won't load

2022-02-05 Thread Michael Stone
It seems to be some kind of incompatibility in swig. Upstream .cc files are built with swig 3, debian has swig 4. If the package is built with the upstream .cc files (ditching the associated lines in debian/rules) it seems to work fine.

Bug#1005044: python3-subnettree: package completely broken, module won't load

2022-02-05 Thread Michael Stone
Package: python3-subnettree Version: 0.33-1+b3 Severity: grave Justification: renders package unusable Documentation says: A simple example which associates CIDR prefixes with strings:: >>> import SubnetTree >>> t = SubnetTree.SubnetTree() >>> t["10.1.0.0/16"] = "Network 1" >>> t