Bug#1040812: marked as done (ocaml-pprint build-depends on dropped transitional package.)
Your message dated Wed, 12 Jul 2023 10:49:14 +0200
with message-id <f7539196-264e-560d-7456-a518dc1fbe6a@debian.org>
and subject line Re: Bug#1040812: ocaml-pprint build-depends on dropped transitional package.
has caused the Debian Bug report #1040812,
regarding ocaml-pprint build-depends on dropped transitional package.
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.)
--
1040812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040812
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: ocaml-pprint
Version: 20220103-1
Tags: trixie, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian-qa@lists.debian.org
Usertags: edos-uninstallable
ocaml-pprint build-depends on dune, in bullseye this was a transitional package
built by the ocaml-dune source package and depending on the ocaml-dune
binary package. However in ocaml-dune 3.8.2-1 the transitional package
was dropped. It is still present in unstable as a cruft package but
is completely gone from testing.
Presumablly you need to update your build-dependency to build-depend on
dune instead of ocaml-dune.
--- End Message ---
--- Begin Message ---
Version: 20220103-2
Le 11/07/2023 à 04:13, Peter Green a écrit :
ocaml-pprint build-depends on dune, in bullseye this was a transitional
package
built by the ocaml-dune source package and depending on the ocaml-dune
binary package. However in ocaml-dune 3.8.2-1 the transitional package
was dropped. It is still present in unstable as a cruft package but
is completely gone from testing.
Already fixed in last version, hence closing.
Cheers,
--
Stéphane
--- End Message ---
Reply to: