all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: 55809@debbugs.gnu.org
Subject: bug#55809: guix challenge with diffoscope fails to clean up temporary directory
Date: Sun, 05 Jun 2022 09:55:36 -0700	[thread overview]
Message-ID: <87o7z73v93.fsf@contorta> (raw)

[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]

When I run a command such as:

  guix challenge --verbose --diff=diffoscope gavl 2>&1 | tee gavl

It works for the most part, producing the diffoscope output, but ends
with a bunch of warnings regarding removing the temporary directory it
created to compare the files:

  warning: failed to delete /tmp/guix-directory.5TokII/share/doc: Permission denied
  warning: failed to delete /tmp/guix-directory.5TokII/share: Permission denied
  warning: failed to delete /tmp/guix-directory.5TokII: Directory not empty

The permissions on the directory are read-only, which is presumably why
it cannot remove them:

  $ ls -latr /tmp/guix-directory.5TokII/
  total 28
  dr-xr-xr-x   3 vagrant vagrant  4096 Dec 31  1969 share
  dr-xr-xr-x   3 vagrant vagrant  4096 Dec 31  1969 lib
  dr-xr-xr-x   3 vagrant vagrant  4096 Dec 31  1969 include
  dr-xr-xr-x   5 vagrant vagrant  4096 Dec 31  1969 .
  drwxrwxrwt 168 root    root    12288 Jun  5 09:28 ..


The warnings are at best distracting, and at worst end up effectively
making it impossible to see the diffoscope output without redirecting to
a file, as the source files can take up many many lines in the scroll
buffer.


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

             reply	other threads:[~2022-06-05 16:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05 16:55 Vagrant Cascadian [this message]
2022-06-13 10:30 ` bug#55809: guix challenge with diffoscope fails to clean up temporary directory Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7z73v93.fsf@contorta \
    --to=vagrant@reproducible-builds.org \
    --cc=55809@debbugs.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.