Package Details: tuxguitar 1.6.3-1

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: 62
Popularity: 2.21
First Submitted: 2018-01-05 17:06 (UTC)
Last Updated: 2024-06-13 22:59 (UTC)

Dependencies (19)

Required by (1)

Sources (3)

Pinned Comments

Visne commented on 2024-04-13 10:54 (UTC) (edited on 2024-06-11 21:53 (UTC) by Visne)

I've adopted the package and updated to the latest version. 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. It should now support ARM64 (please let me know if it works for you).

Let me know if you run into any issues.

Latest Comments

1 2 3 4 5 6 .. 11 Next › Last »

Visne commented on 2024-06-13 23:00 (UTC) (edited on 2024-06-13 23:00 (UTC) by Visne)

@Toufik That's great, enjoy.

@actionless You're right, that makes more sense. Updated now.

Toufik commented on 2024-06-12 07:47 (UTC)

Good job Visne, it works out of the box now. Thanks a lot.

actionless commented on 2024-06-12 04:46 (UTC) (edited on 2024-06-12 04:47 (UTC) by actionless)

i think swt should be added to the source array

Visne commented on 2024-06-11 21:55 (UTC)

Version 1.6.3 was released 5 days ago, so I've updated the PKGBUILD to that now. I hope that fixes the issue for both of you too.

Also ARM64 should be supported now, but I don't have a device to test it on. Please let me know if it works on ARM64.

Toufik commented on 2024-06-11 16:36 (UTC)

Exactly same error as Darkmind and no idea how to solve that. But it doesn't look like a java error does it ?

[INFO] Executing tasks

compile-native:
[exec] gcc -I/home/toff/.cache/yay/tuxguitar/src/tuxguitar-1.6.2/desktop/build-scripts/native-modules/tuxguitar-fluidsynth-linux-x86_64/../common-include -fPIC -c -o org_herac_tuxguitar_player_impl_midiport_fluidsynth_MidiSynth.o org_herac_tuxguitar_player_impl_morg_herac_tuxguitar_player_impl_midiport_fluidsynth_MidiSynth.c: Dans la fonction « Java_org_herac_tuxguitar_player_impl_midipidiport_fluidsynth_MidiSynth.c
[exec] ort_fluidsynth_MidiSynth_getPropertyOptions »:
[exec] org_herac_tuxguitar_player_impl_midiport_fluidsynth_MidiSynth.c:396:85: erreur: passage de l'argument 4 de « fluid_settings_foreach_option» depuis un type pointeur incompatible [-Wincompatible-pointer-types]
[exec]   396 |                 fluid_settings_foreach_option(handle->settings, (char *)jkey, data, fluid_settings_foreach_option_callback );
[exec]       |                                                                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[exec]       |                                                                                     |
[exec]       |                                                                                     void (*)(void *, char *, char *)
[exec] Dans le fichier inclus depuis /usr/include/fluidsynth.h:99,
[exec]                  depuis org_herac_tuxguitar_player_impl_midiport_fluidsynth_MidiSynth.c:4:
[exec] /usr/include/fluidsynth/settings.h:169:68: note: « fluid_settings_foreach_option_t » {alias « void (*)(void *, const char *, const char *)»} attendu mais l'argument est de type « void (*)(void *, char *, char *) »
[exec]   169 |                                    fluid_settings_foreach_option_t func);
[exec]       |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
[exec] make: *** [GNUmakefile:14: org_herac_tuxguitar_player_impl_midiport_fluidsynth_MidiSynth.o] Error 1
[INFO] ------------------------------------------------------------------------

[snip]
[INFO] tuxguitar-fluidsynth-linux-x86_64 SNAPSHOT ......... FAILURE [  0.908 s]
[INFO] tuxguitar-synth-lv2 SNAPSHOT ....................... SKIPPED
[INFO] tuxguitar-synth-lv2-linux-x86_64 SNAPSHOT .......... SKIPPED
[INFO] tuxguitar-linux-swt-x86_64 SNAPSHOT ................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  21.939 s
[INFO] Finished at: 2024-06-11T10:20:02+02:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (compile-native) on project tuxguitar-fluidsynth-linux-x86_64: An Ant BuildException has occured: exec returned: 2
[ERROR] around Ant part ...<exec failonerror="true" dir="../../..//TuxGuitar-fluidsynth/jni/" executable="make">... @ 4:88 in /home/toff/.cache/yay/tuxguitar/src/tuxguitar-1.6.2/desktop/build-scripts/native-modules/tuxguitar-fluidsynth-linux-x86_64/target/antrun/build-compile-native.xml
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (compile-native) on project tuxguitar-fluidsynth-linux-x86_64: An Ant BuildException has occured: exec returned: 2
around Ant part ...<exec failonerror="true" dir="../../..//TuxGuitar-fluidsynth/jni/" executable="make">... @ 4:88 in /home/toff/.cache/yay/tuxguitar/src/tuxguitar-1.6.2/desktop/build-scripts/native-modules/tuxguitar-fluidsynth-linux-x86_64/target/antrun/build-compile-native.xml
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:333)

Visne commented on 2024-05-26 23:34 (UTC)

The goal it's trying to execute is here, I'm not sure how to recover the actual commands it's trying to run though. Maybe the that command/the output of that command is already in the error message?

Darkmind2007 commented on 2024-05-26 23:23 (UTC) (edited on 2024-05-26 23:24 (UTC) by Darkmind2007)

When I try to install the latest update I get the following error. Has anyone faced it and know what could be the root cause?

Is there a specific Java version that needs to be used for compilation?

[INFO] tuxguitar-fluidsynth-linux-x86_64 SNAPSHOT ......... FAILURE [  0.857 s]
[INFO] tuxguitar-synth-lv2 SNAPSHOT ....................... SKIPPED
[INFO] tuxguitar-synth-lv2-linux-x86_64 SNAPSHOT .......... SKIPPED
[INFO] tuxguitar-linux-swt-x86_64 SNAPSHOT ................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  16.131 s
[INFO] Finished at: 2024-05-27T00:18:07+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (compile-native) on project tuxguitar-fluidsynth-linux-x86_64: An Ant BuildException has occured: exec returned: 2
[ERROR] around Ant part ...<exec failonerror="true" dir="../../..//TuxGuitar-fluidsynth/jni/" executable="make">... @ 4:88 in /home/darkmind/.cache/pacaur/tuxguitar/src/tuxguitar-1.6.2/desktop/build-scripts/native-modules/tuxguitar-fluidsynth-linux-x86_64/target/antrun/build-compile-native.xml
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (compile-native) on project tuxguitar-fluidsynth-linux-x86_64: An Ant BuildException has occured: exec returned: 2
around Ant part ...<exec failonerror="true" dir="../../..//TuxGuitar-fluidsynth/jni/" executable="make">... @ 4:88 in /home/darkmind/.cache/pacaur/tuxguitar/src/tuxguitar-1.6.2/desktop/build-scripts/native-modules/tuxguitar-fluidsynth-linux-x86_64/target/antrun/build-compile-native.xml

coderkun commented on 2024-04-14 08:22 (UTC) (edited on 2024-04-14 08:23 (UTC) by coderkun)

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!

coderkun commented on 2024-04-14 08:13 (UTC) (edited on 2024-04-14 08:14 (UTC) by coderkun)

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.

Visne commented on 2024-04-13 18:39 (UTC)

Should be fixed now, can you retry?