From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Divan Santana <divan@santanas.co.za>
Cc: 37369@debbugs.gnu.org, help-guix@gnu.org
Subject: Re: bug#37369: Getting network-manager-openconnect to work
Date: Sun, 29 Sep 2019 09:54:25 +0200 [thread overview]
Message-ID: <20190929075425.4yuz27fhm5jwvujm@pelzflorian.localdomain> (raw)
In-Reply-To: <20190928153443.r4kbd3tninivufq6@pelzflorian.localdomain>
Regarding openconnect, no workarounds are necessary anymore for me on
core-updates, which uses a more recent network-manager@1.14.4 and will
soon be on Guix master.
Regards,
Florian
next prev parent reply other threads:[~2019-09-29 7:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 9:57 Getting network-manager-openconnect to work Divan Santana
2019-09-10 11:21 ` pelzflorian (Florian Pelz)
2019-09-11 7:38 ` bug#37369: " Efraim Flashner
2019-09-11 7:38 ` Efraim Flashner
2019-09-11 11:39 ` pelzflorian (Florian Pelz)
2019-09-11 11:39 ` pelzflorian (Florian Pelz)
2019-09-11 20:46 ` Ludovic Courtès
2019-09-12 5:34 ` pelzflorian (Florian Pelz)
2019-09-16 15:57 ` Ludovic Courtès
2019-09-16 16:06 ` pelzflorian (Florian Pelz)
2019-09-27 16:37 ` bug#37369: " pelzflorian (Florian Pelz)
2019-09-28 14:00 ` Divan Santana
2019-09-28 14:00 ` Divan Santana
2019-09-28 14:16 ` Divan Santana
2019-09-28 14:16 ` Divan Santana
2019-09-28 15:34 ` pelzflorian (Florian Pelz)
2019-09-29 7:54 ` pelzflorian (Florian Pelz) [this message]
2019-09-29 7:54 ` pelzflorian (Florian Pelz)
2019-09-28 15:34 ` pelzflorian (Florian Pelz)
2019-09-28 16:47 ` pelzflorian (Florian Pelz)
2019-09-28 16:47 ` pelzflorian (Florian Pelz)
2019-10-03 11:51 ` Divan Santana
2019-10-03 11:51 ` Divan Santana
2019-09-16 11:53 ` pelzflorian (Florian Pelz)
2019-09-16 11:53 ` pelzflorian (Florian Pelz)
2020-04-12 19:46 ` divan
2020-05-04 19:43 ` bug#37369: (no subject) Divan Santana via web
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=20190929075425.4yuz27fhm5jwvujm@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=37369@debbugs.gnu.org \
--cc=divan@santanas.co.za \
--cc=help-guix@gnu.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.
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.