"Alfred M. Szmidt" <ams@gnu.org> writes:

>    It seems to build on my system:
>
> 	   icterid$ make build/vc-fossil
> 	   emacs --batch -l /home/philip/Code/src/nongnu/admin/elpa-admin.el	\
> 		    -f elpaa-batch-make-one-package vc-fossil
> 	   Cloning branch vc-fossil:
> 	   +refs/heads/*:refs/remotes/origin/Preparing worktree (new branch 'elpa/vc-fossil')
> 	   HEAD is now at 7815c30d7 vc-fossil.el: Update from fossil.
> 	   *
>
> 	   ======== Building tarball archive-devel/vc-fossil-20210928.0.20210928.73744.tar...
> 	   ######## Built new package archive-devel/vc-fossil-20210928.0.20210928.73744.tar!
> 	   ======== Building tarball archive/vc-fossil-20210928.tar...
> 	   ######## Built new package archive/vc-fossil-20210928.tar!
>
>    Did you change the history or do you have a local commit with
>    "20210928.0.." as a version number?
>
> No, but could it be how the string is constructed?

ELPA uses functions based on version-to-list to find the commit that the
tarball is based on. From the error message you got, it might be that
you were using an invalid versioning scheme. Consider how

    (version-to-list "1.0.0") ; => (1 0 0)

but

    (version-to-list "1.0..0")

throws an error.

> 	   ======== Building tarball archive-devel/vc-fossil-20210928.0.20210928.73744.tar...
> 	   							        ^^^^^^^^ ^^^^^
> If that those two parts are missing/empty then you will get vc-fossil-20210928.0...tar...

What do you mean, I seem to have everything necessary in the tarball: