From: Kozo <gitlabcanada@runbox.com>
To: 42043@debbugs.gnu.org
Subject: bug#42043: Acknowledgement ([BUG] Can not update nix-channels after adding)
Date: Thu, 25 Jun 2020 13:56:59 -0600 [thread overview]
Message-ID: <f2aa91ac7f8982b5423602d7c3d1d4ab1eff7ef8.camel@runbox.com> (raw)
In-Reply-To: <handler.42043.B.159310142711067.ack@debbugs.gnu.org>
Greetings,
Issue seems to be initially permission based but even if I use sudo, it
works but says 0 channels are updated. nix-env -i finds no packages.
How do you suggest I proceed?
Thank you,
Kozo
On Thu, 2020-06-25 at 16:11 +0000, GNU bug Tracking System wrote:
> 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 42043@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.
>
next prev parent reply other threads:[~2020-06-25 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 16:09 bug#42043: [BUG] Can not update nix-channels after adding Kozo
2020-06-25 16:41 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
[not found] ` <handler.42043.B.159310142711067.ack@debbugs.gnu.org>
2020-06-25 19:56 ` Kozo [this message]
2020-06-25 20:00 ` Kozo via web
2022-07-14 3:26 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f2aa91ac7f8982b5423602d7c3d1d4ab1eff7ef8.camel@runbox.com \
--to=gitlabcanada@runbox.com \
--cc=42043@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.