From: David Pirotte <david@altosw.be>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guile-devel@gnu.org
Subject: Re: guile-lib: essentially empty guile-library.info in 0.2.8 tarball
Date: Sun, 14 Apr 2024 17:02:32 -0300 [thread overview]
Message-ID: <20240414170232.2e636ce5@tintin> (raw)
In-Reply-To: <877ch22mz6.fsf@wireframe>
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
Hello Vagrant,
> Something seems to be amiss with the generation process for
> guile-library.info, which appears to be mostly empty in the 0.2.8
> tarball, and calling "make -C doc guile-library.info" seems to fail to
> actually (re)generate it.
Indeed, thanks for the report. I'll look into this asap and once
fixed, will release 0.2.8.1 - hopefully within the next few days.
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-04-14 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 23:13 guile-lib: essentially empty guile-library.info in 0.2.8 tarball Vagrant Cascadian
2024-04-14 20:02 ` David Pirotte [this message]
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=20240414170232.2e636ce5@tintin \
--to=david@altosw.be \
--cc=guile-devel@gnu.org \
--cc=vagrant@debian.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 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).