From: David Pirotte <david@altosw.be>
To: "Tommi Höynälänmaa" <tommi.hoynalanmaa@gmail.com>
Cc: wingo@pobox.com, guile-user <guile-user@gnu.org>,
Thorsten Alteholz <debian@alteholz.de>
Subject: Re: Files missing in the release package
Date: Sun, 25 Nov 2018 15:00:28 -0200 [thread overview]
Message-ID: <20181125150028.1653e1ef@capac> (raw)
In-Reply-To: <ecc78be6-089f-74f8-4872-4c698c9aa6ab@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
Hi Tommi,
Please send these messages to guile-user, which is the recommended email
address for guile-cairo
> The package guile-cairo-1.1.10 in the release area is missing file
> build-aux/git-version-gen. Consequently autoreconf doesn't work and a
> Debian package can't be build. When I do git clone for the code the file
> is downloaded OK. File gitlog-to-changelog is missing from the release
> package, too, but I'm not sure if it is needed.
I see Daniel did change the configure.ac AC_INIT call, so the version string is
computed ... which is permitted [1]. You see, the problem here is you are not
supposed t rerun ./autogen.sh when you install using a tarball
This said, I know Debian asks (for license checks if I remember correctly), that
Debian maintainers do rerun 'autoreconf -vif':
I suggest you manually change this AC_INIT call, and replace the m4_esyscmd
by the version you are releasing, in this case 1.10.0
[ not that this is version 1.10.0 (not 1.1.10)
Daniel,
I see you also manually added AC_SUBST(VERSION, 1.10.0) (line 40), I think this
not necessary and redundant?
David
[1]
https://www.gnu.org/software/autoconf/manual/autoconf-2.67/html_node/Initializing-configure.html
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
parent reply other threads:[~2018-11-25 17:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <ecc78be6-089f-74f8-4872-4c698c9aa6ab@gmail.com>]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181125150028.1653e1ef@capac \
--to=david@altosw.be \
--cc=debian@alteholz.de \
--cc=guile-user@gnu.org \
--cc=tommi.hoynalanmaa@gmail.com \
--cc=wingo@pobox.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).