Re: xlsx2csv package may not be required.
On Fri, Mar 17, 2023 at 10:29 AM Adam Dinwoodie via Cygwin-apps wrote: > > On Thu, Mar 16, 2023 at 07:58:48PM -0600, Doug Henderson via Cygwin-apps > wrote: > > There is a current pure python version of xlsx2csv which runs for many > > versions of Python 2 and Python 3. > > > > It may not be necessary to provide a package for it in cygwin. > > Instead, users may install the pure python package from PYPI > > https://pypi.org/ using pip or another python package manager. > > Installing using pip or similar is an option for the vast majority of > packages that are available through the Cygwin installer; by that logic > it wouldn't make sense to provide most of the Python packages we > provide. Which wouldn't be an invalid strategy, but it would be a very > big change in how we handle things! > > I think the advantage of using the Cygwin packages is a better > likelihood of packages actually being compatible with Cygwin, rather > than having some weird and unpredictable package dependency issue. A > pure Python xlsx2csv is very unlikely to be affected by that sort of > issue, but providing it as a Cygwin package means users shouldn't need > to even think about whether the package is a pure Python package or not. I agree with Adam. I would have no problem to release the python package no if not for the problem to the laptop I guess one month from now I will be able to be operative again (assuming the target supplier of the laptop https://frame.work/ will not have delivery problem) Regards Marco
[ANNOUNCEMENT] Updated: Perl distributions
The following Perl distributions have been updated to their latest release version available on CPAN: noarch -- perl-Business-ISBN-Data-20230316.001-1 perl-Business-ISMN-1.203-1 perl-Data-Compare-1.28-1 perl-ExtUtils-MakeMaker-7.68-1 perl-Net-DNS-1.37-1 perl-Test-Simple-1.302194-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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
Updated: Perl distributions
The following Perl distributions have been updated to their latest release version available on CPAN: noarch -- perl-Business-ISBN-Data-20230316.001-1 perl-Business-ISMN-1.203-1 perl-Data-Compare-1.28-1 perl-ExtUtils-MakeMaker-7.68-1 perl-Net-DNS-1.37-1 perl-Test-Simple-1.302194-1 -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
Case ID:5780603542
[New Ticket]#6217425547.pdf Description: Binary data -- 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: [PATCH 0/3] fix unlink/rename failure in hyper-v container
Hi Yoshinao, On Mar 18 14:29, Yoshinao Muramatsu wrote: > Hi Corinna. > I'm Yoshinao Muramatsu. Thank you for your thoughtful guidance. > I have not modified the patch yet, > but I have made some observations and post the results. > > I forgot to mention in my first post that there is a workaround > for this issue, which is to use process isolation unless > hyper-v isolation is absolutely necessary > (mainly caused by build number difference between host and container). Ok, but that's a propoerty we'll never be able to test. > In the logs, here we can find some differences. > But I believe it is unclear if it will always be so. > If additional inspections are done, they will be costly. Assuming we can pull some information from the filesystem flags, the cost is negligible. We just check bits in a filesystem bitmask. > I would also like to see better support for POSIX unlink/rename > semantics in the container mechanism. Yeah, but... do you have high hopes? Assuming we can fetch useful info from the filesystem flags, we could basically do both, add your patch to have a workaround in case the Windows call returns INVALID_PARAMETER, and an early test for a FS flag which can be used down the road to avoid the workaround. > Therefore, I think it is not a bad idea to simply retry rather than spending > time every time to check the conditions to deal with rare situations. > However, in certain situations it happens all the time. > (So if we can cache it that would be great.) > But performance in the vast majority of other situations is more important. The filesystem info is cached, so the filesystem flags are only checked the first time we open a file on the filesystem. > In the following logs, c:\ is the normal ntfs volume in the container, > andc:\opt is the volume of the bind mounted host. > Where the differences are > - 0x0020 Supports Disk Quotas > - 0x0100 Supports Open By FileID > - 0x0200 Supports USN Journal I just updated the csih package to 0.9.13. The getVolInfo tool now prints *all* known filesystem flags. > == hyper-v container (has issue) > $ mount > C:/cygwin64/bin on /usr/bin type ntfs (binary,auto) > C:/cygwin64/lib on /usr/lib type ntfs (binary,auto) > C:/cygwin64 on / type ntfs (binary,auto) > C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto) > > $ /usr/lib/csih/getVolInfo.exe /cygdrive/c/ > Device Type: 7 > Characteristics: 20020 > Volume Name: <> > Serial Number : 3456656850 > Max Filenamelength : 255 > Filesystemname : > Flags : 1c706df > ...snip... > > $ /usr/lib/csih/getVolInfo.exe /cygdrive/c/opt/ > Device Type: 7 > Characteristics: 20020 > Volume Name: <> > Serial Number : 955187689 > Max Filenamelength : 255 > Filesystemname : > Flags : 2c706ff > ...snip... This is disappointing. One of the newer filesystem flags is 0x400, FILE_SUPPORTS_POSIX_UNLINK_RENAME. As you can see, the flag is set. But the POSIX functionality doesn't work here, right? However, what's really curious here is the fact that the FILE_SUPPORTS_OPEN_BY_FILE_ID flag is missing. NTFS always supports this since Windows 2003! So we could use this flag as indicator that, probably, POSIX rename/unlink won't work. Corinna
[ANNOUNCEMENT] csih 0.9.13-1
The following packages have been uploaded to the Cygwin distribution: * csih-0.9.13-1 New: getVolInfo now prints all the latest known filesystem flags. CSIH (cygwin-service-installation-helper is a script library used to assist installing cygwin services, such as sshd. It is derived in part from various other sources. It is intended to be 'sourced' by configuration scripts such as ssh-host-config, syslog-config, or iu-config, and that script can then make use of the shell functions defined by this package. -- 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
csih 0.9.13-1
The following packages have been uploaded to the Cygwin distribution: * csih-0.9.13-1 New: getVolInfo now prints all the latest known filesystem flags. CSIH (cygwin-service-installation-helper is a script library used to assist installing cygwin services, such as sshd. It is derived in part from various other sources. It is intended to be 'sourced' by configuration scripts such as ssh-host-config, syslog-config, or iu-config, and that script can then make use of the shell functions defined by this package.
