3 a@s6dZddlZddlmZdZdZdZdifddZdS) z Version determination functions These are in their own file so they can be imported by setup.py before we have any of our dependencies installed. N)utilz27.2z27.2.2~18.04.1z{version}{feature_suffix}c Csd}x2t|jD]"\}}|dj|r(dnd|d7}qWtjdsPtjt|dStjjtjjt }tjj tjj |drd d d d d g}yt j |\}}|j|St jk rdddg}t j |\}}tj|j|dSXtjt|dS)a$Return the packaged version as a string Prefer the binary PACKAGED_VESION set by debian/rules to DEB_VERSION. If unavailable, check for a .git development environments: a. If run in our upstream repo `git describe` will gives a leading XX.Y so return the --long version to allow daily build recipes to count commit offset from upstream's XX.Y signed tag. b. If run in a git-ubuntu pkg repo, upstream tags aren't visible, parse the debian/changelog in that case z {enabled}{name}+-)enablednamez@@PACKAGED_VERSION)versionfeature_suffixz.gitgitZdescribez --abbrev=8z--match=[0-9]*z--longzdpkg-parsechangelogz-Sr)sorteditemsformatPACKAGED_VERSION startswith VERSION_TMPLospathdirname__file__existsjoinrsubpstripProcessExecutionError __VERSION__) _argsfeaturesr keyvalueZtopdircmdout_r"2/usr/lib/python3/dist-packages/uaclient/version.py get_versions(     r$) __doc__Zos.pathruaclientrrrrr$r"r"r"r#s