From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: 1.1.0rc1 available for test!
Date: Thu, 09 Apr 2020 20:20:15 -0700 [thread overview]
Message-ID: <871row58nk.fsf@yucca> (raw)
In-Reply-To: <87369c1ixm.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2041 bytes --]
On 2020-04-09, Ludovic Courtès wrote:
> Hello Guix!
>
> I’ve run “make release” from the new ‘version-1.1.0’ branch and uploaded
> the result:
>
> https://web.fdn.fr/~lcourtes/software/guix/1.1.0rc1
The only tarball I see there is:
https://web.fdn.fr/~lcourtes/software/guix/1.1.0rc1/guix-1.0.1.13450-01d5f2.tar.gz
Which does not correspond to the commit from 01d5f2 (which happens to be
a few hundred commits behind master)...
Which commit was it actually built with? I know it's not a release, per
se, but git tags would be *really* helpful even for release candidates...
When building my own local guix tarballs, I found it disturbingly easy
to get the wrong version information into the tarball .version and
.tarball-version and consequently the resulting tarball...
It also appears to be missing gnu/services/linux.scm, which causes it to
fail to build when I attempt to build the debian package:
[ 49%] LOAD gnu/tests/linux-modules.scm
WARNING: (guix build download-nar): `dump-port*' imported from both (guix serialization) and (guix progress)
;;; Failed to autoload make-page-map in (charting):
;;; missing interface for module (charting)
;;; Failed to autoload make-page-map in (charting):
;;; missing interface for module (charting)
random seed for tests: 1586480372
error: failed to load 'gnu/tests/linux-modules.scm':
ice-9/eval.scm:293:34: no code for module (gnu services linux)
Some deprecated features have been used. Set the environment
variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
program to get more information. Set it to "no" to suppress
this message.
make[3]: *** [Makefile:5859: make-go] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>'
But gnu/services/linux.scm is present in git...
I notice gnu/services/linux.scm is also missing in some of my locally
built git snapshot tarballs, so there appears to be something broken in
the tarball generation process.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-04-10 3:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 20:51 1.1.0rc1 available for test! Ludovic Courtès
2020-04-09 21:33 ` Danny Milosavljevic
2020-04-10 1:56 ` pelzflorian (Florian Pelz)
2020-04-10 10:38 ` Ludovic Courtès
2020-04-10 12:06 ` Mathieu Othacehe
2020-04-10 14:35 ` pelzflorian (Florian Pelz)
2020-04-10 14:47 ` pelzflorian (Florian Pelz)
2020-04-13 18:12 ` pelzflorian (Florian Pelz)
2020-04-10 3:20 ` Vagrant Cascadian [this message]
2020-04-10 10:29 ` Ludovic Courtès
2020-04-10 11:24 ` Alex Sassmannshausen
2020-04-10 12:01 ` Mathieu Othacehe
2020-04-10 12:19 ` Alex Sassmannshausen
2020-04-10 12:07 ` Alex Sassmannshausen
2020-04-10 12:17 ` Mathieu Othacehe
2020-04-10 13:11 ` Alex Sassmannshausen
2020-04-10 13:53 ` Mathieu Othacehe
2020-04-10 14:19 ` Ludovic Courtès
2020-04-10 16:02 ` Alex Sassmannshausen
2020-04-10 15:42 ` Alex Sassmannshausen
2020-04-10 22:38 ` Ludovic Courtès
2020-04-11 9:11 ` alex sassmannshausen
2020-04-11 13:16 ` Amin Bandali
2020-04-11 13:48 ` Pierre Neidhardt
2020-04-10 15:45 ` Alex Sassmannshausen
2020-04-11 10:51 ` Vincent Legoll
2020-04-11 22:26 ` Ludovic Courtès
2020-04-12 6:43 ` Vincent Legoll
2020-04-13 10:50 ` Ludovic Courtès
2020-04-13 11:46 ` Vincent Legoll
2020-04-13 12:36 ` Vincent Legoll
2020-04-13 16:14 ` Vincent Legoll
2020-04-13 20:24 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871row58nk.fsf@yucca \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).