Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 26 Jul 2005 09:10:02 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Luke Kendall <luke DOT kendall AT cisra DOT canon DOT com DOT au>
cc: cygwin AT cygwin DOT com
Subject: Re: Download Incomplete.  Try again?
In-Reply-To: <20050726031421.CFD1E8355D@pessard.research.canon.com.au>
Message-ID: <Pine.GSO.4.61.0507260900500.4962@slinky.cs.nyu.edu>
References: <20050726031421 DOT CFD1E8355D AT pessard DOT research DOT canon DOT com DOT au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Luke,

Please make sure your mailer respects the Reply-To: header -- I set it for
a reason.  There was no need to Cc: me -- I read the list.

On Tue, 26 Jul 2005, Luke Kendall wrote:

> On 25 Jul, Igor Pechtchanski replied to:
>
> > > Is there a way to test if a downloaded cygwin will cause the
> > > "Download Incomplete.  Try again?" error, except by running
> > > setup.exe?
> >
> > Yes, there is.  There is no magic in setup.exe (well, not much, in
> > any case).  Check the filenames, file sizes and md5sums against
> > setup.ini, not the md5.sum files.
>
> Really?!  I modified my md5cychk script to perform that check.  Our old,
> stable, working Cygwin mirror installs and runs fine, and all the
> md5.sum files check correctly against the package files.  But 53 of the
> package files differ in their version against the setup.ini file.
>
> Ah, wait!  Should I only check md5s if a package filename (and hence
> version) in setup.ini matches against a file in the package directory?

Yes.

> Does setup.exe only complain if setup.ini files are a *subset* of the
> files in the package directory?  At the moment I'm checking for perfect
> congruence.

setup.exe only complains if any of the files *it has just downloaded* do
not have the same size or MD5 sum as what's stored in setup.ini.  It does
not match those against *other* files.  So yes, the filenames have to
match perfectly.

> [snip]
>
> > > By looking through the mailing list archives, I got the impression that
> > > this happened when the setup.ini file got out of sync with the
> > > collection of packages - but Christopher explained that setup.ini only
> > > gets updated occasionally.
> >
> > Exactly.
> >
> > > And I can confirm that: many of the package versions in setup.ini don't
> > > match the versions of the packages present, even in stable and
> > > installable cygwin mirrors.
> > >
> > > Is that because setup.ini gets updated manually?
> >
> > Probably yes.  If the mirroring process catches the main Cygwin
> > repository in a state where a package is uploaded, but setup.ini
> > hasn't been updated, the repository will be in an inconsistent state.
>
> Can setup.ini be out of date for long periods, because it is updated
> manually?

I missed the "manually" bit.  As Chris already said, setup.ini does *not*
get updated manually.  It does, however, get updated independently of when
the uploads happen, so there can be a window of inconsistency, as
described above.

> > > Would you like me to try to design an easy system to regenerate it
> > > automatically when packages are updated?  (I'm imagining a tree of
> > > per-package description parts which change infrequently, and a script
> > > which adds the file size and md5 sig automatically.  Perhaps it should
> > > even be a Makefile.)
> >
> > Eh?  There's more to it than that -- setup.ini also has versions, etc.
>
> Oh!  But when we mirror a site, we only see a single setup.ini file.

I meant the package versions.  As in filenames.  See above.

> > > [snip email about setup.ini size/md5sum mismatch (with raw e-mail
> > > addresses, I might add)]
>
> [Oh: the cygwin-xfree address itself?  Sorry. :-(  ]
>
> > > But is that the cause of the problem?
> >
> > Yes.
> >
> > > If not, does anyone know what the real problem is?
> > >
> > > If the only way is by running setup.exe, is that unlikely to damage an
> > > older, working Cygwin install?
> >
> > If you run setup in download mode, you will not affect the existing
> > install.
>
> I think it does: the download would fail with the above error message,
> so you would know not to proceed?

This was unclear: you think it does affect the existing install, or you
think it does the right thing?  Again, if you run setup and select
"Download only", it should not do *anything* with the existing
installation other than add files to the setup package cache.

> I think I'm starting to understand.  (With some gaps, though.)

Good (the understanding, not the gaps).  There's always the source of
setup.exe to guide you though the hairy (and magic) parts...  :-)
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/