Bug#1002984: marked as done (FTBFS with ocaml-migrate-parsetree 2.3.0)
Your message dated Sat, 22 Jan 2022 06:18:41 +0000
with message-id <E1nB9jV-0001kf-E9@fasolo.debian.org>
and subject line Bug#1002984: fixed in mlpost 0.9-2
has caused the Debian Bug report #1002984,
regarding FTBFS with ocaml-migrate-parsetree 2.3.0
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.)
--
1002984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002984
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: mlpost
Version: 0.9-1
Severity: important
Tags: ftbfs
Dear Maintainer,
Your package FTBFS with ocaml-migrate-parsetree 2.3.0 with the
following error:
> File "customdoc/img.ml", line 2, characters 5-18:
> 2 | open OCaml_403.Ast
> ^^^^^^^^^^^^^
> Error: Unbound module OCaml_403
This was discovered while preparing the transition to OCaml 4.13.1.
Packages rebuilt with OCaml 4.13.1 are available at:
https://ocaml.debian.net/transitions/ocaml-4.13.1/
Cheers,
--
Stéphane
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: mlpost
Source-Version: 0.9-2
Done: Stéphane Glondu <glondu@debian.org>
We believe that the bug you reported is fixed in the latest version of
mlpost, 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 1002984@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 mlpost 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: Sat, 22 Jan 2022 06:49:41 +0100
Source: mlpost
Architecture: source
Version: 0.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org>
Changed-By: Stéphane Glondu <glondu@debian.org>
Closes: 1002984
Changes:
mlpost (0.9-2) unstable; urgency=medium
.
* Apply upstream patch to upgrade to ppxlib (Closes: #1002984)
Checksums-Sha1:
f9e946a2e81ae4609729f003d781c932b03acda5 2141 mlpost_0.9-2.dsc
7ab84cadff71b1a3247a75c64149f47901755e7a 5924 mlpost_0.9-2.debian.tar.xz
Checksums-Sha256:
0416ddcbfca88de7ed4a4f9c0dc333b988f7ecf6d77ef4064441d4d55b40f25a 2141 mlpost_0.9-2.dsc
4e318ff4b6505cf2faccae7c76c3418f16e0fca380b1b93dac874639aafd233d 5924 mlpost_0.9-2.debian.tar.xz
Files:
5231c99bad44b4c5dde3f9dde8315045 2141 tex optional mlpost_0.9-2.dsc
fb37fa19e0b4526b467d5f0dcce18de8 5924 tex optional mlpost_0.9-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmHrnWQSHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBM8oH/A5JNjyxg0Wa9iBA4LIlaYpYcx8JyMzT
ThA9fhIFaJdkyPVbnM6aZ4ept3ZdByDiwtAFWJ+tZqNziDTQfuIzbrmenMua1SfS
b2F68otqde1Zb6reXFteYrTFyB/agvJSorgFxn/b81AVlD5W7uK1wy8zVyWg0Dgh
noS4Uhjcp4HWU0dyNLYyALV64ShVzb28OfSdWR+2i83o+J/5olcjdLPLb6gzoeTo
4q0AKZ8c3FXT8W6i/WuYgOEdQEZjTc0fZBpi3rDFKu6Bs6/IVJqoKWU1UD7BopCo
RX5pRxssOZcoGtulXDiKZ9iA49nWuvDujTCEmE+HxS5gHb+0ENltFSQ=
=itWS
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: