testing/himitsu-ssh: upgrade to 1984a42ebfc0a4975c05aa8fc1d4030010b0c8db v1 APPLIED

Drew DeVault: 1
 testing/himitsu-ssh: upgrade to 1984a42ebfc0a4975c05aa8fc1d4030010b0c8db

 1 files changed, 3 insertions(+), 3 deletions(-)

[PATCH] testing/himitsu-ssh: upgrade to 1984a42ebfc0a4975c05aa8fc1d4030010b0c8db Export this patch

---
 testing/himitsu-ssh/APKBUILD | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/testing/himitsu-ssh/APKBUILD b/testing/himitsu-ssh/APKBUILD
index 8a711cc36a..19367904c6 100644
--- a/testing/himitsu-ssh/APKBUILD
+++ b/testing/himitsu-ssh/APKBUILD
@@ -1,7 +1,7 @@
 # Maintainer: Drew DeVault <sir@cmpwn.com>
 pkgname=himitsu-ssh
-pkgver="0_git20220616"
-_commit=8a15d0b69633bfa799427374d4b98006ca8bf9ac
+pkgver="0_git20220619"
+_commit=1984a42ebfc0a4975c05aa8fc1d4030010b0c8db
 pkgrel=0
 pkgdesc="SSH integration for Himitsu"
 url="https://himitsustore.org"
@@ -28,5 +28,5 @@ package() {
 }
 
 sha512sums="
-29145d1a19b5a656692818a764ceaf29f6c9c86a09e010d7e580b918b1a8203d617fbfe52e40eb45395f025afdd2aa903f90117e3a0d6044d0e70d734fc0418c  himitsu-ssh-8a15d0b69633bfa799427374d4b98006ca8bf9ac.tar.gz
+3fb6b40509245ae576a47af4f0e2b454d299ac255cff3e7e91f281a718c24f29244335fcc97b4e56612805fd8e97d2290ed7af38217aa09bcfee8f0e54b8a440  himitsu-ssh-1984a42ebfc0a4975c05aa8fc1d4030010b0c8db.tar.gz
 "

base-commit: 2bb9ed0294111950b0440726000993a9aec37d57
-- 
2.36.1

omni <no-reply@dispatch.alpinelinux.org>

2 years ago

I think it should be `testing/himitsu-ssh: upgrade to 0_git20220619`?

-- 
via https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/35483#note_242633

Drew DeVault <no-reply@dispatch.alpinelinux.org>

2 years ago

With _git packages I have always used the commit message in this format, with the commit sha that the upgrade pertains to.

-- 
via https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/35483#note_242634

omni <no-reply@dispatch.alpinelinux.org>

2 years ago

Aha, I haven't seen that. Usually `0_git20220619`, from `CommitDate`, is the `pkgver` after all and would imply the latest commit on that date, but I'm not sure how you'd then handle fast iterations, where you want to update a package the same day it's already been upgraded to an earlier commit of the current day. I guess that'd be a corner case.

-- 
via https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/35483#note_242635