From: selfisekai <selfisekai@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] vscode package broken
Date: Sat, 27 Feb 2021 23:51:03 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29105@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
New issue by selfisekai on void-packages repository
https://github.com/void-linux/void-packages/issues/29105
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: `Void 5.10.19_1 x86_64-musl AuthenticAMD uptodate rF`
*output of ``xuname`` (part of xtools)*
* package: `vscode-1.53.2_1`
*affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
### Expected behavior
Run the VS Code
### Actual behavior
```
[laura@suzumiya ~]$ code-oss
Warning: 'app' is not in the list of known options, but still passed to Electron/Chromium.
```
### Steps to reproduce the behavior
run `code-oss`
next reply other threads:[~2021-02-27 22:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 22:51 selfisekai [this message]
2021-02-27 23:05 ` Johnnynator
2021-02-27 23:09 ` selfisekai
2021-02-27 23:33 ` electron{9,10}: broken on musl ericonr
2021-02-27 23:33 ` ericonr
2021-02-27 23:42 ` ericonr
2021-02-28 2:01 ` fosslinux
2021-02-28 2:02 ` fosslinux
2021-02-28 3:13 ` selfisekai
2021-02-28 7:41 ` fosslinux
2021-02-28 7:41 ` fosslinux
2021-02-28 13:55 ` selfisekai
2021-03-05 5:46 ` kawaiiamber
2022-03-24 10:06 ` git-bruh
2022-06-23 2:15 ` github-actions
2022-06-25 6:10 ` fosslinux
2022-06-27 7:22 ` selfisekai
2022-09-28 1:04 ` mjeveritt
2022-09-28 1:05 ` mjeveritt
2022-09-28 1:39 ` q66
2022-09-28 1:39 ` [ISSUE] [CLOSED] " q66
2023-02-08 22:02 ` sistematico
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29105@inbox.vuxu.org \
--to=selfisekai@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).