all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Laura Lazzati <laura.lazzati.15@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: SELinux log
Date: Wed, 12 Jun 2019 11:25:09 -0300	[thread overview]
Message-ID: <CAPNLzUORBNi-0FNa1UZnaV2WX+ak4r4OB6N==qTvHKSJVP9EwA@mail.gmail.com> (raw)
In-Reply-To: <87y3277wri.fsf@elephly.net>

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

Yes, I know.  The lines I proposed were untested, though, and some of
> them required adjustment, so I was curious to know what exact changes
> you performed locally and where.

After writing the previous email I have realized I could have done it in a
separate file, right? Like I said, I cloned the repo copied the the
etc/guix-daemon.cil, under /root, added the types/ rules and replaced the
typeattributeset in the "sections" of the file.

>
> > BTW, when they are finished how can I share that file
> > without pushing it?
>
> You can share a git formatted patch as an email attachment.
>
Ok, I will do it then.

>
> When you run “which guix” what does it say?  What does “readlink -f
> $(which guix)” say?
>
I first get the result of evaluating `which guix` saying it is not found,
and then thar readlink has no operand, see:

/usr/bin/which: no guix in
(/home/laura/.local/bin:/home/laura/bin:/usr/share/Modules/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin)
readlink: missing operand

Regards :)

[-- Attachment #2: Type: text/html, Size: 1673 bytes --]

  reply	other threads:[~2019-06-12 14:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04 21:28 SELinux log Laura Lazzati
2019-06-05  9:39 ` Ricardo Wurmus
2019-06-06 14:24   ` Laura Lazzati
2019-06-06 17:58     ` Ricardo Wurmus
2019-06-07  1:46       ` Laura Lazzati
2019-06-07 20:46         ` Ricardo Wurmus
2019-06-07 23:08           ` Laura Lazzati
2019-06-07 23:10             ` Laura Lazzati
2019-06-07 23:12               ` Laura Lazzati
2019-06-08  7:03                 ` Ricardo Wurmus
2019-06-08 14:36                   ` Laura Lazzati
2019-06-08 14:50                     ` Ricardo Wurmus
2019-06-08 14:57                       ` Laura Lazzati
2019-06-08 16:56                         ` Ricardo Wurmus
2019-06-09 16:29                           ` Laura Lazzati
2019-06-10  2:08                             ` Laura Lazzati
2019-06-10  8:12                               ` Ricardo Wurmus
2019-06-11 10:48                                 ` Laura Lazzati
2019-06-11 12:23                                   ` Ricardo Wurmus
2019-06-12  1:58                                     ` Laura Lazzati
2019-06-12  6:42                                       ` Ricardo Wurmus
2019-06-12 13:27                                         ` Laura Lazzati
2019-06-12 13:34                                           ` Ricardo Wurmus
2019-06-12 14:25                                             ` Laura Lazzati [this message]
2019-06-12 20:12                                               ` Ricardo Wurmus
2019-06-12 21:01                                                 ` Laura Lazzati
2019-06-13  6:49                                                   ` Ricardo Wurmus
2019-06-13 17:53                                                     ` Laura Lazzati
2019-06-13 18:52                                                       ` Ricardo Wurmus
2019-06-14 17:24                                                         ` Laura Lazzati
2019-06-16 22:15                                                           ` Laura Lazzati
2019-06-17  1:44                                                             ` Ricardo Wurmus
2019-06-17  3:32                                                               ` Laura Lazzati

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='CAPNLzUORBNi-0FNa1UZnaV2WX+ak4r4OB6N==qTvHKSJVP9EwA@mail.gmail.com' \
    --to=laura.lazzati.15@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.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.
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.