From: ng0 <ng0@pragmatique.xyz>
To: 27311@debbugs.gnu.org
Subject: bug#27311: Acknowledgement (Enlightenment: 'cpufreq binary needs suid or has to be owned by root')
Date: Sun, 11 Jun 2017 16:35:19 +0000 [thread overview]
Message-ID: <20170611163519.cbzr2s2xanftl33c@abyayala> (raw)
In-Reply-To: <handler.27311.B.149710706324063.ack@debbugs.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
GNU bug Tracking System transcribed 0.7K bytes:
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> bug-guix@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 27311@debbugs.gnu.org.
>
> Please do not send mail to help-debbugs@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 27311: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=27311
> GNU Bug Tracking System
> Contact help-debbugs@gnu.org with problems
>
It seems as if Nix has a solution to some of the problems I encounter
with Enlightenment. I'll try and fix most of the bugs I reported.
--
ng0
OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-11 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 15:03 bug#27311: Enlightenment: 'cpufreq binary needs suid or has to be owned by root' ng0
[not found] ` <handler.27311.B.149710706324063.ack@debbugs.gnu.org>
2017-06-11 16:35 ` ng0 [this message]
2017-06-11 17:25 ` bug#27311: Acknowledgement (Enlightenment: 'cpufreq binary needs suid or has to be owned by root') ng0
2017-06-21 8:00 ` Ricardo Wurmus
2018-08-05 9:44 ` Efraim Flashner
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=20170611163519.cbzr2s2xanftl33c@abyayala \
--to=ng0@pragmatique.xyz \
--cc=27311@debbugs.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.
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.