From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] ffmpeg-devel-32bit incorrectly has 64-bit dependencies
Date: Fri, 05 Feb 2021 03:44:30 +0100 [thread overview]
Message-ID: <20210205024430.y8jV1gnb26v4CIkDP0-pHSR63waB5_5Dbe4aHzY2kDw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5194@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
Closed issue by Headwind81 on void-packages repository
https://github.com/void-linux/void-packages/issues/5194
Description:
### System
* xuname:
bash: xuname: command not found
* package:
ffmpeg-devel-32bit-4.1_1
### Expected behavior
'xbps-install ffmpeg-devel-32bit' should install 32-bit dependencies.
### Actual behavior
It instead incorrectly installs 64-bit dependencies.
### Steps to reproduce the behavior
Running 'xbps-query -Rx ffmpeg-devel', then 'xbps-query -Rx ffmpeg-devel-32bit', shows the same outputs (they each depend on the same 64-bit packages). Presumably the 32-bit version should have 32-bit dependencies. It's my understanding that the -32bit packages are generated automatically, and therefore that automation must have failed in this case.
parent reply other threads:[~2021-02-05 2:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-5194@inbox.vuxu.org>]
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=20210205024430.y8jV1gnb26v4CIkDP0-pHSR63waB5_5Dbe4aHzY2kDw@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).