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: Sun, 24 Apr 2022 02:50:12 +0200	[thread overview]
Message-ID: <20220424005012.agi4fg7pkluzsonm@pelzflorian.localdomain> (raw)
In-Reply-To: <20220423135119.GC17925@gac.attlocal.net>

Hi jgart.


Now that I think about it -- there are cases when the news simply
won’t be displayed, namely if the commit referred to in the news entry
was already present in the old commit.

Could this be the case, that the news file refers to a commit you
already had before pulling?

Then the only way to view the news would be

guix pull --list-generations



On Sat, Apr 23, 2022 at 01:51:19PM -0400, jgart wrote:
> 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.

OK, so this will always be the same output as `guix pull -N`.


> > 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`?
>

What I meant to say is pull.scm contains a line

(generation-file-name profile previous))

which you can replace by

(pk (generation-file-name profile previous)))

to peek at which generation-file-name is used for the channel news.

The goal is to find out at which point pull.scm does something
unexpected.

Now this was a bad example, since the generation-file-name does not
seem so interesting.  But you could try change within pull.scm

(match (channel-news-for-commit channel new old)

to

(match (channel-news-for-commit (pk channel) (pk new) (pk old))

which would be expected to show the same information as `guix
describe` before and after the last guix pull.

This would be expected to contain anything that was added to the news
file.

Regards,
Florian


  reply	other threads:[~2022-04-24  0: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)
2022-04-23 17:51   ` jgart
2022-04-24  0:50     ` pelzflorian (Florian Pelz) [this message]
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=20220424005012.agi4fg7pkluzsonm@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).