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

Bug#1115621: marked as done (liblambda-term-ocaml-dev: recommends liblambda-term-ocaml-doc which is not in unstable)

Your message dated Tue, 23 Sep 2025 08:34:53 +0000
with message-id <E1v0yU9-0016Po-36@fasolo.debian.org>
and subject line Bug#1115621: fixed in lambda-term 3.3.2-2
has caused the Debian Bug report #1115621,
regarding liblambda-term-ocaml-dev: recommends liblambda-term-ocaml-doc 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.)


-- 
1115621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115621
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Subject: liblambda-term-ocaml-dev: recommends liblambda-term-ocaml-doc which is not in unstable
Package: liblambda-term-ocaml-dev
Version: 3.3.2-1+b28
Severity: minor
User: submit@bugs.debian.org
Usertags: package-relations

Dear maintainer,

I see that the package liblambda-term-ocaml-dev (version 3.3.2-1+b28)
recommends liblambda-term-ocaml-doc which is not in unstable.

This can be seen in
https://packages.debian.org/unstable/liblambda-term-ocaml-dev

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/liblambda-term-ocaml-doc

Returns 404, usually it means that has never been in Debian.


Thank you,

-- 
Carles Pina i Estany
https://carles.pina.cat | carles@pina.cat | cpina@debian.org

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Source: lambda-term
Source-Version: 3.3.2-2
Done: Stéphane Glondu <glondu@debian.org>

We believe that the bug you reported is fixed in the latest version of
lambda-term, 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 1115621@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 lambda-term 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: Tue, 23 Sep 2025 10:10:20 +0200
Source: lambda-term
Architecture: source
Version: 3.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org>
Changed-By: Stéphane Glondu <glondu@debian.org>
Closes: 1115621
Changes:
 lambda-term (3.3.2-2) unstable; urgency=medium
 .
   * Team upload
   * Do not recommend liblambda-term-ocaml-doc (Closes: #1115621)
   * Bump Standards-Version to 4.7.2
   * Bump debian/watch version to 5
Checksums-Sha1:
 a79603a21c84a60c5cc472ba7afd4e521676c425 2061 lambda-term_3.3.2-2.dsc
 e7dd1bebc159f8b9ebaf61385e5937ba8b4e1479 3156 lambda-term_3.3.2-2.debian.tar.xz
Checksums-Sha256:
 6c974609804475389c54fc945c551ac2725f85cb997515ef8379e7bc08e20810 2061 lambda-term_3.3.2-2.dsc
 940ec681725c943016119d6ba9072309d184128ca5e29bd39f462f4131cbcf80 3156 lambda-term_3.3.2-2.debian.tar.xz
Files:
 6b97dcc2d9396f5916ad4bda2a2b8957 2061 ocaml optional lambda-term_3.3.2-2.dsc
 421ca2192e92483b9f9af554f4c01e7f 3156 ocaml optional lambda-term_3.3.2-2.debian.tar.xz

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

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmjSVikSHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCBqS4H/RnPJdg25nsM1QNdwWqsgglaEiZYjxis
g4rKsIpQqQvTBp8T+1xM+c7v/0Yjcs4pbTuktOKRDtSb+yMAe5PaBWRA4ae6yNwE
4iD1TytJLWruo4FFSqkycYCgFGG9soFoYPLFFr/Re4MKJvtv1lpu8U/Rll3yFUdW
33wk5afPvSnvBK0DlOH58+Eel+KZ96sXNxmPVWcG2KONjigqBLU8oz21rulvePXn
Swcc3602HS+oT401uLivgiD98YFuc2n2FKiGl6laWOzQfB3IfoVBCu1fyux+Rwx5
xUIpa+T101LZuWC12kTtgK3hyrFbhcm+ldFg7mmOoxEBxwBDCgjsWqs=
=74lS
-----END PGP SIGNATURE-----

Attachment: pgpE8i5z0yi0a.pgp
Description: PGP signature


--- End Message ---
Reply to: