From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: cygwin@cygwin.com
Subject: Re: installed 3.5.1-1 but uname shows 3.4.9-1.x86_64
Date: Sun, 3 Mar 2024 16:22:02 -0700 [thread overview]
Message-ID: <06b1586f-c38a-4b05-bbe9-e134523dfdf6@SystematicSW.ab.ca> (raw)
In-Reply-To: <CAJ1FpuNMJLBg9ZT0gc-_t=bWe9nQOfNdtqCgSgMqxMKbf+_6qw@mail.gmail.com>
On 2024-03-03 15:29, Doug Henderson via Cygwin wrote:
> A recent run of setup showed it installed 3.5.1-1 but uname -a reports
> 3.4.9-1.x86_64
>
> $ uname -a
> CYGWIN_NT-10.0-19045 mars 3.4.9-1.x86_64 2023-09-06 11:19 UTC x86_64 Cygwin
>
> I used setup to reinstall cygwin 3.5.1-1 but uname still reports
> 3.4.9-1. I don't see any errors reported during setup execution. Is
> there another way to check the cygwin version from bash?
/proc/version - `less` does not work on these files
> Remind me where setup saves its log files, and is there a way to get
> extra debugging info to help diagnose this issue.
/var/log/setup.log{.full,} - .full is latest - .log is summary of that and prior
> The cache shows
>
"D:\Users\USER\Down_Loads\cygwin64cache\https%3a%2f%2fmirrors.kernel.org%2fsourceware%2fcygwin%2f\x86_64\release\cygwin\cygwin-3.5.1-1.tar.xz"
> as the latest file in its folder
Hint - closer mirrors are:
https://muug.ca/mirror/cygwin/ - no or little lag
http://mirror.cpsc.ucalgary.ca/mirror/cygwin.com/ - few hours lag
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2024-03-03 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 22:29 Doug Henderson
2024-03-03 23:22 ` Brian Inglis [this message]
2024-03-04 2:24 ` Doug Henderson
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=06b1586f-c38a-4b05-bbe9-e134523dfdf6@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).