Re: gEDA-dev: gEDA/gaf 20060906 source tarballs released

[Stuart Brorson <sdb-at-NOSPAMcloud9_dot_net>]

>>>> The geda-gschem package fails to compile on SuSE 9.3.
>>>> The compiler is gcc-3.3.5. It doesn't like the missing "static void" 
>>>> statment in the definition of the function print_dialog_get_property in 
>>>> x_print.c.
>> 
>> I hate to say this, but I found and fixed that bug in CVS.   The
>> problem was that the fcn print_dialog_get_property had mysteriously
>> lost its declaration.   I put it back.
>> 
>> Unfortunately, I fixed it *after* Ales
>> produced his release.  On the other hand, I *did* fix it for the
>> gEDA/gaf release I put on the gEDA CD, which you can get from the gEDA
>> download site.  The CD release you want is 20060907.
>> 
>> I'll let Ales decide if he wants to respin the tarballs. . . . .
>> Personally, I'd just replace the geda-gschem tarball with a fixed one,
>> but wouldn't bump the rev date since it's such a hassle.
>
> Please no!! A number of packaging systems store cryptographic hashes of 
> distfiles.  Changing them without changing the name always triggers a big 
> headache for package maintainers.  What happens is some users have the old 
> ones, some have the new ones, some amount of complaing later the packager 
> realizes something has changed.  Then you get to down load the new files, do 
> diffs to figure out what happened, and now users with the old files suddenly 
> get complaints about checksum mismatches....

Funny you should say that.   After I wrote my last e-mail I decided to
just take matters into my own hands and fix the problem.  Accordingly,
I made a tarball of the fixed geda-gschem and logged into seul.org in
preparation to upload the fixed tarball.  Once in there I noticed that
Ales put a .md5 file in the  directory.  "Oh, oh", I thought to
myself.  "I need to deal with the .md5 stuff too".  That's when I
dropped the project, leaving the old geda-gschem file in place

I guess I could create the MD5 sum and stick it into the project
directory.  However, are there other crypto signatures I would need to
worry about if I were to fix the file?

Stuart


_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev