Arch Linux User Repository

Hi,

a little fun fact. If you reinstall mediathekview-xdg while an instance of mediathekview is running then the junit SingleInstanceTest fail.

So stop the running instance first. ;)

regards j0inty

INFO] Running mediathek.tool.MVInfoFileTest [ERROR] OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended WARNING: A Java agent has been loaded dynamically (/home/j0inty/.m2/repository/net/bytebuddy/byte-buddy-agent/1.14.15/byte-buddy-agent-1.14.15.jar) WARNING: If a serviceability tool is in use, please run with -XX:+EnableDynamicAgentLoading to hide this warning WARNING: If a serviceability tool is not in use, please run with -Djdk.instrument.traceUsage for more information WARNING: Dynamic loading of agents will be disallowed by default in a future release [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.471 s - in mediathek.tool.MVInfoFileTest [INFO] Running mSearch.daten.DatenFilmTest [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.035 s - in mSearch.daten.DatenFilmTest [INFO] [INFO] Results: [INFO] [ERROR] Failures: [ERROR] SingleInstanceTest.instance1_not_active:12 expected: <false> but was: <true> [ERROR] SingleInstanceTest.instance2_activity_test:20 expected: <false> but was: <true> [INFO] [ERROR] Tests run: 93, Failures: 2, Errors: 0, Skipped: 0 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 30.967 s [INFO] Finished at: 2025-03-20T19:21:17+01:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) on project MediathekView: There are test failures. [ERROR] [ERROR] Please refer to /home/j0inty/.cache/yay/mediathekview-xdg/src/MediathekView-14.2.0/target/surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException ==> FEHLER: Ein Fehler geschah in build(). Breche ab... -> Fehler beim Erstellen: mediathekview-xdg-exit status 4 -> Die folgenden Pakete konnten nicht installiert werden. Ein manueller Eingriff ist erforderlich: mediathekview-xdg - exit status 4

@martin-de indeed, building in a container worked with Java 22. I synced some changes from the community package. I'll have a look into whether the version pinning can be avoided.

You should build the package by the recommended way in a clean chroot, then you can also build it for the current Java version 22.

The Java version should be passed in a variable and not a fixed value (as David Runge did with the _java_version variable). This makes changes easier and is less prone to errors.

The question is whether a specific version needs to be specified at all, because the developer specifies Java-20 as the minimum requirement for version 14.0.0, and that is always guaranteed in a current Arch environment.

@dreieck sadly I coudn't get the package to build with openjdk 22.

You could try to do a partial upgrade (yes, I know: bad) of the package jdk21-openjdk:

pacman -Sy jdk21-openjdk

and then proceed with the upgrade or uninstall mediathekview-xdg, do the upgrade and the re-install.

Up to date version of java in Arch Linux now is version 22.

Dependency java-runtime-openjdk=21 causes conflicts/ breakage of input, consider if you can update it to newer version (maybe java-runtime-openjdk>=21?)

Regards!

Thank you for your response. I tried it again with the additional dependency, and the package could now be built in a clean chroot. namcap still gives a warning

 mediathekview-xdg W: Dependency included, but may not be needed ('xdg-user-dirs')

out, so the dependency is probably only needed to build the package.

However... if you start "mediathek" from the terminal, you see hundreds of exceptions and it doesn't work properly either. For example, the applications hang when trying to open the filter settings. There are again a lot of exceptions and the dialog window appears small and without content in the upper left corner of the screen. You can move it and enlarge it, but in result the application hangs now.

I'm not sure if this is a program problem that can only be solved upstream, or a bug in building the package; In any case, the application cannot be used. The warning about the missing profiles still appears, but I'm not sure what the implications are. For the moment, I am back on version 13.9.1

@martin-de Cause was a missing dependency. Please try again!

@martin-de I can't reproduce the issue. I get the warnings as well. But the package build works for me.

edit: I can reproduce the issue now in a containerized environment

Building process failed:

 [WARNING] The requested profile "linux" could not be activated because it does not exist.
 [WARNING] The requested profile "install4j-linux" could not be activated because it does not exist.
 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) on project MediathekView: There are test failures.

Aborting and no package created.