Sandro and others,
Per one of the primary developers, all vestiges of PYTHON are now
removed from XASTIR.
See below in-line for definitive information.
At this point if someone would do a re-pull from Git and
re-package for Debian it would in my estimation clear things for
moving forward towards Sid/Bullseye.
Respectfully,
David A Aitcheson - KB3EFS
-------- Forwarded Message --------
Xastir_tigerpoly.py is now removed from Xastir's git repo. It
will no longer
be part of any future release.
In the meantime, since Debian won't pull from git, a trivial
patch for the debian package would just be to remove the script
from scripts/Makefile.am so it isn't installed, and to remove
the python dependency from the package. There is no python
usage in Xastir other than that script, which hasn't been used
in something like 10 years. I think the last release of
TIGER/LINE data was in 2006, and the script probably hasn't been
used since.
On Wed, Nov 27, 2019 at 06:43:25PM -0700, we recorded a
bogon-computron collision of the <russo@bogodyn.org>
flavor, containing:
There is exactly ONE
python script in Xastir, a little-used script called
"Xastir_tigerpoly.py" that has almost no current
applicability to anything.
It is designed to take a decades-obsolete map
topological map format and c
converts it to shapefile. It is highly unlikely that
anybody will even be
able to find the data it was meant to process.
I have no idea if it would work with python3, but it is
irrelevant. Nothing
in Xastir actually depends on python other than this script.
Unless someone
really wants this script, one could run Xastir without even
having *any*
version of python installed.
They should simply remove the dependency on python. Absolutely
nobody will
ever notice.
I ought to just remove the script altogether, and will for the
next release.
It has long since beeen irrelevant.
On Wed, Nov 27, 2019 at 08:03:34PM -0500, we recorded a
bogon-computron collision of the
<david.aitcheson@gmail.com> flavor, containing:
> Guys,
> > A "?" that is off list(s) to avoid "boat rocking".
> > What part of Xastir uses py2?
> > I work from Source Code so maybe I am missing
something.
> > I know you don't build binaries so this is a
non-issue for me, and just
> a curiosity.
> > 73
> Dave
> KB3EFS
> > > -------- Forwarded Message --------
> Subject: Bug#945747: xastir: Python2 removal in
sid/bullseye
> Resent-Date: Thu, 28 Nov 2019 00:09:10 +0000
> Resent-From: Sandro Tosi <morph@paradis.debian.org>
> Resent-To: Debian Hamradio Maintainers
<debian-hams@lists.debian.org>
> Date: Wed, 27 Nov 2019 23:58:54 +0000
> From: Sandro Tosi <morph@paradis.debian.org>
> Reply-To: Sandro Tosi <morph@paradis.debian.org>,
> 945747-maintonly@bugs.debian.org
> To: maintonly@bugs.debian.org
> > > > Source: xastir
> Version: 2.1.4-1
> Severity: normal
> Tags: sid bullseye
> User: debian-python@lists.debian.org
> Usertags: py2removal
> > Python2 becomes end-of-live upstream, and Debian
aims to remove
> Python2 from the distribution, as discussed in
>
https://lists.debian.org/debian-python/2019/07/msg00080.html
> > Your package either build-depends, depends on
Python2, or uses Python2
> in the autopkg tests (the specific reason can be found
searching this
> source package in
>
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt
).
> Please stop using Python2, and fix this issue by one of
the following
> actions.
> > - Convert your Package to Python3. This is the
preferred option. In
> case you are providing a Python module foo, please
consider dropping
> the python-foo package, and only build a python3-foo
package. Please
> don't drop Python2 modules, which still have reverse
dependencies,
> just document them.
> This is the preferred option.
> > - If the package is dead upstream, cannot be
converted or maintained
> in Debian, it should be removed from the distribution. If
the
> package still has reverse dependencies, raise the
severity to
> "serious" and document the reverse dependencies with the
BTS affects
> command. If the package has no reverse dependencies,
confirm that
> the package can be removed, reassign this issue to
ftp.debian.org,
> make sure that the bug priority is set to normal and
retitle the
> issue to "RM: PKG -- removal triggered by the Python2
removal".
> > - If the package has still many users (popcon >=
300), or is needed to
> build another package which cannot be removed, document
that by
> adding the "py2keep" user tag (not replacing the
py2remove tag),
> using the debian-python@lists.debian.org user. Also any
> dependencies on an unversioned python package (python,
python-dev)
> must not be used, same with the python shebang. These
have to be
> replaced by python2/python2.7 dependencies and shebang.
> > This is the least preferred option.
> > If there are questions, please refer to the wiki
page for the removal:
> https://wiki.debian.org/Python/2Removal, or ask for help
on IRC
> #debian-python, or the debian-python@lists.debian.org
mailing list.
> >
-- Tom Russo KM5VY
Tijeras, NM
echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr
[a-m][n-z] [n-z][a-m]
--
Tom Russo KM5VY
Tijeras, NM
echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]
|