From: PaperMountainStudio <PaperMountainStudio@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] transmission depends on qt5 on aarch64-musl, but not on x86_64-glibc
Date: Thu, 29 Oct 2020 10:10:30 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25962@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
New issue by PaperMountainStudio on void-packages repository
https://github.com/void-linux/void-packages/issues/25962
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.4.59_1 aarch64-musl Unknown notuptodate rDDDDDFF*
* package:
*transmission-3.00_3*
### Expected behavior
ran on x86_64-glibc, but I would expect similar output on aarch64-musl
```
> xbps-query -Rx transmission
glibc>=2.29_1
zlib>=1.2.3_1
libssl48>=3.1.1_1
libcrypto46>=3.1.1_1
libcurl>=7.19_1
libevent>=2.1.11_1
```
### Actual behavior
dependencies on aarch64-musl:
```
> xbps-query -Rx transmission
zlib>=1.2.3_1
libssl48>=3.1.1_1
libcrypto46>=3.1.1_1
libcurl>=7.19_1
libevent>=2.1.11_1
musl>=1.1.21_1
qt5-widgets>=5.15.0_1
qt5-network>=5.15.0_1
qt5-dbus>=5.15.0_1
qt5-gui>=5.15.0_1
qt5-core>=5.15.0_1
libstdc++>=4.4.0_1
libgcc>=4.4.0_1
```
### Steps to reproduce the behavior
`xbps-query -Rx transmission` on aarch64-musl
next reply other threads:[~2020-10-29 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 9:10 PaperMountainStudio [this message]
2020-10-29 17:27 ` [ISSUE] [CLOSED] " ahesford
2020-10-29 17:28 ` ahesford
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-25962@inbox.vuxu.org \
--to=papermountainstudio@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).