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
pip install ocassionally hangs
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 -- 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
Cygwin test 3.5.0 tar symlinks error messages and failure status
("Manually" replying to an email in the archive
(https://cygwin.com/pipermail/cygwin/2023-May/253742.html) since I don't have
the original email anymore).
Achim Gratz wrote:
> Brian Inglis via Cygwin writes:
> > Problem writing tar (with Cygwin default sys) symlinks before target
> > created under Cygwin 3.5.0 - error messages are issued and tar exits
> > with failure status!
> […]
> > The only likely culprit between 3.4.6 and that commit seems to be
> > commit 2023-04-18 fa84aa4dd2fb43eaf7fcdfb040aef854f2f19d01 Cygwin: fix
> > errno values set by readlinkat.
> >
> > Still seems to work as expected despite the error messages and failure
> > status.
> >
> > Runs without any messages or failure under Cygwin stable 3.4.6.
We started seeing the same problem after cygwin 3.4.7 was released (I note it
includes the commit Brian mentions). As a workaround, we just ignore the exit
code of the tar command, but understandably we would rather not do that.
Extracting the same archive works fine without warnings or errors on Linux.
> The interface mentioned above is known to be wonky on various systems.
> You might need to re-build tar in oder for it to detect any changed
> level of wonkiness and adapt accordingly.
Do you mean that the tar package would need an update?
// 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: Problems with asciidoctor gem after ruby update
> A corrected package has been released. (ruby-3.2.2-2) Thank you! I can confirm the new pakcage solves the problem. // 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
Problems with asciidoctor gem after ruby update
Hi,
I’m not sure if the issue is cygwin-specific or not, but I do not have a linux
box with a sufficiently new version of ruby to test with. The errors started
showing up after the recent updates of the ruby and rubygems packages.
When installing asciidoctor via `gem install asciidoctor`, a asciidoctor
"binary" is placed in "$HOME/bin". However, when running `asciidoctor` I get:
```
$ asciidoctor
/home/daab/bin/asciidoctor: line 6: /home/daab/bin/ruby: No such file or
directory
```
The asciidoctor binary is looking for ruby in the wrong place (it should be
looking for the system ruby).
Version output:
```
$ asciidoctor -v
Asciidoctor 2.0.18 [https://asciidoctor.org]
Runtime Environment (ruby 3.2.2 (2023-03-30 revision e51014f9c0)
[x86_64-cygwin]) (lc:UTF-8 fs:UTF-8 in:UTF-8 ex:UTF-8)
$ ruby -v
ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x86_64-cygwin]
$ gem -v
3.4.12
```
The asciidcoctor binary on the upgraded system starts with these lines:
```
#!/bin/sh
# -*- ruby -*-
_=_\
=begin
bindir="${0%/*}"
exec "$bindir/ruby" "-x" "$0" "$@"
=end
#!/usr/bin/ruby.exe
#
# This file was generated by RubyGems.
```
On a non-upgraded system, we instead have:
```
#!/usr/bin/ruby.exe
#
# This file was generated by RubyGems.
#
# The application 'asciidoctor' is installed as part of a gem, and
# this file is here to facilitate running it.
#
```
require 'rubygems'
// 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: gcc -pg broken after cygwin update?
> On Dec 7 12:50, Corinna Vinschen via Cygwin wrote: > > On Dec 7 08:58, Daniel Abrahamsson via Cygwin wrote: > > > Hi, > > > > > > This morning I updated cygwin, and after that gcc started producing > > > errors like this: > > > > > > > gcc -Wall -Wextra -Werror -pedantic -Wno-unused-parameter -g -pg > > > > -DVERBOSE -c -o ../obj/.o .c > > > > gcc -o ../bin/ ../obj/.o -pg > > > > /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: > > > > ../obj/.o: in function `exit_eval_failure': > > > /home/daab/dev/someproj/src/.c:17: undefined reference to > > > `__fentry__' > > > > > > If I drop the "pg" flags from the compilation and linking stages, > > > everything works. > > > > > > I typically update cygwin packages once per week, but now it has been > > > maybe a month since I last updated. As far as I can tell from the > > > cygwin-announce archives, there has not been any gcc updates in that > > > period, but I do note that cygwin itself has been updated. Could that > > > be related? > > > Thanks for the report. > > > > This is a dumb bug I introduced into the build system in 3.4.0. I fixed > > that in the git repo, but the automated build of the matching test > > release cygwin-3.5.0-0.17.g95f5b0a62036 is currently not building due to > > some hiccup on cygwin.com. I'll send a new mail as soon as this is > > fixed and you can test it (provided you run at least Windows 8.1). > > Automated builds have been picked up again and the Cygwin test package > 3.5.0-0.17.g95f5b0a62036 should be available later today. You can > install it using setup.exe, just like any other test release. > > Don't forget to install the matching cygwin-devel package, too, that's > the one containing the library libgmon.a, which is what gets linked in > with `gcc -pg'. I can confirm 3.5.0-0.17.g95f5b0a62036 solves the issue with the "-pg" flag. Thank you! 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
gcc -pg broken after cygwin update?
Hi, This morning I updated cygwin, and after that gcc started producing errors like this: > gcc -Wall -Wextra -Werror -pedantic -Wno-unused-parameter -g -pg -DVERBOSE > -c -o ../obj/.o .c > gcc -o ../bin/ ../obj/.o -pg > /usr/lib/gcc/x86_64-pc-cygwin/11/../../../../x86_64-pc-cygwin/bin/ld: > ../obj/.o: in function `exit_eval_failure': /home/daab/dev/someproj/src/.c:17: undefined reference to `__fentry__' If I drop the "pg" flags from the compilation and linking stages, everything works. I typically update cygwin packages once per week, but now it has been maybe a month since I last updated. As far as I can tell from the cygwin-announce archives, there has not been any gcc updates in that period, but I do note that cygwin itself has been updated. Could that be related? 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
