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
