GNU bug report logs - #76151
[PATCH] gnu: jsoncpp: Update to 1.9.6.

Previous Next

To reply to this bug, email your comments to 76151 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Andy Tai <atai <at> atai.org>
To: guix-patches <at> gnu.org
Subject: [PATCH] gnu: jsoncpp: Update to 1.9.6.
Date: Sat, 8 Feb 2025 18:48:53 -0800

[Message part 1 (text/plain, inline)]

[0001-gnu-jsoncpp-Update-to-1.9.6.patch (text/x-patch, attachment)]

Message #8 received at 76151 <at> debbugs.gnu.org (full text, mbox):

From: Sharlatan Hellseher <sharlatanus <at> gmail.com>
To: 76151 <at> debbugs.gnu.org
Cc: andreas <at> enge.fr, z572 <at> z572.online, ludo <at> gnu.org, janneke <at> gnu.org
Subject: [PATCH] gnu: jsoncpp: Update to 1.9.6.
Date: Tue, 18 Feb 2025 22:38:43 +0000

[Message part 1 (text/plain, inline)]

Hi,

It's for core-packaged-team ;-)

--8<---------------cut here---------------start------------->8---
guix refresh --list-dependent jsoncpp 
Building the following 10784 packages would ensure 24531 dependent packages are rebuilt
--8<---------------cut here---------------end--------------->8---

---
Oleg

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 76151 <at> debbugs.gnu.org (full text, mbox):

From: Greg Hogan <code <at> greghogan.com>
To: Sharlatan Hellseher <sharlatanus <at> gmail.com>
Cc: 76151 <at> debbugs.gnu.org, andreas <at> enge.fr, z572 <at> z572.online, ludo <at> gnu.org,
 janneke <at> gnu.org
Subject: Re: [bug#76151] [PATCH] gnu: jsoncpp: Update to 1.9.6.
Date: Thu, 27 Feb 2025 11:48:34 -0500

On Tue, Feb 18, 2025 at 5:39 PM Sharlatan Hellseher
<sharlatanus <at> gmail.com> wrote:
>
> Hi,
>
> It's for core-packaged-team ;-)
>
> --8<---------------cut here---------------start------------->8---
> guix refresh --list-dependent jsoncpp
> Building the following 10784 packages would ensure 24531 dependent packages are rebuilt
> --8<---------------cut here---------------end--------------->8---
>
> ---
> Oleg

The package is not registered to a team, so can it not be applied to
any team branch or a feature branch?

--8<---------------cut here---------------start------------->8---
$ guix show jsoncpp | recsel -p name,version,location
name: jsoncpp
version: 1.9.5
location: gnu/packages/serialization.scm:608:2

name: jsoncpp
version: 1.7.3
location: gnu/packages/serialization.scm:631:2

$ grep gnu/packages/serialiation.scm etc/teams.scm
--8<---------------cut here---------------end--------------->8---

Greg

Message #14 received at 76151 <at> debbugs.gnu.org (full text, mbox):

From: Aaron Covrig <aaron.covrig.us <at> ieee.org>
To: 76151 <at> debbugs.gnu.org
Date: Fri, 7 Mar 2025 17:30:44 -0500

[Message part 1 (text/plain, inline)]

I believe what they mean is that because this package is depended on by
so many other packages, it needs to be upgraded a bit differently. This
is done to prevent massive rebuilds for substitute servers and to
reduce the risk of breakage.

From: https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html
=2D-8<---------------cut here---------------start------------->8---
more than 1,800 dependent packages
core-updates branch (may include major and potentially disruptive
changes). This branch is intended to be merged in master every 6 months
or so. This branch is not expected to be buildable or usable until late
in its development process.
=2D-8<---------------cut here---------------end--------------->8---

What I don't know, is the correct process is for this type of
submission.  I'm seeing a `core-updates-glibc-2.39` branch, but
presumably that is only for glibc; does one need special privileges to
create a new branch or do we just submit the patch based off the master
branch as a patch to a branch that doesn't exist?

=2D-8<---------------cut here---------------start------------->8---
git branch -a | grep -a core
  remotes/origin/core-packages-team
  remotes/origin/core-packages-team-old
  remotes/origin/core-packages-team-old2
  remotes/origin/core-updates-glibc-2.39
=2D-8<---------------cut here---------------end--------------->8---

v/r,

Aaron

P.S.
I just noticed that the latest version of the manual drops the package
number branch definitions; I'm not sure if this was moved to a
different section now; accidentally deleted; or if it is going to be
dropped as a requirement. See:
https://guix.gnu.org/manual/devel/en/html_node/Submitting-Patches.html
https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html

[Message part 2 (application/pgp-signature, inline)]

Message #17 received at 76151 <at> debbugs.gnu.org (full text, mbox):

From: Greg Hogan <code <at> greghogan.com>
To: Aaron Covrig <aaron.covrig.us <at> ieee.org>
Cc: 76151 <at> debbugs.gnu.org
Subject: Re: [bug#76151] (no subject)
Date: Fri, 7 Mar 2025 19:07:58 -0500

On Fri, Mar 7, 2025 at 5:32 PM Aaron Covrig via Guix-patches via
<guix-patches <at> gnu.org> wrote:
>
> I just noticed that the latest version of the manual drops the package
> number branch definitions; I'm not sure if this was moved to a
> different section now; accidentally deleted; or if it is going to be
> dropped as a requirement. See:
> https://guix.gnu.org/manual/devel/en/html_node/Submitting-Patches.html
> https://guix.gnu.org/manual/en/html_node/Submitting-Patches.html

Yes, "manual" is from the last release (in 2022) and "manual/devel" is
up-to-date.

I was going to suggest that we look into why there are so many
dependent packages, and I did, and it is cmake-bootstrap, which I am
working on updating in #70031 and in an imminent c++ branch. So I will
integrate this there, and we should pin cmake to this version of
jsoncpp.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.