Package Details: aws-session-manager-plugin 1.1.61.0-1

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 (troyengel)
Last Packager: P67
Votes: 4
Popularity: 0.112867
First Submitted: 2019-09-17 12:47
Last Updated: 2020-04-17 11:54

Latest Comments

1 2 3 Next › Last »

ElijahLynn commented on 2020-05-16 03:19

[RESOLVED - see bottom] I am getting the error:

session-manager-plugin.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: aws-session-manager-plugin

The issue appears to be that https://s3.amazonaws.com/session-manager-downloads/plugin/1.1.61.0/ubuntu_64bit/session-manager-plugin.deb has a sha256sum of d4d578a64210165ec434d658212304a968acb2efa49074868552427e738ea97c and the sha256sum in PKGBUILD is 21c7778ece8fadaf3f5510c7af5f90b6bbe1c41eb4d71cae57630c8bda8bba3bc19aabd44e2a0abcb56e18306cc05b060e377f2fb57ef78dcfd17bf1e784ce66.

Anyone else getting this?

I had previously installed 1.1.50.0 with https://github.com/ElijahLynn/aur-aws-session-manager-plugin (my first PKGBUILD/AUR) so I do wonder if that may be confusing things, but it seems like the mismatched SHA is the issue.

UPDATE: NVM - Yeah, I was using sha256sum instead of sha512sum. It matches, and does seem to be because of my previous install. I yay --remove aws-session-manager-plugin and reinstalled but same error so then I rm -rf ~/.cache/yay/aws-session-manager-plugin and reinstalled and all is well.

troyengel commented on 2020-04-16 16:31

I really hated to do this, but as I've tried to contact the packager twice (he was initially responding to email, then went MIA) and received no replies I've used the Submit Request to the Arch TU team to add a co-maintainer or orphan the package so someone else can update it. @P67 I'll forward you the auto-generated email and keep you in the loop.

P67 commented on 2020-04-16 16:20

Hey @CallumDenby. Is there a possibility to get this updated? I'd love to collaborate to keep this package up to date..

I've already got a working PKGFILE handy if need be.

languitar commented on 2020-03-27 13:02

Any chance to get this updated?

crou commented on 2019-11-22 02:30

@troyengel you are right, /opt is a much better location! I vote for it :-)

troyengel commented on 2019-11-21 20:07

@crou I was thinking about that overnight as well, I think /opt would be a more LFHS standard / compliant path to use rather than /usr/local (spec)- Amazon is our vendor and delivering a binary payload, which matches the general concept of other vendor tooling we have in AUR (google-cloud-sdk, Zoom, etc.) and how it's delivered to users.

crou commented on 2019-11-21 18:59

I haven't realized before, but is that expected to have this binary installed in /usr/sessionmanagerplugin/ ? /usr/local/sessionmanagerplugin would be more appropriate ;-)

troyengel commented on 2019-11-20 21:59

@CallumDenby I emailed you, easier to chat re: the versions. Not sure myself. :-/

troyengel commented on 2019-11-20 21:51

For anyone upgrading - because we just moved a non-package-tracked symlink into the package proper, you may see this when you attempt to upgrade to 1.1.35.0-3 or above from an older version:

(1/1) checking for file conflicts                                                 [###############################################] 100%
error: failed to commit transaction (conflicting files)
aws-session-manager-plugin: /usr/bin/session-manager-plugin exists in filesystem

Just do a quick sudo rm /usr/bin/session-manager-plugin first then upgrade the package. Standard pacman behaviour, protecting you from possibly making a mistake.

CallumDenby commented on 2019-11-20 21:48

I found the same thing, I'm unsure whether to provide version 1.1.50 without it being documented within the web page. What do you advise?