Re: another korgalore issue with linux-crypto

"Ard Biesheuvel" <[email protected]>
Newsgroups org.kernel.linux.tools
Message-ID <[email protected]>
On Tue, 31 Mar 2026, at 08:45, Ard Biesheuvel wrote:
> On Mon, 30 Mar 2026, at 20:43, Konstantin Ryabitsev wrote:
>> On Sat, Mar 28, 2026 at 06:53:44PM +0100, Ard Biesheuvel wrote:
>>> Hi Konstantin,
>>> 
>>> Not sure whether this happened because my local fork was in a funny state, but I got the following issue related to a 'rm' commit.
>>
>> Yeah, I think it's a real bug, but testing is tricky. I pushed a commit to
>> master/stable-0.6.y that should hopefully fix this (or, at least, make it fail
>> differently). Can you try that out? Using stable-0.6.y may be easier, as
>> master currently pulls in a new library.
>>
>
> Thanks for the fix. I've upgraded to this version now, but the 
> underlying failure condition is no longer there, so I can't really say 
> for sure whether things are any better now.

Actually, I still think something fishy is going on. In my log below, it seems that linuxcrypto is still in a funny state, as the number of messages keeps going up. The last message that was actually newly delivered was

Date: Tue, 31 Mar 2026 13:22:14 +0100
Message-ID: <[email protected]>

When I run kgl on the command line I get

$ korgalore/kgl.sh pull linuxcrypto
Reattempting delivery  [####################################]  1/1
Updating feeds  [####################################]  1/1                                      
Pull complete with no updates.



2026-04-01 02:36:48,183 - INFO - Pull complete with updates:
2026-04-01 02:36:48,183 - INFO -   linuxcrypto: 305
2026-04-01 02:36:48,183 - INFO -   lakml: 1
2026-04-01 02:48:43,747 - INFO - Pull complete with updates:
2026-04-01 02:48:43,747 - INFO -   linuxcrypto: 306
2026-04-01 02:48:43,747 - INFO -   lakml: 1
2026-04-01 03:09:04,468 - INFO - Pull complete with updates:
2026-04-01 03:09:04,469 - INFO -   lakml: 4
2026-04-01 03:18:03,423 - INFO - Pull complete with updates:
2026-04-01 03:18:03,423 - INFO -   lakml: 1
2026-04-01 03:21:04,713 - INFO - Pull complete with updates:
2026-04-01 03:21:04,714 - INFO -   lakml: 1
2026-04-01 03:24:03,478 - INFO - Pull complete with updates:
2026-04-01 03:24:03,478 - INFO -   lakml: 1
2026-04-01 03:48:03,506 - INFO - Pull complete with updates:
2026-04-01 03:48:03,506 - INFO -   lakml: 1
2026-04-01 04:00:04,528 - INFO - Pull complete with updates:
2026-04-01 04:00:04,529 - INFO -   linuxhardening: 1
2026-04-01 04:06:04,315 - INFO - Pull complete with updates:
2026-04-01 04:06:04,315 - INFO -   lakml: 2
2026-04-01 04:12:04,709 - INFO - Pull complete with updates:
2026-04-01 04:12:04,709 - INFO -   lakml: 2
2026-04-01 04:21:03,486 - INFO - Pull complete with updates:
2026-04-01 04:21:03,486 - INFO -   lakml: 2
2026-04-01 04:27:04,117 - INFO - Pull complete with updates:
2026-04-01 04:27:04,117 - INFO -   lakml: 2
2026-04-01 04:33:03,445 - INFO - Pull complete with updates:
2026-04-01 04:33:03,445 - INFO -   lakml: 1
2026-04-01 04:45:06,278 - INFO - Pull complete with updates:
2026-04-01 04:45:06,278 - INFO -   lakml: 1
2026-04-01 04:48:03,127 - INFO - Pull complete with updates:
2026-04-01 04:48:03,128 - INFO -   lakml: 1
2026-04-01 04:57:03,697 - INFO - Pull complete with updates:
2026-04-01 04:57:03,698 - INFO -   lakml: 1
2026-04-01 05:03:04,044 - INFO - Pull complete with updates:
2026-04-01 05:03:04,044 - INFO -   lakml: 3
2026-04-01 05:21:03,855 - INFO - Pull complete with updates:
2026-04-01 05:21:03,855 - INFO -   lakml: 1
2026-04-01 05:24:03,694 - INFO - Pull complete with updates:
2026-04-01 05:24:03,694 - INFO -   lakml: 1
2026-04-01 05:30:04,115 - INFO - Pull complete with updates:
2026-04-01 05:30:04,115 - INFO -   lakml: 1
2026-04-01 05:36:03,918 - INFO - Pull complete with updates:
2026-04-01 05:36:03,918 - INFO -   lakml: 2
2026-04-01 06:24:04,093 - INFO - Pull complete with updates:
2026-04-01 06:24:04,093 - INFO -   lakml: 3
2026-04-01 06:57:06,730 - INFO - Pull complete with updates:
2026-04-01 06:57:06,730 - INFO -   lakml: 8
2026-04-01 07:12:03,525 - INFO - Pull complete with updates:
2026-04-01 07:12:03,525 - INFO -   lakml: 1
2026-04-01 07:27:03,849 - INFO - Pull complete with updates:
2026-04-01 07:27:03,850 - INFO -   lakml: 1
2026-04-01 07:33:03,035 - INFO - Pull complete with updates:
2026-04-01 07:33:03,035 - INFO -   lakml: 1
2026-04-01 08:18:03,301 - INFO - Pull complete with updates:
2026-04-01 08:18:03,301 - INFO -   lakml: 1
2026-04-01 08:39:03,805 - INFO - Pull complete with updates:
2026-04-01 08:39:03,805 - INFO -   lakml: 1
2026-04-01 08:42:04,690 - INFO - Pull complete with updates:
2026-04-01 08:42:04,691 - INFO -   lakml: 1
2026-04-01 08:51:03,168 - INFO - Pull complete with updates:
2026-04-01 08:51:03,168 - INFO -   lakml: 1
2026-04-01 09:00:50,173 - INFO - Pull complete with updates:
2026-04-01 09:00:50,173 - INFO -   linuxcrypto: 306
2026-04-01 09:00:50,173 - INFO -   lakml: 1
2026-04-01 09:03:48,518 - INFO - Pull complete with updates:
2026-04-01 09:03:48,518 - INFO -   linuxcrypto: 307
2026-04-01 09:03:48,518 - INFO -   lakml: 13
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.