luatex panics after update of zlib to 1.3.1
Hallo, after the latest update of Cygwin, especially zlib from 1.3 to 1.3.1, luatex and related programs (lualatex, texdoc, ...) abort with a panic error: the version 1.3 of the header files of zlib (compile time) does not match the version 1.3.1 of the dynamic library (runtime). I assume, luatex from texlive-collection-luatex needs to be recompiled with the updated zlib sources. Best regards Heiko -- 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
[HEADSUP] any usage of cygwin_internal(CW_CMDLINE) in any maintained package?
Hi guys, is anybody of you maintaining a package (or is aware of any package in the Cygwin distro) which is using the cygwin_internal(CW_CMDLINE) call? If not, I will redefine the usage of this call in Cygwin 3.6. The reason is that it's practically unusable, unless the caller only fetches the first string from the output. The call also returns its content in allocated memory which is not free'able by the caller :( Thanks, Corinna
RE: Setting process command name in forked process
> that it matters at all, I'd like to +1 the suggestion/request of picking up > support for > setproctitle(3) in the next available release. >> in which case I'd prefer to implement this via setproctitle(3), given >> this API exists on BSD and Linux. Well, I don't think setproctitle(3) exists on Linux everywhere (at least not on the version that we have around here), but I second that adding it to Cygwin would be beneficial, regardless. prctl(PR_SET_NAME) exists on Linux but is very limited, so we can't even use it for our purposes... We do a hack of modifying the argv[] array, in a way different than Cygwin's, though. Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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: CYGWIN 1.5.3 END OF SUPPORT OR LIFE
Sorry, I have to correct myself in terms of the license: On Jan 30 16:16, Corinna Vinschen via Cygwin wrote: > Hi Marvin, > > On Jan 29 22:24, Marvin.C.Scott--- via Cygwin wrote: > > Good day - > > > > I represent a logistics team of users of CYGWIN freeware for a > > government contract. In my role I am responsible for tracking support > > and end of life for software assets. > > > > In the before mentioned effort mentioned above I have a general > > question. > > > > Do CYGWIN freeware developers or contributors enact any end or > > Careful, please. Cygwin is NOT freeware! > > Cygwin is licensed per the GNU General Public License version 3(*), and > that contains a couple of restrictions and responsibilities you should > be aware of. If you're unsure about the difference, I urge you to > contact your company's laywer to make sure you're in the clear. Cygwin 1.5.3 was not yet under GPL v3. Back in 2003, Cygwin was still under the CYGWIN license, which was going like this: -- This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License (GPL) as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. -- *** NOTE *** In accordance with section 10 of the GPL, Red Hat permits programs whose sources are distributed under a license that complies with the Open Source definition to be linked with libcygwin.a without libcygwin.a itself causing the resulting program to be covered by the GNU GPL. This means that you can port an Open Source(tm) application to cygwin, and distribute that executable as if it didn't include a copy of libcygwin.a linked into it. Note that this does not apply to the cygwin DLL itself. If you distribute a (possibly modified) version of the DLL you must adhere to the terms of the GPL, i.e. you must provide sources for the cygwin DLL. See http://www.opensource.org/docs/definition_plain.html for the precise Open Source Definition referenced above. Red Hat sells a special Cygwin License for customers who are unable to provide their application in open source code form. For more information, please see: http://www.redhat.com/software/tools/cygwin/, or call 866-2REDHAT ext. 3007 -- The "special Cygwin License for customers who are unable to provide their application in open source code form" is not active anymore. Given that, you have to comply with the general rule of the GPL v2, plus the GPL section 10 exception. I.e., you *must not* provide proprietary software linked to the Cygwin DLL to your customers. If in doubt, contact your company lawyer! Corinna -- 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: CYGWIN 1.5.3 END OF SUPPORT OR LIFE
Hi Marvin, On Jan 29 22:24, Marvin.C.Scott--- via Cygwin wrote: > Good day - > > I represent a logistics team of users of CYGWIN freeware for a > government contract. In my role I am responsible for tracking support > and end of life for software assets. > > In the before mentioned effort mentioned above I have a general > question. > > Do CYGWIN freeware developers or contributors enact any end or Careful, please. Cygwin is NOT freeware! Cygwin is licensed per the GNU General Public License version 3(*), and that contains a couple of restrictions and responsibilities you should be aware of. If you're unsure about the difference, I urge you to contact your company's laywer to make sure you're in the clear. > specific date when versions downloaded are available to users? No, we don't. In fact, there's even a "Cygwin time machine" on the net(**), where you can grab basically any old version of Cygwin. > I pose this question as my users currently employ a version prior the > latest 3.4.9-1 September 2023 release. I assume the only negative > impacts of using earlier version would be that my team would not have > current bug fixes. That's the gist of it, plus new features or changed behaviour to more closely follow POSIX. However, if your users actually use version 1.5.3, as the subject of your mail implies, they are using a version which is more than 20(!) years old. Also, Cygwin 1.5.3 only exists in a 32 bit version. Given that practically all recent hardware is 64 bit, most users of Cygwin switched to 64 bit versions of Windows, and recent Cygwin versions (3.4.0 and later) are only available as 64 bit versions, you're *very* far behind. We can't give any kind of support For 20 years old Cygwin releases, naturally. Corinna (*) https://www.gnu.org/licenses/gpl-3.0.en.html (**) http://www.crouchingtigerhiddenfruitbat.org/Cygwin/timemachine.html -- 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: python3 3.9.18-1 hanging
On 30/01/2024 13:13, ggl329 via Cygwin wrote: Hi, On 30/01/2024 10:22, Andrew Murray via Cygwin wrote: Interestingly, this is not something specific to Pillow. Cygwin has also been hanging for NumPy’s GitHub Actions, https://github.com/numpy/numpy/issues/25708, and GitPython, https://github.com/gitpython-developers/GitPython/pull/1814. In my environment, python-numpy stops working too. $ python Python 3.9.16 (main, Mar 8 2023, 22:47:22) [GCC 11.3.0] on cygwin Type "help", "copyright", "credits" or "license" for more information. import numpy help(numpy) ### stop here. By downgrading libopenblas from 0.3.26-1 to 0.3.25-1, it works again. Python 3.9.18 behaves same. This may be related to the issue. probably a different issue. Let me check in the coming days Regards Marco -- 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: pip install ocassionally hangs
On 30/01/2024 12:50, Daniel Abrahamsson via Cygwin wrote: Marco Atzeri wrote: what if you downgrade to 3.9.16 ? Thank you. Yes, downgrading solves the problem. The issue is probably the same as the one reported in "python3 3.9.18-1 hanging". As I was testing this, I noticed a peculiar thing with the Cygwin Setup. I have a script that sets up my Cygwin environment. That scripts calls the installer with a list of packages. When I pin the python version using "python39=3.9.16-1,python39-devel=3.9.16-1", the installer downgrades to 3.9.16-1. But if I run the installer again with the same options, it updates to python 3.9.18-1. Regards, Daniel I reset 3.9.18-1 as test, but the propagation will need some time to be recognized by the Cygwin server and to passed to the mirrors After that Setup should stop to propose upgrade to 3.9.18 Regards Marco -- 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: python3 3.9.18-1 hanging
Hi, On 30/01/2024 10:22, Andrew Murray via Cygwin wrote: Interestingly, this is not something specific to Pillow. Cygwin has also been hanging for NumPy’s GitHub Actions, https://github.com/numpy/numpy/issues/25708, and GitPython, https://github.com/gitpython-developers/GitPython/pull/1814. In my environment, python-numpy stops working too. $ python Python 3.9.16 (main, Mar 8 2023, 22:47:22) [GCC 11.3.0] on cygwin Type "help", "copyright", "credits" or "license" for more information. import numpy help(numpy) ### stop here. By downgrading libopenblas from 0.3.26-1 to 0.3.25-1, it works again. Python 3.9.18 behaves same. This may be related to the issue. -- ggl329 -- 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: pip install ocassionally hangs
Marco Atzeri wrote: > what if you downgrade to 3.9.16 ? Thank you. Yes, downgrading solves the problem. The issue is probably the same as the one reported in "python3 3.9.18-1 hanging". As I was testing this, I noticed a peculiar thing with the Cygwin Setup. I have a script that sets up my Cygwin environment. That scripts calls the installer with a list of packages. When I pin the python version using "python39=3.9.16-1,python39-devel=3.9.16-1", the installer downgrades to 3.9.16-1. But if I run the installer again with the same options, it updates to python 3.9.18-1. Regards, Daniel -- 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: pip install ocassionally hangs
On 29/01/2024 17:00, Daniel Abrahamsson via Cygwin wrote:
Hi,
Since some time ago (perhaps a week or two), "pip install" occassionally hangs.
Ctrl+C does not work. I have to kill the process via the task manager. I can
reproduce the problem somewhat reliably by running:
pip install --force jenkins_job_builder==5.0.4
This is the last thing printed before the process hangs:
Downloading requests-2.31.0-py3-none-any.whl (62 kB)
62.6/62.6 kB 1.2 MB/s eta
0:00:00
Using cached certifi-2023.11.17-py3-none-any.whl (162 kB)
Using cached charset_normalizer-3.3.2-py3-none-any.whl (48 kB)
Downloading idna-3.6-py3-none-any.whl (61 kB)
0.0/61.6 kB ? eta -:--:--
I tried attaching to the python39 process with strace and got the following
message repeated over and over again:
--- Process 41672 (pid: 1250), exception c005 at
Cygwin version: 3.5.0-0.615.g1c13ca67b506.x86_64
Python version: Python 3.9.18
pip version: pip 23.3.2
Regarding the Cygwin version, a colleague ran into the same problem on the 3.4
branch, so I don't think it is related to anything new on the 3.5 branch.
Any ideas on how to debug this?
Regards,
Daniel Abrahamsson
what if you downgrade to 3.9.16 ?
--
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: python3 3.9.18-1 hanging
On 30/01/2024 10:22, Andrew Murray via Cygwin wrote: Hi, Over in Pillow’s GitHub Actions, the Cygwin job has started hanging when running pytest - https://github.com/python-pillow/Pillow/actions/runs/7690866578/job/20955296663 Interestingly, this is not something specific to Pillow. Cygwin has also been hanging for NumPy’s GitHub Actions, https://github.com/numpy/numpy/issues/25708, and GitPython, https://github.com/gitpython-developers/GitPython/pull/1814. The conclusion that these Python developers have come to is that the problem started when Cygwin’s python3 package updated to 3.9.18-1. For the moment, they have downgraded to 3.9.16-1. However, I’m letting you know here about the problem, in case you would like to find a more permanent solution. Thanks thanks, I will look of course as soon I removed from test the problem raised :-( -- 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: zp_octave_finish.dash fails when updating
On 29/01/2024 20:18, Uwe F. Mayer via Cygwin wrote: The script /etc/postinstall/zp_octave_finish.dash from octave-8.4.0-1.tar.bz2 fails during Cygwin update because that script expects the directory /usr/share/octave/packages to exist. Creating that directory fixes this error. CYGWIN_NT-10.0-19045 Windows-10-Laptop 3.5.0-0.617.g030a762535c1.x86_64 2024-01-29 13:16 UTC x86_64 Cygwin thanks Uwe, for the check. I will add on next release Regards Marco -- 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
python3 3.9.18-1 hanging
Hi, Over in Pillow’s GitHub Actions, the Cygwin job has started hanging when running pytest - https://github.com/python-pillow/Pillow/actions/runs/7690866578/job/20955296663 Interestingly, this is not something specific to Pillow. Cygwin has also been hanging for NumPy’s GitHub Actions, https://github.com/numpy/numpy/issues/25708, and GitPython, https://github.com/gitpython-developers/GitPython/pull/1814. The conclusion that these Python developers have come to is that the problem started when Cygwin’s python3 package updated to 3.9.18-1. For the moment, they have downgraded to 3.9.16-1. However, I’m letting you know here about the problem, in case you would like to find a more permanent solution. Thanks -- 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
