Re: Installing runnable Eclipse from Debian packages

> Gervase : > Currently, I have access to the packages 'eclipse'/'eclipse-platform' on > Ubuntu. Having either installed then allows additional packages/plug- > ins to be installed for the various computer languages (e.g. JDT, CDT, > pydev). FWIW I've been running eclipse on debian desktops

"error: Unmet build dependencies: maven default-jdk (>= 2:1.8)" when running dpkg-buildpackage

0-0 dpkg-buildpackage: info: source distribution UNRELEASED dpkg-buildpackage: info: source changed by Steinar Bang dpkg-buildpackage: info: host architecture amd64 dpkg-source --before-build . dpkg-checkbuilddeps: error: Unmet build dependencies: maven default-jdk (>= 2:1.8) dpkg-buildpac

Re: Bug#896708: ITP: maven-cache-cleanup -- Utility to purge timestamped snapshots from Maven repositories

> Emmanuel Bourg : > Package: wnpp > Severity: wishlist > Owner: Emmanuel Bourg > * Package name: maven-cache-cleanup > Version : 1.0.4 > Upstream Author : Yuri Nadestin > * URL : https://github.com/nadestin/tools > * License

Re: Summary: the state of the karaf debian package

I have posted an update to the RFP bug describing the latest fixes/improvements made to the karaf debian package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881297#40 The following fixes/improvements have been made: 1. I've run lintian with the following argument and fixed all of the

Re: Summary: the state of the karaf debian package

>>>>> Steinar Bang <s...@dod.no>: > I believe the following steps are needed to make this an official > package: > 1. Replace the remaining non-karaf boot jars with debian packages, > these packages are: > a. apache felix framework 5.6.10

Re: Summary: the state of the karaf debian package

>>>>> Thorsten Glaser <t.gla...@tarent.de>: > Hi Steinar, > congratulations on getting this far, that’s a nontrivial > amount of work! Thanks! :-) > On Thu, 1 Feb 2018, Steinar Bang wrote: >> 4. lintian no longer gives any warnings on the package (I

Summary: the state of the karaf debian package

My karaf debian package[1] is now in a state where it does what I need for my own use. I'm serving it from my own unofficial APT repository (which I will discontinue if the RFP[2] results in an official karaf package). I don't plan to do any more work on this packaging, except what is needed to

Re: Is it possible to run maven from a postinst mainscript?

> Emmanuel Bourg : >> 1. Some of the dependencies aren't available as debian packages > They'll have to be packaged. What libraries are missing? The non-karaf packages needed for boot, are: mvn:org.apache.felix/org.apache.felix.metatype/1.1.6

Is it possible to run maven from a postinst mainscript?

I am working on a debian package for apache karaf: https://github.com/steinarb/karaf-debian Karaf has an area, called the "system" default repository, containing jar files structured like a maven repository. This repository contains all of the karaf modules, some maven dependencies needed for

Re: Do transitive dependencies need to be specified in the control file?

>>>>> Steinar Bang <s...@dod.no>: > I thought the unmet dependency was libjna-jni that was added by > 'apt --fix-broken install'? And that this was a transitive depdenency? I removed the versions from libjna-java and libjna-platform-java in Depends in the cont

Re: Do transitive dependencies need to be specified in the control file?

> Markus Koschany : >> I tried adding two dependencies, libjna-java and libjna-platform-java to the >> debian/control file: >> Depends: adduser, default-jre (>=1.8), libosgi-core-java (>=6), libjna-java >> (>=4.2.2), libjna-platform-java (>=4.2.2) >

Re: How should the systemd setup in a postinst script look?

>>>>> Emmanuel Bourg <ebo...@apache.org>: > Le 26/01/2018 à 19:26, Steinar Bang a écrit : >> W: karaf: codeless-jar >> usr/share/karaf/system/org/apache/aries/blueprint/org.apache.aries.blueprint.core.compatibility/1.0.0/org.apache.aries.blueprint.core.compa

Do transitive dependencies need to be specified in the control file?

Working on my karaf debian package https://github.com/steinarb/karaf-debian I tried adding two dependencies, libjna-java and libjna-platform-java to the debian/control file: Depends: adduser, default-jre (>=1.8), libosgi-core-java (>=6), libjna-java (>=4.2.2), libjna-platform-java (>=4.2.2)

Re: How should the systemd setup in a postinst script look?

>>>>> Steinar Bang <s...@dod.no>: > However, lintian aren't happy with the results: > sb@lorenzo:~/git/karaf-debian$ lintian ~/git/karaf_4.1.4-8~9.30_all.deb > W: karaf: init.d-script-not-marked-as-conffile etc/init.d/karaf > E: karaf: init.d-script-not-inc

Re: How should the systemd setup in a postinst script look?

>>>>> Steinar Bang <s...@dod.no>: > 4. Changed the "%:" rule of debian/rules to be > dh $@ --with systemd I figured out the problem, I had this %: dh $@ --with-systemd instead of this: %: dh $@ --with systemd Now I again get a .

Re: How should the systemd setup in a postinst script look?

> Eugene Zhukov : > The service will be enabled and started automatically upon package > install, you don't need to do that. > Just put your .service file into debian/ folder and the > rest will be handled by Debian tools. > The line in debian/rules quoted below is also

How should the systemd setup in a postinst script look?

I am trying to get rid of the lintian messages of my apache karaf debian package: https://github.com/steinarb/karaf-debian One of the warnings still present, is: W: karaf: maintainer-script-calls-systemctl postinst:30 The relevant part of the script, is: case "$1" in configure)

Re: dpkg-buildpackage mvn command tries to use /root/.m2/repository

> Markus Koschany : >> until mh_make eventually failed with the following error message: >> Checking the parent dependency in the sub project itests/pom.xml >> Analysing manual/pom.xml... > I suggest to ignore this sub project for now (sounds like it is only > needed for

Re: dpkg-buildpackage mvn command tries to use /root/.m2/repository

>>>>> Steinar Bang <s...@dod.no>: > Outline of the plan > 1. Download the sources and build them with maven (this is where I'm now) > 2. Create the directories that will receive the built karaf stuff: > mkdir -p /etc/karaf > mkdir -p /usr/share/

Re: dpkg-buildpackage mvn command tries to use /root/.m2/repository

> Emmanuel Bourg : > Ok, I suggest reading the excellent article from Markus about mh_make, > the Vincent's tutorial is a good introduction but it isn't really suited > to Java based projects. >

Re: dpkg-buildpackage mvn command tries to use /root/.m2/repository

>>>>> Steinar Bang <s...@dod.no>: > I can try running mh_make, but as this is a multi-module project with > lots of non-standard maven stuff, most of the examples I've been able to > google up hasn't. I tried running mh_make, told it to - Use "karaf" f

Re: dpkg-buildpackage mvn command tries to use /root/.m2/repository

> Emmanuel Bourg : > The rules file disables most of the targets, that looks wrong. Did you > generate the package with mh_make from maven-debian-helper? No, I startet with creating files as in this article

dpkg-buildpackage mvn command tries to use /root/.m2/repository

When I run "dpkg-buildpackage -us -uc -b" on a packaging area with this control file https://gist.github.com/steinarb/5b0b6d771e2fae3873abac15c21a4f82 it fails with: (cd unpacked-src; mvn clean install -DskipTests=true ) [ERROR] Could not create local repository at /root/.m2/repository -> [Help

Tool for automatically resolving maven depdencies to debian dependencies?

Is there a tool that can automatically resolve maven dependencies to the closest matching debian package dependencies? (The tool doesn't necessarily have to go all the way. Something that justs lists the dependencies in a form that can be massaged in a text editor would still be useful (but of

Re: Is it possible to have multiple versions of a java-lib installed?

>>>>> Emmanuel Bourg <ebo...@apache.org>: > Le 17/01/2018 à 23:32, Steinar Bang a écrit : >> Is pulling the jars in from maven central from maven depdencies >> acceptable? Or do they need to be acually built by the packaging >> project? > It's ok at

Re: Is it possible to have multiple versions of a java-lib installed?

>>>>> Emmanuel Bourg <ebo...@apache.org>: > Le 17/01/2018 à 22:44, Steinar Bang a écrit : >> Would be legal for a karaf debian package to bundle its own version of >> these jars? > It's fine as long as they are built from source (i.e. no prebuilt jar >

Re: Is it possible to have multiple versions of a java-lib installed?

One property of karaf: it can load its dependencies using maven. Ie. it will download its dependencies to ~/.m2/repository and use it from there. It doesn't have to be provided by other debian packages. The question is: how much must be in place for karaf to boot far enough to start loading

Re: Is it possible to have multiple versions of a java-lib installed?

> Thorsten Glaser : >> Do you have a compatibility issue with libjna-java? > … those. I used it as an example since it's part of the boot set of apache karaf, which in karaf 4.1.4, is: -rw-r--r-- 1 sb sb 1440500 Dec 15 20:14 jna-4.5.0.jar -rw-r--r-- 1 sb sb

Is it possible to have multiple versions of a java-lib installed?

Is it possible to have multiple versions of a java library, like eg. https://packages.debian.org/stretch/libjna-java installed simultanously? I guess the non-versioned files would collide...? (ie. the unversioned jar in /usr/share/java/ and the maven-repo with version "debian" in

Re: apache-karaf in Debian

>>>>> Steinar Bang <s...@dod.no>: [snip!] > Karaf has a concept of "local maven repository" that would fit in nicely > with debian's maven layout under /usr/share/maven-repo/ > Modifying the setting org.ops4j.pax.url.mvn.localRepository in >

Re: apache-karaf in Debian

Picking up on an old thread. It would be very nice to get a native debian package of karaf, so I've opened this RFP: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881297 Karaf is a small OSGi container/applcation server, that has an SSH daemon, and is provisioned using maven. Basically,

Jaxe in debian?

http://jaxe.sourceforge.net/ Are anyone planning to package this GPL'd XML Editor? Thanx! - Steinar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Ajp13 connector doesn't start listening on port 8009

Platform: Intel PIII, debian testing/unstable (sarge) Blackdown JDK 1.3.1 (j2sdk 1.3.1.0b-2), tomcat4 4.1.16-1, apache 1.3.26-1.1, apache-ssl 1.3.26+1.48-2 My problem is that when I do /etc/init.d/tomcat4 start there is nothing listening on port 8009. Or

Ajp13 connector doesn't start listening on port 8009

Platform: Intel PIII, debian testing/unstable (sarge) Blackdown JDK 1.3.1 (j2sdk 1.3.1.0b-2), tomcat4 4.1.16-1, apache 1.3.26-1.1, apache-ssl 1.3.26+1.48-2 My problem is that when I do /etc/init.d/tomcat4 start there is nothing listening on port 8009. Or

Something pushed out my Blackdown j2re1.3

I tried apt-get update apt-get dist-upgrade on my Intel PIII testing system yesterday, and something seems to have pushed out Blackdown j2re1.3, and tries to install jre1.1 instead. A strange thing, is that it tries installing jre1.1 from the Blackdown server where it doesn't find

Re: Something pushed out my Blackdown j2re1.3

Steinar Bang [EMAIL PROTECTED] wrote: When looking at the Blackdown site with ncftp, I find the directories expected by apt, but the directories are empty, ie. no .deb files. klaus sperner [EMAIL PROTECTED]: my /etc/apt/sources.list says: #java 1.3.1 for debian from blackdown.org; we

Something pushed out my Blackdown j2re1.3

I tried apt-get update apt-get dist-upgrade on my Intel PIII testing system yesterday, and something seems to have pushed out Blackdown j2re1.3, and tries to install jre1.1 instead. A strange thing, is that it tries installing jre1.1 from the Blackdown server where it doesn't find

Re: Something pushed out my Blackdown j2re1.3

Arnaud Vandyck [EMAIL PROTECTED]: Steinar Bang [EMAIL PROTECTED] wrote: I tried apt-get update apt-get dist-upgrade on my Intel PIII testing system yesterday, and something seems to have pushed out Blackdown j2re1.3, and tries to install jre1.1 instead. Replace this line

Re: Something pushed out my Blackdown j2re1.3

Steinar Bang [EMAIL PROTECTED] wrote: When looking at the Blackdown site with ncftp, I find the directories expected by apt, but the directories are empty, ie. no .deb files. klaus sperner [EMAIL PROTECTED]: my /etc/apt/sources.list says: #java 1.3.1 for debian from blackdown.org; we