[SOLVED] repo-add replaces newer version package with old ones

Question

Say I have two versions of nspr.
$ ls -1 nspr*.pkg.tar.xz
nspr-4.10-2-x86_64.pkg.tar.xz
nspr-4.9.6-1-x86_64.pkg.tar.xz
When I run repo-add on both of them, version 4.9.6 will be the one remaining in the database.
$ repo-add custom.db.tar.gz nspr*.pkg.tar.xz
==> Extracting database to a temporary location...
==> Adding package 'nspr-4.10-2-x86_64.pkg.tar.xz'
-> Computing checksums...
-> Removing existing entry 'nspr-4.9.6-1'...
-> Creating 'desc' db entry...
-> Creating 'depends' db entry...
==> Adding package 'nspr-4.9.6-1-x86_64.pkg.tar.xz'
-> Computing checksums...
-> Removing existing entry 'nspr-4.10-2'...
-> Creating 'desc' db entry...
-> Creating 'depends' db entry...
==> Creating updated database file 'custom.db.tar.gz'
I think here the natural order should be used, something like
$ repo-add custom.db.tar.gz $(ls -v nspr*.pkg.tar.xz)
as this is the expected behaviour from most users.
Last edited by luran (2013-10-07 23:43:21)

Answer 1

karol wrote:When only one version of a package will ever be present in the db, why try adding more? Just pass the version you want. You can use 'ls -v' if you prefer, but I think it's the shell's interpretation of the wildcard and not repo-add to blame.
Thanks for your reply. Now I agree repo-add should just process the files according to the order given by the shell.
To anwser your question, I need to make a local repository regularly to be shared with my other machine, because I have a very limited Internet quota and the sharing roughly halves the downloads. Usally I just use the wildcard for all the packages in the cache, and it works fine as long as the package version does not jump to 10+ like the above example. 'ls -v' will do the job for me. Cleaning the old packages could be another option, but occasionally I need to revert some package back to an old version.