unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Mark H Weaver" <mhw@netris.org>, "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: guix-devel@gnu.org
Subject: Re: gnu: imagemagick/fixed: Redirect old sonames to new sonames.
Date: Thu, 18 Mar 2021 14:08:01 +0100	[thread overview]
Message-ID: <8635wsvccu.fsf@gmail.com> (raw)
In-Reply-To: <87y2eksjyc.fsf@netris.org>

Hi Mark,

On Thu, 18 Mar 2021 at 08:51, Mark H Weaver <mhw@netris.org> wrote:

> This is really nasty.  Why is imagemagick grafted, anyway?  I think it
> can simply be updated without causing many rebuilds, no?

--8<---------------cut here---------------start------------->8---
$ guix refresh -l imagemagick@6.9.11-48 | cut -f1 -d':'
Building the following 1269 packages would ensure 2404 dependent packages are rebuilt

$ guix refresh -l imagemagick@6.9.12-2g | cut -f1 -d':'
Building the following 2 packages would ensure 2 dependent packages are rebuilt

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

I am not in the graft dancing but I suspect something wrong here.  I
have never checked but intuitively, I thought that graft has the
priority so “guix refresh -l imagemagick” should display all the
dependents.  Note it is the same story as zstd.


Cheers,
simon



  reply	other threads:[~2021-03-18 13:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 12:51 gnu: imagemagick/fixed: Redirect old sonames to new sonames Mark H Weaver
2021-03-18 13:08 ` zimoun [this message]
2021-03-18 13:40 ` Mark H Weaver
2021-03-18 19:44   ` Leo Famulari
2021-03-20  0:14     ` Mark H Weaver
2021-03-20 18:28       ` Leo Famulari
2021-03-20 20:26         ` Mark H Weaver
2021-03-27  9:36       ` Mark H Weaver
2021-03-27 18:06         ` 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=8635wsvccu.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=lle-bout@zaclys.net \
    --cc=mhw@netris.org \
    /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).