On 09/29/2014 10:14 AM, Achim Gratz wrote: > Eric Blake (cygwin) writes: >> A new release of bash, 4.1.13-6, has been uploaded and will soon reach a >> mirror near you; leaving the previous version at 4.12-5. > > Just out of curiosity, why is this release version -6 instead of -1?
Because of how upstream bash numbers things. They only ship a 4.1 tarball, and then 13 official patches that must be applied by the maintainer on top of that 4.1 tarball. However, it modifies the micro version number according to which upstream patches have been applied. So, this is my sixth time building bash 4.1 for cygwin, and it's just that bash's micro number bumped from 4.1.12 to 4.1.13 in between my -5 and -6 builds. When I eventually get bash 4.3 out the door, it will start at 4.3.27-1 (or a higher micro, as there is still a lot of churn in upstream bash to now patch lower-priority bugs that are no longer Shell Shock attacks thanks to patch 27, but which are still local crashers). -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
