From: phodina <phodina@protonmail.com>
To: phodina <phodina@protonmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix package: error: unsupported manifest format
Date: Mon, 01 Nov 2021 21:56:31 +0000 [thread overview]
Message-ID: <o0Fs_-uhYblQgaberC9Kx8-pe8Bl0pxJhPBZfjxl0OY2fzZIYvlWSEsd_hLHFNFlhLOCZYbCH_6GOKU7kvZHJZxWPcg5mHlnTt22nLNsPa8=@protonmail.com> (raw)
In-Reply-To: <qA7xO7SZrkWITkZqtUucBXQ-1pEOEVOFRNzXquK9RXLANRSKfuuZt8v5zjUY2553qZDw0HTHjOyxE7YI1sv9LGpTtxChkJbbFLl-n03nEQU=@protonmail.com>
On Monday, November 1st, 2021 at 6:09 PM, phodina via <help-guix@gnu.org> wrote:
> Hi,
>
> I've rebooted my laptop with Guix System installed there and I'm faced with this dreadful message when I attempt to install package with guix package -i PKG:
>
> guix package: error: unsupported manifest format
>
> I've tried to do guix pull, which succeeded but I'm still unable to do anything. Also my profile is empty and I have to go to VT as some packages are missing for X session to run.
>
> What is a proper way to resolve this issue?
>
> Does it mean there was a change in the format between Guix update and now the old running Guix daemon is unable to read the new format?
>
> My current Guix version is
>
> 7af3b822178782d6598865e1d6a780a756dd0cb3
So the issue is solved.
The problem was that the symlink:
ls /var/guix/profiles/per-user/user/guix-profile -al
lrwxrwxrwx 1 user users 20 Nov 1 22:35 /var/guix/profiles/per-user/user/guix-profile -> guix-profile-85-link
It pointed to a profile, where the contents of file manifest were empty. Removing this profile and changing the symlink to the older profile solved the problem after relogin.
Though it still make me curious as I don't understand how this could happen.
prev parent reply other threads:[~2021-11-01 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 17:09 guix package: error: unsupported manifest format phodina via
2021-11-01 21:56 ` phodina [this message]
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='o0Fs_-uhYblQgaberC9Kx8-pe8Bl0pxJhPBZfjxl0OY2fzZIYvlWSEsd_hLHFNFlhLOCZYbCH_6GOKU7kvZHJZxWPcg5mHlnTt22nLNsPa8=@protonmail.com' \
--to=phodina@protonmail.com \
--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).