unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Laurent Gatto <laurent.gatto@gmail.com>
To: Fredrik Salomonsson <plattfot@posteo.net>
Cc: help-guix@gnu.org
Subject: Re: C++ error
Date: Wed, 13 Nov 2024 22:33:21 +0100	[thread overview]
Message-ID: <CA+uNOziskAQmxd1gD8+J=T5AwMXKWegfV=Sj8LEmoqT-AZjCyg@mail.gmail.com> (raw)
In-Reply-To: <87msi3ne27.fsf@posteo.net>

Hi Fredrik,

> So something else must be affecting yours.  No idea about what that is
> though.  Did you install guix as a package manager on top of an foreign
> distro or is this a Guix System machine?

I should have specified that this is a Guix system machine.

> Also has this ever worked for you?

I am not sure, to be honest. Here, I tried to report a minimally
reproducible example of wider issues, such as documented here [1]. I
don't know if they are directly related though.

[1] https://lists.gnu.org/archive/html/help-guix/2024-08/msg00040.html

> If so you might trying doing a kind
> of git bisect on your packages using `guix package --switch-generation`.
>
> First find a working generation with `guix package --list-generations`,
> pick the generation that is in the middle of the latest broken
> generation and the older working one.  Switch to that, do the test.  If
> it works then the problem is most likely between that generation and the
> latest broken generation.  If not, then the issue is between the current
> generation and the older working one.  Pick the middle generation
> between the working and broken generation and repeat.
>
> Just keep iterating until you find the generation that introduced the
> issue.  Then you can compare with the previous working generation to see
> if there are any differences in packages.

I will try this. If push comes to shove, I could re-install a new Guix
system, reinstall my packages from my manifest and re-configure my
system and home config. This is among the reasons that brought me to
Guix in the first place, so why not make use of it.

Thanks again for taking the time to help.

Laurent

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


  reply	other threads:[~2024-11-13 21:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12  7:41 C++ error Laurent Gatto
2024-11-12 17:54 ` Fredrik Salomonsson
2024-11-12 20:26   ` Laurent Gatto
2024-11-13  0:50     ` Fredrik Salomonsson
2024-11-13  6:49       ` Laurent Gatto
2024-11-13 19:12         ` Fredrik Salomonsson
2024-11-13 21:33           ` Laurent Gatto [this message]
2024-11-14 18:51             ` Fredrik Salomonsson
2024-11-16 10:56               ` Laurent Gatto
2024-11-16 13:19                 ` Laurent Gatto
2024-11-18 18:49                   ` Fredrik Salomonsson
2024-11-21  8:50                     ` Laurent Gatto

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='CA+uNOziskAQmxd1gD8+J=T5AwMXKWegfV=Sj8LEmoqT-AZjCyg@mail.gmail.com' \
    --to=laurent.gatto@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=plattfot@posteo.net \
    /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).