From: Philip Tricca <philip.b.tricca at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] Some issues with tpm2-tss, tpm2-tools regarding packaging
Date: Thu, 22 Feb 2018 08:41:36 -0800 [thread overview]
Message-ID: <20180222164136.GA6409@intel.com> (raw)
In-Reply-To: 20180222144627.525e4kw5gsjqorbw@f195.suse.de
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
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 determine
> > > the package version via `git describe [...]` in configure.ac. This
> > > doesn't work, because there is no git repository any more. This caused
> > > 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 the
> > > version check failed.
> > >
> >
> > This shouldn't be an issue if the released tarball (as generated by make dist)
> > is used, only when using the source tarball. With the former, there's no need
> > to call bootstrap since a configure script with a PACKAGE_VERSION is shipped.
>
> 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
next reply other threads:[~2018-02-22 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 16:41 Philip Tricca [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-22 20:45 [tpm2] Some issues with tpm2-tss, tpm2-tools regarding packaging Roberts, William C
2018-02-22 20:31 Javier Martinez Canillas
2018-02-22 17:14 Philip Tricca
2018-02-22 16:53 Scheie, Peter M
2018-02-22 16:47 Scheie, Peter M
2018-02-22 15:06 Javier Martinez Canillas
2018-02-22 14:46 Matthias Gerstner
2018-02-22 14:09 Javier Martinez Canillas
2018-02-22 12:34 Matthias Gerstner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180222164136.GA6409@intel.com \
--to=tpm2@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.