I wrote a script for extracting the dist macro value a while back. One of the odd cases is when rpms have what /looks like/ a dist tag in the release field, but is in fact a hard coded part of the release. I've seen some pretty strange things. At any rate, I figured out a way to extract the true dist tag, given the spec and the nvr. I've applied similar changes here for review. On Tue, Jun 10, 2014 at 10:35 AM, Mike McLean <mikem at imponderable.org> wrote: > Also, I suggest piping that git log output through |grep import |head -n > 1. No need to process the entire history and we could have non-import > commits. > E.g. attached patch > > > > On Tue, Jun 10, 2014 at 10:29 AM, Karanbir Singh <mail-lists at karan.org> > wrote: > >> good spot, pushed. >> >> On 06/10/2014 03:27 PM, Mike McLean wrote: >> > typo >> > >> > >> >> -- >> Karanbir Singh >> +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh >> GnuPG Key : http://www.karan.org/publickey.asc >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel at centos.org >> http://lists.centos.org/mailman/listinfo/centos-devel >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20140610/250b27b9/attachment-0007.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Find-true-dist-macro-value.patch Type: text/x-patch Size: 1076 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20140610/250b27b9/attachment-0007.bin>