49 lines
1.6 KiB
Markdown
49 lines
1.6 KiB
Markdown
|
#laptop
|
|||
|
|
#documentation
|
|||
|
|
#issue
|
|||
|
|
#closed
|
|||
|
|
#linux
|
|||
|
|
02/02/2022
|
|||
|
|
|
|||
|
|
Because wifi was broken by a pacman update, I’m reverting to an older point in the repos(01/01/2022).
|
|||
|
|
|
|||
|
|
When updating via pacman -Syyuu, `error: failed to prepare transaction (could not satisfy dependencies)
|
|||
|
|
|
|||
|
|
:: installing expat (2.4.2-1) breaks dependency 'expat=2.4.4' required by lib32-expat
|
|||
|
|
|
|||
|
|
:: installing libcap (2.62-1) breaks dependency 'libcap=2.63' required by lib32-libcap` is returned.
|
|||
|
|
|
|||
|
|
`lib32-expat ` is an xml parser library [Arch WIki](https://archlinux.org/packages/multilib/x86_64/lib32-expat/), and lib32-libcap is some posix document `[arch wiki](https://archlinux.org/packages/multilib/x86_64/lib32-libcap/)`.
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
New solution: downgrade lib32-libcap(2.63-1 to 2.62-1) and lib32-expat(2.4.4-1 to 2.4.2-1)
|
|||
|
|
|
|||
|
|
Was going to use expat 2.4.3 but caused dependency issues with the 64 bit version. V2 successfully worked
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
sudo pacman -U /var/cache/pacman/pkg/[PACKAGE].pkg.tar.zst
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
After the above downgrade, `sudo pacman -Syyuu` with “y” on skip the lib32-expat and lib32-libcap worked, but returned
|
|||
|
|
|
|||
|
|
error: failed to commit transaction (conflicting files)
|
|||
|
|
|
|||
|
|
hwids: /usr/share/hwdata/pci.ids exists in filesystem (owned by hwdata)
|
|||
|
|
|
|||
|
|
hwids: /usr/share/hwdata/pnp.ids exists in filesystem (owned by hwdata)
|
|||
|
|
|
|||
|
|
hwids: /usr/share/hwdata/usb.ids exists in filesystem (owned by hwdata)
|
|||
|
|
|
|||
|
|
[referenced documentation for below as on garuda forums](https://forum.garudalinux.org/t/help-cant-upgrade/16237/2)
|
|||
|
|
|
|||
|
|
Couldn’t figure out how to fix above issue, attempting a different date(15).
|
|||
|
|
|
|||
|
|
|
|||
|
|
|
|||
|
|
ISSUE CLOSED.
|
|||
|
|
|
|||
|
|
Solution, using the rollback repos to rollback to 2022/01/15
|