vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit a6cce2293f8dd8ca787e7617d640304b682d5dfe
Author: Michael Prokop <mika@grml.org>
Date: Sat Apr 24 22:19:12 2021 +0200
Github action: do not install virtualenv + python3-setuptools
pip3 and python3-setuptools are available out of the box on
ubuntu-latest. By not having to install python3-virtualenv we gain ~6
seconds in each of of the codecheck and unit tests runs. So instead
let's rely on system wide pip3, given that we're running in a throw-away
VM anyway.
Thanks: Chris Hofstaedtler
commit 3f776793aa188a538869f2276915b29c7d6e91d5
Author: Michael Prokop <mika@grml.org>
Date: Sat Apr 24 21:58:15 2021 +0200
Fix vulture usage and add vulture to Build-Depends
* grml2iso is a shell script, executing vulture doesn't work on it
* the Debian package build process executes 'make codecheck:', so
everything what's needed for its execution needs to be covered through
the Build-Dependencies, accordingly add add vulture to Build-Depends
commit a5f57b0cb1685060817004b9d66ca1dfa0728b78
Merge: 7cda8fa 40221eb
Author: Michael Prokop <mika@grml.org>
Date: Sat Apr 24 21:54:20 2021 +0200
Merge remote-tracking branch 'origin/pr/46'
commit 40221ebfc36eaccf1634153a0b57ac2db5020966
Author: Manuel Rom <manuel.rom@student.tugraz.at>
Date: Mon Mar 22 11:12:42 2021 +0100
Add Github action workflows for CI/CD
* Add .github/workflows/check-full.yml, enabling:
* Code checks (flake8, black, isort, vulture)
* Unit tests (pytest)
* Adapt the Makefile
* Add vulture to codecheck target
* Add test target with pytest
![[bug history graph]](https://qa.debian.org/data/bts/graphs/g/grml2usb.png){kind=link}