unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
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: Sun, 24 Apr 2022 02:01:55 -0400	[thread overview]
Message-ID: <20220424020155.GB18799@gac.attlocal.net> (raw)
In-Reply-To: <20220424005012.agi4fg7pkluzsonm@pelzflorian.localdomain>

On Sun, 24 Apr 2022 02:50:12 +0200 "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:
> 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

I still do not get any news for the custom channel when I run `guix pull --list-generations`.

On Debian it works but on Void Linux I must have something not set up that I can't pin point at the moment.


  reply	other threads:[~2022-04-24  6:02 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)
2022-04-24  6:01       ` jgart [this message]
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=20220424020155.GB18799@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).