Package Details: vbam-wx 2.2.3-1

Git Clone URL: https://aur.archlinux.org/vbam.git (read-only, click to copy)
Package Base: vbam
Description: Nintendo GameBoy Advance emulator
Upstream URL: https://visualboyadvance-m.org
Licenses: GPL-2.0-only
Conflicts: vbam-sdl
Submitter: arojas
Maintainer: bailwillharr
Last Packager: redraid
Votes: 4
Popularity: 0.63
First Submitted: 2025-03-31 20:37 (UTC)
Last Updated: 2025-11-24 14:53 (UTC)

Dependencies (22)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

nirnakinho commented on 2026-08-09 19:44 (UTC) (edited on 2026-08-09 19:46 (UTC) by nirnakinho)

If you look at https://archlinux.org/packages/extra/x86_64/ffmpeg/ you will see that ffmpeg provides versioned pseudo-packages, e.g. libavcodec.so=63-64

Once you build the vbam-wx package, it takes these versions from the currently installed ffmpeg package. Whenever an update to the ffmpeg package changes those versions, the conflict occurs.

One way is to pushing an update of the vbam PKGBUILD, only incrementing pkrel, whenever a breaking update of ffmpeg happens.

Due to AUR git being disabled right now, the user can do this manually by using their AUR helper to explicity reinstall the package.

One way to mitigate this, could be to put those pseudo-dependencies explicitly in the vbam PKGBUILD, overriding the version numbers to be more generic. However, any non-ABI-compatible update to ffmpeg might break things, though.

bailwillharr commented on 2026-08-09 17:09 (UTC)

@gojira_96 @nirnakinho I'm not sure what was causing this. I managed to replicate your issue when doing makepkg -s, but cleaning the vbam package folder and rerunning makepkg -s seems to fix the issue.

gojira_96 commented on 2026-08-09 16:55 (UTC)

@nirnakinho that worked for me

nirnakinho commented on 2026-08-09 06:09 (UTC)

For me, uninstalling vbam-wx, updating ffmpeg and rebuilding vbam-wx worked.

gojira_96 commented on 2026-08-08 17:43 (UTC) (edited on 2026-08-08 20:40 (UTC) by gojira_96)

vbam-wx is currently broken against ffmpeg 2:9.0-5.1 (breaks on libavcodec.so=62, libavformat.so=62, libavutil.so=60, libswscale.so=9 — the new sonames). Had to remove it to update ffmpeg. any fixes?

edit: in the PKGBUILD, toggling -DENABLE_FFMPEG=OFF / works

redraid commented on 2025-11-24 14:54 (UTC)

Only took maintainership for updating to version 2.2.3

simona commented on 2025-10-11 12:51 (UTC)

can't import pgp keys

voxan24 commented on 2025-10-11 12:25 (UTC)

PGP Key updated, i take the packet only to update the key.

nirnakinho commented on 2025-10-04 21:56 (UTC)

Oh, I just checked the missing key myself. The owner, Zach Bacon, has published a new pgp key with key id A4E3697D524B238DECCF3A17EB0E0FF1C62782D8. That one actually is published on keys.openpgp.org. You might want to uplade the PKGBUILD to use the new key id.

Regards,

nirnakinho commented on 2025-10-04 21:52 (UTC)

tee, instead of telling us how to skip the integrity check, you could simply modify the PKGBUILD and remove the missing PGP key. Alternatively, you could contact the owners of the keys and ask them to publish the keys on the new non-sks keyservers like keys.openpgp.org. Their email addresses are listed in the comments. Alternatively, you could simply remove the validpgpkeys line entirely to make the PKGBUILD skip the pgp integrity check.

Regards,

1 2 Next › Last »