all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Timmy Douglas <mail@timmydouglas.com>
Cc: 67618@debbugs.gnu.org, Raghav Gururajan <rg@raghavgururajan.name>
Subject: [bug#67618] [PATCH]  gnu: harfbuzz: Update to 8.3.0.
Date: Mon, 04 Dec 2023 20:19:49 +0100	[thread overview]
Message-ID: <d5f62efdaa371ba9a7ee7e1c35d6c318f01f750b.camel@gmail.com> (raw)
In-Reply-To: <87cyvmro2g.fsf@gmail.com>

Am Montag, dem 04.12.2023 um 10:21 -0500 schrieb Maxim Cournoyer:
> Hello,
> 
> Timmy Douglas <mail@timmydouglas.com> writes:
> 
> > I was trying to install some software and found that it depended on
> > a newer version of harfbuzz.  I wasn't sure how to verify this
> > doesn't cause issues with other packages that have this as a
> > dependency.
> > Thanks!
> 
> You can find dependents with 'guix refresh -l harfbuzz' and then
> attempt to rebuild them with --keep-going (-k) to see how many of
> them fails.
> 
> I have a set of dirty scripts to help automate these tasks [0].
Adding to that, harfbuzz is a well known GNOME world rebuild (being a
dependency of Pango), so I'll try to build pango and hopefully gtk from
it, but we'll defer this to the gnome-team branch :)

Cheers




  reply	other threads:[~2023-12-04 19:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04  7:11 [bug#67618] [PATCH] gnu: harfbuzz: Update to 8.3.0 Timmy Douglas via Guix-patches via
2023-12-04 15:21 ` Maxim Cournoyer
2023-12-04 19:19   ` Liliana Marie Prikler [this message]
2023-12-06  5:32     ` Timmy Douglas via Guix-patches via
2023-12-06 17:48       ` Maxim Cournoyer
2023-12-19 22:57       ` bug#67618: " Liliana Marie Prikler

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

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

  git send-email \
    --in-reply-to=d5f62efdaa371ba9a7ee7e1c35d6c318f01f750b.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=67618@debbugs.gnu.org \
    --cc=mail@timmydouglas.com \
    --cc=maxim.cournoyer@gmail.com \
    --cc=rg@raghavgururajan.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.