swayfx: Unable to upgrade swayfx / scenefx conflicts

Please fill out the following:

  • Swayfx Version:

swayfx version 0.4-b9dcf5f (Dec 2 2024, branch ‘master’) (based on sway 1.9.0)

  • Description:
    • Attempt to upgrade swayfx to the latest version in Arch through the AUR
paru

 Aur (5) scenefx-0.2.1-2  scenefx-0.1-0.1-2  swayfx-0.4-4

 :: Proceed to review? [Y/n]:

looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing scenefx (0.2.1-2) breaks dependency 'libscenefx.so=1-64' required by swayfx
loading packages...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing scenefx (0.2.1-2) breaks dependency 'libscenefx.so=1-64' required by swayfx
loading packages...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing scenefx (0.2.1-2) breaks dependency 'libscenefx.so=1-64' required by swayfx
loading packages...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing scenefx (0.2.1-2) breaks dependency 'libscenefx.so=1-64' required by swayfx
loading packages...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing scenefx (0.2.1-2) breaks dependency 'libscenefx.so=1-64' required by swayfx
error: packages failed to build: scenefx-0.1-0.1-2  swayfx-0.4-4
paru swayfx

error: failed to prepare transaction (could not satisfy dependencies) :: installing scenefx (0.2.1-2) breaks dependency 'libscenefx.so=1-64' required by swayfx
paru scenefx

error: failed to prepare transaction (could not satisfy dependencies)
:: installing scenefx (0.2.1-2) breaks dependency 'libscenefx.so=1-64' required by swayfx

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 1
  • Comments: 33 (7 by maintainers)

Commits related to this issue

Most upvoted comments

I presume that there were incompatibilities between scenefx-2.0 and swayfx-0.4(the current version), so they made scenefx-0.2.1 able to be installed alongside the 0.1 version (see here) and pointed the deps of swayfx specifically to that package until the rebase (0.5, I think) is fully released.

Yup, this was the case. I’ll try to sort out this packaging issue

I am using garuda-sway and can confirm that your fix works there. Thanks!

FWIW, garuda-update is a convenience wrapper that uses pacman (not yay) but I’m a bit of an amateur at all this so I don’t know if that is related to the current state not-quite-there for others or not.

Fyi, unless you manually installed the package from the AUR, Garuda uses the chaotic AUR by default. That means you are probably using a precompiled binary for which a workaround has already been pushed by the chaotic AUR maintainers.

I presume that there were incompatibilities between scenefx-2.0 and swayfx-0.4(the current version), so they made scenefx-0.2.1 able to be installed alongside the 0.1 version (see here) and pointed the deps of swayfx specifically to that package until the rebase (0.5, I think) is fully released.

Agreed

Running into this now as well.

While of course removing both scenefx-git and swayfx-git before updating works, this is of not very convenient for people who regularly update their system.

To solve this we can also move to the Hyprland approach: Instead of relying on specific .so/library versions, rely on specific git packages. This way you don’t run into library dependency issues, though at the risk of having the wrong libraries at runtime. But this should only be an issue when scenefx updates it’s library version while not triggering a rebuild for swayfx.

For the specific recent case of the wlroots 0.19 and sway 1.11 rebase this approach works great as both scenefx and swayfx need to be updated.

The only change needed to get this to work is to update the swayfx-git PKGBUILD:

diff --git a/PKGBUILD b/PKGBUILD
index 0fcaf06..b2ca7bd 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -12,11 +12,11 @@ makedepends=(
 	"wayland-protocols"
 )
 depends=(
+	"scenefx-git"
 	"cairo"
 	"gdk-pixbuf2"
 	"libevdev.so"
 	"libinput"
-	"libscenefx-0.4.so"
 	"libjson-c.so"
 	"libpixman-1.so"
 	"libudev.so"

What’s your opinion on this approach?

Agreed!

Running into this now as well.

While of course removing both scenefx-git and swayfx-git before updating works, this is of not very convenient for people who regularly update their system.

To solve this we can also move to the Hyprland approach: Instead of relying on specific .so/library versions, rely on specific git packages. This way you don’t run into library dependency issues, though at the risk of having the wrong libraries at runtime. But this should only be an issue when scenefx updates it’s library version while not triggering a rebuild for swayfx.

For the specific recent case of the wlroots 0.19 and sway 1.11 rebase this approach works great as both scenefx and swayfx need to be updated.

The only change needed to get this to work is to update the swayfx-git PKGBUILD:

diff --git a/PKGBUILD b/PKGBUILD
index 0fcaf06..b2ca7bd 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -12,11 +12,11 @@ makedepends=(
 	"wayland-protocols"
 )
 depends=(
+	"scenefx-git"
 	"cairo"
 	"gdk-pixbuf2"
 	"libevdev.so"
 	"libinput"
-	"libscenefx-0.4.so"
 	"libjson-c.so"
 	"libpixman-1.so"
 	"libudev.so"

What’s your opinion on this approach?

Want me to keep my broken install, or should I go ahead and just reinstall if this is not a straight forward fix?

You can go ahead and reinstall. I have the specific versions locally to test. Thanks for your testing! 😄

@ErikReider you can see at the top of the screenshot for swayfx: 0.4-3. The issues started when 0.4-4 was released with the new dependency chain.

For scenefx, I have the dependency of swayfx 0.4-3 installed:

Image

I know how to “fix” it on my end by removing and reinstalling, but I kept it installed in case you want to keep trying to fix it on your end 😃

@coderj001 @martinstark sorry for the issues here. I believe it should now be fixed