Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Fri, 3 Sep 2004 16:41:18 +1000 (EST) From: luke DOT kendall AT cisra DOT canon DOT com DOT au Subject: Re: Setup problem: incomplete nonexistent package To: cygwin AT cygwin DOT com In-Reply-To: <20040903013358.9E1FF8454B@pessard.research.canon.com.au> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20040903064118.809428512B@pessard.research.canon.com.au> Here's an executive summary: it's a mystery. It just started working. In slightly more detail, rsync from another site did replace the TeXmacs package. But re-running setup still failed on TeXmacs. Our local mirror is shared via Samba (v 2.2something). Some hours later, with no extra rsyncs (in fact, after no actions of any kind except running the check script), setup.exe worked. I've appended the md5 check script anyway. Should there be an md5.sum file for setup.exe, setup.bz2 and setup.ini? On 3 Sep, luke wrote: > I tried again installing from our mirror, and it failed with an > incomplete download message on TeXmacs-1.0.3.3-1. I chose not to try > again, and then setup terminated with a runtime exception (as it always > does in that situation: "Runtime exception ... This application has > requested that the Runtime terminate it in an unusual way. Please > contact the application's support team for more information."). > > It also left no log files at all under c:/cygwin/var/log (in fact, the > directory had not been created), and the next time I ran setup it had > not remembered any of the settings I'd chosen. > > I just tried again and it failed the same way, the same package, and > didn't create the log directory so I can't give more details. It did > remember my setup settings the 2nd time, though. > > So, actually, I'm pretty badly off - I have no Cygwin any more (I have > an old version of U/Win I've used to collect some of the info above). > Oh, speaking of which, here's the U/Win ls and md5sum for our setup > directory in our mirror: > > ..../cygwin$ ls -l //samba/mirror/cygwin > total 1858 > drwxrwxr-t 7 322674 262825 512 Sep 1 13:05 mail-archives > drwxrwxr-t245 322674 262825 512 Aug 31 18:40 release > -rw-rw-r-- 1 322674 262825 79753 Sep 3 02:20 setup.bz2 > -rwxrwxr-x 1 322674 262825 268800 Apr 26 01:03 setup.exe > -rwxrwxr-x 1 322674 262825 268800 Oct 7 2003 setup.exe.old > -rw-rw-r-- 1 322674 262825 331860 Sep 3 02:20 setup.ini > drwxrwxr-t 2 322674 262825 512 Apr 4 02:41 tmp > ..../cygwin$ /usr/bin/md5sum.exe //samba/mirror/cygwin/setup.exe > 51db88989d4886688ed9241406961b0e //samba/mirror/cygwin/setup.exe > > > > > luke > > > > Also, read about the "upset" script if you want to have packages on your > > local server in addition to the mirrored ones. Google for "upset script > > site:cygwin.com". > > HTH, > > Igor > > Thanks, I'll have a look - if I can figure out how to install Cygwin > again! > > The mirror site we are currently using, and which I used last night for > the direct attempt, was kernel.org. (I didn't know that I'd chosen > the same site that our SysAdmin rsync to make our mirror, when I chose > it!) > > Setup.exe says it's version 2.427. Our mirror is 2.06GB (2,220,822,916 bytes), > 2,739 files, 491 folders. Sept 3rd 2004. > > I'll try another reboot and see if that helps. No joy. We also synced to another mirror and it didn't help. I've run my script and checked, and some checksums failed, but not the TeXmacs-1.0.3.3-1 one: Summary of files with broken checksums: In ./binutils: md5.sum: FAILED md5sum: WARNING: 1 of 6 computed checksums did NOT match In ./check: check-0.8.4-1-src.tar.bz2: FAILED md5sum: WARNING: 1 of 3 computed checksums did NOT match In ./ncurses/libncurses5: libncurses5-5.2-1-src.tar.bz2: FAILED md5sum: WARNING: 1 of 3 computed checksums did NOT match I'll append the check script in case it's of use to others. (Sorry for the delay, other more urgent problems cropped up for me.) I notice that there is no md5.sum file for setup.exe, setup.bz2 and setup.ini, which I imagine are pretty critical. How do I tell if any of those are suspect? -rw-rw-r-- 1 cameron postdrop 79738 Sep 1 03:00 setup.bz2 -rwxrwxr-x 1 mirror postdrop 268800 Apr 26 01:03 setup.exe -rw-rw-r-- 1 cameron postdrop 331839 Sep 1 03:00 setup.ini $ md5sum setup.bz2 setup.exe setup.ini a1a3a8cc37f1068f769869a70adb3e9b setup.bz2 51db88989d4886688ed9241406961b0e setup.exe aab5a01b13cdcb372b47f3bb632f2371 setup.ini To pick an example one with an apparent problem, check-0.8.4-1-src.tar.bz2: : [luke AT cage] .../check; ls check-0.8.4-1-src.tar.bz2 check-0.8.4-1.tar.bz2 md5.sum setup.hint : [luke AT cage] .../check; md5sum --check md5.sum check-0.8.4-1-src.tar.bz2: FAILED check-0.8.4-1.tar.bz2: OK setup.hint: OK md5sum: WARNING: 1 of 3 computed checksums did NOT match : [luke AT cage] .../check; cat md5.sum 2869c0fb14b9e277931dbe3df22de1ab check-0.8.4-1-src.tar.bz2 52155707ea1c471ff4ec950009174e59 check-0.8.4-1.tar.bz2 925e6963dec65e9da0489cb2d74a638d setup.hint And from our setup.bz2file: @ check sdesc: "A unit test framework for C" ldesc: "Check is a unit test framework for C. It features a simple interface for defining unit tests, putting little in the way of the developer. Tests are run in a separate address space, so Check can catch both assertion failures and code errors that cause segmentation faults or other signals. The output from unit tests can be used within source code editors and IDEs. More information at: http://check.sourceforge.net/" category: Devel requires: cygwin version: 0.8.4-1 install: release/check/check-0.8.4-1.tar.bz2 70344 52155707ea1c471ff4ec950009174e59 source: release/check/check-0.8.4-1-src.tar.bz2 96934 2869c0fb14b9e277931dbe3df22de1ab luke ---------------------- md5cygchk ------------------------------ #!/bin/sh # # Check all the md5 signatures for a Cygwin mirror. # # Author: Luke Kendall # ECHO=echo MD5ARG= MYNAME=`basename "$0"` TMP=/tmp/md5cyg$$ USAGE="Usage: $MYNAME [-q] cygwin-mirror-directory Where -q means quiet, and cygwin-mirror-directory should be the directory where you find setup.bz2 setup.exe setup.ini E.g.: $MYNAME /u/mirror/cygwin/release" trap 'rm -f $TMP; exit 1' if [ "x$1" = "x-q" ] then MD5ARG="--status" ECHO=":" shift fi if [ $# != 1 ] then echo "$USAGE" >&2 exit 1 fi cd $1 || exit 1 if [ ! -s ../setup.bz2 ] then echo "$MYNAME: Not a cygwin download (no file setup.bz2 in $1 parent)" >&2 exit 1 fi find . -type d -print | \ while read dir do pushd "$dir" > /dev/null if [ -s md5.sum ] then $ECHO "$dir:" if md5sum $MD5ARG --check md5.sum then : else { echo echo "In $dir:" md5sum --check md5.sum 2>&1 | grep -v OK } >> $TMP fi elif [ `ls -l | grep "^-" | wc -l` = 0 ] then : else echo "Worrying: $dir has no md5.sum file" >&2 echo "Worrying: $dir has no md5.sum file" >> $TMP fi popd > /dev/null done if [ -s $TMP ] then echo "Summary of files with broken checksums:" cat $TMP rm $TMP exit 1 else $ECHO "--- All files checked okay. ---" exit 0 fi trap '' 0 -- 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/