Your message dated Sat, 21 Oct 2006 22:10:22 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixing version-tracking for already fixed-in-NMU bug
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: saxon-catalog
Version: 20000203-5
Severity: serious
saxon-catalog fails to build from source.
1. The build-dependencies don't provide "jar".
2. If "jar" is available (kaffe 1.0.7-3):
[...]
install -d -o root -g root -m 755 debian/tmp
cd debian/tmp; jar xf ../../kosek.jar cz; jar vcf ../saxon-catalog.jar cz
cz: no such file or directory
make: *** [install] Error 2
BTW: Your other serious bug on saxon-catalog is > half a year old and
you have other critical and grave bug reports.
Kind regards,
Martin
--- End Message ---
--- Begin Message ---
Version: 20020210-0.1
This bug was fixed in an NMU, but never closed. I'm closing it with the
correct version so that its status can be properly version-tracked.
For reference:
saxon-catalog (20020210-0.1) unstable; urgency=low
.
* Non maintainer upload (0-day NMU policy)
* use new upstream of 20020210, depend on libsaxon-java (>= 6.5.4)
* added java-runtime dependency (Closes: #178360)
* Standards version 3.6.1, debhelper v4, really include the
source in the package and overhaul the build process
(Closes: #203108)
* fix grammar in description (Closes: #115670)
* wrote manpage saxoncat.1
Regards,
Adam
--- End Message ---
