From: Divya <divya@subvertising.org>
To: Kaelyn <kaelyn.alexi@protonmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Using Pipewire for PulseAudio and JACK in Guix
Date: Sat, 02 Nov 2024 17:18:14 +0000 [thread overview]
Message-ID: <45DA1653-EDFD-4D67-BF67-52802C09474C@subvertising.org> (raw)
In-Reply-To: <bgt8dl3twiBThWbrkOaGe7jF2Xr_QgPrmlD7ff_ikbwOTK5FqOM7DsdmEO7eKJdqDzDO7DrmxouomyB0YuFkd0xWTr1Tw5NIt-v9ztuUpLc=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 3470 bytes --]
On 2 November 2024 16:08:32 GMT, Kaelyn <kaelyn.alexi@protonmail.com> wrote:
>
>
>
>
>
>On Saturday, November 2nd, 2024 at 6:36 AM, Divya Ranjan via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> wrote:
>
>>
>>
>> Hello Ricardo,
>>
>> Ricardo Wurmus rekado@elephly.net writes:
>>
>> > Hi,
>> >
>> > > Also, I saw that jack_mixer0 is missing from the main guix package
>> > > repository, I’d like to have that added. Since its the most minimal
>> > > and straightforward JACK mixer I’ve been using over the last 4-5
>> > > years. Since its a Python + C application mostly, so one shouldn’t
>> > > have any major issues packaging it? Any advice would be great.
>> >
>> > have you attempted to package it yet? I can help with review and
>> > testing.
>>
>>
>> Indeed, I have. A package definition can be found at my repository0, currently most things seem to be working, but I get this error while doing `guix package --install-from-file=audio.scm`:
>>
>> #+begin_src shell
>> $ guix package --install-from-file=/home/divya/.config/guix/packages/audio.scm
>> The following package will be installed:
>> jack-mixer 19
>>
>> substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'... 100.0%
>> substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
>> The following derivation will be built:
>> /gnu/store/1cnsydazihgzs0wv6l6mh4cmm894q2l1-jack-mixer-19.drv
>>
>> 65.4 MB will be downloaded
>> python-pygobject-3.47.0 239KiB 311KiB/s 00:01 ▕██████████████████▏ 100.0%
>> gcc-11.4.0 28.2MiB 4.2MiB/s 00:07 ▕██████████████████▏ 100.0%
>> gcc-toolchain-11.4.0 6KiB 68KiB/s 00:00 ▕██████████████████▏ 100.0%
>> building /gnu/store/1cnsydazihgzs0wv6l6mh4cmm894q2l1-jack-mixer-19.drv...
>> 0% 'install' ▕ ▏builder for `/gnu/store/1cnsydazihgzs0wv6l6mh4cmm894q2l1-jack-mixer-19.drv' failed with exit code 1 build of /gnu/store/1cnsydazihgzs0wv6l6mh4cmm894q2l1-jack-mixer-19.drv failed View build log at '/var/log/guix/drvs/1c/nsydazihgzs0wv6l6mh4cmm894q2l1-jack-mixer-19.drv.gz'. guix package: error: build of` /gnu/store/1cnsydazihgzs0wv6l6mh4cmm894q2l1-jack-mixer-19.drv' failed
>> #+end_src
>>
>> I’ve attached the build logs, let me know if you have an idee about what’s failing and maybe test the package definition yourself.
>
>Hi,
>
>I just glanced at the build log you attached. The first thing I saw was meson erroring from an unhandled Python error, and scrolling up quickly revealed the error. It looks like your install phase is failing because it is trying to write outside of the store:
>
> PermissionError: [Errno 13] Permission denied: '/etc/xdg'
>
>It looks like that project's meson.build hard-codes a reference to a path under /etc/xdg at https://github.com/jack-mixer/jack_mixer/blob/main/meson.build#L49
>
>Cheers,
>Kaelyn
>
>>
>>
>> Also, do I need to take the discussion of this package in a separate thread?
>>
>> 0: https://codeberg.org/divyaranjan/dotfiles/src/branch/master/.config/guix/packages/audio.scm
>>
>> Regards,
>>
>> --
>> Divya Ranjan,
>> Philosophy, Mathematics, Libre Software.
Hello Kaelyn,
Thanks for pointing it out, indeed its trying to write into /etc/xdg.
How does one handle such a case when packaging in Guix?
Regards,
Divya Ranjan
[-- Attachment #2: Type: text/html, Size: 4620 bytes --]
next prev parent reply other threads:[~2024-11-02 17:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 13:27 Using Pipewire for PulseAudio and JACK in Guix Divya Ranjan via Development of GNU Guix and the GNU System distribution.
2024-10-28 13:46 ` Divya Ranjan via Development of GNU Guix and the GNU System distribution.
2024-11-01 7:31 ` Ricardo Wurmus
2024-11-02 13:36 ` Divya Ranjan via Development of GNU Guix and the GNU System distribution.
2024-11-02 16:08 ` Kaelyn via Development of GNU Guix and the GNU System distribution.
2024-11-02 17:18 ` Divya [this message]
2024-11-02 23:00 ` Ricardo Wurmus
2024-11-03 6:18 ` Divya Ranjan via Development of GNU Guix and the GNU System distribution.
2024-11-03 11:50 ` Ricardo Wurmus
2024-11-13 13:10 ` divya
2024-12-15 11:26 ` Maxim Cournoyer
2024-11-07 9:41 ` Divya Ranjan via Development of GNU Guix and the GNU System distribution.
2024-10-31 18:19 ` Divya
-- strict thread matches above, loose matches on Subject: below --
2024-11-01 13:11 Noé Lopez via Development of GNU Guix and the GNU System distribution.
2024-11-03 6:21 ` Divya Ranjan via Development of GNU Guix and the GNU System distribution.
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=45DA1653-EDFD-4D67-BF67-52802C09474C@subvertising.org \
--to=divya@subvertising.org \
--cc=guix-devel@gnu.org \
--cc=kaelyn.alexi@protonmail.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).