Actually, it does work when I add the package to a repository. Seems that only local installation (pacman -U
) does not honor the replaces
declaration. But that should not be your concern.
So all good now. Thanks!
Git Clone URL: | https://aur.archlinux.org/tuxguitar.git (read-only, click to copy) |
---|---|
Package Base: | tuxguitar |
Description: | A multitrack guitar tablature editor and player |
Upstream URL: | https://www.tuxguitar.app/ |
Licenses: | LGPL-3.0-or-later |
Replaces: | tuxguitar-common, tuxguitar-gtk2 |
Submitter: | Barthalion |
Maintainer: | Visne |
Last Packager: | Visne |
Votes: | 61 |
Popularity: | 2.61 |
First Submitted: | 2018-01-05 17:06 (UTC) |
Last Updated: | 2024-04-15 21:40 (UTC) |
Actually, it does work when I add the package to a repository. Seems that only local installation (pacman -U
) does not honor the replaces
declaration. But that should not be your concern.
So all good now. Thanks!
I doesn’t to the trick for me. Pacman still not handles that nicely but errors out:
# pacman -U tuxguitar-1.6.2-3-x86_64.pkg.tar.zst
loading packages...
resolving dependencies...
looking for conflicting packages...
Packages (1) tuxguitar-1.6.2-3
Total Installed Size: 86.54 MiB
Net Upgrade Size: 86.54 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [#############################################################################] 100%
(1/1) checking package integrity [#############################################################################] 100%
(1/1) loading package files [#############################################################################] 100%
(1/1) checking for file conflicts [#############################################################################] 100%
error: failed to commit transaction (conflicting files)
tuxguitar: /usr/share/applications/tuxguitar.desktop exists in filesystem (owned by tuxguitar-common)
tuxguitar: /usr/share/mime/packages/tuxguitar.xml exists in filesystem (owned by tuxguitar-common)
Errors occurred, no packages were upgraded.
If I read the description of replaces in the wiki correctly, conflicts should be used:
If providing an alternate version of an already existing package or uploading to the AUR, use the conflicts and provides arrays, which are only evaluated when actually installing the conflicting package.
Or maybe use both? Thanks a again for maintaining this package.
Should be fixed now, can you retry?
Ah, I think replaces
would be appropriate here. I'll add it in a sec.
Thanks for taking over and updating the package.
When I try to update to the new package, I get the following error:
error: failed to commit transaction (conflicting files)
tuxguitar: /usr/share/applications/tuxguitar.desktop exists in filesystem (owned by tuxguitar-common)
tuxguitar: /usr/share/mime/packages/tuxguitar.xml exists in filesystem (owned by tuxguitar-common)
Errors occurred, no packages were upgraded.
Would it make sense to declare “tuxguitar-common” and “tuxguitar-gtk” as conflics or as provided? Of course I can uninstall the old package(s) manually but it would be nice if that would be handled by pacman automatically.
I've adopted the package and updated to 1.6.2. Sadly this means that GTK2 support is dropped (SWT dropped support back in 2018...). I'm not sure if anyone was using this on Arch Linux ARM, but temporarily support for that is also dropped. They did some work on that upstream though but it is not part of 1.6.2 yet, so hopefully it can be supported after the next release.
Let me know if you run into any issues.
Until everything is sorted here, I made a temporary binary package of a helge17 fork: https://aur.archlinux.org/packages/tuxguitar-bin You can test it (I personally found version 1.6.1 quite stable and usable) without uninstalling this package. More details in the pinned comment.
ping @buzo
per @rasmuoy this project has indeed migrated to github https://github.com/helge17/tuxguitar
This project seems to have been forked and moved to github, https://sourceforge.net/p/tuxguitar/discussion/522984/thread/0a8c900ddd/?limit=25#e036 should this be updated?
They have released version 1.6
Pinned Comments
Visne commented on 2024-04-13 10:54 (UTC)
I've adopted the package and updated to 1.6.2. Sadly this means that GTK2 support is dropped (SWT dropped support back in 2018...). I'm not sure if anyone was using this on Arch Linux ARM, but temporarily support for that is also dropped. They did some work on that upstream though but it is not part of 1.6.2 yet, so hopefully it can be supported after the next release.
Let me know if you run into any issues.