On Nov 23, 2016, at 1:08 PM, Jordi Massaguer Pla
Hello packagers,
we are facing an issue when updating runc. It happens that docker requires runc, but requires a very specific git commit of it. Thus, when we packaged a previous version of docker (1.12.1), we did packaged runc as
runc-1.0.0+git22222
(it was not 22222 but the commit, but this is better for explaining it, see below)
Now, we packaged a new version of docker, which requires runc to be commit 1111, thus we did
runc-1.0.0+git11111
However, zypper won't see 1.0.0+git11111 as an update to 1.0.0+git22222, but as a downgrade.
So, how to fix this?
I assume by “commit” you mean the hash? At least that’s the impression I get from the bugzilla, "0.1.1+gitcc29e3d" etc.
Since git commits are a hash and don’t monotonically increase like svn revisions, you need another way of versioning them (and I’m assuming the upstream repo doesn’t have appropriately versioned tags?). One solution I came across (sorry, I don’t remember where), and use in one of my internal RPMs that I build from a Github repo, is to use a revision count first and then the hash. Here’s an example from my php5-ffmpeg spec:
====
# To export tarball from git:
# $ git archive --prefix=ffmpeg-php/ -o ffmpeg-php-