Hello,
Le 05/06/2022 à 18:27, zzz a écrit :
This is a dependency of the i2p project that I work on.
If there's any maintainer available to bring it up-to-date,
I'd really appreciate it.
I gave it a try tonight, packaging version 3.5.50. I guess it is OK, the main thing is probably that the src/bin/sh.script.in has been renamed to
src/bin/App.sh.in, and a file src/bin/App.shconf.in has been added alongside. I felt like I could ignore it, do you have any opinion about it?
Hello,
Le 05/06/2022 à 18:27, zzz a écrit :
This is a dependency of the i2p project that I work on.
If there's any maintainer available to bring it up-to-date,
I'd really appreciate it.
I gave it a try tonight, packaging version 3.5.50. I guess it is OK, the
main thing is probably that the src/bin/sh.script.in has been renamed to src/bin/App.sh.in, and a file src/bin/App.shconf.in has been added
alongside. I felt like I could ignore it, do you have any opinion about it?
My packaging allows mpj and i2p to build successfully, so I guess I will upload the package soon.
You can see my packaging work at [0].
Le 2022-06-05 18:27, zzz a écrit :
This is a dependency of the i2p project that I work on.
If there's any maintainer available to bring it up-to-date,
I'd really appreciate it.
thanks!
I wonder if service wrapper is really necessary for i2p. As I understand it's mostly used to turn a Java application into a service on Windows, handle
the logs and restart the application if it crashes. But Debian has its own tools to manage services. The same reasonning applies to
libcommons-daemon-java used by activemq.
Emmanuel Bourg
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 42:11:48 |
Calls: | 6,648 |
Files: | 12,193 |
Messages: | 5,329,573 |