From: Caleb Herbert <csh@bluehome.net>
To: help-guix@gnu.org
Subject: Re: chromebook-ucm-conf
Date: Sat, 02 Dec 2023 12:12:09 -0600 [thread overview]
Message-ID: <8734wkiidi.fsf@bluehome.net> (raw)
In-Reply-To: 1b7ba9f1-6c62-8a45-3b2b-795beefdcc40@bluehome.net
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
Hi Guix,
I still need help getting audio to work. I recently updated the code to
the package.
I'm still trying to package these ALSA configs, but alsa-lib might need
to be updated.
https://codeberg.org/csh/guix-channel/src/branch/main/kolev/packages/linux.scm
I haven't packaged anything before. I don't know how to get this whole
thing to work.
Thanks,
--
Caleb Herbert
https://bluehome.net/csh/
OpenPGP fingerprint: 631C C434 A56B 5CBD FF21 2346 9764 3795 FA3E 4BCE
What's a fingerprint? https://emailselfdefense.fsf.org/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next reply other threads:[~2023-12-02 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 18:12 Caleb Herbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-20 18:28 chromebook-ucm-conf Caleb Herbert
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=8734wkiidi.fsf@bluehome.net \
--to=csh@bluehome.net \
--cc=help-guix@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.
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).