unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: jgart <jgart@dismail.de>, 54264@debbugs.gnu.org
Subject: [bug#54264] [PATCH] gnu: socat: Update to 1.7.4.3.
Date: Tue, 08 Mar 2022 17:29:26 +0100	[thread overview]
Message-ID: <87tuc84dcp.fsf_-_@gnu.org> (raw)
In-Reply-To: <handler.54264.D54264.16467474782286.notifdone@debbugs.gnu.org> (GNU bug Tracking System's message of "Tue, 08 Mar 2022 13:52:02 +0000")

Hello,

help-debbugs@gnu.org (GNU bug Tracking System) skribis:

> Patch pushed as 3cd42883c4ad693ed1f79c6be35e1aa3e010e10a.

I reverted it in 0e91da1d34250650f7549595867e1be4f8e93fd8 because it
triggered a massive rebuild:

--8<---------------cut here---------------start------------->8---
$ guix refresh -l socat
Building the following 6713 packages would ensure 13327 dependent
packages are rebuilt: […]
--8<---------------cut here---------------end--------------->8---

This is because GnuTLS depends on socat:

  guix graph -t reverse-package socat -M2 | xdot -f fdp -

So I think this should go to core-updates, or we could define a variant
for this new version but leave the ‘socat’ variable unchanged.

Thoughts?

Ludo’.




  parent reply	other threads:[~2022-03-08 16:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-05 17:24 [bug#54264] [PATCH] gnu: socat: Update to 1.7.4.3 jgart via Guix-patches via
2022-03-08 13:50 ` bug#54264: " Guillaume Le Vaillant
     [not found] ` <handler.54264.D54264.16467474782286.notifdone@debbugs.gnu.org>
2022-03-08 16:29   ` Ludovic Courtès [this message]
2022-03-08 16:42     ` [bug#54264] " Guillaume Le Vaillant
2022-03-11  9:58       ` bug#54264: " Guillaume Le Vaillant
2022-03-11 21:03         ` [bug#54264] " jgart via Guix-patches via

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=87tuc84dcp.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=54264@debbugs.gnu.org \
    --cc=glv@posteo.net \
    --cc=jgart@dismail.de \
    /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).