Arch Linux User Repository

@hightowe Hi!

The best source for that information is probably the Arch Wiki's guide: https://wiki.archlinux.org/title/creating_packages

The main steps involved are updating the hashes when files change. Altering it for 4.0 probably just means locating a few Perl dependencies and adding them to the dependencies section. Everything runs through Git, and there are only two important files to change.

And, I can understand that being a frustrating solution, to need to run a VM just for that. If it's a lot of trouble, I could probably spend a day learning what I need to package the new dependencies, since it's easy to test on my machine - but I might need to ask some questions, if I run into issues with Perl.

@SammyPoot -

I might be interested in trying to take this on, but I am not an Arch Linux user. Is there some good packaging documentation that you could point me to that I could review? I sort of hate booting an Arch VM just to package kpcli -- that almost feels disingenuous -- but I would consider it if the learning curve on Arch packaging is not too steep.

Thx.

Hello @hightowe!

It's quite possible that it's the same here - on closer inspection, it looks like a lot of the ones I'd been worried about are already part of the distribution? CPAN wasn't the clearest, when I was scanning through the full dependency list for File::KDBX.

But, being this wildly off about the process suggests to me that I should give this over to someone with more Perl experience than me.

Hi @Sammy -

I recently assisted the kpcli Fedora maintainer work through this and there was really only additional package beyond File::KDBX that needed attention (Crypt::Argon2). I am not personally an Arch user, but I would be surprised if the Perl package delta between Fedora and Arch is very large. Would you mind sharing some additional details about your findings and perhaps I can assist in some way...?

-- Lester

Looking deeper into packaging File:KDBX, I feel like it's probably beyond me - there are over ten knock-on dependencies that I can't find in the AUR, that I'd also need to package and maintain. Someone more experienced may be needed.

I'll update the package with the correct README to ensure that it can build for the time being, though.

Hi @SammyPoot -

I wanted to let you know that kpcli 4.0 has been released: https://sourceforge.net/projects/kpcli/files/

For it to support KDBX4 files, File::KDBX will also need to be packaged.

Sincerely,

Lester (kpcli author)

@oktoberfest All done, should work fine now!

@oktoberfest Oop, yes! 3.8 came out, and because there's only one README for the entire project, each release breaks the old files. I'm working on it.

I tried to install kpcli and get following error :

==> Validating source files with sha256sums... kpcli-3.7.pl ... Passed kpcli-3.7-README ... FAILED ==> ERROR: One or more files did not pass the validity check!

In PKGBUILD the sha256 for kpcli-3.7-README is: 92a0b6508e5e6ec66f0890dfd9ef925917e108388e50a2aba0ba542ed6fad0f1

Using "sha256sum kpcli-3.7-README" I get: 9e0d52c5e212c069d23c537b35fda6f37e0d6f6011519e6ae12042196d5ebe66 kpcli-3.7-README

After putting this value in PKGBUILD everything compiles fine.

@hightowe Oooh, interesting. Thanks for letting me know!