Re: Help needed to upgrade cdk
Hi, On 2019-11-19 19:40, Andreas Tille wrote: > I've sat together with Egon Willighagen who is member of CDK upstream > team to update the cdk package[1]. So far the switch from ant to maven > seems to have basically succeeded. However, for some reason it does not > build modules in the correct sequence and thus we are running into: [...] The build failure is indeed caused by inability to establish the correct ordering of artifacts in Debian build (not sure why this happens). I usually solve such problems manually. Ignoring cdk-test gets the build process a little further, but there are still dependencies to disentangle. I will give it a look. Best wishes, Andrius
Re: jax-maven-plugin_0.1.8-1~exp2 has rejected
Am 19.11.19 um 22:18 schrieb Mechtilde Stehmann: [...] > I already pushed my work without repacking to salsa. I think I should > renew it, but I can't remove the old wrong one. You don't need to remove the old files. With git-buildpackage you can do: gbp clone https://salsa.debian.org/java-team/jax-maven-plugin.git cd jax-maven-plugin gbp import-dsc ../jax-maven-plugin_0.1.8+dfsg-1.dsc signature.asc Description: OpenPGP digital signature
Re: jax-maven-plugin_0.1.8-1~exp2 has rejected
Am 19.11.19 um 20:31 schrieb Markus Koschany: > Hello, > > Am 19.11.19 um 09:23 schrieb Mechtilde Stehmann: >> Hello to the list, >> >> to fullfill the policy I will repack the orig.tar.gz of the package above. >> >> How ist the best way to do so? >> >> Should I do a new start to prepare the new package >> jax-maven-plugin_0.1.8+dfsg-1~exp1? > > I believe the canonical way of repacking upstream tarballs is to add a > Files-Excluded paragraph to debian/copyright and then you can use uscan > to repack the tarball. > > https://wiki.debian.org/UscanEnhancements > > If you have to repack the tarball for DFSG reasons then 0.1.8+dfsg-1 > should be fine, in case you want to upload to unstable. If you really > wish to upload to experimental then 0.1.8+dfsg-1~exp1 is also ok. > >> How can I work on at salsa.debian.org/java-team/jax.maven-plugin? > > Just push the repacked tarball to the Git repository? I already pushed my work without repacking to salsa. I think I should renew it, but I can't remove the old wrong one. Kind regards -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature
Re: Help needed to upgrade cdk
Am 19.11.19 um 18:40 schrieb Andreas Tille: > Hi, > > I've sat together with Egon Willighagen who is member of CDK upstream > team to update the cdk package[1]. So far the switch from ant to maven > seems to have basically succeeded. However, for some reason it does not > build modules in the correct sequence and thus we are running into: > > > [INFO] cdk SUCCESS [ 0.033 > s] > [INFO] cdk-base ... SUCCESS [ 0.003 > s] > [INFO] cdk-interfaces . SUCCESS [ 1.894 > s] > [INFO] cdk-core ... SUCCESS [ 2.407 > s] > [INFO] cdk-standard ... SUCCESS [ 1.406 > s] > [INFO] cdk-atomtype ... SUCCESS [ 0.209 > s] > [INFO] cdk-valencycheck ... SUCCESS [ 0.240 > s] > [INFO] cdk-misc ... SUCCESS [ 0.007 > s] > [INFO] cdk-diff ... FAILURE [ 0.025 > s] > ... > [ERROR] Failed to execute goal on project cdk-diff: Could not resolve > dependencies for project org.openscience.cdk:cdk-diff:jar:2.3: Cannot access > ossrh (https://oss.sonatype.org/content/repositories/snapshots) in offline > mode and the artifact org.openscience.cdk:cdk-test:jar:tests:debian has not > been downloaded from it before. -> [Help 1] [...] That means that cdk build-depends on itself. You are trying to build a module which depends on another module of the same project. If cdk-test.jar is really built before cdk-diff then it should be possible to work around it by using a local system path which requires a patch for pom.xml (to avoid downloading cdk-test.jar from the internet for DFSG reasons). You can also try to ignore cdk-test.jar in debian/maven.ignoreRules because I doubt you really need it. Regards, Markus signature.asc Description: OpenPGP digital signature
Re: jax-maven-plugin_0.1.8-1~exp2 has rejected
Hello, Am 19.11.19 um 09:23 schrieb Mechtilde Stehmann: > Hello to the list, > > to fullfill the policy I will repack the orig.tar.gz of the package above. > > How ist the best way to do so? > > Should I do a new start to prepare the new package > jax-maven-plugin_0.1.8+dfsg-1~exp1? I believe the canonical way of repacking upstream tarballs is to add a Files-Excluded paragraph to debian/copyright and then you can use uscan to repack the tarball. https://wiki.debian.org/UscanEnhancements If you have to repack the tarball for DFSG reasons then 0.1.8+dfsg-1 should be fine, in case you want to upload to unstable. If you really wish to upload to experimental then 0.1.8+dfsg-1~exp1 is also ok. > How can I work on at salsa.debian.org/java-team/jax.maven-plugin? Just push the repacked tarball to the Git repository? Regards, Markus signature.asc Description: OpenPGP digital signature
Help needed to upgrade cdk
Hi, I've sat together with Egon Willighagen who is member of CDK upstream team to update the cdk package[1]. So far the switch from ant to maven seems to have basically succeeded. However, for some reason it does not build modules in the correct sequence and thus we are running into: [INFO] cdk SUCCESS [ 0.033 s] [INFO] cdk-base ... SUCCESS [ 0.003 s] [INFO] cdk-interfaces . SUCCESS [ 1.894 s] [INFO] cdk-core ... SUCCESS [ 2.407 s] [INFO] cdk-standard ... SUCCESS [ 1.406 s] [INFO] cdk-atomtype ... SUCCESS [ 0.209 s] [INFO] cdk-valencycheck ... SUCCESS [ 0.240 s] [INFO] cdk-misc ... SUCCESS [ 0.007 s] [INFO] cdk-diff ... FAILURE [ 0.025 s] ... [ERROR] Failed to execute goal on project cdk-diff: Could not resolve dependencies for project org.openscience.cdk:cdk-diff:jar:2.3: Cannot access ossrh (https://oss.sonatype.org/content/repositories/snapshots) in offline mode and the artifact org.openscience.cdk:cdk-test:jar:tests:debian has not been downloaded from it before. -> [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/DependencyResolutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :cdk-diff Egon says cdk-test should be build before cdk-diff and we have no idea why its not. According to Egon the travis build works nicely. Any idea why this is different in a pbuilder chroot? Any help would be welcome Andreas. [1] https://salsa.debian.org/java-team/cdk -- http://fam-tille.de
Re: jax-maven-plugin_0.1.8-1~exp2 has rejected
Hello to the list, to fullfill the policy I will repack the orig.tar.gz of the package above. How ist the best way to do so? Should I do a new start to prepare the new package jax-maven-plugin_0.1.8+dfsg-1~exp1? How can I work on at salsa.debian.org/java-team/jax.maven-plugin? Thanks in advance for some hints Mechtilde Am 10.11.19 um 20:00 schrieb Thorsten Alteholz: > > Hi Mechtilde, > > can you please be a bit more verbose about why these newly to your > debain/copyright > added files are licensed under the Apache license? > After a short glimpse on the given websites, I would think that their license > is not > compatible with the DFSG. > > Thanks! > Thorsten > signature.asc Description: OpenPGP digital signature
