Updated: setup.exe (Release 2.867)

Corinna Vinschen corinna-cygwin@cygwin.com
Mon Feb 16 09:33:00 GMT 2015

On Feb 16 14:12, Luke Kendall wrote:
> On 10/02/15 09:39, Luke Kendall wrote:
> >On 06/02/15 21:23, Corinna Vinschen wrote:
> > > "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.
> >
> >Hmm, that's interesting.
> >
> >I based what I said on my experience; I've tried to work out how it fits
> >together by looking at the files we get via rsyncing from mirrors.  It's
> >not like I've read some reference that describes the Cygwin packaging
> >and release process and procedures (I have a feeling that such a
> >reference would be setup.exe's source code, by I may also be quite
> >mistaken about that).
> >
> >But the mismatches have been so common, and persisted so long, that I
> >(perhaps wrongly) came to the conclusion that relying on the md5.sum
> >file was bad, simply because in all the mismatches I've seen over the
> >last several months (I'm guessing something like six), setup.ini has
> >been correct and the package md5.sum has been wrong; and the error has
> >persisted for many, many days.
> >
> >I suppose another possibility is that we *think* we're rsyncing nightly,
> >and we're not, and it's only the automated consistency check that's
> >really running each night!  I'll check into that possibility.
> Just to close this off: this was indeed the answer.  We had rsync-ed -src
> and debuginfo packages at one point, but they were being excluded those from
> the nightly updates.  (I was unaware of that.)
> So I was wrong.  I apologise for the mistake.

No reason to apologize.  But it's nice to know the problem is known
and fixed.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20150216/64cca77a/attachment.sig>

More information about the Cygwin mailing list