From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <help-guix-bounces+larch=yhetil.org@gnu.org>
Received: from mp2.migadu.com ([2001:41d0:303:e224::])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	by ms8.migadu.com with LMTPS
	id OKPcBjVnqWVhAAEAe85BDQ:P1
	(envelope-from <help-guix-bounces+larch=yhetil.org@gnu.org>)
	for <larch@yhetil.org>; Thu, 18 Jan 2024 19:00:21 +0100
Received: from aspmx1.migadu.com ([2001:41d0:303:e224::])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	by mp2.migadu.com with LMTPS
	id OKPcBjVnqWVhAAEAe85BDQ
	(envelope-from <help-guix-bounces+larch=yhetil.org@gnu.org>)
	for <larch@yhetil.org>; Thu, 18 Jan 2024 19:00:21 +0100
X-Envelope-To: larch@yhetil.org
Authentication-Results: aspmx1.migadu.com;
	dkim=pass header.d=posteo.net header.s=2017 header.b=j3eZJTqg;
	dmarc=pass (policy=none) header.from=posteo.net;
	spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org;
	s=key1; t=1705600821;
	h=from:from:sender:sender:reply-to:subject:subject:date:date:
	 message-id:message-id:to:to:cc:mime-version:mime-version:
	 content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references:list-id:list-help:
	 list-unsubscribe:list-subscribe:list-post:dkim-signature;
	bh=Ui5rogMVRaVmsgGihQe9bNjppFxVM4ZKpnO/QqcmfaM=;
	b=UlnkkGzlX7BEioeINGudN9D7ytDBOJ7w5qPLBgShAhAzUQpYGMxRen/+XwQJCGQrM7fIJC
	LLzQRzWxJ54+RYUowB96Xanfd77YTGt8uG+RA91Aksf+Y8zpupR9z7MLzMH9TwVEk2uUZY
	gnTVGdQCt5AIZxeJTeblf9AI0w3fCysZfESy2T3SjWTdb+kWHwzV+o3eXWBy8ML/jSieC+
	JttMpw3Fyi2Jy+3P+Fcl9tRx6lYbRlX5rgsmsPBp+A0LBxfSz43UYozFwPuf6hoJCDCCIO
	NunflDX5dr2tIkwy4360WmHWV0twJDZLOt8Tbh1jn/rdc5Vo7J06rAJRrFaIRw==
ARC-Authentication-Results: i=1;
	aspmx1.migadu.com;
	dkim=pass header.d=posteo.net header.s=2017 header.b=j3eZJTqg;
	dmarc=pass (policy=none) header.from=posteo.net;
	spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"
ARC-Seal: i=1; s=key1; d=yhetil.org; t=1705600821; a=rsa-sha256; cv=none;
	b=B+FTVaHwerNp4875yDgF7XEFuSflzLSvKp2tZ50csm1+rnhvPfSUxtmLxqc1F8qF050g6T
	1ulITscJDQ8NAUBJF9Kw6I5mFZ7M6GV5FTXPTLxo0LqAa26GEL4FSyeXYXoOn9eys2AlqR
	fgsRTmENt6+Hvwnk4U/o+mTEy78jj4GcSyLFMmYGG8ZU43+FDdaD1OJIQ2uzsWzI3herpw
	+qmQpbha4v8F4KBAuT1Pf7o+DM78ht22Fs8m/gCnzqmJdf8ICttPMDVy3F5JWNH9jfVryG
	RAKyM5H9jgw7CWmY7Xw/zM9KS27f+7CPXPpU0JtLzueia5JpD+Had/u8XfMcJQ==
Received: from lists.gnu.org (lists.gnu.org [209.51.188.17])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by aspmx1.migadu.com (Postfix) with ESMTPS id 00BE31A29E
	for <larch@yhetil.org>; Thu, 18 Jan 2024 19:00:21 +0100 (CET)
Received: from localhost ([::1] helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <help-guix-bounces@gnu.org>)
	id 1rQWfu-0004aR-VH; Thu, 18 Jan 2024 12:59:34 -0500
Received: from eggs.gnu.org ([2001:470:142:3::10])
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <plattfot@posteo.net>)
 id 1rQWfs-0004a1-V7
 for help-guix@gnu.org; Thu, 18 Jan 2024 12:59:32 -0500
Received: from mout02.posteo.de ([185.67.36.66])
 by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <plattfot@posteo.net>)
 id 1rQWfq-0000kC-Iq
 for help-guix@gnu.org; Thu, 18 Jan 2024 12:59:32 -0500
Received: from submission (posteo.de [185.67.36.169]) 
 by mout02.posteo.de (Postfix) with ESMTPS id 00CFF240103
 for <help-guix@gnu.org>; Thu, 18 Jan 2024 18:59:26 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017;
 t=1705600767; bh=9+/D2QkjNz9/2E0HVdrFGsDOoWsT892PS1KybzCLbow=;
 h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:
 Content-Transfer-Encoding:From;
 b=j3eZJTqgi06B5GDBI+vOmUMCT1OlsNCrEIgzXQBaMNJjAm/PxqI61HPfMOkGO9xMF
 baQTJHldiiZDR9F9xdmr5VyntII8+NlKQ6As13rgtHz8kSrBAFA3p5MyTIAKy5Mprk
 d9Tgcf514OybxWhrWz4xcTo3s9Rb38gKmtGZ8OGQADBYw92UzEwYW1yWoWJJUfflHP
 dL65O9aqa6g0zg5ufcL7hlXFH/iw0me0wEuUdxrMv5lsQhQQ2CttBOIMM9AagRtuKG
 KVv9Lib6E2PJTDuPV/MXFdMn0MrSkiB26uXQZSmCvLdjrPS9BCfCbffPmGyWa5cfc/
 wlZ7Js/CV6Y1w==
Received: from customer (localhost [127.0.0.1])
 by submission (posteo.de) with ESMTPSA id 4TG9Vj43Njz9rxG;
 Thu, 18 Jan 2024 18:59:25 +0100 (CET)
From: Fredrik Salomonsson <plattfot@posteo.net>
To: Simon Tournier <zimon.toutoune@gmail.com>, Felix Lechner
 <felix.lechner@lease-up.com>, help-guix <help-guix@gnu.org>
Subject: Re: Best practice when dealing with a broken package for guix home?
In-Reply-To: <87cytyj2xb.fsf@gmail.com>
References: <87h6jfzf14.fsf@posteo.net> <87y1cr2xyj.fsf@lease-up.com>
 <87sf2x2mmu.fsf@d2.com> <87r0ig1y2b.fsf@lease-up.com>
 <87cytyj2xb.fsf@gmail.com>
Date: Thu, 18 Jan 2024 17:59:23 +0000
Message-ID: <875xzq4j5w.fsf@d2.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=185.67.36.66; envelope-from=plattfot@posteo.net;
 helo=mout02.posteo.de
X-Spam_score_int: -43
X-Spam_score: -4.4
X-Spam_bar: ----
X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
 RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001,
 SPF_HELO_NONE=0.001, SPF_PASS=-0.001,
 T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-BeenThere: help-guix@gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <help-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-guix>,
 <mailto:help-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/help-guix>
List-Post: <mailto:help-guix@gnu.org>
List-Help: <mailto:help-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-guix>,
 <mailto:help-guix-request@gnu.org?subject=subscribe>
Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org
Sender: help-guix-bounces+larch=yhetil.org@gnu.org
X-Migadu-Flow: FLOW_IN
X-Migadu-Country: US
X-Migadu-Spam-Score: -9.40
X-Spam-Score: -9.40
X-Migadu-Queue-Id: 00BE31A29E
X-Migadu-Scanner: mx12.migadu.com
X-TUID: KnPvuI+jhgs4

Hi,

Simon Tournier <zimon.toutoune@gmail.com> writes:

> Hi,
>
> On mar., 16 janv. 2024 at 18:41, Felix Lechner via <help-guix@gnu.org> wr=
ote:
>> On Tue, Jan 16 2024, Fredrik Salomonsson wrote:
>>
>>>  Or how do you deal with cases when they happen?
>>
>> I maintain a custom Guix with patches on top, plus my own channel.
>
> Well, for what it is worth, I think the good practise is to send
> contributions when something broken on master is fixed and not keep the
> fix in your own patched Guix version.

Agreed.  I should have probably worded my initial question a bit better.
I assumed that the package has already been reported by either myself or
someone else and that patches for it to be fixed was already submitted.
What prompted me to ask this question was [mpv-mpris][0].  Since it's
been broken since at least Dec 26 2023 and is the one that is holding up
my upgrade.  And I'm not trying to single anyone out, I totally
understand things take time especially during holidays.  I just got
thinking if there is a good practice to workaround it while I wait for
it to be fixed.  As doing any of my usual workarounds would require a
bit of work as it was mpv that changed and broke mpv-mpris.

[0] https://issues.guix.gnu.org/68044

> That said, I do not use =E2=80=9Cguix home=E2=80=9D so my way probably do=
es not make
> sense.  What I do is that I have separated manifest files.  For
> instance, I have emacs.scm for my Emacs stuff, ocaml.scm for my OCaml
> stuff, compiler.scm for some compilers that I use, base.scm for all the
> basic stuff as coreutils etc.
>
> When one package is broken, it impacts only one manifest.  So it
> mitigates the issue for upgrading.

I did this before, and while it did helped reduce the impact of a broken
package.  It did complicate my upgrade as I needed to have my own update
script etc.  What I like with guix home is that it can essentially
reproduce my home environment on any of my machines by both installing
the packages needed and configuration.  Which is a huge time saver as I
had the issue when I used Arch that I never really got my home
environment to work the same on my desktop and laptop.

>
> What I am not fully happy is that =E2=80=9Cguix weather=E2=80=9D does not=
 have a
> codified exit status.  It had been discussed [1] but no consensus.  It
> would ease:
>
>   guix weather -m path/to/manifests/foo.scm \
>     && guix upgrade -p path/to/profiles/foo
>
> Cheers,
> simon
>
>
> 1: guix weather exit status?
> Leo Famulari <leo@famulari.name>
> Thu, 08 Jul 2021 16:35:03 -0400
> id:YOdhd7FfMOvKjTQe@jasmine.lan
> https://lists.gnu.org/archive/html/guix-devel/2021-07
> https://yhetil.org/guix/YOdhd7FfMOvKjTQe@jasmine.lan

Didn't know that about guix weather.  I don't really use it that much as
my desktop is generally powerful enough to just chew threw packages that
lacks substitutes.  And I usually starts by upgrading that before moving
on to my laptop and other machines running guix.

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