Your message dated Sat, 23 Nov 2019 09:34:15 +0000
with message-id <e1iyrnz-0002p1...@fasolo.debian.org>
and subject line Bug#945301: fixed in fcml 1.2.0-2
has caused the Debian Bug report #945301,
regarding libhsdis0-fcml: fails to install: find: '/usr/lib/jvm': No such file 
or directory
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
945301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945301
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libhsdis0-fcml
Version: 1.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Setting up libhsdis0-fcml:amd64 (1.2.0-1) ...
  find: '/usr/lib/jvm': No such file or directory
  dpkg: error processing package libhsdis0-fcml:amd64 (--configure):
   installed libhsdis0-fcml:amd64 package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.29-3) ...
  Errors were encountered while processing:
   libhsdis0-fcml:amd64


cheers,

Andreas

Attachment: libhsdis0-fcml_1.2.0-1.log.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Source: fcml
Source-Version: 1.2.0-2

We believe that the bug you reported is fixed in the latest version of
fcml, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 945...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt <sk...@debian.org> (supplier of updated fcml package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 23 Nov 2019 10:15:42 +0100
Source: fcml
Architecture: source
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt <sk...@debian.org>
Changed-By: Stephen Kitt <sk...@debian.org>
Closes: 945301
Changes:
 fcml (1.2.0-2) unstable; urgency=medium
 .
   * Check that /usr/lib/jvm exists before processing it. Closes: #945301.
   * Process all template maintainer scripts without listing them
     explicitly.
   * Remove symlinks in prerm rather than postrm, to avoid having invalid
     symlinks at any time.
   * Fix the generated symlinks (“hdis” → “hsdis”).
Checksums-Sha1:
 7abefa3c9ebf8f7b94a1731f9354a45358a6d3d0 2022 fcml_1.2.0-2.dsc
 ec9c5715dc18cfe17ef00f20812694805790a722 15800 fcml_1.2.0-2.debian.tar.xz
 8a881075a3d192735ff86a4cd04fba3bad3cdda9 7402 fcml_1.2.0-2_source.buildinfo
Checksums-Sha256:
 97442dd61e0ea07e3953051a02c72db4a49b29cef3e24dea9f8d670b06f0029c 2022 
fcml_1.2.0-2.dsc
 ca1ca447b8506348ccbd81f6de2218667c20bcdaf94bcb98eecdbc7ec17826d0 15800 
fcml_1.2.0-2.debian.tar.xz
 0ae30aecd9a4facdf042ba0a723dd96ecbc746fe2aa937ad6cc9d0817ac466f2 7402 
fcml_1.2.0-2_source.buildinfo
Files:
 773138f174eadbbcf6ebf86826a1c845 2022 devel optional fcml_1.2.0-2.dsc
 30af8835c1f7543eb6aba4973e9a7a1f 15800 devel optional 
fcml_1.2.0-2.debian.tar.xz
 5a7d906a8ca4c858c858fc21ffa02c93 7402 devel optional 
fcml_1.2.0-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAl3Y+TwACgkQgNMC9Yht
g5yFSw//dy+1aZfi682GVfB/rwVyV00Igefmd7UlmjBAFeT+04mJFky0pEF2oPxk
bXD3Wiwdq0QNVhDd5AJ2qRVQE/tFQPZZS6IQuu2g5EuI+IpJNBva9TXgFnInDeu+
AdVHgrKM2duaCJEMDvPP13MIlh2w6d/H95tkbJXj70kgY4vyre7BKgAjm5MXxcV4
NHSY/hV8hrAmWD+UW1nB8s6BcnR1sCozFKbR7mBH8MLTrReQ3W22R78CetkVIQVv
qLjP4pvfzty2B37L8pxjMEwBIKpiQzSClqmFstQEdTdPG+pK8WtbkMtCmjwTik4j
6RzNIma8N4EwjcqBKeC2Kytp5bocbY/XYatCiUX3j5nwoFkGouOgdRuDAlPucNHN
0e4h8KLIHUf3eq3zAOFukhCVZWtSrFoS9oVyO/XzfsR4Bs5S9QkBlWEPKDHUqKgE
TWr6ww2yP544HivXGeHlBVdWxoCvNnF7rUbYBoCxlGkUOcIEYsvGGJfU3Q583oiv
aDOiWSjQdtI1qbXvyC43VyQAn9JmKGlESDJUH2BW6Dfopr9w75m23rlqqDROnxLR
+KzoBd+9XsmSfE4xL2C4tk0QnXqW4KCFFiU1/uj9+rtf/BH2nRvOQ6mg41gX+n7N
O9aq7tCPPPCa6FxNJwQX7JQf2u01GIxO3R6+m7SRotav1lKv1bM=
=iH9W
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to