Package Details: java-service-wrapper 3.5.54-1

Git Clone URL: https://aur.archlinux.org/java-service-wrapper.git (read-only, click to copy)
Package Base: java-service-wrapper
Description: Enables a Java Application to be run as a Windows Service or Unix Daemon
Upstream URL: https://wrapper.tanukisoftware.com/doc/english/introduction.html
Licenses: GPL2, custom:tanuki-community
Submitter: None
Maintainer: erikol
Last Packager: skydrome
Votes: 143
Popularity: 0.000010
First Submitted: 2011-09-28 06:51 (UTC)
Last Updated: 2023-11-08 23:50 (UTC)

Dependencies (2)

Sources (1)

Pinned Comments

skydrome commented on 2020-02-06 04:41 (UTC) (edited on 2020-02-06 04:44 (UTC) by skydrome)

pacman.conf

[home_skydrome_Arch]
Server = https://download.opensuse.org/repositories/home:/skydrome/Arch/x86_64

Add key

wget https://download.opensuse.org/repositories/home:/skydrome/Arch/x86_64/home_skydrome_Arch.key
pacman-key --add home_skydrome_Arch.key
pacman-key --lsign-key 2e4b3a0b799d7113

Latest Comments

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

japodhi commented on 2023-09-28 03:16 (UTC)

I encountered a problem while trying to install i2p. Here's a snippet of the output from yay -S i2p:

==> Starting prepare()...
==> Sources are ready.
==> Making package: java-service-wrapper 3.5.51-1 (Thu 28 Sep 2023 05:58:14 AM EAT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: java-service-wrapper-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
i2p - exit status 8
java-service-wrapper - exit status 4

I tried drilling down to try and find the possible cause, but I was only moderately successful. Java is set to java-17-openjdk. I tried building the latest version 3.5.54, but I was met with a complaint about this setting javac.target.version=1.4 being set to an unsupported version.

ika commented on 2023-08-02 06:29 (UTC)

i dont know why line 32 is what it is but it seems to cause problems. removing source /etc/profile allows this pkgbuild to finish

Lynuxed commented on 2023-02-03 17:46 (UTC) (edited on 2023-02-03 17:58 (UTC) by Lynuxed)

New Arch Linux install, fully updated, using bash shell.

==>Starting build()...
/etc/profile.d/jre.sh: line 3: append_path: command not found
==> ERROR: A failure occurred in build().
    Aborting...

Deleting line 32, the package was able to finish building and install.

skydrome commented on 2023-01-28 00:09 (UTC)

append_path comes from sourcing /etc/profile, only reason your shell wouldn't do that is if it spawns non-interactive

Fijxu commented on 2023-01-27 23:58 (UTC)

/etc/profile.d/jre.sh: line 3: append_path: command not found

I got this error in my two machines using Arch Linux, fully updated, deleting the line 32 solves it and make it able to build and install it

mozlima commented on 2022-12-01 20:01 (UTC) (edited on 2022-12-02 19:13 (UTC) by mozlima)

     [exec] make: *** [Makefile-linux-x86-64.make:50: wrapperjni_unix.o] Error 1

BUILD FAILED
/home/user/.cache/yay/java-service-wrapper/src/wrapper_3.5.51_src/build.xml:771: exec returned: 2

Fixed by installing the JDK version to the same version of default JRE version in the system

miguelmsoler commented on 2022-05-09 17:50 (UTC)

The problem with keys was solved with:

sudo pacman -Sy && sudo pacman -S archlinuxcn-keyring

wget https://download.opensuse.org/repositories/home:/skydrome/Arch/x86_64/home_skydrome_Arch.key
pacman-key --add home_skydrome_Arch.key
pacman-key --lsign-key 2e4b3a0b799d7113

miguelmsoler commented on 2022-04-20 21:53 (UTC)

I just run this and get the same. Is the url ok?

****@maquinola:~|⇒  wget https://download.opensuse.org/repositories/home:/skydrome/Arch/x86_64/home_skydrome_Arch.key
--2022-04-20 18:50:21--  https://download.opensuse.org/repositories/home:/skydrome/Arch/x86_64/home_skydrome_Arch.key
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving download.opensuse.org (download.opensuse.org)... 195.135.221.134, 2001:67c:2178:8::13
Connecting to download.opensuse.org (download.opensuse.org)|195.135.221.134|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1101 (1.1K)
Saving to: ‘home_skydrome_Arch.key’

home_skydrome_Arch.key                               100%[=====================================================================================================================>]   1.08K  --.-KB/s    in 0s

2022-04-20 18:50:23 (15.5 MB/s) - ‘home_skydrome_Arch.key’ saved [1101/1101]

****@maquinola:~|⇒  gpg --import home_skydrome_Arch.key                                                              
gpg: key 2E4B3A0B799D7113: 1 signature not checked due to a missing key
gpg: key 2E4B3A0B799D7113: "home:skydrome OBS Project <home:skydrome@build.opensuse.org>" 1 new signature
gpg: Total number processed: 1
gpg:         new signatures: 1
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   2  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:   2  signed:   0  trust: 2-, 0q, 0n, 0m, 0f, 0u
****@maquinola:~|⇒  sudo pacman-key --list-keys skydrome                                                             
pub   rsa2048 2020-02-06 [SC] [expired: 2022-04-16]
      30CB2356946B338AA9DA2C782E4B3A0B799D7113
uid           [ expired] home:skydrome OBS Project <home:skydrome@build.opensuse.org>

skydrome commented on 2022-04-20 21:11 (UTC)

try, gpg --import home_skydrome_Arch.key should show [expires: 2024-06-27]

miguelmsoler commented on 2022-04-20 15:20 (UTC)

@skydrome I refreshed keys and after that I got this when y run pacman-keys --list-keys skydrome

pub   rsa2048 2020-02-06 [SC] [expired: 2022-04-16]
      30CB2356946B338AA9DA2C782E4B3A0B799D7113
uid           [ expired] home:skydrome OBS Project <home:skydrome@build.opensuse.org>

This key is expired.

I even tried to reset keys and populate everything again removing /etc/pacman.d/gnupg and running pacman-key --init and pacman-key --populate archlinux but the problem persists.