From: Ricardo Wurmus <rekado@elephly.net>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 41367@debbugs.gnu.org
Subject: bug#41367: cups: "Can't create temporary file"
Date: Mon, 18 May 2020 12:18:54 +0200 [thread overview]
Message-ID: <877dx9h7g1.fsf@elephly.net> (raw)
In-Reply-To: <20200517224218.7039bea4@scratchpost.org>
Danny Milosavljevic <dannym@scratchpost.org> writes:
> Found a previous bug report at
>
> https://lists.gnu.org/archive/html/bug-guix/2018-10/msg00177.html
Alternative URL:
https://issues.guix.gnu.org/33105
I also ran into this problem and making the directory group-writable
fixed it.
--
Ricardo
next prev parent reply other threads:[~2020-05-18 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 18:54 bug#41367: cups: "Can't create temporary file" Danny Milosavljevic
2020-05-17 19:05 ` Efraim Flashner
2020-05-17 20:42 ` Danny Milosavljevic
2020-05-18 10:18 ` Ricardo Wurmus [this message]
2020-05-26 13:58 ` Danny Milosavljevic
2020-05-26 14:04 ` Danny Milosavljevic
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=877dx9h7g1.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=41367@debbugs.gnu.org \
--cc=dannym@scratchpost.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).