Re: Python for Windows reports wrong local time when run under Cygwin on Europe/Moscow TZ

2021-06-07 Thread Russell VT via Cygwin
What version(s) of the timezone files are installed on each?

Also, seems one of the Python versions came from Windows, rather than
Cygwin?



On Mon, Jun 7, 2021 at 12:01 AM Mike Kaganski via Cygwin 
wrote:

> Hello,
>
> Running Cygwin 3.1.7-1 on Windows 10 Version 21H1 (OS Build 19043.985),
> I have this issue:
>
> when I start Cygwin's Python, I have correct time reported:
>
> > mikek@DESKTOP-8SHAE9Q ~
> > $ python
> > Python 3.8.9 (default, Apr 21 2021, 23:14:29)
> > [GCC 10.2.0] on cygwin
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> import datetime
> > >>> datetime.datetime.now()
> > datetime.datetime(2021, 6, 7, 9, 40, 15, 318391)
>
> But running Python for Windows (it doesn't matter which, specifically
> for the test I used the one from MS Store [1]), I have incorrect local
> time:
>
> > mikek@DESKTOP-8SHAE9Q ~
> > $ "C:/Program
> >
> Files/WindowsApps/PythonSoftwareFoundation.Python.3.8_3.8.2800.0_x64__qbz5n2kfra8p0/python3.8.exe"
> > Python 3.8.10 (tags/v3.8.10:3d8993a, May  3 2021, 11:48:03) [MSC
> > v.1928 64 bit (AMD64)] on win32
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> import datetime
> > >>> datetime.datetime.now()
> > datetime.datetime(2021, 6, 7, 7, 40, 55, 503775)
>
> Note how the latter output reports 2021-06-07 07:40, while the former
> reports 2021-06-07 09:40. The difference is 2 hours.
>
> Starting the same Python for Windows from cmd.exe has it correct:
>
> > C:\Users\mikek>python
> > Python 3.8.10 (tags/v3.8.10:3d8993a, May  3 2021, 11:48:03) [MSC
> > v.1928 64 bit (AMD64)] on win32
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> import datetime
> > >>> datetime.datetime.now()
> > datetime.datetime(2021, 6, 7, 9, 41, 21, 925240)
>
> Cygwin reports correct timezone:
>
> > $ echo $TZ
> > Europe/Moscow
>
> Starting Python for Windows using a different timezone (specifically, '$
> TZ=UTC "C:/Program
> Files/WindowsApps/PythonSoftwareFoundation.Python.3.8_3.8.2800.0_x64__qbz5n2kfra8p0/python3.8.exe"')
>
> gives correct time for *that* time zone.
>
> This is a problem, because in our project (LibreOffice), we use Cygwin
> as environment for unit testing, where LibreOffice's own Python (also
> built natively for Windows) is used, and at some times (from 00:00 till
> 02:00) it reports wrong dates, which makes tests fail locally on
> affected systems(see [2]).
>
> Thank you!
>
>
> [1] https://www.microsoft.com/en-us/p/python-38/9mssztt1n39l
>
> [2]
>
> https://gerrit.libreoffice.org/c/core/+/92217/2#message-f55091795e7cde9d75adc00ddb69451121b644f6
>
>
> --
>
> Best regards,
>
> Mike Kaganski
>
>
> --
> Problem reports:  https://cygwin.com/problems.html
> FAQ:  https://cygwin.com/faq/
> Documentation:https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>


-- 
Russell M. Van Tassell 

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: realpath issue with native[strict] symlinks

2021-06-07 Thread Jeremy Drake via Cygwin
On Fri, 28 May 2021, Jeremy Drake wrote:

> On Thu, 27 May 2021, Jeremy Drake wrote:
>
> > > > Treating mapped/subst drives as though they were not symlinks, without
> > > > messing with intermedate symlinks.
> > >
> > > It was that simple, surprise, surprise...
> >
> > It turns out it wasn't, after all.  This only seems to work at the root of
> > a subst-ed drive.  I just got the following error:
>

There was another report of someone running into an issue with this
change, though not exactly the same situation as mine:
https://github.com/msys2/msys2-runtime/issues/41#issuecomment-854913283

It seems that a mapped network drive is being 'dereferenced', confusing
eclipse trying to find source files from debug info from an arm
cross-compiler.

Unfortunately I have not heard back whether or not my patch helps this
case.

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Windows Azure server CYGWIN version 3.2.0 Getting an error while executing man command

2021-06-07 Thread Brian Inglis

On 2021-06-03 22:45, Brian Inglis wrote:

On 2021-06-03 16:08, Lei Zhang wrote:
Encounter a bug on Windows, and the bug details are below, please take 
a look when you get a moment, thanks!

Account: Cygwin Solutions
Product : CYGWIN
Reference # 32959457
Issue [Azure][Server][CYGWIN and 3.2.0][Getting an error while 
executing man command]

Product version: 3.2.0
Environment: Desktop
OS: Windows 10 Insider Preview
OS build: 20346.1.210427-1648
Repro Steps:
1. Schedule WS2019 Azure edition OS.
2. Add roles and features.
3. Install the application with all defaults.
4. Launch the application.
5. Type man help or any other man commands and press enter.
6. Output is generated without any error.
7. Upgrade to latest OS build.
8. Type man help or any other man commands and press enter.
9. Observe.
Actual Results:
Getting an error while performing man command.
Expected Results:
Should view the manual of the particular man command.


Pretty vague description: Works Just Fine For Me!
Without access to your Azure server VM, build, install, update, and 
terminal logs, we have no idea what you may be running and what error 
you may be encountering.
When you report problems you must be very explicit and specific about 
what you are typing and seeing, and the edition, version, release, patch 
level of Windows you are running e.g. "Windows Server 2019 Datacenter: 
Azure Edition ... a new Windows Server image on Azure that has a unique 
build number and codebase", plus all the details on the "Upgrade to 
latest OS build", to which few or none of our support volunteers may 
have access, in which case you may have to participate in running tests, 
and reporting results accurately, to assist those trying to help you.


In addition, those service VMs could have almost any level of security 
restrictions applied during setup, so it is unlikely but possible that 
Cygwin may just be unable to run effectively under such an environment.
Many Cygwin users have encountered problems with defective commercial 
"security"/monitoring products "BLODA" in Cygwin's Big List of Dodgy 
Apps (a list https://cygwin.com/faq/faq.html#faq.using.bloda of 
applications that interfere with the normal working of Cygwin by 
intrusively injecting themselves in the system call chain) where the 
only solutions were to have them ignore all Cygwin programs and DLLs, 
deinstall the products, or use a different system.


Please attach as plain text files:

* the output log from your Azure server VM, of running the Cygwin 
diagnostic command:

 $ cygserver -hrsv > cygcheck-hrsv.log
as requested at "Problem reports: https://cygwin.com/problems.html";, at 
the bottom of all posts to the mailing list
* the contents of the initial /var/log/setup.log.full from running the 
Cygwin install

* the summary /var/log/setup.log from Cygwin installs
* the log /var/log/mandb-index.log from updating the man-db index during 
post-install

* any changed man or man-db configuration files under /etc/ or ~/.
* any commands affecting man in your ~/.bash_/zsh_/.../profile startup 
scripts
* a terminal log of your commands entered and output including errors 
encountered, or
* copy and paste the *actual* commands entered into the terminal and 
also the *verbatim* output and error messages generated.


That way the support volunteers have a chance of diagnosing what may be 
wrong with your installation, and suggesting what actions may be taken 
to resolve your problems, without requiring access to your system, or 
the ability to read your mind. ;^>


Support volunteers respond on the mailing list to subscribers.
If you are not subscribed to the Cygwin support mailing list, please at 
least check the list archives for responses at e.g.


https://cygwin.com/pipermail/cygwin/current/
https://www.mail-archive.com/cygwin@cygwin.com/
http://cygwin.1069669.n5.nabble.com/

or you could use NNTP<->ML gateways at e.g.

news://news.gmane.io/gmane.os.cygwin

--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


RE: Windows Azure server CYGWIN version 3.2.0 Getting an error while executing man command

2021-06-07 Thread Lei Zhang
Hi,

I am following up regarding the issue below.  Please take a look when you get a 
chance!

Thanks,
Lei

From: Lei Zhang
Sent: Thursday, June 3, 2021 3:08 PM
To: cygwin@cygwin.com
Subject: Windows Azure server CYGWIN version 3.2.0 Getting an error while 
executing man command

Dear developer,

Encounter a bug on Windows, and the bug details are below, please take a look 
when you get a moment, thanks!


Account: Cygwin Solutions
Product : CYGWIN
Reference # 32959457
Issue [Azure][Server][CYGWIN and 3.2.0][Getting an error while executing man 
command]

Product version: 3.2.0
Environment: Desktop
OS: Windows 10 Insider Preview
OS build: 20346.1.210427-1648

Repro Steps:
1. Schedule WS2019 Azure edition OS.
2. Add roles and features.
3. Install the application with all defaults.
4. Launch the application.
5. Type man help or any other man commands and press enter.
6. Output is generated without any error.
7. Upgrade to latest OS build.
8. Type man help or any other man commands and press enter.
9. Observe.

Actual Results:
Getting an error while performing man command.

Expected Results:
Should view the manual of the particular man command.


Best Regards,
Lei

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Python for Windows reports wrong local time when run under Cygwin on Europe/Moscow TZ

2021-06-07 Thread Mike Kaganski via Cygwin

Hello,

Running Cygwin 3.1.7-1 on Windows 10 Version 21H1 (OS Build 19043.985), 
I have this issue:


when I start Cygwin's Python, I have correct time reported:


mikek@DESKTOP-8SHAE9Q ~
$ python
Python 3.8.9 (default, Apr 21 2021, 23:14:29)
[GCC 10.2.0] on cygwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import datetime
>>> datetime.datetime.now()
datetime.datetime(2021, 6, 7, 9, 40, 15, 318391)


But running Python for Windows (it doesn't matter which, specifically 
for the test I used the one from MS Store [1]), I have incorrect local time:



mikek@DESKTOP-8SHAE9Q ~
$ "C:/Program 
Files/WindowsApps/PythonSoftwareFoundation.Python.3.8_3.8.2800.0_x64__qbz5n2kfra8p0/python3.8.exe"
Python 3.8.10 (tags/v3.8.10:3d8993a, May  3 2021, 11:48:03) [MSC 
v.1928 64 bit (AMD64)] on win32

Type "help", "copyright", "credits" or "license" for more information.
>>> import datetime
>>> datetime.datetime.now()
datetime.datetime(2021, 6, 7, 7, 40, 55, 503775)


Note how the latter output reports 2021-06-07 07:40, while the former 
reports 2021-06-07 09:40. The difference is 2 hours.


Starting the same Python for Windows from cmd.exe has it correct:


C:\Users\mikek>python
Python 3.8.10 (tags/v3.8.10:3d8993a, May  3 2021, 11:48:03) [MSC 
v.1928 64 bit (AMD64)] on win32

Type "help", "copyright", "credits" or "license" for more information.
>>> import datetime
>>> datetime.datetime.now()
datetime.datetime(2021, 6, 7, 9, 41, 21, 925240)


Cygwin reports correct timezone:


$ echo $TZ
Europe/Moscow


Starting Python for Windows using a different timezone (specifically, '$ 
TZ=UTC "C:/Program 
Files/WindowsApps/PythonSoftwareFoundation.Python.3.8_3.8.2800.0_x64__qbz5n2kfra8p0/python3.8.exe"') 
gives correct time for *that* time zone.


This is a problem, because in our project (LibreOffice), we use Cygwin 
as environment for unit testing, where LibreOffice's own Python (also 
built natively for Windows) is used, and at some times (from 00:00 till 
02:00) it reports wrong dates, which makes tests fail locally on 
affected systems(see [2]).


Thank you!


[1] https://www.microsoft.com/en-us/p/python-38/9mssztt1n39l

[2] 
https://gerrit.libreoffice.org/c/core/+/92217/2#message-f55091795e7cde9d75adc00ddb69451121b644f6



--

Best regards,

Mike Kaganski


--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple