Github messages for voidlinux
 help / color / mirror / Atom feed
From: balejk <balejk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: sstp-client
Date: Fri, 29 Dec 2023 19:09:00 +0100	[thread overview]
Message-ID: <20231229180900.CUbSAHocvvUsuNJAxIetPd2uZBfthJJ1MhgWCDcA5sI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46669@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]

New comment by balejk on void-packages repository

https://github.com/void-linux/void-packages/issues/46669#issuecomment-1872254468

Comment:
>  I also assembled nm-sstp-plugin template, see [that comment](https://github.com/void-linux/void-packages/issues/46670#issuecomment-1872214252) but still can't connect. Unfortunately VPN server is not mine so can't check logs. 

Sorry, I don't use NM so I cannot help you there. But I suggest you try
to install version 1.0.18 and check whether that works (see below). Also
note that if you are using musl you will need to apply a patch for it to
compile - see the project's git log, it should be something like the
second commit after the release of 1.0.18.

> @balejk what kind of issues have you encouraged?

Please see the issue that I have opened at the project's Gitlab
repository, I hope I have described it there in enough detail.

If you could confirm that you are experiencing the same issue (since it
seems that you are using version 1.0.19 which should be the first one
that is affected) it would be great if you could mention it in the issue
with some details, especially if you are using sstpc in a different way
than me (i. e. via NM).


      parent reply	other threads:[~2023-12-29 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 22:00 [ISSUE] " michalszmidt
2023-10-17 17:43 ` balejk
2023-12-19  2:45 ` [ISSUE] [CLOSED] " sgn
2023-12-29 16:50 ` michalszmidt
2023-12-29 18:09 ` balejk [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=20231229180900.CUbSAHocvvUsuNJAxIetPd2uZBfthJJ1MhgWCDcA5sI@z \
    --to=balejk@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).