Re: xlsx2csv package may not be required.
On 2023-03-22 13:13, Brian Inglis wrote: > On 2023-03-22 01:14, Jari Aalto via Cygwin-apps wrote: > > On 2023-03-18 17:56, marco atzeri via Cygwin-apps wrote: > > > 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) > > > > I agree, it's better to have native Python package which is more > > likely to be kept up to date by the upstream. > > > > So, anyopne packaging the Python PIP version, please go ahead and > > remove the current package. > > Hi Jari, > > So no issue if I adopt and package with cygport? > It's a utility I use around tax time and sometimes elsewhen. If you go ahead and take maintenance of the Pyhon PIP version of xlsx2csv, I think we can retire the current xlsx2csv package as it is not particularly active in git: https://github.com/dilshod/xlsx2csv.git 2023-03-13 78be285 tdilshod Merge pull request #248 from NoSuck/hyperlinks-crash-string-bytes 2023-03-13 140e4cf tdilshod Merge pull request #252 from hugovk/replace-deprecated-BadZipfile 2023-01-09 3180d94 tdilshod version 0.8.1 (tag: 0.8.1) 2022-12-23 9b6c2df tdilshod include hidden rows option 2022-10-02 4beb5a8 tdilshod fix python2 support Jari
Re: ITA xlsx2csv (was Re: python2 removal)
On 2023-03-16 18:57, Jon Turney via Cygwin-apps wrote: > On 16/03/2023 15:53, Brian Inglis via Cygwin-apps wrote: > > On 2023-03-16 07:29, Jon Turney wrote: > > > > > The critical piece of data I'm missing here is which of these is true: > > > a) This package contains a script with a python shebang. The current > > > version doesn't work when python is python3, so an upgrade is needed > > > to continue working when python2 is removed, or > > > b) This package contains a script with a python shebang. The current > > > version will continue to work when python is python3. > > > > Unfortunately only a generic cygbuild sh script is supplied with the > > package - does nothing but complain without some other "magic" script or > > data! ;^> > > Jari's Debian 8/9 xlsx2csv releases have been updated to 0.20+20161027 > > from 0.11+20120814. > > > > $ sed 1q xlsx2csv.py > > #!/usr/bin/env python I updated the the latest from upstream repository and it shoudl now work with Python 3. thanks, Jari
Re: xlsx2csv package may not be required.
On 2023-03-18 17:56, marco atzeri via Cygwin-apps wrote: > 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) I agree, it's better to have native Python package which is more likely to be kept up to date by the upstream. So, anyopne packaging the Python PIP version, please go ahead and remove the current package. Jari
Re: [ATTN MAINTAINER] tig
On 2023-01-16 12:42, Jon Turney wrote: > On 13/01/2023 16:59, Libor Ukropec via Cygwin-apps wrote: > > C:/cygwin64/bin/tig.exe: error while loading shared libraries: > > cygpcreposix-0.dll: cannot open shared object file: No such file or > > directory > > > > Manual installation of "libpcreposix0 8.45-1" seems resolving the problem. > > I added libpcre1 and libpcreposix0 to the requires: for tig. > > Jari, > > Please update your local copy, to try to ensure these are correct in any > future release. Thanks, added. Jari
Re: [ATTN MAINTAINER] tig
On 2022-12-13 18:14, Libor Ukropec via Cygwin-apps wrote: > Dne 12.12.2022 v 17:32 Adam Dinwoodie via Cygwin-apps napsal(a): > > On Sun, Dec 11, 2022 at 11:15:35PM +0100, Libor Ukropec via Cygwin-apps > > wrote: > > > Hello Jari, > > > > > > cygwin contains "tig" in version 2.4.1 (2019-07-30) and there's already > > > 2.5.4 (2021) with many bug fixes and improvements available. > > > Can I kindly ask whether it is possible to update the package? > > > I do not see a git repository for the tig package, so I attached the > > > cygport > > > file if it can save you some effort (in compare to the following > > > scallywag, > > > I've added the LICENSE info the script) > > > > > > Scallywag report is here: > > > https://github.com/cygwin/scallywag/actions/runs/3670966767 > > > > I believe Jari's repo for the tig Cygwin packaging is on GitHub[0], and > > it looks like it's using the old pre-Cygport packaging mechanism. I've > > not looked through that repo myself (yet, at least) but it looks like > > there are some patches that imply a naïve build might not work > > perfectly. Or those packages might be entirely obsolete... > I did not look for the GitHub, but the naive compile and run worked with few > custom actions in the cygport script. > > > > [0]: https://github.com/jaalto/cygwin-package--tig > > > > FWIW, I'd be happy to at least attempt to add this package to my small > > Cygwin Git packaging empire, and take responsibility for keeping it up > > to date going forwards. But that's only if Jari wants to relinquish > > Yes, let's wait for Jari's answer > > that hat, and even then I think Libor clearly gets first refusal given > > they've written the new Cygport file. > > > Here comes my weak English. Will I be refused by Jari or do you mean that I > will refuse you because I did the Cygport file? Hi, Thanks for the heads up. I've uploaded new version and added the *.cygport in my Github repository of tig for possible new maintainer in the future. The patches deal some fixes in the xmlto(1) of manual pages build. Jari
