🤖 Package update #1099
🤖 Package update #1099
Conversation
vm-packages
force-pushed
the
package-update
branch
from
45b3bcf to
bda828d
Compare
vm-packages
force-pushed
the
package-update
branch
from
bda828d to
b5bde85
Compare
vm-packages
force-pushed
the
package-update
branch
from
b5bde85 to
09f078e
Compare
vm-packages
force-pushed
the
package-update
branch
from
4951414 to
5d7f606
Compare
|
@d35ha thanks for reviewing this PR! the bot updates the Package update PR every wednesday if we do not merge it first (we could trigger manually only, but we did it this way to ensure we do not forget it). So when you test the changes, if it is good to go ensure you merge the PR before the update is triggered. Now you need to test all new changes before approving & merging the PR as we need to ensure that what is merged is working. Ensure you test not only that packages install correctly (as our test suite already does this), but that you test the tools locally. This is specially important for the tools in the FLARE-VM default configuration (such as cyberchef, notepad++, ghidra, and wireshark), as we need to ensure these tools work properly as FLARE and others rely on them. |
vm-packages
force-pushed
the
package-update
branch
2 times, most recently
from
1ac1234 to
e70cb7c
Compare
vm-packages
force-pushed
the
package-update
branch
from
e70cb7c to
d4ca1c0
Compare
vm-packages
force-pushed
the
package-update
branch
from
d4ca1c0 to
7e2f9f2
Compare
|
@emtuls the bot has updated the PR today 😄 |
|
Just tested everything and they all worked as expected except our typical ImHex issue, but I believe we can add the 'No-GPU' release version in addition to the one we have been adding and that would solve our issue, as noted here: #940 (comment). I downloaded and tested the 'No-GPU' latest version of ImHex and it worked well. :) |
Automated package update