uname -a tag name problem resolved

Matthew Dillon dillon at apollo.backplane.com
Thu Jul 30 22:42:44 PDT 2015

    A number of people reported the wrong tag in the uname output, e.g.
    where it is listing a release tag (v4.2.2) on a system built with master:

    ... 4.3-DEVELOPMENT DragonFly v4.2.2.180.gd30866-DEVELOPMENT.

    The problem was due to a bad 'v4.2.2' tag, and although we deleted
    the tag, tag deletions do not propagate to git clients so anyone who
    had already picked it up wound up being stuck with it.

    To fix the problem I have tagged v4.3.1 in the master branch, which as
    a newer tag will show up in the uname output for any new builds of
    master.  This is not a critical fix so people don't need to rush to
    rebuild master or anything like that.  It will print correctly the next
    time you happen to rebuild master, is all.

					Matthew Dillon 
					<dillon at backplane.com>

More information about the Users mailing list