From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: gns3-server: update to version 2.2.43.
Date: Mon, 30 Oct 2023 19:56:34 +0100 [thread overview]
Message-ID: <20231030185634.ADXtF9BSdxNCrTYubZXY7aFxsa6_R0Eii45KhlyKLbY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46778@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
There's a closed pull request on the void-packages repository
gns3-server: update to version 2.2.43.
https://github.com/void-linux/void-packages/pull/46778
Description:
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (X64-GlibC)
Hey lads, i tried to update GNS3 server, as it was an idea i got for a school project, basically, the web ui was broken before version 2.2.40.
However the building process acted weird: it went SUPER FAST, with warnings, sure, but all the way through.
It's weird to me, so i'll make this a draft PR, if someone can confirm me it's a normal behavior, then i'll make it a normal PR, but i think something is wrong here, even tho xbps-src went all way through.
I also removed the importlib patch as the modifications brought by it were already in the distant repo, it was no longer useful.
prev parent reply other threads:[~2023-10-30 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 17:30 [PR PATCH] " SpidFightFR
2023-10-19 17:33 ` SpidFightFR
2023-10-19 23:00 ` classabbyamp
2023-10-20 5:03 ` SpidFightFR
2023-10-21 13:15 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-21 13:17 ` SpidFightFR
2023-10-27 17:12 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-27 17:33 ` SpidFightFR
2023-10-30 17:19 ` biopsin
2023-10-30 18:56 ` SpidFightFR [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231030185634.ADXtF9BSdxNCrTYubZXY7aFxsa6_R0Eii45KhlyKLbY@z \
--to=spidfightfr@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).