GNS3 2.2.25

[tsndqst]

General

• This is a new package and it conforms to the quality requirements

Have the results of the proposed changes been tested?

• I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
• I generally don't use the affected packages but briefly tested this PR

Does it build and run successfully?

(Please choose at least one native build and, if supported, at least one cross build. More are better.)

• I built this PR locally for my native architecture, (x86_64-glibc)
• I built this PR locally for these architectures (if supported. mark crossbuilds):
  • aarch64-musl
  • armv7l
  • armv6l-musl

[paper42]

Next time you can force push to a PR instead of opening a new one.

[tsndqst]

Next time you can force push to a PR instead of opening a new one.

True. I made a new PR because I made a new branch. The old branch had the 2.2.23 version number in it so I wanted to avoid confusion by creating a new branch with the correct name.

[tsndqst]

I missed something in gns3-gui. Working on a fix now.

[tsndqst]

@paper42 can you take another look? I did a bit of refactoring to get tests working instead of skipping them altogether. It involved adding a couple packages but they were pretty straight forward.

I also removed python3-sentry package since it was only used for crash reports and apparently isn't included in the upstream packages.

[paper42]

python3-sentry needs to be added to removed-packages like in #32495

GitHub doesn't detect you as the author of the commits, could you add the email you are using in the commits to your GitHub profile?

[tsndqst]

Thanks @paper42
I'll make a separate PR for removal of python3-sentry once this PR is merged.
I updated my email address in GitHub as well.