Maxima 5.26.0 tagged in Git & posted to SF

I created (a couple of weeks ago) an annotated tag (git tag -a) which
has the name or annotation '5.26.0' to work around the
problem created by a dash. make dist-gzip builds a tarball and
rpmbuild gets most of the
way through its work; everything is compiled but then rpmbuild craps
out with an error
about a directory (I forget the error was). I looked at the build directory
and it looks like the top-level 5.26.0 directory is missing,
i.e. the children of 5.26.0 in a normal build tree are at the place in the
directory hierarachy where I expected to find 5.26.0.

So I don't know where to go from here. I reverted the git tag stuff
on branch-5_26 but maybe we can fix it on the trunk.

best

Robert Dodier

On 12/21/11, Raymond Toy <toy.raymond at gmail.com> wrote:
> On Sun, Dec 18, 2011 at 4:18 PM, Robert Dodier
> <robert.dodier at gmail.com>wrote:
>
>> Hi,
>>
>> I've tagged 5.26.0 (on the branch-5_26 branch) in Git and
>> built rpms and tar.gz and uploaded them to the SF file manager.
>> http://sourceforge.net/projects/maxima/files
>>
>> Please give it a try and let us know if it works or doesn't.
>>
>> For the record, I reverted the Git stuff to set VERSION in
>> configure.in -- it led to some problem in rpmbuild about
>> a missing directory. Maybe someone can figure out what's
>> up with that.
>>
>>
> Sorry for the trouble.  It looks like the VERSION can't contain dashes.  If
> we replace the dashes in the version with underscores, it seems to work.
> I've never tried to create an RPM before, and it's still not quite working
> for me, but rpmbuild at least tries to reconfigure and build from the
> sources.
>
> If you could test that for me and let me  if that actually works, I can
> apply the fix in configure.in.
>
> Ray
>