Bug#826734: mh_install doesn't work with dh-exec
My understanding from what algernon said in IRC, it's just a matter of
using standard debhelper interface to access to debian/.poms file.
Perhaps a small dh/mh helper like this:
$ cat mh_readpoms
#!/usr/bin/perl -w
use strict;
use Debian::Debhelper::Dh_Lib;
my $package = $ARGV[0];
init();
if ($package) {
my $file = pkgfile($package,"poms");
if ($file) {
my @poms=filedoublearray($file);
foreach my $pom (@poms) {
print join(" ", @$pom) . "\n";
}
}
}
and do:
mh_readpoms $p | while read ...
in the main mh_install function.
This might just do the trick as filedoublearray call is needed for
dh-exec to kick-in.
Cheers,
--
Ondřej Surý <ond...@sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
On Wed, Jun 8, 2016, at 15:28, Emmanuel Bourg wrote:
> Le 8/06/2016 à 15:18, Ondřej Surý a écrit :
>
> > java/lib/icepatch2-3.6.2.pom --artifact=java/lib/icepatch2-3.6.2.jar
> > java/lib/glacier2-3.6.2.pom --artifact=java/lib/glacier2-3.6.2.jar
> > java/lib/freeze-3.6.2.pom --artifact=java/lib/freeze-3.6.2.jar
>
> Thank you for the example. mh_install supports wildcards for the
> --artifact parameter. You can write something like this:
>
> path/to/pom.xml --artifact=lib/foo-*.jar
>
> But this won't work with your example since the path of the pom also
> contains the version number.
>
> I'm not sure we can easily interface mh_install with dh-exec, but it
> should be possible to teach him to expand the environment variables.
>
> Emmanuel Bourg
>
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
Please use
debian-j...@lists.debian.org for discussions and questions.
Bug#826734: mh_install doesn't work with dh-exec
Hi Emmanuel,
this is the debian/libzeroc-ice-java.poms:
$ cat debian/libzeroc-ice-java.poms
java/lib/ice-3.6.2.pom --artifact=java/lib/ice-3.6.2.jar
java/lib/icebox-3.6.2.pom --artifact=java/lib/icebox-3.6.2.jar
java/lib/icediscovery-3.6.2.pom
--artifact=java/lib/icediscovery-3.6.2.jar
java/lib/icelocatordiscovery-3.6.2.pom
--artifact=java/lib/icelocatordiscovery-3.6.2.jar
java/lib/icegrid-3.6.2.pom --artifact=java/lib/icegrid-3.6.2.jar
java/lib/icestorm-3.6.2.pom --artifact=java/lib/icestorm-3.6.2.jar
java/lib/icepatch2-3.6.2.pom --artifact=java/lib/icepatch2-3.6.2.jar
java/lib/glacier2-3.6.2.pom --artifact=java/lib/glacier2-3.6.2.jar
java/lib/freeze-3.6.2.pom --artifact=java/lib/freeze-3.6.2.jar
and here's f.e. debian/libzeroc-ice-java.links:
$ cat debian/libzeroc-ice-java.links
#!/usr/bin/dh-exec
usr/share/java/freeze-${VERSION}.jar usr/share/java/freeze.jar
usr/share/java/glacier2-${VERSION}.jar usr/share/java/glacier2.jar
usr/share/java/ice-${VERSION}.jar usr/share/java/ice.jar
usr/share/java/icebox-${VERSION}.jar usr/share/java/icebox.jar
usr/share/java/icediscovery-${VERSION}.jar
usr/share/java/icediscovery.jar
usr/share/java/icelocatordiscovery-${VERSION}.jar
usr/share/java/icelocatordiscovery.jar
usr/share/java/icegrid-${VERSION}.jar usr/share/java/icegrid.jar
usr/share/java/icepatch2-${VERSION}.jar usr/share/java/icepatch2.jar
usr/share/java/icestorm-${VERSION}.jar usr/share/java/icestorm.jar
usr/share/java/freeze-${VERSION}-source.jar
usr/share/java/freeze-source.jar
usr/share/java/glacier2-${VERSION}-source.jar
usr/share/java/glacier2-source.jar
usr/share/java/ice-${VERSION}-source.jar usr/share/java/ice-source.jar
usr/share/java/icebox-${VERSION}-source.jar
usr/share/java/icebox-source.jar
usr/share/java/icediscovery-${VERSION}-source.jar
usr/share/java/icediscovery-source.jar
usr/share/java/icelocatordiscovery-${VERSION}-source.jar
usr/share/java/icelocatordiscovery-source.jar
usr/share/java/icegrid-${VERSION}-source.jar
usr/share/java/icegrid-source.jar
usr/share/java/icepatch2-${VERSION}-source.jar
usr/share/java/icepatch2-source.jar
usr/share/java/icestorm-${VERSION}-source.jar
usr/share/java/icestorm-source.jar
With upstream bump to 3.6.3, I will have to modify *.poms, but *.links
will be ok, as I export VERSION from the d/rules.
(P.S.: I have no clue about Java at all, so this is what the package has
and I only used dh-exec to make it simpler).
Cheers,
--
Ondřej Surý <ond...@sury.org>
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
On Wed, Jun 8, 2016, at 15:15, Emmanuel Bourg wrote:
> Hi Ondřej,
>
> What kind of substitution would you like to perform in the debian/*.poms
> files? Could you post an example please?
>
> Emmanuel Bourg
>
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
Please use
debian-j...@lists.debian.org for discussions and questions.
Bug#826734: mh_install doesn't work with dh-exec
Package: maven-repo-helper
Version: 1.8.12
Severity: normal
Dear maintainer(s),
I have recently helped with zeroc-ice packaging and the debian/*.poms
contains an upstream version number, so it would be very convenient if
dh-exec would work, so I could dynamically replace ${VERSION} at the
build time.
Unfortunately the build breaks as it looks like mh_install is not
using standard debhelper mechanisms to access the files:
14:39 < algernon> ondrej: hm, perhaps mh_install is doing its own
magic, and doesn't go through debhelpers thing that makes executable
files work :/ │
Could you perhaps work with dh-exec maintainer to resolve this?
Cheers,
Ondrej
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
__
This is the maintainer address of Debian's Java team
.
Please use
debian-j...@lists.debian.org for discussions and questions.
Bug#719842: [pkg-db-devel] Bug#719842: db5.3: FTBFS: jh_linkjars: Invalid option: N
Control: tags -1 + pending It has been already applied to git and it will be available in next upload. O. -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server On 7. 7. 2014, at 1:59, John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de wrote: Hi Ondřej! Is there anything that speaks against applying Thorsten's patch to fix the FTBFS of db5.3 on m68k? If not, would you be so kind and apply his patch so that db5.3 is also built on this particular Debian port? I'd also be happy to do an NMU if necessary. The m68k port has lots of fans in the retro-computing scene (Apple, Atari and Amiga users) and we recently got some (small) funding from Debian approved by our DPL Lucas Nussbaum to support our work. I am fully aware of the fact that m68k machines are (currently) not something what most people would use for production. However, the port is now on a very good way and we have several people investing some time to revive the port and our users appreciate it. PS: Even Greg Kroah-Hartman likes the m68k port when I was asking him at LinuxTag and he said the code is there to stay in the kernel since the port helps finding compatibility regressions in the kernel which can also affect other, newer architectures. Thanks a lot! Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#628288: FTBFS: [javac] /build/user-lucene2_2.9.4+ds1-1-amd64-JNLFNr/lucene2-2.9.4+ds1/contrib/db/bdb/src/java/org/apache/lucene/store/db/DbDirectory.java:201: cannot find symbol
Package: lucene2 Severity: normal The correct patch was provided in #621398, I have also informed you to wait for libdb-java (= 5.1.4), so you get the correct version with 'db.jar'. Please apply the former patch and it will fix this error. And really please do Build-Depend just on libdb-java, so we don't have to open new bug for every Berkeley DB transition we do. Thanks, -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#621398: libdb4.7-java removed from unstable
Package: lucene2 severity 621398 serious thank you Hi, just a heads-up. Since the java builds become recently broken on several architectures for db4.7 I have decided to remove Java support from db4.7 now rather than waiting for lucene2 to gracefuly transition to libdb5.1-java. Sorry for the hasty move, but lucene2 is the only user of lidb4.7-java, and it's not worth the effort of fixing db4.7 which is obsolete anyway. O. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#623506: javahelper: doesn't handle debhelper BUILD SYSTEM OPTIONS
Package: javahelper Version: 0.33 Severity: normal my dh call is: %: dh $@ -Ddist -Bbuild --with=javahelper jh_linkjars fails with: jh_linkjars -O-Ddist -O-Bbuild Invalid option: O Usage: jh_linkjars [options] [target] Options: -h --help: show this text -V --version: show the version -v --verbose: show more information while running -t --transitive: transitively link jars -n --no-act: don't actually do anything, just print the results -u --unlink: remove the links instead of adding them make: *** [build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 A simple workaround is to create following rule: override_jh_linkjars: jh_linkjars [Error commes from unstable pbuilder and not stable system.] O. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages javahelper depends on: ii bsdmainutils8.0.13 collection of more utilities from ii dctrl-tools 2.14.5 Command-line tools to process Debi ii debhelper 8.0.0helper programs for debian/rules ii devscripts 2.10.69+squeeze1 scripts to make the life of a Debi ii dpkg-dev1.15.8.10Debian package development tools ii fastjar 2:0.98-3 Jar creation utility ii libarchive-zip-perl 1.30-3 Perl module for manipulation of ZI javahelper recommends no packages. Versions of packages javahelper suggests: pn cvs none (no description available) ii gawk 1:3.1.7.dfsg-5 GNU awk, a pattern scanning and pr pn tofrodos none (no description available) -- no debconf information __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#621398: Still uses libdb4.7
Package: lucene2 Version: 2.9.3+ds1-1 Severity: normal User: pkg-db-de...@lists.alioth.debian.org Usertags: db5.1 Your package currently still uses Berkeley DB version 4.7 (libdb4.7). However, there is a newer Berkeley DB version in the archive (libdb5.1), with a compatible API. Berkeley DB version 4.7 will be eventually removed from unstable in favor of version 5.1. Please port your package to libdb5.1 as soon as possible. In most cases only change required is to update build depends from libdb4.7-dev to libdb-dev, or just recompile the package. More complicated scenarios: - Package does check for DB_VERSION_MAJOR == 4 - this should be updated to (DB_VERSION_MAJOR 4) || ((DB_VERSION_MAJOR == 4) (DB_VERSION_MINOR = XX)). - Configure checks - sometime there is a list of db-4.7 db-4.6 db-4.2, etc., this needs to be updated to just db (or db-5.1 db-5 db), or at least list the 'db' in the front You can see example patch in cyrus-imapd-2.2: http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.2.git;a=blob;f=debian/patches/99-berkelydb-5.1.dpatch;hb=HEAD - The packages which use Berkeley DB transactional mode need to upgrade the database files before the upgrade. This is fairly straightforward and is well documented on the Berkeley DB website. But you probably already know that because it's not the first Berkeley DB transition. The example script can be found in the cyrus-imapd-2.4 (not yet released): http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.4.git;a=blob;f=debian/cyrus-upgrade-db;hb=HEAD Thanks, -- Ondřej Surý ond...@debian.org -- System Information: Debian Release: squeeze/sid APT prefers maverick-updates APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 'maverick-proposed'), (500, 'maverick-backports'), (500, 'maverick') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35-28-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
