* git-version-gen: allow 'snapshot' as .tarball-version contents
@ 2019-10-13 16:30 Bruno Haible
2019-10-13 19:52 ` Dmitry V. Levin
0 siblings, 1 reply; 5+ messages in thread
From: Bruno Haible @ 2019-10-13 16:30 UTC (permalink / raw)
To: bug-gnulib
Hi,
git-version-gen currently rejects some forms of .tarball-version:
$ cat > .tarball-version
20191011
$ build-aux/git-version-gen .tarball-version; echo
20191011
$ cat > .tarball-version
snapshot
$ build-aux/git-version-gen .tarball-version; echo
build-aux/git-version-gen: WARNING: .tarball-version is missing or damaged
UNKNOWN
I need a non-numeric version for continuous publishing of gettext snapshot
tarballs, and I want the tarballs to be called gettext-snapshot.tar.gz,
not gettext-UNKNOWN.tar.gz.
This patch fixes the problem.
2019-10-13 Bruno Haible <bruno@clisp.org>
git-version-gen: Allow 'snapshot' as .tarball-version contents.
* build-aux/git-version-gen: Don't map non-numeric .tarball-version
contents to the empty string.
diff --git a/build-aux/git-version-gen b/build-aux/git-version-gen
index 45b5656..d855645 100755
--- a/build-aux/git-version-gen
+++ b/build-aux/git-version-gen
@@ -142,11 +142,9 @@ then
v=`cat $tarball_version_file` || v=
case $v in
*$nl*) v= ;; # reject multi-line output
- [0-9]*) ;;
- *) v= ;;
esac
test "x$v" = x \
- && echo "$0: WARNING: $tarball_version_file is missing or damaged" 1>&2
+ && echo "$0: WARNING: $tarball_version_file is damaged" 1>&2
fi
if test "x$v" != x
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: git-version-gen: allow 'snapshot' as .tarball-version contents
2019-10-13 16:30 git-version-gen: allow 'snapshot' as .tarball-version contents Bruno Haible
@ 2019-10-13 19:52 ` Dmitry V. Levin
2019-10-13 21:18 ` Bruno Haible
0 siblings, 1 reply; 5+ messages in thread
From: Dmitry V. Levin @ 2019-10-13 19:52 UTC (permalink / raw)
To: bug-gnulib
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
Hi,
On Sun, Oct 13, 2019 at 06:30:47PM +0200, Bruno Haible wrote:
> Hi,
>
> git-version-gen currently rejects some forms of .tarball-version:
>
> $ cat > .tarball-version
> 20191011
> $ build-aux/git-version-gen .tarball-version; echo
> 20191011
> $ cat > .tarball-version
> snapshot
> $ build-aux/git-version-gen .tarball-version; echo
> build-aux/git-version-gen: WARNING: .tarball-version is missing or damaged
> UNKNOWN
>
> I need a non-numeric version for continuous publishing of gettext snapshot
> tarballs, and I want the tarballs to be called gettext-snapshot.tar.gz,
I wonder how users of these tarballs would be able to identify
snapshots if there is no version information.
--
ldv
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: git-version-gen: allow 'snapshot' as .tarball-version contents
2019-10-13 19:52 ` Dmitry V. Levin
@ 2019-10-13 21:18 ` Bruno Haible
2019-10-13 21:31 ` Assaf Gordon
0 siblings, 1 reply; 5+ messages in thread
From: Bruno Haible @ 2019-10-13 21:18 UTC (permalink / raw)
To: bug-gnulib
Dmitry V. Levin wrote:
> > I need a non-numeric version for continuous publishing of gettext snapshot
> > tarballs, and I want the tarballs to be called gettext-snapshot.tar.gz,
>
> I wonder how users of these tarballs would be able to identify
> snapshots if there is no version information.
They can remember the date at which they downloaded the snapshot.
Ideally a download would have a stable URL _and_ a version number. In some
cases, this is not possible or extra effort. I find that for CI tarballs a
stable URL is the more important feature.
Bruno
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: git-version-gen: allow 'snapshot' as .tarball-version contents
2019-10-13 21:18 ` Bruno Haible
@ 2019-10-13 21:31 ` Assaf Gordon
2019-10-13 21:40 ` Bruno Haible
0 siblings, 1 reply; 5+ messages in thread
From: Assaf Gordon @ 2019-10-13 21:31 UTC (permalink / raw)
To: Bruno Haible, bug-gnulib
Hello Bruno,
On 2019-10-13 3:18 p.m., Bruno Haible wrote:
> Dmitry V. Levin wrote:
>>> I need a non-numeric version for continuous publishing of gettext snapshot
>>> tarballs, and I want the tarballs to be called gettext-snapshot.tar.gz,
>>
>> I wonder how users of these tarballs would be able to identify
>> snapshots if there is no version information.
>
> I find that for CI tarballs a
> stable URL is the more important feature.
>
Somewhat related:
If you're posting the tarballs to ftp.gnu.org or alpha.gnu.org ,
the upload script (build-aux/gnupload) can create symlinks,
and even provide examples of symlinking a "-latest.tar.gz" to a
versioned one:
----
$ gnupload --help
[...]
4. Create a symbolic link foobar-latest.tar.gz -> foobar-1.0.tar.gz
and likewise for the corresponding .sig file:
gnupload --to ftp.gnu.org:foobar \
--symlink foobar-1.0.tar.gz foobar-latest.tar.gz \
foobar-1.0.tar.gz.sig foobar-latest.tar.gz.sig
----
Would that help with a stable URL for testing?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: git-version-gen: allow 'snapshot' as .tarball-version contents
2019-10-13 21:31 ` Assaf Gordon
@ 2019-10-13 21:40 ` Bruno Haible
0 siblings, 0 replies; 5+ messages in thread
From: Bruno Haible @ 2019-10-13 21:40 UTC (permalink / raw)
To: Assaf Gordon; +Cc: bug-gnulib
Hello Assaf,
> >> I wonder how users of these tarballs would be able to identify
> >> snapshots if there is no version information.
> >
> > I find that for CI tarballs a
> > stable URL is the more important feature.
> >
>
> Somewhat related:
>
> If you're posting the tarballs to ftp.gnu.org or alpha.gnu.org ,
> the upload script (build-aux/gnupload) can create symlinks,
> and even provide examples of symlinking a "-latest.tar.gz" to a
> versioned one:
> ----
> $ gnupload --help
> [...]
> 4. Create a symbolic link foobar-latest.tar.gz -> foobar-1.0.tar.gz
> and likewise for the corresponding .sig file:
> gnupload --to ftp.gnu.org:foobar \
> --symlink foobar-1.0.tar.gz foobar-latest.tar.gz \
> foobar-1.0.tar.gz.sig foobar-latest.tar.gz.sig
> ----
>
> Would that help with a stable URL for testing?
Yes, symlinks like this solve the problem.
However, the continuous integration happens on non-GNU machines, and
I'm not sure I would want to upload the secret part of my (or anyone else's)
GPG key to a cloud platform, for security reasons. It could/would compromise
the trust people have in the gnu-keyring.gpg.
Bruno
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-10-13 21:40 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-13 16:30 git-version-gen: allow 'snapshot' as .tarball-version contents Bruno Haible
2019-10-13 19:52 ` Dmitry V. Levin
2019-10-13 21:18 ` Bruno Haible
2019-10-13 21:31 ` Assaf Gordon
2019-10-13 21:40 ` Bruno Haible
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).