unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Nathan Dehnel <ncdehnel@gmail.com>
Cc: 42118@debbugs.gnu.org
Subject: bug#42118: Editing pulseaudio config file fails with "No such file or directory"
Date: Tue, 30 Jun 2020 12:43:32 +0200	[thread overview]
Message-ID: <8104d8d87ddfcd1572dd6e0dd553a2fcaa7483f0.camel@student.tugraz.at> (raw)
In-Reply-To: <CAEEhgEsW4VTRPXMkspfE9vcP5DNZCBV-7h2cxcbJFgEoY7pk6Q@mail.gmail.com>

Am Dienstag, den 30.06.2020, 05:22 -0500 schrieb Nathan Dehnel:
> Thanks for the tip. Do I have to put the entire file inside a string
> in guix? It's quite long.
mixed-text-file allows you to split the string into multiple parts, but
that is essentially the idea, yes.  There are of course other ways of
building it, but it is your task to ensure, that those end up with the
result you want.  In my personal opinion, explicit coding tends to be
best suited to accomplish this.

> https://guix.gnu.org/manual/en/html_node/G_002dExpressions.html
> 
> It mentions "local-file" so I did this:
>                         (script-file (local-file
> "/home/nathan/.config/pulse/default.pa"))))))
> 
> guix system reconfigure then completed, but pulseaudio does not seem
> to reflect the change in settings.
That should work up to a certain extent – what this basically does is
copy your local default.pa into the Guix store and then
/etc/pulse/default.pa is a symlink to that file in the Guix store. 
Depending on the content of default.pa, that may not actually be what
you want, but unless you're doing very weird things in there, it may
also be a perfectly valid configuration.
Can you check, that /etc/pulse/default.pa is indeed what you want it to
be?  IIRC, you may have to reboot for /etc to change.

Regards, Leo





  parent reply	other threads:[~2020-06-30 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29  7:34 bug#42118: Editing pulseaudio config file fails with "No such file or directory" Nathan Dehnel
2020-06-29 10:27 ` Leo Prikler
     [not found]   ` <CAEEhgEsW4VTRPXMkspfE9vcP5DNZCBV-7h2cxcbJFgEoY7pk6Q@mail.gmail.com>
2020-06-30 10:43     ` Leo Prikler [this message]
     [not found]       ` <CAEEhgEttgmXiegOkxptmPDGPSmuXJRDPpvmDkJPgUWzkn_-kXA@mail.gmail.com>
2020-07-01  8:15         ` Leo Prikler
     [not found]           ` <CAEEhgEvV5CFpE6aG9fnKopDd1MeXCMHZ_0bt_3DevNfNA4eJiQ@mail.gmail.com>
2020-07-01 10:57             ` Leo Prikler
2020-07-01 11:52               ` Nathan Dehnel
2020-07-01 12:01               ` Ricardo Wurmus
2020-07-07  2:59                 ` Nathan Dehnel
2022-09-29  0:39                   ` Maxim Cournoyer

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=8104d8d87ddfcd1572dd6e0dd553a2fcaa7483f0.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=42118@debbugs.gnu.org \
    --cc=ncdehnel@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.
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).