all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Benjamin <benjamin@uvy.fr>
Cc: Raghav Gururajan <rg@raghavgururajan.name>,
	Liliana Marie Prikler <liliana.prikler@gmail.com>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	66990-done@debbugs.gnu.org
Subject: bug#66990: [PATCH 0/3] fix build of network-manager-fortisslvpn and openfortivpn
Date: Sat, 25 Nov 2023 23:17:25 +0100	[thread overview]
Message-ID: <87wmu532bu.fsf@gnu.org> (raw)
In-Reply-To: <cover.1699374647.git.benjamin@uvy.fr> (benjamin@uvy.fr's message of "Tue, 7 Nov 2023 17:33:05 +0100")

Hi Benjamin & Liliana,

Benjamin <benjamin@uvy.fr> skribis:

> [0] https://gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn/-/commit/084ef529c5fb816927ca54866f66b340265aa9f6
> [1] https://github.com/adrienverge/openfortivpn/pull/1148
>
> Benjamin (3):
>   gnu: Add ppp-2.4.9.
>   gnu: openfortivpn: fix build.
>   gnu: network-manager-fortisslvpn: fix build.

I went ahead and applied these changes, moving the links above as
comments in the code.  Hopefully we’ll be able to switch to ppp 2.5.0
real soon as fixed have now been merged upstream.

Thanks,
Ludo’.




      parent reply	other threads:[~2023-11-25 22:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 16:33 [bug#66990] [PATCH 0/3] fix build of network-manager-fortisslvpn and openfortivpn Benjamin
2023-11-07 16:36 ` [bug#66990] [PATCH 1/3] gnu: Add ppp-2.4.9 Benjamin
2023-11-07 16:36 ` [bug#66990] [PATCH 2/3] gnu: openfortivpn: fix build Benjamin
2023-11-07 16:36 ` [bug#66990] [PATCH 3/3] gnu: network-manager-fortisslvpn: " Benjamin
2023-11-07 17:07   ` Liliana Marie Prikler
2023-11-25 22:17 ` Ludovic Courtès [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=87wmu532bu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=66990-done@debbugs.gnu.org \
    --cc=benjamin@uvy.fr \
    --cc=liliana.prikler@gmail.com \
    --cc=maxim.cournoyer@gmail.com \
    --cc=rg@raghavgururajan.name \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.