public inbox for tools@linux.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <mricon@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "Kernel.org Tools" <tools@kernel.org>,
	 Andi Shyti <andi.shyti@kernel.org>
Subject: Re: korgalore bug: Feed state not found for lch@ list
Date: Mon, 9 Feb 2026 15:17:47 -0500	[thread overview]
Message-ID: <20260209-hungry-phenomenal-unicorn-1ad4be@lemur> (raw)
In-Reply-To: <695ccea6-bb19-4f6d-99cf-1d898b53b1cc@kernel.org>

On Sat, Feb 07, 2026 at 09:52:05PM +0100, Krzysztof Kozlowski wrote:
>   File
> "/home/krzk/.local/share/pipx/venvs/korgalore/lib/python3.13/site-packages/korgalore/pi_feed.py",
> line 227, in find_epochs
>     raise PublicInboxError(f"No existing epochs found in {epochs_dir}.")
> korgalore.PublicInboxError: No existing epochs found in
> /home/krzk/.local/share/korgalore/lch/git.

I *think* this is from the code that wrongly assumes this is a migration from
the previous data structure during korgalore-0.1 days and then falls on its
face.

I added a fix in master and stable-0.5.y -- would you be able to clone that
and try?

    git clone https://git.kernel.org/pub/scm/utils/korgalore/korgalore.git
    cd korgalore
    git checkout stable-0.5.y (or use master)
    pipx install --force .

-K

  reply	other threads:[~2026-02-09 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-07 20:52 korgalore bug: Feed state not found for lch@ list Krzysztof Kozlowski
2026-02-09 20:17 ` Konstantin Ryabitsev [this message]
2026-02-10 16:30   ` Krzysztof Kozlowski
2026-02-11 15:14     ` Konstantin Ryabitsev
2026-02-11 15:20       ` Krzysztof Kozlowski

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260209-hungry-phenomenal-unicorn-1ad4be@lemur \
    --to=mricon@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=krzk@kernel.org \
    --cc=tools@kernel.org \
    /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