unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: jgart <jgart@dismail.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 15:49:51 +0200	[thread overview]
Message-ID: <20220423134951.usjgbrzfiohwfe7r@pelzflorian.localdomain> (raw)
In-Reply-To: <20220422200541.GB29728@gac.attlocal.net>

On Fri, Apr 22, 2022 at 08:05:41PM -0400, jgart wrote:
> On void linux, I don't see channel news for a custom channel.
> 
> How do you suggest I debug this?

Assuming you have previously pulled a channel version before the
commit of the news entry and then pull a channel version after, the
news should be displayed.  If not, I’d try to run

guix repl

and then copy all contents of

~/.config/guix/current/share/guile/site/3.0/guix/scripts/pull.scm

and paste them into the repl and press enter.

Then I’d try what

(display-news %current-profile)

prints (if anything).

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)))

Hope it helps.

Regards,
Florian

P.S. I would also try the debug feature

,trace (display-news %current-profile)

but it has no effect for me.


  reply	other threads:[~2022-04-23 13:50 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) [this message]
2022-04-23 17:51   ` jgart
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=20220423134951.usjgbrzfiohwfe7r@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=help-guix@gnu.org \
    --cc=jgart@dismail.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).