From: Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr>
To: zimoun <zimon.toutoune@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: Error: cannot close compressed log file
Date: Thu, 12 May 2022 11:34:44 +0200 [thread overview]
Message-ID: <fc3edc53-1105-4a95-75ff-d41d7d015167@iphc.cnrs.fr> (raw)
In-Reply-To: <867d6ts29w.fsf@gmail.com>
Le 10/05/2022 à 19:52, zimoun a écrit :
> Hi,
>
> On Mon, 09 May 2022 at 12:50, Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr> wrote:
>
>> When trying to install a custom package the build stop after downloading
>> the source code with this error:
>>
>> guix install: error: cannot close compressed log file (gzip error = -1)
> Well, I guess this message comes from ’nix/libstore/build.cc’:
>
> --8<---------------cut here---------------start------------->8---
> void DerivationGoal::closeLogFile()
> {
> if (gzLogFile) {
> int err;
> err = gzclose(gzLogFile);
> gzLogFile = NULL;
> if (err != Z_OK) throw Error(format("cannot close compressed log file (gzip error = %1%)") % err);
> }
> --8<---------------cut here---------------end--------------->8---
>
> which seems very unexpected. :-)
>
Yes, none of my partitions were full. I don't know.
After a guix gc it works again, I don't understand what was the problem
as there was no logs :/
Best regards,
Emmanuel Medernach
next prev parent reply other threads:[~2022-05-12 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 10:50 Error: cannot close compressed log file Emmanuel Medernach
2022-05-10 17:52 ` zimoun
2022-05-12 9:34 ` Emmanuel Medernach [this message]
2022-05-13 8:30 ` zimoun
2023-02-08 9:58 ` Emmanuel Medernach
2023-02-08 13:48 ` Simon Tournier
2023-02-08 14:57 ` Emmanuel Medernach
2023-02-09 7:33 ` Emmanuel Medernach
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=fc3edc53-1105-4a95-75ff-d41d7d015167@iphc.cnrs.fr \
--to=emmanuel.medernach@iphc.cnrs.fr \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).