Re: request for help: jhove
Le 30/04/2018 à 21:37, Jeff Breidenbach a écrit : > I'd love to actually update to the most recent upstream. The build > system switched > from ant to maven, and I am completely unfamiliar with it. I suggest removing (or renaming) the debian directory and running mh_make. Ignore anything that is related to tests, deployment, QA (like jacoco) and focus on the core modules to keep it simple. This will generate a first buildable version of the project. You can gradually enable more modules and tests later if it works well. Emmanuel Bourg
Re: Import git repo from alioth to salsa
Hi, Il 30/04/2018 19:22, Emmanuel Bourg ha scritto: > I've moved the geogebra repository, could you check if it's ok? > > https://salsa.debian.org/java-team/geogebra It is, thank you! > I think I'll just complete the mass migration myself, but I'll need help > afterward to check if everything is ok (like missing or empty > repositories). I'll also need help to migrate the ~60 packages still in > Subversion. I can help to check, at least for my packages. I can also check others, but maybe will not be as good as spotting problems. For svn, I think I can help, although if you already have a list (as Markus asked) that would help. BTW, this recalls me that libjgrapht0.8 (which is my only package still on svn) is probably in the need of some dust removal. Debian also ships libjgrapht0.6 as a separate source package. Both are terribly old, since upstream has released 1.1.0. However, I am a bit unsure on how to handle this situation: I do not know much the API remained stable between 0.6, 0.6 and 1.1.0 and thus how to manage the update causing the least inconvenience possible. I also have a similar problem with libstax2-api-java and libwoodstox-java. Maybe it is better to wait for the end of the migration, but if someone could at some point enlighten me on the best practices, I would be grateful. Thanks, Giovanni. -- Giovanni MascellaniPostdoc researcher - Université Libre de Bruxelles
Re: request for help: jhove
I'd love to actually update to the most recent upstream. The build system switched from ant to maven, and I am completely unfamiliar with it. First, I got a fatal error about not finding org.sonatype.oss:oss-parent:pom, so I tried deleting that section of the pom.xml. Then the build can't find jacoco-mavin-plugin is missing. That's where I'm currently stuck. control/ Build-Depends: javahelper, debhelper, maven-debian-helper, libmaven-shared-utils-java, quilt, cdbs, libjacoco-java Build-Depends-Indep: default-jdk rules/ JAVA_HOME=/usr/lib/jvm/default-java %: dh $@ --with javahelper
Re: request for help: jhove
I'd love to actually update to the most recent upstream. The build system switched from ant to maven, and I am completely unfamiliar with it. First, I got a fatal error about not finding org.sonatype.oss:oss-parent:pom, so I tried deleting that section of the pom.xml. Then the build can't find jacoco-mavin-plugin is missing. That's where I'm currently stuck. control/ Build-Depends: javahelper, debhelper, maven-debian-helper, libmaven-shared-utils-java, quilt, cdbs, libjacoco-java Build-Depends-Indep: default-jdk rules/ JAVA_HOME=/usr/lib/jvm/default-java %: dh $@ --with javahelper
Re: request for help: jhove
Hi Jeff, Le 30/04/2018 à 19:05, Jeff Breidenbach a écrit : > Is someone willing to help out? I'm appreciative of assistance at any > level: advice, patches, NMU, package adoption. Thank you in advance. We'll be happy you help with specific Java issues (either on this list or on the #debian-java IRC channel for a more interactive debugging session). Regarding #895761 it seems that setting the source encoding will fix the errors reported (just add the attribute encoding="ISO-8859-1" to the tasks in the build.xml file). Emmanuel Bourg
Re: Import git repo from alioth to salsa
Le 30/04/2018 à 13:42, Giovanni Mascellani a écrit : > Thank you very much for working on this migration. Is manual migration > of one's packages helpful, neutral or disruptive? I would like to upload > geogebra (and maybe other packages), and would take the chance to > migrate it and update Vcs-* tags, but I can wait for the migration to > finish if this would disturb your scripts. Hi Giovanni, I've moved the geogebra repository, could you check if it's ok? https://salsa.debian.org/java-team/geogebra I think I'll just complete the mass migration myself, but I'll need help afterward to check if everything is ok (like missing or empty repositories). I'll also need help to migrate the ~60 packages still in Subversion. Emmanuel Bourg
request for help: jhove
I'm the Debian package maintainer for jhove, which is an image validator and really useful for libraries and other cultural heritage institutions. It is about to get kicked out due to bug #895761. The right thing to do is update the jhove to the current upstream version. However, I haven't touched Java packaging for a very long time, and since then the world has changed. My first attempt went nowhere. Is someone willing to help out? I'm appreciative of assistance at any level: advice, patches, NMU, package adoption. Thank you in advance.
Re: Import git repo from alioth to salsa
Dear Emmanuel, Il 30/04/2018 09:25, Emmanuel Bourg ha scritto: > Yes, I plan to do that once I'm confident the migration worked properly. Thank you very much for working on this migration. Is manual migration of one's packages helpful, neutral or disruptive? I would like to upload geogebra (and maybe other packages), and would take the chance to migrate it and update Vcs-* tags, but I can wait for the migration to finish if this would disturb your scripts. Thanks, Giovanni. -- Giovanni MascellaniPostdoc researcher - Université Libre de Bruxelles
Re: Import git repo from alioth to salsa
Le 29/04/2018 à 04:00, Paul Wise a écrit : > I'd suggest deleting the migrated repositories so that DSA doesn't > have to store a copy of them in the alioth archive forever. Yes, I plan to do that once I'm confident the migration worked properly. Emmanuel Bourg