unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Fredrik Salomonsson <plattfot@posteo.net>
To: help-guix <help-guix@gnu.org>
Subject: Best practice when dealing with a broken package for guix home?
Date: Sun, 14 Jan 2024 23:11:35 +0000	[thread overview]
Message-ID: <87h6jfzf14.fsf@posteo.net> (raw)


Hi,

Using guix home to manage my home environment is awesome.  But one thing
I haven't figured out is a good way of handling when one package is
broken.  As that effectively blocks any upgrade until that it is fixed.

There are generally three things I do in that case:

1) Temporarily remove it from my configuration if I don't use that
program that often.

2) Use `options->transformation` to pick a commit/branch etc that
compiles.

3) Copy an older definition that works to my custom channel, add a
prefix and use that until it is fixed.

If an issue isn't reported I usually send in a bug report with a patch
based on 2 or 3.  But most often someone else have reported it and I'm
just waiting on the patches to land upstream.

My question what is the best practice for this?  It feels that there
should be an easier/quicker way of handling this.  E.g. just tell guix
to use the definition of the current generation for that broken package
and continue with the rest.  Maybe something with the time-machine?

Thanks
-- 
s/Fred[re]+i[ck]+/Fredrik/g


             reply	other threads:[~2024-01-14 23:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-14 23:11 Fredrik Salomonsson [this message]
2024-01-15  1:21 ` Best practice when dealing with a broken package for guix home? Felix Lechner via
2024-01-16 17:50   ` Fredrik Salomonsson
2024-01-17  2:41     ` Felix Lechner via
2024-01-18 11:28       ` Simon Tournier
2024-01-18 17:59         ` Fredrik Salomonsson
2024-01-18 19:18           ` Tomas Volf
2024-01-18 21:54             ` Felix Lechner via
2024-01-15  4:55 ` Carlo Zancanaro
2024-01-16 17:53   ` Fredrik Salomonsson

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=87h6jfzf14.fsf@posteo.net \
    --to=plattfot@posteo.net \
    --cc=help-guix@gnu.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.
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).