Package Details: salt-py3 3001.1-1

Git Clone URL: https://aur.archlinux.org/salt-py3.git (read-only, click to copy)
Package Base: salt-py3
Description: Central system and configuration manager
Upstream URL: http://saltstack.org/
Licenses: Apache
Conflicts: salt, salt-raet, salt-zmq
Provides: salt
Replaces: salt, salt-raet, salt-zmq
Submitter: zer0def
Maintainer: zer0def (xuhcc)
Last Packager: zer0def
Votes: 6
Popularity: 0.74
First Submitted: 2020-01-21 13:36
Last Updated: 2020-08-07 23:34

Latest Comments

1 2 Next › Last »

tqre commented on 2020-08-08 15:16

You are right, the order matters. This is actually also stated in pacman tips & tricks in ArchWiki under a red warning sign. Thanks for this, learned something new :)

zer0def commented on 2020-08-08 14:07

You can clearly notice that, due to how your shell handles file ordering through glob expansion, it adds 3001.1-1 before 3000.2:

$ ls -1 salt-py3-*
salt-py3-3001.1-1-any.pkg.tar.zst
salt-py3-3001-2-any.pkg.tar.zst
$ repo-add asdf.db.tar.gz salt-py3-*.pkg.tar.zst
==> Extracting asdf.files.tar.gz to a temporary location...
==> Adding package 'salt-py3-3001.1-1-any.pkg.tar.zst'
  -> Computing checksums...
  -> Creating 'desc' db entry...
  -> Creating 'files' db entry...
==> Adding package 'salt-py3-3001-2-any.pkg.tar.zst'
==> WARNING: A newer version for 'salt-py3' is already present in database
  -> Computing checksums...
  -> Removing existing entry 'salt-py3-3001.1-1'...
  -> Creating 'desc' db entry...
  -> Creating 'files' db entry...
==> Creating updated database file 'asdf.db.tar.gz'
$ rm asdf.*
$ repo-add asdf.db.tar.gz salt-py3-3001-2-any.pkg.tar.zst salt-py3-3001.1-1-any.pkg.tar.zst 
==> Adding package 'salt-py3-3001-2-any.pkg.tar.zst'
  -> Computing checksums...
  -> Creating 'desc' db entry...
  -> Creating 'files' db entry...
==> Adding package 'salt-py3-3001.1-1-any.pkg.tar.zst'
  -> Computing checksums...
  -> Removing existing entry 'salt-py3-3001-2'...
  -> Creating 'desc' db entry...
  -> Creating 'files' db entry...
==> Creating updated database file 'asdf.db.tar.gz'

tqre commented on 2020-08-08 10:58

Sorry, maybe I was not clear enough. It doesn't happen on installing, and no extraeous helpers are involved. I'm running a custom pacman repository locally for salt-py3, and after building the new package and when adding it to the repo by running:

sudo repo-add /srv/http/saltmaster.db.tar.gz /srv/http/salt-py3*.pkg.tar.zst

I had both package versions in the directory. This resolves easily enough by just removing the old package from the root.

Maybe repo-add doesn't process version numbers right in this case?

zer0def commented on 2020-08-08 01:22

Installing the previous version over the current one with pacman results in warning: downgrading package salt-py3 (3001.1-1 => 3001-2), so get a better pacman helper, I suppose.

tqre commented on 2020-08-08 00:23

Having the previous package in same repo results in the newer package to look old!

==> Extracting saltmaster.db.tar.gz to a temporary location...
==> Extracting saltmaster.files.tar.gz to a temporary location...
==> Adding package '/srv/http/salt-py3-3001.1-1-any.pkg.tar.zst'
  -> Adding package signature...
  -> Computing checksums...
  -> Removing existing entry 'salt-py3-3001-2'...
  -> Creating 'desc' db entry...
  -> Creating 'files' db entry...
==> Adding package '/srv/http/salt-py3-3001-2-any.pkg.tar.zst'
==> WARNING: A newer version for 'salt-py3' is already present in database
  -> Adding package signature...
  -> Computing checksums...
  -> Removing existing entry 'salt-py3-3001.1-1'...
  -> Creating 'desc' db entry...
  -> Creating 'files' db entry...
==> Creating updated database file '/srv/http/saltmaster.db.tar.gz'

zer0def commented on 2020-06-19 15:03

Thanks again, xuhcc. :)

xuhcc commented on 2020-06-19 12:09

It seems that salt now supports msgpack>=1.0, they just forgot to update requirements file (https://github.com/saltstack/salt/issues/56007). I applied this patch and so far it works fine:

diff --git a/requirements/base.txt b/requirements/base.txt
index 27923c00e4..56d9131f29 100644
--- a/requirements/base.txt
+++ b/requirements/base.txt
@@ -1,5 +1,5 @@
 Jinja2
-msgpack>=0.5,!=0.5.5,<1.0.0
+msgpack>=0.5,!=0.5.5
 PyYAML
 MarkupSafe
 requests>=1.0.0

demaio commented on 2020-04-01 21:26

Ah. Yes of course, downgrading could work. But I think I will try with a virtualenv and pip. Less risk of breakage. Thanks anyway!

Other upstreams have started vendoring/including python-msgpack with their sources (e.g. borg backup) but I don't know how this is possible through packaging (without upstream supporting it).

zer0def commented on 2020-04-01 20:38

https://archive.archlinux.org/packages/p/python-msgpack/

demaio commented on 2020-04-01 20:22

Hi. Thanks for your package! How does the the python-msgpack<1.0.0 work for you? As there is no python-msgpack<1.0.0 available... neither in the official repo nor in the AUR.