Re: Setup not asking for proxy user,password / was Resend: pdfseparate does nothing for me?
Ian Lambert writes: > Setup is not as lucky, is unable to get setup.ini, and never asks for user, > password. > It also only lists the download site I last used. It's quite clear that setup and your proxy miscommunicate about the authentication. > myuser@mypc ~/junk/cygwin > $ wget https://cygwin.com/setup-x86_64.exe > --2016-12-01 10:52:10-- https://cygwin.com/setup-x86_64.exe > Resolving superproxy.our.wonder.place (superproxy.our.wonder.place)... > an.ip.address.here > Connecting to superproxy.our.wonder.place > (superproxy.our.wonder.place)|an.ip.address.here|:port... connected. > Proxy tunneling failed: Proxy Authentication RequiredUnable to establish SSL > connection. Again, the proxy is supposed to reply with a 407 error when it requires to authenticate the request source. It obviously errors out, but it does not appear to actually request authentication. If it would do that, then setup would ask for the user/password combination. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Pre-compiled Perl::Critic ?
Jim Reisert AD1C writes: > Would it be possible to release a pre-compiled version of > Perl::Critic? I built it yesterday from CPAN sources, and it took > about nine *hours* to finish! The laptop I built it on has an Intel > I7-6600U, 16 GB of memory and an SSD, so I don't know why it should > have taken so long! Last I looked it pulled in a lot of dependencies that I don't really care to maintain. Plus Perl::Critic is in itself a somewhat controversial endeavour, so I'm not sure it would find that many users. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[patch] /etc/postinstall/GeoIP-database.sh terminates with exit code 1
Hello,
The file /etc/postinstall/GeoIP-database.sh has an error;
it needs an absolute path in the first existence test (line 4 below).
The correct contents of the file becomes:
$ cat -n /tmp/GeoIP-database.sh
1 for f in /usr/share/GeoIP/*.dat; do
2 case ${f##*/} in
3 GeoLiteCountry.dat)
4 [ -e /usr/share/GeoIP/GeoIP.dat ] || /bin/ln -s ${f##*/}
/usr/share/GeoIP/GeoIP.dat
5 ;;
6 GeoLite*.dat)
7 [ -e ${f/Lite/IP} ] || /bin/ln -s ${f##*/} ${f/Lite/IP}
8 ;;
9 esac
10 done
The uncorrected mistake makes the script terminate with this message:
(From /var/log/setup.log.full)
2016/12/01 18:26:35 running: C:\cygwin\bin\bash.exe --norc --noprofile
"/etc/postinstall/GeoIP-database.sh"
/bin/ln: failed to create symbolic link '/usr/share/GeoIP/GeoIP.dat': File
exists
2016/12/01 18:26:35 abnormal exit: exit code=1
Patch:
$ diff -u /etc/postinstall/GeoIP-database.sh /tmp/GeoIP-database.sh
--- /etc/postinstall/GeoIP-database.sh 2016-11-08 21:47:53.0 +0100
+++ /tmp/GeoIP-database.sh 2016-12-01 18:50:18.768493100 +0100
@@ -1,7 +1,7 @@
for f in /usr/share/GeoIP/*.dat; do
case ${f##*/} in
GeoLiteCountry.dat)
-[ -e GeoIP.dat ] || /bin/ln -s ${f##*/} /usr/share/GeoIP/GeoIP.dat
+[ -e /usr/share/GeoIP/GeoIP.dat ] || /bin/ln -s ${f##*/}
/usr/share/GeoIP/GeoIP.dat
;;
GeoLite*.dat)
[ -e ${f/Lite/IP} ] || /bin/ln -s ${f##*/} ${f/Lite/IP}
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Setup not asking for proxy user,password / was Resend: pdfseparate does nothing for me?
On 2016-12-01 10:10, Ian Lambert wrote: > On Thu, 11/17/16, Achim Gratz wrote: > Ian Lambert writes: >> Explorer is using a proxy configuration script, defined by others. > Looking back at your older posts it seems your proxy requires a > password. I have no idea how the configuration script sets up things > for you, but apparently it bypasses the registry settings that it > would normally use. >> Setup is being run with --no-admin. -p has been tried, but there is >> no option for user/passwd. > Setup.exe supposedly should ask for that information via a dialog > box when the proxy indicates it needs it, but it seems that your > proxy just doesn't return the required 407 response header. If you > could figure out (via wget most likely) what the communication with > your proxy looks like (with and without password) that might lead to > somewhere. > I finally observed wget fail because of authentication, then work > when given user, password. > Screen output is below. > Subsequent wgets work without giving password, so there is some > caching of authentication, apparently, at least for wget (and > apt-cyg). > Setup is not as lucky, is unable to get setup.ini, and never asks for > user, password. > It also only lists the download site I last used. You can change the web site using apt-cyg mirror or edit /etc/setup/setup.rc /last-mirror/+1 directly. > myuser@mypc ~/junk/cygwin > $ wget https://cygwin.com/setup-x86_64.exe > --2016-12-01 10:52:10-- https://cygwin.com/setup-x86_64.exe > Resolving superproxy.our.wonder.place > (superproxy.our.wonder.place)... an.ip.address.here > Connecting to superproxy.our.wonder.place > (superproxy.our.wonder.place)|an.ip.address.here|:port... connected. > Proxy tunneling failed: Proxy Authentication RequiredUnable to > establish SSL connection. > myuser@mypc ~/junk/cygwin > $ wget --user=myuser --password=mypasswd > https://cygwin.com/setup-x86_64.exe > --2016-12-01 10:53:22-- https://cygwin.com/setup-x86_64.exe > Resolving superproxy.our.wonder.place > (superproxy.our.wonder.place)... an.ip.address.here > Connecting to superproxy.our.wonder.place > (superproxy.our.wonder.place)|an.ip.address.here|:port... connected. > Proxy request sent, awaiting response... 200 OK > Length: 910336 (889K) [application/octet-stream] > Saving to: ‘setup-x86_64.exe’ > setup-x86_64.exe 100% > [===>] > 889.00K 719KB/s in 1.2s > 2016-12-01 10:53:24 (719 KB/s) - ‘setup-x86_64.exe’ saved > [910336/910336] curl -v sometimes shows when server status codes are returned instead of web pages, allowing you to add options to proceed further, step by step. wget -d can also provide more useful information. Packet analyzers like wireshark etc. can let you see what programs like setup are doing (wrong), when compared to wget working correctly. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Pre-compiled Perl::Critic ?
Would it be possible to release a pre-compiled version of Perl::Critic? I built it yesterday from CPAN sources, and it took about nine *hours* to finish! The laptop I built it on has an Intel I7-6600U, 16 GB of memory and an SSD, so I don't know why it should have taken so long! Thanks - Jim -- Jim Reisert AD1C, , http://www.ad1c.us -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fullscreen application with Cygwin/X in multiwindow mode
On Thu, Dec 1, 2016 at 6:23 AM, Jon Turney wrote: > Patches are always welcome. > > I think this should be pretty straightforward to add, although it might be a > bit tedious. > > [1],[2] should help you get started :) > > Looking at this in a little more detail, I wasn't quite accurate in my > statement above: There is very limited support for this state, in that > windows which are created with it are probably shown correctly. > > I think what's needed is extend the handling of _NET_WM_STATE messages so it > can handle a window being changed to _NET_WM_STATE_FULLSCREEN. (At the > moment _NET_WM_STATE is, only handled when it can be mapped down to an > equivalent WM_CHANGE_STATE message, see [3]) > > [1] https://x.cygwin.com/docs/cg/cygwin-x-cg.html > [2] https://specifications.freedesktop.org/wm-spec/wm-spec-latest.html > [3] > https://cgit.freedesktop.org/~jturney/xserver/commit/?h=cygwin-release-1.19&id=55c2ca8cd9287850077102d4ba662cfd2c571ca9 Thanks for the references. I'll see if I can come up with a patch. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fullscreen application with Cygwin/X in multiwindow mode
On Tue, Nov 29, 2016 at 5:37 AM, Andrey Repin wrote: > Depends, what you mean by "fullscreen". All too often people say "fullscreen" > when in fact they mean "borderless windowed". Greetings Andrey. Perhaps I'm using the incorrect term, but I think a borderless maximized window would work fine for viewing PDF's. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Installer names not meaningful enough
Lee Dilkie sent the following at Thursday, December 01, 2016 7:19 AM >On 12/1/2016 5:51 AM, Roberto Ríos Gallardo wrote: >> Please give the installers more meaningful names. In particular, make >> sure "cygwin" is part of it. "setup-x86_64.exe" is not very obvious. >> A version number would be nice too. > >I'd agree that adding "cygwin" to the setup program would be nice >but it's certainly not the windows "way", lots of programs use just >"setup.exe". I've nominated "getcygwin" => getcygwin64.exe or getcygwin32.exe https://sourceware.org/ml/cygwin/2013-09/msg00316.html - Barry Disclaimer: Statements made herein are not made on behalf of NIAID.
Re: Installer names not meaningful enough
On 12/1/2016 8:25 AM, Vlado wrote: > On 1.12.2016 13:51, Eliot Moss wrote: >> I think that including the version of the setup program could be helpful >> - I tend >> to add it (renaming the file by hand). However, clearly we've lived >> with things this >> way for a long time ... More than a score years. > > I disagree. > I have a script to update Cygwin. This script checks for new version of > setup, downloads, verifies signature, etc. Things would become much more > complicated with variable setup file name. > Finally: Why should I care about the exact version number of setup? > Script makes backups of the old setup files like setup.exe.0001, 0002, > ..., just for a cause, but never in the past I did have to looking for > the setup with exact version number. > The only reason would be if you had an older version of the .ini file. When the data prerequisites of the .ini file change there is a new version of setup to handle that. -- cyg Simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Installer names not meaningful enough
On 1.12.2016 13:51, Eliot Moss wrote: I think that including the version of the setup program could be helpful - I tend to add it (renaming the file by hand). However, clearly we've lived with things this way for a long time ... I disagree. I have a script to update Cygwin. This script checks for new version of setup, downloads, verifies signature, etc. Things would become much more complicated with variable setup file name. Finally: Why should I care about the exact version number of setup? Script makes backups of the old setup files like setup.exe.0001, 0002, ..., just for a cause, but never in the past I did have to looking for the setup with exact version number. Vlado -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Installer names not meaningful enough
On 12/1/2016 7:18 AM, Lee Dilkie wrote: > > > On 12/1/2016 5:51 AM, Roberto Ríos Gallardo wrote: >> Please give the installers more meaningful names. In particular, make >> sure "cygwin" is part of it. "setup-x86_64.exe" is not very obvious. A >> version number would be nice too. >> > > I'd agree that adding "cygwin" to the setup program would be nice but it's certainly not the windows > "way", lots of programs use just "setup.exe". > > Versioning can't be added to the file name because the setup program itself isn't versioned, or at > least isn't the same version as the cygwin you are installing... the cygwin version come from the > servers... I think that including the version of the setup program could be helpful - I tend to add it (renaming the file by hand). However, clearly we've lived with things this way for a long time ... Eliot Moss -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fullscreen application with Cygwin/X in multiwindow mode
On 29/11/2016 11:37, Andrey Repin wrote: But ideally this would be fixed by adding support for _NET_WM_STATE_FULLSCREEN to the WM. Any idea how much effort would be required to implement the fullscreen support? Any major hurdles to overcome? It may be something I could work on in my spare time. Patches are always welcome. I think this should be pretty straightforward to add, although it might be a bit tedious. [1],[2] should help you get started :) Looking at this in a little more detail, I wasn't quite accurate in my statement above: There is very limited support for this state, in that windows which are created with it are probably shown correctly. I think what's needed is extend the handling of _NET_WM_STATE messages so it can handle a window being changed to _NET_WM_STATE_FULLSCREEN. (At the moment _NET_WM_STATE is, only handled when it can be mapped down to an equivalent WM_CHANGE_STATE message, see [3]) [1] https://x.cygwin.com/docs/cg/cygwin-x-cg.html [2] https://specifications.freedesktop.org/wm-spec/wm-spec-latest.html [3] https://cgit.freedesktop.org/~jturney/xserver/commit/?h=cygwin-release-1.19&id=55c2ca8cd9287850077102d4ba662cfd2c571ca9 Depends, what you mean by "fullscreen". All too often people say "fullscreen" when in fact they mean "borderless windowed". The difference is crucial. For the latter, you don't do anything short of setting some additional flags on your window and size it to display resolution. In this context, _NET_WM_STATE_FULLSCREEN means 'borderless maximized' -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Installer names not meaningful enough
On 12/1/2016 5:51 AM, Roberto Ríos Gallardo wrote: Please give the installers more meaningful names. In particular, make sure "cygwin" is part of it. "setup-x86_64.exe" is not very obvious. A version number would be nice too. I'd agree that adding "cygwin" to the setup program would be nice but it's certainly not the windows "way", lots of programs use just "setup.exe". Versioning can't be added to the file name because the setup program itself isn't versioned, or at least isn't the same version as the cygwin you are installing... the cygwin version come from the servers... -lee -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Installer names not meaningful enough
Please give the installers more meaningful names. In particular, make sure "cygwin" is part of it. "setup-x86_64.exe" is not very obvious. A version number would be nice too. -- Delay not, Caesar. Read it instantly. -- Shakespeare, "Julius Caesar" 3,1 Here is a letter, read it at your leisure. -- Shakespeare, "Merchant of Venice" 5,1 [Quoted in "VMS Internals and Data Structures", V4.4, when referring to I/O system services.] -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: remote GTK apps nor workin correctly in Cygwin/X
Hi David, On Wed, Nov 30, 2016 at 1:36 PM, David Cunningham wrote: > *** BUG *** > In pixman_region32_init_rect: Invalid rectangle passed > Set a breakpoint on '_pixman_log_error' to debug I got this exact same message on my Ubuntu LTS 14.04 system, which hasn't even heard of Cygwin. (It was either the Ristretto image viewer or the PDF viewer). It may be unrelated to Cygwin. Csaba -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
