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

Bug#877356: marked as done (yojson: Please consider putting /usr/bin/ydump into its own binary package)

Your message dated Wed, 12 Jun 2024 18:00:11 +0000
with message-id <E1sHSGZ-00Afvu-N8@fasolo.debian.org>
and subject line Bug#877356: fixed in yojson 2.2.1-1
has caused the Debian Bug report #877356,
regarding yojson: Please consider putting /usr/bin/ydump into its own binary 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.)


-- 
877356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877356
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: yojson
Version: 1.3.2-1+b1
Severity: wishlist

Hi,

currently /usr/bin/ydump is part of the libyojson-ocaml-dev binary
package. Due to an ongoing OCaml transition, that package has been
uninstallable for a while.

The botch binary package needs /usr/bin/ydump for some of its
functionality and thus Depends on libyojson-ocaml-dev. But since
libyojson-ocaml-dev is uninstallable, so is botch.

Since, OCaml is statically linked, the problem could be averted by
putting /usr/bin/ydump in its own binary package. Then botch could just
depend on that new binary package instead of depending on
libyojson-ocaml-dev.

The advantage would be that in situations like right now during an OCaml
transition, botch would still be installable.

Thanks!

cheers, josch

--- End Message ---
--- Begin Message --- 
Source: yojson
Source-Version: 2.2.1-1
Done: Julien Puydt <jpuydt@debian.org>

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

Debian distribution maintenance software
pp.
Julien Puydt <jpuydt@debian.org> (supplier of updated yojson 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, 11 Jun 2024 09:06:37 +0200
Source: yojson
Binary: libyojson-ocaml libyojson-ocaml-dbgsym libyojson-ocaml-dev yojson-tools yojson-tools-dbgsym
Architecture: source amd64
Version: 2.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org>
Changed-By: Julien Puydt <jpuydt@debian.org>
Description:
 libyojson-ocaml - JSON library for OCaml - runtime package
 libyojson-ocaml-dev - JSON library for OCaml - development package
 yojson-tools - JSON library for OCaml - tools
Closes: 877356
Changes:
 yojson (2.2.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Bump standards-version to 4.7.0
   * Move tools to their own package (Closes: #877356)
Checksums-Sha1:
 63f6da8237ebe48b2361706cf4f705f85e6fee45 2246 yojson_2.2.1-1.dsc
 16ca7bbfd1a41a3864f7389126a615bb0b206866 58073 yojson_2.2.1.orig.tar.gz
 ae6d5ae064436e6727f07a07468e5d5c9a41d78e 4456 yojson_2.2.1-1.debian.tar.xz
 5f5f8c364ceeae9f0daafbe073f5d3a8d60d1bb0 48696 libyojson-ocaml-dbgsym_2.2.1-1_amd64.deb
 880d72e308a0547a81d82e472735734a81628bc5 904032 libyojson-ocaml-dev_2.2.1-1_amd64.deb
 c33356e28c3c11d643154c8354ae4de4a3eeb9cd 568356 libyojson-ocaml_2.2.1-1_amd64.deb
 00c653f47eeb253ff6eefa6a787f962d82a70d4e 130952 yojson-tools-dbgsym_2.2.1-1_amd64.deb
 baabfe6659e824075104b90968b252b493982600 360972 yojson-tools_2.2.1-1_amd64.deb
 c2ce6c7ab6067e47910f7f75b46bd4188f3982e0 9162 yojson_2.2.1-1_amd64.buildinfo
Checksums-Sha256:
 ea91d01551b867f5e0b9c2454155004d8c06df7aea9319dd98eaf6e726faab6b 2246 yojson_2.2.1-1.dsc
 b7d5c215c87c041aa4b9fd91aeb52a852e014ccc29a3a0f7a8acc1e4316d92bc 58073 yojson_2.2.1.orig.tar.gz
 a1c45ed615491f687e4ae63806651676127228565d3ec86c659d3c2118acbc95 4456 yojson_2.2.1-1.debian.tar.xz
 77cfeabd87d3d7136235f179d44bc1ce571554080d1acc26d23cabe49fdb7d9d 48696 libyojson-ocaml-dbgsym_2.2.1-1_amd64.deb
 29657bb7058f1677cb1ff538f11b2edab0bd1345dd4e2a68f8c8f3a1d593929a 904032 libyojson-ocaml-dev_2.2.1-1_amd64.deb
 266dae18ba125cdba613fd31a0e55667121505fa850ccb234b0c2309ec02d5fc 568356 libyojson-ocaml_2.2.1-1_amd64.deb
 65d9a1636c27504d339d5cc1a34f3115df3c13e3aa3ea1200fed1ee6e09b546a 130952 yojson-tools-dbgsym_2.2.1-1_amd64.deb
 6a5c2cf7710e6b409e3c89443f9f35dbb6fc62a4938a3c1e9c88c5c4264fbeae 360972 yojson-tools_2.2.1-1_amd64.deb
 ce643a4a16518dfaa0c1ba81d9d983c2802882d6de46529cea23d13b433a5f77 9162 yojson_2.2.1-1_amd64.buildinfo
Files:
 3a389e697cc528d6ed1132bbf31bba33 2246 ocaml optional yojson_2.2.1-1.dsc
 9a55512b4b6a948e289ee3e9b2e62944 58073 ocaml optional yojson_2.2.1.orig.tar.gz
 64e7b4bdc348a1c5bdfdcb1c271fe038 4456 ocaml optional yojson_2.2.1-1.debian.tar.xz
 8e974d5d67b27ef6db165bc79f290109 48696 debug optional libyojson-ocaml-dbgsym_2.2.1-1_amd64.deb
 2adf5c47b7fa7d6e982a7fc02d4d4f9a 904032 ocaml optional libyojson-ocaml-dev_2.2.1-1_amd64.deb
 c34184682e6aaf3017283dcb05d31139 568356 ocaml optional libyojson-ocaml_2.2.1-1_amd64.deb
 3fcb68200d669b7f1bb012525d959a74 130952 debug optional yojson-tools-dbgsym_2.2.1-1_amd64.deb
 aafef8ec2b9a3bfcddbd56d8a3c0b435 360972 ocaml optional yojson-tools_2.2.1-1_amd64.deb
 f070aa64be42f5978c1bd3f04476e2a5 9162 ocaml optional yojson_2.2.1-1_amd64.buildinfo

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

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmZooIgSHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRl18QAI9gTpfgYgMQtSCyQ3Uq1vkrVKX3iWZ7
cwgFiRZTMlEZlqTc9V7OB9Pt3KYzFSqWXAdSoj4HzMna+Q/1hSNSJGYu4xAtp71/
tK88thie0A/qoswbfU3j/WBI3OLaAak7IaoY2Dgn7Ca6RtD0+F7M/r1uKY5hVypt
QklKCMoZa5xMU6gMMHKK4Aap5rfJkpPhBzOv5tYhezlH6aOv16BftJrGYsD89/S/
WRoRCAQ5fAHdM6I+TN02UOZt76UF49EZeRTmYVv2Z1Wy7bdxz7M+D/DoA4vqahoI
/opggqnJNvh/xjjMqgP72Fe5RXfO4CzqfmsHg14domaj0ffR2j+F8TZDaSxO7wxt
0QPb17DfdftGkkcaxVsZaHqwNio0NvzXEBpplrtjcETQhScWbrdA8zqqsTHTKGLr
kBE6+E4ILl1MFrh0EHRNUZ/cIukE2VEVsClFnDk6BKbVf3rQMI44SB1x17fxOuVa
E86SE+hGqz9NvfnuLsp0Fc6Laonj5Wuixu+MUCyZrreHuHVaAFfmaY3bYw0o+ofE
ExCF4dewgwWPU91N7T7GHMK5Wc7bnL1+lP168Pq8ebgGYoDGr8ufkTA5Jr4Fkx8V
8UXKHlaYJK8tuBl/irh1CSx5dSeWEAUxhxLkza/EWVLXkXUNjoCUbO5kxOWHN0/j
9TwCah+s+gJH
=hf8U
-----END PGP SIGNATURE-----

Attachment: pgpJbyxhdvFGR.pgp
Description: PGP signature


--- End Message ---
Reply to: