From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============2603416945280756654==" MIME-Version: 1.0 From: Philip Tricca Subject: Re: [tpm2] Some issues with tpm2-tss, tpm2-tools regarding packaging Date: Thu, 22 Feb 2018 08:41:36 -0800 Message-ID: <20180222164136.GA6409@intel.com> In-Reply-To: 20180222144627.525e4kw5gsjqorbw@f195.suse.de List-ID: To: tpm2@lists.01.org --===============2603416945280756654== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi Matthias, On Thu, Feb 22, 2018 at 03:46:27PM +0100, Matthias Gerstner wrote: > > > - The distribution tarballs of tpm2-tss and tpm2-tools try to determi= ne > > > the package version via `git describe [...]` in configure.ac. This > > > doesn't work, because there is no git repository any more. This cau= sed > > > e.g. the pkgconfig files like sapi.pc to contain an empty version > > > number, which in turn caused tpm2-tools to fail to build, because t= he > > > version check failed. > > > = > > = > > This shouldn't be an issue if the released tarball (as generated by mak= e dist) > > is used, only when using the source tarball. With the former, there's n= o need > > to call bootstrap since a configure script with a PACKAGE_VERSION is sh= ipped. > = > this is true. I can't use the 1.3.0 release tarball at the moment, > because of the missing README, LICENSE and CHANGELOG files. It should > work with the next release tarball then. We've been queuing up changes in the 1.x branch for another release and these fixes are among them. Now that the new AC commands are in and tested we're ready for another minor release. I've got time blocked off to get the first RC out tomorrow. I'll be sure to get a message out to the list to announce the new RC when it's up on github. Thanks again for the valuable feedback, Philip --===============2603416945280756654==--