Broken package monitoring
noraj opened this issue · 9 comments
broken packages reason
- climber: Error ImportError: No module named resource
From upstream repo it say just clone master branch knipknap/exscript#145 and I've saw that PKGBUILD did that.
UPDATE: He's included exscript itself, not using from repo.
https://github.com/raffaele-forte/climber/tree/master/Exscript
I think we need to remove exscript folder from the package.
File "/usr/share/climber/Exscript/protocols/SSH2.py", line 26, in <module>
from paramiko.resource import ResourceManager
ImportError: No module named resource
- eapeak:
from scapy.layers.l2 import EAP
ImportError: cannot import name EAP
From scapy docs, it's refactored from layers.l2 to layers.eap
https://scapy.readthedocs.io/en/latest/api/scapy.layers.eap.html
- eapeak:
from scapy.layers.l2 import EAP ImportError: cannot import name EAP
From scapy docs, it's refactored from layers.l2 to layers.eap
https://scapy.readthedocs.io/en/latest/api/scapy.layers.eap.html
There were two pull requests addressing this problem. One was merged and later reverted as it seems to introduce some other issues. The maintainer recommended a rewrite in python 3, but is not interessted (Feb 219) in doing so.
It received the last update in 2018. So it should be removed
I guess that bof-detector package is broken? I couldn't access the repo, it seems that the GitHub account was deleted.
I'm having some issues with stegoveritas, seems similar to what's addressed here: #2751, but I'm running on a fresh Black Arch install and getting this issue.
Traceback (most recent call last):
File "/usr/lib/python3.9/multiprocessing/pool.py", line 125, in worker
result = (True, func(*args, **kwds))
File "/usr/lib/python3.9/site-packages/stegoveritas/modules/image/analysis/brute_lsb.py", line 13, in run_dump
image.veritas.test_output(o)
File "/usr/lib/python3.9/site-packages/stegoveritas/stegoveritas.py", line 79, in test_output
m = magic.from_buffer(thing, mime=True)
AttributeError: module 'magic' has no attribute 'from_buffer'
@tylerstonge please open an individual issue for this. I can't reproduce your issue right now, please provide
- which iso did you use to install and if you did an online install (if applicable)
- the package version of stegoveritas
- the exact command you ran
-
genisys
#3460
Upstream https://github.com/Cryptonian007/Genisys
was removed, seems that Cryptonian007 was a fork of https://github.com/noob-coder123/Genisys. But noob-coder123 (9 commits, v2.1) if far behind (Cryptonian007 was 53 commits, v2.5) so we have to choose a more up to date fork in https://github.com/noob-coder123/Genisys/network/members like https://github.com/ahayder/Genisys or https://github.com/baratt/Genisys that were up to date at that time. But those are dead forks, it doesn't seem to have any active fork.
- pacu
Several dependencies are missing or out of date. Example:
➜ pacu
Traceback (most recent call last):
File "/usr/share/pacu/pacu/main.py", line 23, in <module>
import jq # type: ignore
^^^^^^^^^
<class 'ModuleNotFoundError'>: No module named 'jq'
Pacu was not able to start because a required Python package was not found.
Run `sh install.sh` to check and install Pacu's Python requirements.