Your message dated Wed, 24 Sep 2025 07:51:54 +0000 with message-id <E1v1KI6-005dDg-2v@fasolo.debian.org> and subject line Bug#1116151: fixed in meta-ocaml 6 has caused the Debian Bug report #1116151, regarding ocaml-platform: recommends libmigrate-parsetree-ocaml-dev which is not in unstable 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.) -- 1116151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116151 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: ocaml-platform: recommends libmigrate-parsetree-ocaml-dev which is not in unstable
- From: Carles Pina i Estany <carles@pina.cat>
- Date: Wed, 24 Sep 2025 06:34:01 +0100
- Message-id: <[🔎] aNOCyscoDSg_agk0@pina.cat>
Subject: ocaml-platform: recommends libmigrate-parsetree-ocaml-dev which is not in unstable Package: ocaml-platform Version: 5 Severity: minor User: submit@bugs.debian.org Usertags: package-relations Dear maintainer, I see that the package ocaml-platform (version 5) recommends libmigrate-parsetree-ocaml-dev which is not in unstable. This can be seen in https://packages.debian.org/unstable/ocaml-platform . Search for "Package not available". Should it be dropped or changed? I see that https://tracker.debian.org has information on the not available packages: - https://tracker.debian.org/pkg/libmigrate-parsetree-ocaml-dev : removed in 2024 Thank you, -- Carles Pina i Estany https://carles.pina.cat | carles@pina.cat | cpina@debian.orgAttachment: signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: 1116151-close@bugs.debian.org
- Subject: Bug#1116151: fixed in meta-ocaml 6
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Wed, 24 Sep 2025 07:51:54 +0000
- Message-id: <E1v1KI6-005dDg-2v@fasolo.debian.org>
- Reply-to: Stéphane Glondu <glondu@debian.org>
Source: meta-ocaml Source-Version: 6 Done: Stéphane Glondu <glondu@debian.org> We believe that the bug you reported is fixed in the latest version of meta-ocaml, 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 1116151@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 meta-ocaml 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: Wed, 24 Sep 2025 09:18:51 +0200 Source: meta-ocaml Architecture: source Version: 6 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org> Changed-By: Stéphane Glondu <glondu@debian.org> Closes: 1116151 Changes: meta-ocaml (6) unstable; urgency=medium . * Do no longer recommend libmigrate-parsetree-ocaml-dev (Closes: #1116151) * Bump Standards-Version to 4.7.2 Checksums-Sha1: 53212673d175b2f49d0ccece4d47053cddb5d849 1526 meta-ocaml_6.dsc 29b5f5c41e28e2a159d25370f103a6a51327faa0 4228 meta-ocaml_6.tar.xz Checksums-Sha256: c9dfca128ad906773120a69cd32f53910c99bfd4462d92ea69c4a26c0ebe4d84 1526 meta-ocaml_6.dsc 95ed54133d5226bc77f8e393ff16afcf0fe2c7582f972629e087f33f5230cf5f 4228 meta-ocaml_6.tar.xz Files: 679cad4f99342356eae779a14424ec2b 1526 devel optional meta-ocaml_6.dsc 63c755571fc7f75dd5ea664d18c9461e 4228 devel optional meta-ocaml_6.tar.xz -----BEGIN PGP SIGNATURE----- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmjTm6sSHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCB/78H/ixC9VmMf+tynnLlYUfvlp/jRut3oP0S GtBen3rIkKtuuqB03HzooEYmhAvFW6LuTsQOgZDoc1r9whn7uRZ4AhtDocp8M+vF wsIFSFB5/xrBfdT8xyHaTSSkL3dJxv4SqOg5IOJHQjlCWOjovrWcTLP1LkSEYbpQ 2sa37dY6u/Yoo35XlrGhgYRgI1USnSrhdoUUWOdgO5jd5W+E92s24Cl6cnOlg1Zx C8Y7w0YrUzCboaqybuWXglyAk+dneywS5azlMHikigqxDT7RvkxD0eHiZnZLeW2z hCSwELzQGusNne5x8lIJBNviZWuidwR9vDRgmbCkDHVzNkF9FszXfPQ= =B4eo -----END PGP SIGNATURE-----Attachment: pgpwR9ZdPCXrd.pgp
Description: PGP signature
--- End Message ---