ciscoPacketTracer{7,8}: use libxml2_13 that has patches for CVEs, fix desktop icons, refactor#426866
Conversation
|
I'm wondering when #421740 will be merged from |
It can be tracked with nixpk.gs, when specifying the PR number. |
c8e8c46 to
29fa099
Compare
5a2ac99 to
98e95ab
Compare
|
I'm not sure why eval fails and what can we do about it, it should be unrelated to the PR |
|
cc previous reviewers and mergers: @jopejoe1 @griffi-gh @khaneliman @ryand56 |
|
Eval failure looks to be #432489 (comment) |
|
I think it would be better to rebase into staging-next, it is acceptable to merge into staging-next non-mass rebuilds that depend on something already on staging-next |
Now it is almost the same as ciscoPacketTracer8, the major difference is the installed dependencies.
98e95ab to
0088256
Compare
This comment was marked as outdated.
This comment was marked as outdated.
2 similar comments
This comment was marked as outdated.
This comment was marked as outdated.
|
|
Unable to build following instructions but Getting the message: |
|
Thanks for volunteering as a maintainer |
When I last tried it, going to https://netacad.com was like navigating a maze, but I think for legal reasons we should still keep that. To easily download it, you can find the .deb file for the version you see in the error message on this site: https://www.computernetworkingnotes.com/ccna-study-guide/download-packet-tracer-for-windows-and-linux.html |
|
No yeah I did that, got the correct hash but for some reason nixpkgs-review wasn't picking it up :c |
This fixes the security warning, as
libxml2_13includes CVE patches. I also made some other refactoring changes and smaller fixes.Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.Add a 👍 reaction to pull requests you find important.