Re: Setup.exe issues between Win2k and WinXP - does it use different logic for setup retrieval or package ver selection
On Feb 4 12:03, Brian Keener wrote: Brian Keener wrote: ftp://ftp.gtlib.gatech.edu/pub/cygwin/ http://prc-tools.sourceforge.net/install ftp://sourceware.mirrors.tds.net/pub/sourceware.org/cygwin/ the prc-tools is for my Palm code but both last-mirrors have the same mirrors in the same order. The continuing saga - right after my last post on this setup started reporting the same packages for both the WinXP and the Win2k machine as it should and that as worked for several checks since then but now today and this is too weird - I went to update using setup and all both the WinXp and the Win2k laptop both reported a boat load full of packages that needed updating and in most cases the new was less than the current. I am still using the same mirrors as documented above. Any thought on this as all? Why I keep seeing this and now it happened on both machines not just the Win2k. Could that be a result of the setup.ini problem? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: Setup.exe issues between Win2k and WinXP - does it use different logic for setup retrieval or package ver selection
Corinna Vinschen wrote: Could that be a result of the setup.ini problem? That most recent issue yes - I reported that before cgf reported the upset issue and my issue cleared up when he resolved that. I was able to update as expected after his fix. My previous posts as to why WinXP would report one set of updates and my Win2k a different set I never did figure out. After several attempts at updating and the two versions reporting differences they miraculously resolved themselves and I still have no clue. But yes both systems are in sync and up to date. Thanks bk
Re: Setup.exe issues between Win2k and WinXP - does it use different logic for setup retrieval or package ver selection
Brian Keener wrote: ftp://ftp.gtlib.gatech.edu/pub/cygwin/ http://prc-tools.sourceforge.net/install ftp://sourceware.mirrors.tds.net/pub/sourceware.org/cygwin/ the prc-tools is for my Palm code but both last-mirrors have the same mirrors in the same order. The continuing saga - right after my last post on this setup started reporting the same packages for both the WinXP and the Win2k machine as it should and that as worked for several checks since then but now today and this is too weird - I went to update using setup and all both the WinXp and the Win2k laptop both reported a boat load full of packages that needed updating and in most cases the new was less than the current. I am still using the same mirrors as documented above. Any thought on this as all? Why I keep seeing this and now it happened on both machines not just the Win2k. Thanks bk
Re: Setup.exe issues between Win2k and WinXP - does it use different logic for setup retrieval or package ver selection
More on this. Brian Keener wrote: Mirror Error: Setup.ini signature file ftp://ftp.gtlib.gatech.edu/pub/cygwin/setup.bz2.sig from ftp://ftp.gtlib.gatech.edu/pub/cygwin/ failed to verify. Possible corrupt mirror? Setup.ini rejected. I found several emails regarding the -X command line option for setup.exe to ignore the sig files which took care of the above errors - yes I should have searched more for command line options or the word signature - my apologies. Although I'm not sure why the Win2k install was seeing this but the WinXp install was not. After that I started digging deeper WinXp said certain packages were current but the Win2k install wanted the earlier version. As I mention previously: If I then look at the downloaded setup.ini files on each machine in the download directory the files match what setup showed for that machine - IE the setup.ini file for the same mirror for the 2 different machines is different even though I ran the setup.ini simultaneously so I could see what happened that was different. I did this test again but went a step further. I saved the setup.exe from cygwin.com on both machines and ran it - this created a setup.ini file for each of the mirrors I previously mentioned. Looking at the WinXp version for 2 packages I know had issues (libcairo-devel and libcairo) the setup.ini from the gatech mirror had the current versions (1.8...). When I looked at the Win2k version it showed the older versions (1.6...). I then downloaded the setup.bz2 from the gatech mirror on each machine and when I bunzip2'd it on each machine the libcairo entries on the Winxp matched the setup.ini and the setup from setup.bz2 on the win2k also had the correct versions but the setup.ini file looks strange - see examples: This is from setup.bz2: setup-timestamp: 1232614829 setup-version: 2.573.2.3 @ libcairo-devel sdesc: Cross-device vector graphics library (development files) ldesc: Cairo is a vector graphics library with cross-device output support. Currently supported output targets include the X Window System and in-memory image buffers. PostScript and PDF file output is planned. Cairo is designed to produce identical output on all output media while taking advantage of display hardware acceleration when available (eg. through the X Render Extension). category: X11 requires: cygwin libcairo2 libfontconfig-devel libfreetype2-devel libglitz-devel libpixman1-devel libpng12-devel libX11-devel libxcb-devel libxcb-render-devel libxcb-render-util-devel libXrender-devel zlib version: 1.8.6-1 install: release/X11/cairo/libcairo-devel/libcairo-devel-1.8.6-1.tar.bz2 129458 6e3f9c0035411386cb7536f755101df8 source: release/X11/cairo/cairo-1.8.6-1-src.tar.bz2 6467933 fe2a51e7153b02fae60a9b09df234500 [prev] version: 1.6.4-2 install: release/X11/cairo/libcairo-devel/libcairo-devel-1.6.4-2.tar.bz2 116101 fd59249e987b9b601e6645e7f6aced59 source: release/X11/cairo/cairo-1.6.4-2-src.tar.bz2 4983611 d8037f7f113bf8c3601d04ff4cba0e46 @ libcairo2 sdesc: Cross-device vector graphics library (runtime) ldesc: Cairo is a vector graphics library with cross-device output support. Currently supported output targets include the X Window System and in-memory image buffers. PostScript and PDF file output is planned. Cairo is designed to produce identical output on all output media while taking advantage of display hardware acceleration when available (eg. through the X Render Extension). category: X11 requires: cygwin libfontconfig1 libfreetype26 libglitz1 libpixman1_0 libpng12 libX11_6 libxcb1 libxcb-render0 libxcb-render-util0 libXrender1 zlib version: 1.8.6-1 install: release/X11/cairo/libcairo2/libcairo2-1.8.6-1.tar.bz2 418727 143c593fb16f6ab074eb8838e6127717 source: release/X11/cairo/cairo-1.8.6-1-src.tar.bz2 6467933 fe2a51e7153b02fae60a9b09df234500 [prev] version: 1.6.4-2 install: release/X11/cairo/libcairo2/libcairo2-1.6.4-2.tar.bz2 431551 9de3b276afd7861f75c79cdab0eb628a source: release/X11/cairo/cairo-1.6.4-2-src.tar.bz2 4983611 d8037f7f113bf8c3601d04ff4cba0e46 and this is from the setup.ini that resulted: setup-timestamp: 1231305645 setup-version: 2.573.2.3 @ libcairo-devel sdesc: Cross-device vector graphics library (development files) ldesc: Cairo is a vector graphics library with cross-device output support. Currently supported output targets include the X Window System and in-memory image buffers. PostScript and PDF file output is planned. Cairo is designed to produce identical output on all output media while taking advantage of display hardware acceleration when available (eg. through the X Render Extension). category: X11 requires: cygwin libcairo2 libX11-devel libXrender-devel libfontconfig-devel libfreetype2-devel libglitz-devel libpixman1-devel libpng12-devel zlib version: 1.6.4-2 install: release/X11/cairo/libcairo-devel/libcairo-devel-1.6.4-2.tar.bz2 116101 fd59249e987b9b601e6645e7f6aced59 source: release/X11/cairo/cairo-1.6.4-2-src.tar.bz2 4983611
Setup.exe issues between Win2k and WinXP - does it use different logic for setup retrieval or package ver selection
I have noticed a different in my 2 machines I keep Cygwin on. If I use a self compiled version (same compile) on each machine I get different results as to the Package version selection - for now I will leave this out of the discussion. Trying to determine what this might be - I went and ran the setup.exe on each machine directly from the cygwin.com site (www.cygwin.com). One machine is a laptop and WinXP and the other is a desktop Win2k. They each use the same mirrors and the last-mirror file on each shows: ftp://ftp.gtlib.gatech.edu/pub/cygwin/ http://prc-tools.sourceforge.net/install ftp://sourceware.mirrors.tds.net/pub/sourceware.org/cygwin/ the prc-tools is for my Palm code but both last-mirrors have the same mirrors in the same order. Yet when I ran setup.exe from the web the WinXP machine advised: unable to get http://prc-tools.sourceforge.net/install/setup.ini.sig from http://prc-tools.sourceforge.net/install which really doesn't surprise me as there probably is a setup.ini.sig. But on the Win2k machine I got: Mirror Error: Setup.ini signature file ftp://ftp.gtlib.gatech.edu/pub/cygwin/setup.bz2.sig from ftp://ftp.gtlib.gatech.edu/pub/cygwin/ failed to verify. Possible corrupt mirror? Setup.ini rejected. And then when I click ok it gives me the same message about the setup.ini.sig from prc-tools - again understandable. But why does the XP machine not have an issue with the gatech mirror but the Win2k machine does and it happens each time not just once. When I click OK on the message about the prc-tools message for setup.ini.sig I then get the message about the corrupt mirror but this time for the sourceware.mirrors.tds.net site. But when you click ok it then continues to download the setup.ini and parse it. This brings us back to the original message about the difference in selected packages - the WinXP machine says I need to update libapr1, util-linux, xinit, and xterm and in this case the Win2k machine says no updates are needed but the two machines are at the same version of each of these packages. If I then look at the downloaded setup.ini files on each machine in the download directory the files match what setup showed for that machine - IE the setup.ini file for the same mirror for the 2 different machines is different even though I ran the setup.ini simultaneously so I could see what happened that was different. Any thoughts - are there supposed to be 2 versions based on if it is Win2k vs WinXP bk
