* [ISSUE] conflict between rpi3-firmware and linux-firmware-broadcom
@ 2021-01-06 20:48 xaltsc
2021-01-06 20:58 ` ericonr
2021-01-06 20:59 ` [ISSUE] [CLOSED] " ericonr
0 siblings, 2 replies; 3+ messages in thread
From: xaltsc @ 2021-01-06 20:48 UTC (permalink / raw)
To: ml
[-- 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`
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: conflict between rpi3-firmware and linux-firmware-broadcom
2021-01-06 20:48 [ISSUE] conflict between rpi3-firmware and linux-firmware-broadcom xaltsc
@ 2021-01-06 20:58 ` ericonr
2021-01-06 20:59 ` [ISSUE] [CLOSED] " ericonr
1 sibling, 0 replies; 3+ messages in thread
From: ericonr @ 2021-01-06 20:58 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/27722#issuecomment-755685963
Comment:
Sorry for the confusion, `rpi3-firmware` was removed in 4a487cf40bbec87ab88a2c709ba5079a63fe0e4f, and `rpi3-base` in ddc8991d7d5487e5842488b9778965a1ffa99536. You're supposed to always use `rpi-base` and `rpi-firmware` (at least for now).
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ISSUE] [CLOSED] conflict between rpi3-firmware and linux-firmware-broadcom
2021-01-06 20:48 [ISSUE] conflict between rpi3-firmware and linux-firmware-broadcom xaltsc
2021-01-06 20:58 ` ericonr
@ 2021-01-06 20:59 ` ericonr
1 sibling, 0 replies; 3+ messages in thread
From: ericonr @ 2021-01-06 20:59 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Closed 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 said, this is due to a bug in XBPS.
### Steps to reproduce the behavior
- `xbps-install rpi3-base rpi3-firmware`
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-01-06 20:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-06 20:48 [ISSUE] conflict between rpi3-firmware and linux-firmware-broadcom xaltsc
2021-01-06 20:58 ` ericonr
2021-01-06 20:59 ` [ISSUE] [CLOSED] " ericonr
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).