Github messages for voidlinux
 help / color / mirror / Atom feed
From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Discord Support For Musl
Date: Thu, 20 Jan 2022 12:46:45 +0100	[thread overview]
Message-ID: <20220120114645.hbsbowJ9yTYI6zgiFN2sOKu2k3_XvUNIJvtkSlIBm48@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35132@inbox.vuxu.org>

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

Closed issue by JuniorSuperTux on void-packages repository

https://github.com/void-linux/void-packages/issues/35132

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.15.14_1 x86_64-musl GenuineIntel notuptodate rFF
* package:  
  discord-0.0.16_2

### Expected behavior
Puts Discord in local repo
### Actual behavior
```
=> xbps-src: updating repositories for host (x86_64-musl)...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/musl/x86_64-musl-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/musl/nonfree/x86_64-musl-repodata' ...
[*] Updating repository `https://alpha.de.repo.voidlinux.org/current/musl/debug/x86_64-musl-repodata' ...
=> xbps-src: updating software in / masterdir...
=> xbps-src: cleaning up / masterdir...
=> discord-0.0.16_2: removing autodeps, please wait...
=> ERROR: discord-0.0.16_2: this package cannot be built for x86_64-musl.
```
### Steps to reproduce the behavior
```
./xbps-src pkg discord
```

  reply	other threads:[~2022-01-20 11:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 11:25 [ISSUE] " JuniorSuperTux
2022-01-20 11:46 ` Johnnynator [this message]
2022-01-20 11:46 ` Johnnynator

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=20220120114645.hbsbowJ9yTYI6zgiFN2sOKu2k3_XvUNIJvtkSlIBm48@z \
    --to=johnnynator@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).