Re: How to run autogen?

Sorry we had trouble with this.  It seems expecting automatic-git-repo
every time is unwise.

It really is a nice thing to get a unique version number (based on tags
and branches etc..) from the git version in use!   However ... that's
not what we have here every time so we cannot rely on that.

I will adjust this 3.6.0.pre2 and get pre3 out soon so that it does NOT
expect to set versioning via git.

On 6/13/22 10:15, Orion Poplawski wrote:
> It seems like packaging/common/set_zmanda_version assumes that it will be run
> inside of an amanda git repo (or a tarball?), but in this case it is running
> inside of my rpm git repo.  I've hacked around it with:
>
> diff -up amanda-tag-3.6.0.pre2/packaging/common/set_zmanda_version.rpm
> amanda-tag-3.6.0.pre2/packaging/common/set_zmanda_version
> --- amanda-tag-3.6.0.pre2/packaging/common/set_zmanda_version.rpm
> 2022-06-13 10:11:28.949102992 -0600
> +++ amanda-tag-3.6.0.pre2/packaging/common/set_zmanda_version   2022-06-13
> 10:12:17.984937574 -0600
> @@ -14,7 +14,7 @@
>
>  selfdir=$(readlink -e ${BASH_SOURCE[0]})
>  selfdir=$(dirname ${selfdir})
> -src_root=$(git rev-parse --show-toplevel)
> +src_root=.
>  if [ "$(type -t get_yearly_tag)" != "function" ]; then
>      . ${selfdir}/build_functions.sh
>  fi
>
> and creating FULL_VERSION and PKG_REV manually.
>
Confidentiality Notice | The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, re-transmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers.