Your message dated Sun, 23 Jul 2023 19:52:20 +0000
with message-id <e1qnf7s-007ggg...@fasolo.debian.org>
and subject line Bug#1041758: fixed in cudf 0.10-2
has caused the Debian Bug report #1041758,
regarding libcudf-dev is not installable due to bogus janitor change
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 ow...@bugs.debian.org
immediately.)


-- 
1041758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcudf-dev
Version: 0.10-1
Severity: serious
X-Debbugs-Cc: team+jani...@tracker.debian.org

The following packages have unmet dependencies:
 libcudf-dev : Depends: libtinfo6 (= 6.1+20181013-2+deb10u2) but 6.4+20230625-1 
is to be installed
               Depends: libncurses-dev (= 6.1+20181013-2+deb10u2) but 
6.4+20230625-1 is to be installed

This is due to:

https://salsa.debian.org/ocaml-team/cudf/-/merge_requests/2

cudf (0.10-1) unstable; urgency=medium
...
  [ Debian Janitor ]
...
   * Remove constraints unnecessary since buster (oldstable):
     + libcudf-dev: Replace dependency on transitional package libncurses5-dev
       with replacement libtinfo6 (= 6.1+20181013-2+deb10u2), libncurses-dev (=
       6.1+20181013-2+deb10u2) in Depends.
...


I haven't checked whether the replacement package names are correct,
but the = dependences hardcoded in debian/control are clearly wrong.

--- End Message ---
--- Begin Message ---
Source: cudf
Source-Version: 0.10-2
Done: Stéphane Glondu <glo...@debian.org>

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

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


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

Format: 1.8
Date: Sun, 23 Jul 2023 21:14:07 +0200
Source: cudf
Architecture: source
Version: 0.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers <debian-ocaml-ma...@lists.debian.org>
Changed-By: Stéphane Glondu <glo...@debian.org>
Closes: 1041758
Changes:
 cudf (0.10-2) unstable; urgency=medium
 .
   * Team upload
   * Fix bogus dependencies in libcudf-dev (Closes: #1041758)
Checksums-Sha1:
 7c670662ab6f56d6e84992387655c887ffcd00a5 1977 cudf_0.10-2.dsc
 3c1b6ba13a60d597a725718ea4eef0b8fd9c8cda 5316 cudf_0.10-2.debian.tar.xz
Checksums-Sha256:
 5c586adf53dcb19a6cc8d27000f1b365e4049487eab3353d5a8b004f7f96d4c0 1977 
cudf_0.10-2.dsc
 dfdd4d1ff9b795d89271a24c2e69518ccc58b3fe7c091c7a87741b340cf13e28 5316 
cudf_0.10-2.debian.tar.xz
Files:
 4c73107bd75bdde8f0700afbdf9d6fcc 1977 devel optional cudf_0.10-2.dsc
 7bbbab579d2536ed1374dcb9511f3522 5316 devel optional cudf_0.10-2.debian.tar.xz

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

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmS9fH4SHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCByjAH/1SfYGZ8UmGO6CswB64MUToQIcmXKuGd
iK4zXK2tEpTUwOyJb6a0U9eBMuB79oXh+sfAypBTWUFHqX0cUhf5DkLyV4BzLXik
r1omdaadFqmoCbGBopR17T5fX9ulywRvga9RF710RqqF/z5Nsfh6gz7wUJuDpOBo
+UxKCGVsTkongJOj4ATMWAht/tvlCa/tdQojhMAIYaxQFNE0K1CfmDRBkR/un/aH
OfuJpGLm1ouhRKkQCWbaz8gzpUVxju4yDO3UzOjrcvQQjnvLGVL8rFp6YcQA9aI6
HSZiPT9AJ+nttocQZzOoIX9HIUHMO8rxAiZSTY7lqq+5tPMwSilqZZg=
=wGE6
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to