Package Details: aws-session-manager-plugin 1.2.234.0-2

Git Clone URL: https://aur.archlinux.org/aws-session-manager-plugin.git (read-only, click to copy)
Package Base: aws-session-manager-plugin
Description: AWS Session Manager Plugin for aws-cli.
Upstream URL: https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html
Keywords: aws aws-cli plugin session-manager
Licenses: custom
Submitter: CallumDenby
Maintainer: P67
Last Packager: P67
Votes: 5
Popularity: 0.130120
First Submitted: 2019-09-17 12:47
Last Updated: 2021-08-27 09:23

Latest Comments

1 2 3 4 Next › Last »

P67 commented on 2021-08-27 09:24

Hey @dhummel.

Indeed, I've released a new pkgrel, removing these extra spaces. Thanks!

dhummel commented on 2021-08-11 04:46

There seems to be some extra spaces after pkgver:

diff --git a/PKGBUILD b/PKGBUILD
index 4d21d36..335b629 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@
 # Contributor: Callum Denby <me@callumdenby.com>

 pkgname=aws-session-manager-plugin
-pkgver=1.2.234.0       
+pkgver=1.2.234.0
 pkgrel=1
 pkgdesc="AWS Session Manager Plugin for aws-cli."
 arch=('x86_64')

ElijahLynn commented on 2021-07-09 21:33

For those getting the validity check failure and using yay:

rm -rf ~/.cache/yay/aws-session-manager-plugin/

languitar commented on 2021-03-25 08:44

Removing the cached file helped. Pretty annoying when upstream changes contents without changing versions.

troyengel commented on 2021-03-24 18:47

@gdamjan - it's in a numbered subdirectory if you look, the problem is a vendor is secretly replacing one archive file with another by the same name, something which Amazon has done before with this package if you read past comments. The only real solution is to wait a bit until the final one reveals itself then update the PKGBUILD to match what everyone sees. A vendor really should not be doing what they do, the shasum of a released (tarball, package, etc.) should never change - you bump the version if you do that, which they do not - it appears that they just repackage and overwrite the same named file.

2021-03-24 23:00 UTC - the archive downloaded from my laptop just now matches the same sha512sum as when I built the update about 23h ago; no change here yet, PKGBUILD working

gdamjan commented on 2021-03-24 14:59

ahh, the archive seems to have been cached. maybe change source=($pkgname-$pkgver.deb::…the url)

gdamjan commented on 2021-03-24 14:57

b581e68546f102df1b196feeb852f5029495c8c5671efa4493b0ede4b7acb5daa6ded4fd632dfe5d17c2439e20c016597ce5ec0d08eb4209ce81f17767b94238 session-manager-plugin.deb

troyengel commented on 2021-03-24 13:32

@languitar - this has happened before with Amazon's download, I just updated my work laptop and it validated fine. I suspect that (a) they swapped out the package with a hidden fix, and (b) there's a geo-based CDN delivering the download and I'm getting one version of the DEB, you're getting another version as the CDNs are not in sync (as it's the same filename, one of them simply skipped re-syncing it).

Since it's passing sha512sum for me just now, I'll assume this laptop hit the same CDN as my other machine last night - for now, you can just edit the pkgbuild until they converge upstream and we get the same DEB file (sha512) for everyone... (and we can update the pkgbuild when the dust settles, if needed)

languitar commented on 2021-03-24 08:15

For me, the validity check fails now

troyengel commented on 2021-03-24 00:04

P67 must be out right now, backup maintainer here - I updated to the new 1.2.54.0 release and deprecated 32bit support while I was in there.