From: xaltsc <xaltsc@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] conflict between rpi3-firmware and linux-firmware-broadcom
Date: Wed, 06 Jan 2021 21:48:49 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27722@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
New issue by xaltsc on void-packages repository
https://github.com/void-linux/void-packages/issues/27722
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.9.16_1 aarch64-musl GenuineIntel uptodate rF` (inside a chroot)
* package:
`rpi3-firmware-20170113_1`, `linux-firmware-broadcom-20201218_1` and therefore `rpi3-base-0.1_3`
### Expected behavior
`xbps-install rpi3-base rpi3-firmware` installs both packages as intended.
### Actual behavior
XBPS installs both packages until it fails with the following error:
```
ERROR: rpi3-firmware-20170113_1: file `/usr/lib/firmware/brcm/brcmfmac43430-sdio.bin' already installed by package linux-firmware-broadcom-20201218_1.
```
It's possible to work around this by installing `rpi3-firmware` before `rpi3-base`, but, as @ericonr say, this is due to a bug in XBPS.
### Steps to reproduce the behavior
- `xbps-install rpi3-base rpi3-firmware`
next reply other threads:[~2021-01-06 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 20:48 xaltsc [this message]
2021-01-06 20:58 ` ericonr
2021-01-06 20:59 ` [ISSUE] [CLOSED] " ericonr
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-27722@inbox.vuxu.org \
--to=xaltsc@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).