[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1003741: marked as done (ocaml-conduit FTBFS on bytecode architectures)



Your message dated Fri, 14 Jan 2022 22:40:15 +0000
with message-id <E1n8VF1-000HkP-IZ@fasolo.debian.org>
and subject line Bug#1003741: fixed in ocaml-conduit 4.0.2-3
has caused the Debian Bug report #1003741,
regarding ocaml-conduit FTBFS on bytecode architectures
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 owner@bugs.debian.org
immediately.)


-- 
1003741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003741
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: ocaml-conduit
Version: 4.0.2-2
Severity: important
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=ocaml-conduit&ver=4.0.2-2

...
   dh_install -a
dh_install: warning: Cannot find (any matches for) "/usr/lib/ocaml/conduit/*.a" (tried in ., debian/tmp)

dh_install: warning: libconduit-ocaml-dev missing files: /usr/lib/ocaml/conduit/*.a
dh_install: warning: Cannot find (any matches for) "/usr/lib/ocaml/*lwt*/*.a" (tried in ., debian/tmp)

dh_install: warning: libconduit-lwt-ocaml-dev missing files: /usr/lib/ocaml/*lwt*/*.a
dh_install: error: missing files, aborting
make: *** [debian/rules:9: binary-arch] Error 25

--- End Message ---
--- Begin Message ---
Source: ocaml-conduit
Source-Version: 4.0.2-3
Done: Stéphane Glondu <glondu@debian.org>

We believe that the bug you reported is fixed in the latest version of
ocaml-conduit, 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 1003741@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stéphane Glondu <glondu@debian.org> (supplier of updated ocaml-conduit 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Fri, 14 Jan 2022 22:17:37 +0100
Source: ocaml-conduit
Architecture: source
Version: 4.0.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org>
Changed-By: Stéphane Glondu <glondu@debian.org>
Closes: 1003741
Changes:
 ocaml-conduit (4.0.2-3) unstable; urgency=medium
 .
   * Fix FTBFS on bytecode architectures (Closes: #1003741)
   * Build conduit-lwt-unix
Checksums-Sha1:
 b3d2783db8e5d39d638d11d6eca7ff9b871e08d7 2221 ocaml-conduit_4.0.2-3.dsc
 989b7f85c1ed314dfd99f9cb4a4e5266e4140e0b 2624 ocaml-conduit_4.0.2-3.debian.tar.xz
Checksums-Sha256:
 d6510eb302250d9addae39fd26128614d44cacee5124d48602db9202f9bc1641 2221 ocaml-conduit_4.0.2-3.dsc
 8b42396bfd325ef30db43b41316df521694d03fbb2a0a6e7a135f2f745939de4 2624 ocaml-conduit_4.0.2-3.debian.tar.xz
Files:
 8d35e44f38ab0af7b5b721a0db6f4008 2221 ocaml optional ocaml-conduit_4.0.2-3.dsc
 344a2ca5fa3ea643b739eb8520f07d97 2624 ocaml optional ocaml-conduit_4.0.2-3.debian.tar.xz

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

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmHh6i0SHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCB8K4H/jJUPktIKlvnGeum8eSr0lgkG/xSUcfG
uN3W96AjUGNl+tRrFgX/tiy1Iysw8Mcr8pSjZ5xhrzdEeUJ6UKAo4IXRHPgcUHKr
QTZFcu2JceeXxwHECIXMLRHfwa/mpHkv1Xese9+ecB9Rk/YU/wt1SWlqaPoll6B8
XCMy0SiE6ZBaLhcyb0ZzsGlV5CUPVGOkoa4vP7jbEYgHo84MNXZ/lzSoQRBfY9F0
bsIqD/krlAQ85lEvP9QKwerO4fPpQW4RZEMnasE6S5z6iaF504xwqVtdhYZLw9kZ
38NPeGGopsrPT1aoPyJGdVnLJ4tn5piWv9OlgOGyYcWUEFAzJ885qqQ=
=pI5u
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: