From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] vscode: live share plugin from market place needs openssl to work
Date: Sat, 30 Jan 2021 02:55:04 +0100 [thread overview]
Message-ID: <20210130015504.GvMJtiqAFEGxKiSDH5nAFRdFcimB3izPvyZio_amSa0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11926@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
Closed issue by lalincedeldeserto on void-packages repository
https://github.com/void-linux/void-packages/issues/11926
Description:
### System
* xuname:
*output of ``xuname`` (part of xtools)*
Void 4.19.45_1 x86_64 GenuineIntel uptodate rrFF
* package:
*affected package(s) including the version*
vscode live-share from microsoft (search into vscode market place)
I installed correctly from the marketplace live-share plugin but it doesn't start because it needs openssl.
File log:
[liveshare-log.zip](https://github.com/void-linux/void-packages/files/3217031/liveshare-log.zip)
A screenshot to the extension:
![image](https://user-images.githubusercontent.com/33136381/58331045-8b30a480-7e38-11e9-88b3-298ccbb261fc.png)
prev parent reply other threads:[~2021-01-30 1:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11926@inbox.vuxu.org>
2019-05-31 12:27 ` voidlinux-github
2019-05-31 12:28 ` voidlinux-github
2019-05-31 12:28 ` voidlinux-github
2019-05-31 13:58 ` voidlinux-github
2019-06-18 5:21 ` voidlinux-github
2019-06-18 19:17 ` voidlinux-github
2019-10-01 11:57 ` voidlinux-github
2019-10-13 2:36 ` voidlinux-github
2019-10-13 6:29 ` voidlinux-github
2019-10-13 6:30 ` voidlinux-github
2019-10-13 6:31 ` voidlinux-github
2019-10-13 6:34 ` voidlinux-github
2021-01-30 1:55 ` ericonr
2021-01-30 1:55 ` ericonr [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=20210130015504.GvMJtiqAFEGxKiSDH5nAFRdFcimB3izPvyZio_amSa0@z \
--to=ericonr@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).