[Slackbuilds-users] progress update turns it in a python thing ?

[Tonus]

Hi all,
(I've change my subscribed email and will soon update the SB scripts I 
maintain.)

I've sent a message to the 'progress' package maintainer, 
dzlatanidis at gmail.com, a bit more than one week ago.

Got no response and, as the thing appears to be fully broken, I thought 
it is a good idea to ring a bell here. (Additionally, since gmail 
terminated simple login and this looks like a template mistake, it 
might not have been seen.)

Here what I sent :

> From: Tonus <tonus1 at gmail.com>
> To: d.zlatanidis at gmail.com
> Date: Sun, 5 Jun 2022 19:37:01 +0200
> Subject: Troubles with progess 
> Hi,
> I've seen a progress update on the repo and blindly installed it.
> Problem, it seems quite different than the previous one :
> PACKAGE NAME: progress-0.14-x86_64-1_SBo
> COMPRESSED PACKAGE SIZE: 28K
> UNCOMPRESSED PACKAGE SIZE: 90K
> PACKAGE LOCATION: repo/local/SBo-15.0/progress-0.14-x86_64-1_SBo.tgz
> PACKAGE DESCRIPTION:
> progress: progress (Linux tool to show progress)
> progress:
> progress: This tool can be described as a Tiny, Dirty, Linux-and-OSX-Only C
> progress: command that looks for coreutils basic commands (cp, mv, dd, tar,
> progress: gzip/gunzip, cat, etc.) currently running on your system and displays
> progress: the percentage of copied data. It can also show estimated time and
> progress: throughput, and provides a `top-like` mode (monitoring).
> progress:
> progress: Homepage: https://github.com/Xfennec/progress
> progress:
> progress:
> FILE LIST:
> ./
> install/
> install/slack-desc
> usr/
> usr/bin/
> usr/bin/progress
> usr/doc/
> usr/doc/progress-0.14/
> usr/doc/progress-0.14/LICENSE 
> usr/doc/progress-0.14/README.md 
> usr/doc/progress-0.14/progress.SlackBuild 
> usr/man/
> usr/man/man1/ 
> usr/man/man1/progress.1.gz
> 
> PACKAGE NAME: progress-1.6-x86_64-1_SBo
> COMPRESSED PACKAGE SIZE: 16K
> UNCOMPRESSED PACKAGE SIZE: 60K
> PACKAGE LOCATION: /tmp/progress-1.6-x86_64-1_SBo.tgz
> PACKAGE DESCRIPTION:
> progress: progress (Linux tool to show progress)
> progress:
> progress: This tool can be described as a Tiny, Dirty, Linux-and-OSX-Only C
> progress: command that looks for coreutils basic commands (cp, mv, dd, tar,
> progress: gzip/gunzip, cat, etc.) currently running on your system and displays
> progress: the percentage of copied data. It can also show estimated time and
> progress: throughput, and provides a `top-like` mode (monitoring).
> progress:
> progress: Homepage: https://github.com/Xfennec/progress
> progress:
> progress:
> FILE LIST:
> ./
> install/
> install/slack-desc
> usr/
> usr/doc/
> usr/doc/progress-1.6/
> usr/doc/progress-1.6/LICENSE
> usr/doc/progress-1.6/README.rst
> usr/doc/progress-1.6/progress.SlackBuild
> usr/lib64/
> usr/lib64/python3.9/
> usr/lib64/python3.9/site-packages/
> usr/lib64/python3.9/site-packages/progress-1.6-py3.9.egg-info/
> usr/lib64/python3.9/site-packages/progress-1.6-py3.9.egg-info/PKG-INFO
> usr/lib64/python3.9/site-packages/progress-1.6-py3.9.egg-info/SOURCES.txt
> usr/lib64/python3.9/site-packages/progress-1.6-py3.9.egg-info/dependency_links.txt
> usr/lib64/python3.9/site-packages/progress-1.6-py3.9.egg-info/top_level.txt
> usr/lib64/python3.9/site-packages/progress/
> usr/lib64/python3.9/site-packages/progress/__init__.py
> usr/lib64/python3.9/site-packages/progress/__pycache__/
> usr/lib64/python3.9/site-packages/progress/__pycache__/__init__.cpython-39.pyc
> usr/lib64/python3.9/site-packages/progress/__pycache__/bar.cpython-39.pyc
> usr/lib64/python3.9/site-packages/progress/__pycache__/colors.cpython-39.pyc
> usr/lib64/python3.9/site-packages/progress/__pycache__/counter.cpython-39.pycusr/lib64/python3.9/site-packages/progress/__pycache__/spinner.cpython-39.pycusr/lib64/python3.9/site-packages/progress/bar.py
> usr/lib64/python3.9/site-packages/progress/colors.py
> usr/lib64/python3.9/site-packages/progress/counter.py
> usr/lib64/python3.9/site-packages/progress/spinner.py
> 
> Could it be a erroneous automated build ? It doesn't seem to be a 
> python package.

I think it might be a safe solution to revert, if possible, last update.

Regards

-- 
Regards,

Tonus