Bug#843099: boto package outdated because of authentification encryption "upgrade"
Le Thu, Nov 03, 2016 at 08:36:10PM +0100, Reiner Keller a écrit : > > I have since months problems using Saltstack provision in a single setup > run on the Debian AWS images because it delivers only with an outdated > python-boto package which is sadly actually also the only public > available version for Jessie: > > Package: python-boto > Version: 2.34.0-2 Hi Reiner, it looks like what you need is a "backport" of 2.40.0-1 to Jessie (https://backports.debian.org/). Perhaps you can first ask to the package maintainer if he would like to prepare one and if not, please do not hesitate to ask here. If you are familiar with Debian packaging, you are also welcome to prepare a backport yourself and ask for sponsorship here. Note also that version 2.38.0-1 will always be available from our "snaphot" archive. Since it is a frozen snapshot, there is no support for it (which means no correction of security bugs), but provided that you understand the issues with installing unsupported packages, it still may be useful for your purposes. http://snapshot.debian.org/package/python-boto/2.38.0-1/ I hope it helps. Have a nice day, Charles -- Charles Plessy Tsurumi, Kanagawa, Japan
Bug#843099: boto package outdated because of authentification encryption "upgrade"
Package: cloud.debian.org Hello, I have since months problems using Saltstack provision in a single setup run on the Debian AWS images because it delivers only with an outdated python-boto package which is sadly actually also the only public available version for Jessie: Package: python-boto Version: 2.34.0-2 First time I could update it by URL request from testing with: Package: python-boto Version: 2.38.0-1 but this possibility is also gone and makes it hard to auto-setup instances with python-boto usage in e.g. (especially?) eu-central-1. Luckily I had saved the first version of testing which I can install by states but they need always a 2nd run to have this version activated and it would also nice if you can get this or the actual testing version 2.40.0-1 setup ;) Sadly/luckily I am not the only with this problems. Just didn't find the AWS article but as here written the authentication has mandatory switched (and is in new regions like eu-central-1 the only available one): http://lists.openstack.org/pipermail/openstack-dev/2015-January/054129.html > boto 2.35.0 just released, and makes hmac-v4 authentication mandatory for EC2 end points Bests Reiner
