Archlinux packages publish automation

BarbUk commented 4 years ago

I made two archlinux packages (cf: https://github.com/gbrlsnchs/pilgo/pull/2).

If you want to automate the releases, there is a github action available.

Let me know if I can help.

gbrlsnchs commented 4 years ago

@BarbUk, first of all, thank you very much for your contribution!

Automation seems nice, but I'm afraid we'll need to keep in touch in order for this to work, e.g. if for some reason my SSH is revoked and automation stops working. Is it OK for you?

Also, I need to inform you my public key, right? I'm not sure how the AUR works, but if that's the case, we can do that via email or something.

BarbUk commented 4 years ago

You just need to create an account on AUR: https://aur.archlinux.org/ and upload your public key in your account settings.

I can then add your user a maintainer of the package so you can publish / update the package.

I can also subscribe to the releases notification to update the package.

gbrlsnchs commented 4 years ago

Alright, @BarbUk, here is my AUR account. It'd be awesome to have this sort of automation.

BarbUk commented 4 years ago

You are now a maintainer for the two packages:

Packages have been updated to v0.4.0.

gbrlsnchs commented 4 years ago

Just a heads-up, @BarbUk, I tried automating new releases with no success. I'm still debugging why, since my keys are correct (I tested locally on my machine).

gbrlsnchs commented 4 years ago

Hey, it worked, Pilgo is automatically published to AUR now. :smile:

BarbUk commented 4 years ago

Hey, it worked, Pilgo is automatically published to AUR now.

Perfect ! I got the new version when updating this morning

kakawait commented 4 years ago

@BarbUk still same error with latest version

==> Making package: pilgo-bin 0.5.0-2 (Sat 02 May 2020 12:49:09 PM CEST)
==> Retrieving sources...
  -> Found linux.tar.gz
==> Validating source files with sha256sums...
    linux.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: pilgo-bin

BarbUk commented 4 years ago

@kakawait It's because the archive is named linux.tar.gz (the name don't change between release).

I've updated the pkgbuild to use a unique source name, the issue should be fixed.

kakawait commented 4 years ago

Maybe @gbrlsnchs could help us?

BarbUk commented 4 years ago

Maybe @gbrlsnchs could help us?

Do you still have the issue with the last package ?

BarbUk commented 4 years ago

The last pgkrel is ok for me:

==> Making package: pilgo-bin 0.5.0-3 (Sat 02 May 2020 05:41:34 PM +04)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found pilgo-bin-0.5.0.tar.gz
==> Validating source files with sha256sums...
    pilgo-bin-0.5.0.tar.gz ... Passed

kakawait commented 4 years ago

I don't test yet. But was thinking about if each new version we've issue regarding unversioned name.

BarbUk commented 4 years ago

Check my initial reply:

I've updated the pkgbuild to use a unique source name, the issue should be fixed.

BarbUk commented 4 years ago

the issue should be fixed.

For this release and the following.

gbrlsnchs commented 4 years ago

Also, I noticed the GitHub Actions I used doesn't reset pkgrel. I'll change to a fork that handles that.

@BarbUk Do you think the change you made is enough or it's better to change things on this repo's side?

BarbUk commented 4 years ago

The change is enough because the source file now have a unique file name. The new source will now be downloaded in case of a new release.

kakawait commented 4 years ago

Nice. Thank you for your work 😍

gbrlsnchs / pilgo

Archlinux packages publish automation #3