unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: Ethan Blanton <elb@kb8ojh.net>, 62294@debbugs.gnu.org
Subject: bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream
Date: Tue, 04 Apr 2023 19:31:47 +0200	[thread overview]
Message-ID: <867curtuyk.fsf@gmail.com> (raw)
In-Reply-To: <ZCxPC6sPREuu1ipV@jasmine.lan>

Hi Leo,

On Tue, 04 Apr 2023 at 12:23, Leo Famulari <leo@famulari.name> wrote:

>> Well, graft does not seem recommended because it would update to two
>> versions.  And update the package would be a core-updates.
>> 
>> Well, maybe it could be of the current core-updates dance.  Could you
>> send a patch for core-updates?
>
> GnuPG does have a large number of dependent packages, but I'd argue
> that's either 1) a bug or 2) something we should ignore and update
> freely. It's a critical package, and did not used to have such a large
> number of dependents. It's really a problem for the distro if we don't
> allow ourselves to update packages like this freely.

Maybe I am doing something wrong, I get:

--8<---------------cut here---------------start------------->8---
$ guix refresh -l gnupg | cut -f1 -d':'
Building the following 1491 packages would ensure 2880 dependent packages are rebuilt
--8<---------------cut here---------------end--------------->8---

So the impact is ~10% of all the packages.  From a quick look, some
packages are intensive to rebuild, to my knowledge.

Are you proposing to graft?


Cheers,
simon




  reply	other threads:[~2023-04-04 17:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 13:01 bug#62294: gnupg is pinned at 2.2.32 for bug that is fixed upstream Ethan Blanton via Bug reports for GNU Guix
2023-04-04  9:48 ` Simon Tournier
2023-04-04 16:23   ` Leo Famulari
2023-04-04 17:31     ` Simon Tournier [this message]
2023-04-05  1:27       ` Leo Famulari
2023-04-05  6:49         ` Simon Tournier
2023-04-06 13:22           ` Ethan Blanton via Bug reports for GNU Guix
2023-05-07 15:03             ` Maxim Cournoyer
2023-04-04 16:33 ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=867curtuyk.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=62294@debbugs.gnu.org \
    --cc=elb@kb8ojh.net \
    --cc=leo@famulari.name \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).