public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Alexander Kleinsorge <aleks@physik.tu-berlin.de>
Cc: cygwin@cygwin.com
Subject: Re: cat /proc/version mainly broken
Date: Mon, 18 Mar 2019 10:39:00 -0000	[thread overview]
Message-ID: <20190318103928.GH3908@calimero.vinschen.de> (raw)
In-Reply-To: <b510c11ae0cecd4fcc1ef1e68ad1f5e7@physik.tu-berlin.de>

[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]

On Mar 18 11:05, Alexander Kleinsorge wrote:
> Hi Cygwin,
> there is an Issue wit "cat /proc/version" (tested on 2 different Windows 7,
> 64 bit PC, both had no issue some month ago).
> 
> $ cat /proc/version
> CYGWIN_NT-6.1-WOW version vaÜð0aìð0aìð0a0Ç0aìð0a (corinna@calimero) (gcc
> version 7.4.0 20181206 (Fedora Cygwin 7.4.0-1) (GCC) ) Z
> 
> update to 3.0.4-1 (not sure what was before, as proc/version is hiding it).
> 
> $ cat /proc/version
> CYGWIN_NT-6.1-WOW version †aÜð0aìð0aìð0a0Ç0aìð0a (corinna@calimero) (gcc
> version 7.4.0 20181206 (Fedora Cygwin 7.4.0-1) (GCC) ) Z
> 
> I test this every some month, and it always worked fine for years, but now
> it is broken with at least 3.x.x on different Windows-7 PC (also different
> Admin).
> Either a Windows-7-Ipdate from Microsoft or a Cygwin-Update changed
> something here.
> 
> Who can confirm the issue? It should be easy to find out what is going on
> then.

Yikes.  I change uname but missed to patch /proc/version as well.
Fixed in git.  Please try the latest developer snapshot from
https://cygwin.com/snapshots/


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-03-18 10:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 10:05 Alexander Kleinsorge
2019-03-18 10:39 ` Corinna Vinschen [this message]
2019-03-18 18:08   ` Achim Gratz
2019-03-19  8:27     ` Corinna Vinschen

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=20190318103928.GH3908@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=aleks@physik.tu-berlin.de \
    --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).