DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type:content-transfer-encoding; q=dns; s=default; b=rc/
	k0GO16WSpjRfJTtQQfpf3CGKGXmfmb6WhRQkZqKPUha/+vOM+lA1B4X6RhlbPm19
	oJYHdy8mV7so/g+ctknPkR3PJeMEmOjULyi7VRpCCZUlRNObSIpdxs1NnWmM39WI
	o+uiGIPo6o41CMoITCPKivh8qCFkK0AU12TziWJY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
From: =?UTF-8?Q?Bj=C3=B6rn_Kautler?= <Bjoern AT Kautler DOT net>
Date: Mon, 25 Aug 2014 19:33:04 +0200
Message-ID: <CAKChYSru=H790F9i7xCxOctGbyjX7WSp2AkYrg_KVRmtX-Q19w@mail.gmail.com>
Subject: setup.exe handles same packages in multiple mirrors badly
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hi,

I usually start setup.exe like "setup.exe -K
http://cygwinports.org/ports.gpg" and select the cygwinports mirror
and a "normal" mirror in the mirror selection page to have the
packages from both mirrors readily available, selectable and
updatable.

Unfortunatley, setup.exe seems to not handle this properly if a
package is present on both mirrors. When I look at the available
versions for the git packages, then I only see the 1.8 versions from
cygwinports, not the newly released ones from the normal mirror. (yes,
I made sure I selected a mirror where the packages are already
available)

In such a case I think setup.exe should provide the versions of all
the mirrors for selection and auto-select the newest version
cross-mirror for update.

Regards
Björn

--
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