From: Marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mc-4.7.5.3-1
Date: Fri, 05 Aug 2011 09:14:00 -0000 [thread overview]
Message-ID: <4E3BB450.8010801@gmail.com> (raw)
In-Reply-To: <j1gb11$62p$1@dough.gmane.org>
On 8/5/2011 10:53 AM, Oleksandr Gavenko wrote:
> 05.08.2011 10:41, Marco atzeri пиÑеÑ:
>> On 8/5/2011 9:34 AM, Oleksandr Gavenko wrote:
>>> But I have issue.
>>>
>>> 'setup.ini' does not contain entry for new version.
>>> So can not be installed through setup.exe.
>>>
>>> Then I change 'setup.ini' to:
>>>
>>> version: 4.7.5.3-1
>>> install: release/mc/mc-4.7.5.3-1.tar.bz2 1581910
>>> 249bd9605be1bbcc8306ee3ab11b208e
>>> [prev]
>>> version: 4.6.1-2
>>> install: release/mc/mc-4.6.1-2.tar.bz2 496091
>>> 319bd9a93a1649c63a6094adec4da616
>>> source: release/mc/mc-4.6.1-2-src.tar.bz2 3954074
>>> a63c4c686d07f2fa28e92a14fbe22edc
>>>
>>> setup.exe purpose upgrade to new version.
>>
>> you have likely a proxy/cache problem.
>> The setup.ini reports 4.7.5.3-1 as current version
>>
> I use rsync://mirrors.kernel.org/mirrors/sourceware
>
> setup.bz2 have updated contend. But setup.ini outdated!
>
> If I run setup.exe on local copy of repo setup uses setup.ini.
>
> I rsync with --delete. Why mirrors provide outdated files?
> Or I am something missing?
>
http://mirrors.kernel.org/sourceware/cygwin/setup.ini
looks fine
have you catched the mirror during the sync with the primary ?
Regards
Marco
--
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
next prev parent reply other threads:[~2011-08-05 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 11:25 Marco atzeri
2011-08-05 7:34 ` Oleksandr Gavenko
2011-08-05 7:42 ` Marco atzeri
2011-08-05 8:53 ` Oleksandr Gavenko
2011-08-05 9:14 ` Marco atzeri [this message]
2011-08-05 10:39 ` Oleksandr Gavenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E3BB450.8010801@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).