View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0008410||Kali Linux||Tool Upgrade Request||public||2023-08-03 16:03||2023-08-08 22:42|
|Summary||0008410: Villain - New Version|
Hi, thank you for adding my project in kali-rolling!
Thank your for your time.
FYI, added a new update mechanism that compares file signatures from the main branch of the project's repo against local installation file signatures and proceeds to upgrade. This should be sufficient to maintain the project up to date in kali without the tool being re-packaged every now and then. The -u (--update) option that your team wisely removed before adding Villain in kali-rolling (as it would not work) has been substituted with option -s (--skip-update). The new update routine is in Villain.py (lines 740-830), in case you need to inspect it.
*Among various new and existing files, requirements.txt has also changed.
Something that would really help us keep the package update would be if you could create git tags for the point releases. Right now our update process checks for any change in the villain repository, but that brings to much noise. With release tags it would only pop us when the new version is ready. This is not mandatory, we can keep it as it is right now, but just to let you know.
Anyway, thanks for checking your tool being packaged ;) It's intended to be announced in this next release
|2023-08-03 16:03||t3l3machus||New Issue|
|2023-08-03 16:03||t3l3machus||Status||new => assigned|
|2023-08-03 16:03||t3l3machus||Assigned To||=> sbrun|
|2023-08-07 19:47||t3l3machus||Note Added: 0018281|
|2023-08-08 22:42||daniruiz||Note Added: 0018291|
|2023-08-08 22:42||daniruiz||Assigned To||sbrun => daniruiz|
|2023-08-08 22:42||daniruiz||Status||assigned => resolved|
|2023-08-08 22:42||daniruiz||Resolution||open => fixed|