Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to upgrade swayfx / scenefx conflicts #384

Open
martinstark opened this issue Feb 19, 2025 · 16 comments
Open

Unable to upgrade swayfx / scenefx conflicts #384

martinstark opened this issue Feb 19, 2025 · 16 comments
Labels
bug Something isn't working

Comments

@martinstark
Copy link

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
@martinstark martinstark added the bug Something isn't working label Feb 19, 2025
@LAURAilway
Copy link

LAURAilway commented Feb 19, 2025

This is caused by some fun shenanigans in the way that scenefx was updated.
You can force uninstall scenefx (pacman -Rdd) and then either just install scenefx-1.0 or install the newest version of scenefx and 1.0 alongside it, after that, you can update swayfx again.
Note that at the moment, scenefx-1.0 is the required version for swayfx.

@martinstark
Copy link
Author

did swayfx recently change from scenefx to scenefx-1.0? I haven't changed anything manually around this since I installed swayfx, and since swayfx-0.4-4 was released the other day paru wants to install both scenefx-0.2.1-2 and scenefx-0.1-0.1-2

@LAURAilway
Copy link

LAURAilway commented Feb 19, 2025

Mb, 0.1, not 1.0.
It did not, the current version of scenefx is scenefx-0.2.1.
However, swayfx explicitly depends on scenefx-0.1, and while updating scenefx does in fact pull in the scenefx-0.1 package as well, paru seems to not factor that in regarding the dependency checks, so it thinks that after updating scenefx past 0.1.x, swayfx will be left without that dependency.
Sry for the confusion with the 1.0 typo.

@martinstark
Copy link
Author

martinstark commented Feb 19, 2025

I guess this is why it's confused?

Image

I have the "correct" version of scenefx, but using the original scenefx package rather than the scenefx-0.1 version.

I'm a bit confused why the AUR package was updated the other day while there is no new release of scenefx itself. I guess that's where the dependency chain was updated, rather than in this repo.

I guess the best way forward (as you say) is to force uninstall and then reinstall again, or I just run into these conflicts...

error: failed to commit transaction (conflicting files)
scenefx-0.1: /usr/include/scenefx/render/fx_renderer/fx_effect_framebuffers.h exists in filesystem (owned by scenefx)
scenefx-0.1: /usr/include/scenefx/render/fx_renderer/fx_renderer.h exists in filesystem (owned by scenefx)
scenefx-0.1: /usr/include/scenefx/render/pass.h exists in filesystem (owned by scenefx)
scenefx-0.1: /usr/include/scenefx/types/fx/blur_data.h exists in filesystem (owned by scenefx)
scenefx-0.1: /usr/include/scenefx/types/fx/shadow_data.h exists in filesystem (owned by scenefx)
scenefx-0.1: /usr/include/scenefx/types/wlr_scene.h exists in filesystem (owned by scenefx)
scenefx-0.1: /usr/lib/libscenefx.so exists in filesystem (owned by scenefx)
scenefx-0.1: /usr/lib/libscenefx.so.1 exists in filesystem (owned by scenefx)
scenefx-0.1: /usr/lib/pkgconfig/scenefx.pc exists in filesystem (owned by scenefx)

@LAURAilway
Copy link

LAURAilway commented Feb 19, 2025

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.

@WillPower3309
Copy link
Owner

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

@WillPower3309
Copy link
Owner

Hello, would anyone be able to confirm if the new AUR package update fixes this issue?

@martinstark
Copy link
Author

without having modified anything since I created this ticket, still cannot install due to the conflict with the original scenefx package

Image

@martinstark
Copy link
Author

martinstark commented Feb 21, 2025

I believe the scenefx-0.1 package needs to be marked as conflicts with scenefx-0.2, so that I get the option to switch it out during install?

edit,
would it not make sense to use the 0.1 release of the original scenefx package instead of publishing an entirely separate package for that version?

@johnny32
Copy link

It doesn't work for me yet. I'm getting this error during the install step of yay:

Image

Last message says "Install for the following packages failed. A manual intervention is required".

What I understand is swayfx pulls scenefx-0.1 as a dependency, but maybe looks like the error on my screenshot says scenefx (the newer, 0.2 version) dependency is not found. Maybe I'm wrong though.

@DeliciousHair
Copy link

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.

@martinstark
Copy link
Author

that uses pacman (not yay)

yay also uses pacman, and so does paru. yay and paru are convenience wrappers for pacman.

@coderj001
Copy link

It doesn't work for me yet. I'm getting this error during the install step of yay:

Image

Last message says "Install for the following packages failed. A manual intervention is required".

What I understand is swayfx pulls scenefx-0.1 as a dependency, but maybe looks like the error on my screenshot says scenefx (the newer, 0.2 version) dependency is not found. Maybe I'm wrong though.

Image

I also have the same issue, I tried to install scenefx-0.1 manually, but still it's not working.

@WillPower3309
Copy link
Owner

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

@LAURAilway
Copy link

LAURAilway commented Feb 21, 2025

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.

@DeliciousHair
Copy link

Thanks, I should have looked closer. However, I was simply trying to respond to the request to verify the fix worked is all, which I guess I got wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants