X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Date: Fri, 5 Feb 2010 09:46:27 -0700 From: Tom Schutter To: cygwin AT cygwin DOT com Subject: Re: unable to install multiple packages from the command line Message-ID: <20100205164627.GA14688@proxix.com> References: <20100203181210 DOT GU3947 AT proxix DOT com> <4B6C3D71 DOT 7080208 AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B6C3D71.7080208@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Fri 2010-02-05 09:46, Dave Korn wrote: > On 03/02/2010 18:12, Tom Schutter wrote: > > Installing multiple packages from the the command line used to work, but no > > longer does for me. It installs the first requested package, but none of > > the rest. > > > Note that --help doesn't say exactly how to specify multiple packages. A > > comma separated list used to work. Specifying multiple --packages options > > gives no warning or error, but only installs the last requested package. > > After investigating, I can't reproduce any problem. The glitch I mentioned > yesterday was just a pilot error owing to me using an old script from before > -C and -P became separate options. > > > PS C:\cygwin> C:\cygwin\setup.exe --quiet-mode --no-shortcuts --root C:\cygwin --local-package-dir C:\cygwin\LocalPackageDir --packages netcat,procps > > Starting cygwin install, version 2.680 > > > getUrlToStream http://mirrors.xmission.com/cygwin//setup.bz2.sig > > Added manual package netcat > > Changing gid back to original > > Visited: 63 nodes out of 1678 while creating dependency order. > > So that's very odd. Can you check the cached setup.ini in your local > package dir and see if it's damaged or for some other reason doesn't mention > procps? And try adding "-D -L" to your command-line and see if that makes any > difference? I checked the setup.ini, and AFAICT it is not damaged. It does mention procps. I can pick *any* pair (or list) of packages and only the first will be installed. If I then try to install the second package, it installs OK. I have also reproduced this on another machine. When I ran the "-D -L" test, I got a "current ini file is from a newer version of setup.exe" message. My setup was version 2.680. I went ahead with the test using the older setup.exe. The outcome did not change. I then retried the test with setup.exe version 2.682. No change, only the first package installs. -- Tom Schutter First American Spatial Solutions 303-440-7272 x6822 512-977-6822 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple