This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Updated: setup.exe (Release 2.867)


On Feb  6 13:05, Luke Kendall wrote:
> On 06/02/15 05:07, Corinna Vinschen wrote:
> >Hi folks,
> >
> >A new version of Setup, release 2.867, has been uploaded to
> >
> >   https://cygwin.com/setup-x86.exe     (32 bit version)
> >   https://cygwin.com/setup-x86_64.exe  (64 bit version)
> >
> >The changes compared to 2.864 are mostly not visible:
> >
> >- There's one fix to the output when mistyping a command line option.
> >
> >- More importantly, Setup now understands SHA512 checksums additionally
> >   to MD5 checksums.  We're going to switch to using SHA512 checksums in
> >   the setup.ini files in a couple of weeks and this requires all of you
> >   to use the newer Setup version.
> >
> >
> >Please send bug reports, as usual, to the public mailing list
> >cygwin AT cygwin DOT com.
> >
> >
> >Have fun,
> >Corinna
> >
> 
> I was just wondering, will you be dropping the md5.sum files from the
> package directories at the same time?

The md5.sum files are created for all ftp dirs on sourceware.org, not
only for the Cygwin dirs.  Right now we still need the md5.sum files
to support people who haven't upgraded setup yet.  If the files get
removed (not created anymore) at one point is up to the overseers crew.

>   Just this week I
> noticed that cygwin64-gcc-4.8.3-4-src.tar.xz's md5 checksum in its md5.sum
> file was incorrect (but its md5 in setup.ini was of course correct).

"Of course"?  In fact upset (the script creating the setup.ini files)
reads the content of md5.sum and uses the checksums in there if
available to create the setup.ini entry.  It only computes its own
checksum if the md5.sum file is missing the info.  So, afaics, in border
cases in which a file gets replaced, there is a chance that the
setup.ini checksum is incorrect as well.  In theory that's not supposed
to happen because replacing a distro package should always include
bumping the subversion, thus creating a new file and just removing the
old one.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: pgpyVBg8Na84S.pgp
Description: PGP signature


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]