Arch Linux User Repository

@banana1 All done! Thanks for the heads up on the update. I've also hopefully fixed the problem with the README file not redownloading automatically, too.

Hi. Release 3.4 of kpcli is out since 2020-04-25. Maybe it could also come here. Thanks and regards.

Ah, no harm done! I'm glad you managed to fix it. I'm not sure if this means that I've messed something up - I had assumed it'd pull down a new README - but I'll have a look.

No problem!

My apologies, as usual the solution pops up as soon as I have asked the question (openly), it seems to have been a pacman caching problem of some sorts, after running yay -Sc it validated properly. Previously I only checked the yay buildDir, maybe passing --redownload would have worked – I guess I was stuck with a broken README back from when the Sourceforge disaster recovery was active?

Still, thanks for your (still pretty quick, imo) answer!

I'm a bit confused, @saviola

I'm installing the package through the helper Yay, which appears to be handling it correctly. I've done a full re-install of the package, just to be sure, and it validates properly.

Could you tell me which package manager this is happening with? I'll try and replicate the problem.

Sorry for the slight delay in answering.

For the last several months (since the last update, I guess), the 3.3-1 update fails to install for me, because the README fails the validity check. When I manually download the README from https://iweb.dl.sourceforge.net/project/kpcli/README and run sha256sum, it shows the correct checksum though.

I am using the yay AUR helper. Since kpcli is the only package where something like this has happened I first wanted to ask here if anyone has an idea (or anyone is also using yay and it works for them) what the issue might be and if this could be a problem on my end somehow, before I raise this issue on the yay repository.

thank you very much for advice. installing perl-crypt-rijndael once more works like a charm <3

Hi, @jasondaigo.

Perl has updated to 5.30, but a few AUR packages haven't been re-compiled into the correct directory. pacman -Qqo '/usr/lib/perl5/5.28' will tell you which packages still have files in the old directory - assuming it's the same as my last version. There should be a Pacman hook that warns you about them.

You'll have to reinstall perl-crypt-rijndael and the other outdated packages.

Alternatively, you can install Crypt::Rindael through cpan as a temporary workaround.

doesnt work anymore aftzer some base package unpdated.error is:
Can't locate Crypt/Rijndael.pm in @INC (you may need to install the Crypt::Rijndael module) (@INC contains: /usr/lib/perl5/5.30/site_perl /usr/share/perl5/site_perl /usr/lib/perl5/5.30/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5/5.30/core_perl /usr/share/perl5/core_perl) at /usr/bin/kpcli line 38. BEGIN failed--compilation aborted at /usr/bin/kpcli line 38.

Hello, @heichblatt

seems the disaster has been recovered, but the "kent" mirror is not there.

Please update the sources to https://datapacket.dl.source.... (or a different mirror) and it will work again, thanks.

(Also, the README file can have https too now.)