From: jgart <jgart@dismail.de>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: Guix Channel News Does not work on Foreign Distros for Custom Channels (ignoring Debian)
Date: Sat, 23 Apr 2022 13:51:19 -0400 [thread overview]
Message-ID: <20220423135119.GC17925@gac.attlocal.net> (raw)
In-Reply-To: <20220423134951.usjgbrzfiohwfe7r@pelzflorian.localdomain>
On Sat, 23 Apr 2022 15:49:51 +0200 "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:
> On Fri, Apr 22, 2022 at 08:05:41PM -0400, jgart wrote:
> Then I’d try what
>
> (display-news %current-profile)
>
> prints (if anything).
Hi Florian,
Thanks for the help!
This is what I get:
```
scheme@(guix scripts pull)>
(display-news %current-profile)
guix repl: no channel news since generation 28
hint: Run `guix pull -l' to view the news for earlier generations.
```
> Then I’d try to repeat the same after I surround interesting parts of
> the display-news or display-channel-specific-news procedures with
>
> (pk …)
>
> for example instead of
>
> (generation-file-name profile previous))
>
> write
>
> (pk (generation-file-name profile previous)))
What are the argument types of profile and previous in
`generation-file-name`? strings or absolute path to a profile and string?
Could you share an explicit example of how to call `generation-file-name`?
It would be much appreciated. Maybe we can work on documenting the
function further here for others as a result of that.
all best,
jgart
next prev parent reply other threads:[~2022-04-23 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 0:05 Guix Channel News Does not work on Foreign Distros for Custom Channels (ignoring Debian) jgart
2022-04-23 13:49 ` pelzflorian (Florian Pelz)
2022-04-23 17:51 ` jgart [this message]
2022-04-24 0:50 ` pelzflorian (Florian Pelz)
2022-04-24 6:01 ` jgart
2022-04-24 12:24 ` pelzflorian (Florian Pelz)
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=20220423135119.GC17925@gac.attlocal.net \
--to=jgart@dismail.de \
--cc=help-guix@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).