Package Details: muwire 0.8.13-1

Git Clone URL: (read-only, click to copy)
Package Base: muwire
Description: An I2P file sharing program
Upstream URL:
Licenses: GPL3
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 9
Popularity: 0.000000
First Submitted: 2019-10-03 14:23 (UTC)
Last Updated: 2022-08-23 21:20 (UTC)

Dependencies (6)

Required by (0)

Sources (3)

Pinned Comments

dbermond commented on 2020-11-04 18:52 (UTC)

@txtsd AUR helpers are not supported. Manage the needed pgp key[1][2][3] and use makepkg[4]. The Arch Wiki is your friend.





Latest Comments

1 2 3 4 Next › Last »

Tio commented on 2022-01-28 10:23 (UTC)

Ah I apologize. I should have looked there. Thanks!

dbermond commented on 2022-01-28 00:50 (UTC)

@Tio See my comment from 2020-11-04 (I have pinned it now). You need to manage the needed pgp key. See the Arch Wiki (specially regarding searching and receiving keys).

Tio commented on 2022-01-27 22:57 (UTC)

I get this error:

==> Verifying source file signatures with gpg...
    muwire git repo ... FAILED (unknown public key A72832072D525E41)
==> ERROR: One or more PGP signatures could not be verified!
Failed to build muwire

TheEndri99 commented on 2021-11-07 19:57 (UTC)

@dbermond Thank you for your quick answer. I was able to build it with java 11 as you wrote!

dbermond commented on 2021-11-07 16:08 (UTC)

@TheEndri99 You need java11 to build and use this package. The current upstream version (0.8.10) does not work with java17. Don't forget to configure java11 as the default JVM with archlinux-java.

TheEndri99 commented on 2021-11-07 15:54 (UTC)

I am not able to build this package. It fails at:

"Task :core:compileGroovy startup failed: General error during instruction selection: PermittedSubclasses requires ASM9".

I have not installed i2p, since it is not required and I have openjdk 17 installed. Do I need to install something else?

dbermond commented on 2021-09-18 12:44 (UTC)

@yochananmarqos No, it does not work. Taking the example of 0.8.8 (which is the one that has java16 restriction to build), specifying 'java-environment>=11' 'java-environment<16' at makedepends installs both java11 and java16 on the chroot, being java16 the default one, causing the build to fail. And specifying only 'java-environment>=11' at makedepends installs java16, which also makes the build to fail.

yochananmarqos commented on 2021-09-17 22:39 (UTC)

@dbermond: Adding java-environment>=11 restricts the JDK version for building, that's all. I'm not sure why were not on the same page here.

dbermond commented on 2021-09-17 22:36 (UTC)

@yochananmarqos I see no contradiction. You are saying that we need to add java-environment here at makedepends because it's needed by gradle, which in turn is a direct makedepend for this package. So you add to makedepends everything that other makedepends also depends on? This is not needed.

This package does not require the environment and it does not need to be listed here. This is simple like that. Please refer to the Arch Linux Java packaging guidelines as I already said. It's very clear in saying what should be the dependencies for java packages.

yochananmarqos commented on 2021-09-17 22:11 (UTC)


java-environment is not required here

java-environment is required by gradle

You just contradicted yourself.

The JDK used to build and the JRE used at runtime should match.

I see your point about which JDK / JRE version to use in a chroot. Only specifying >=11 should work for now.