Re: Running texconfig breaks backspace in Bash/MinTTY

2016-03-20 Thread Ken Brown

On 3/18/2016 4:14 PM, Yaakov Selkowitz wrote:

On 2016-03-18 06:34, Ken Brown wrote:

The best long-term solution is to get rid of the need for texconfig by
making
tlmgr work on Cygwin[*].


No thanks.  Don't we have all of TeX Live packaged already?  Wouldn't
using this conflict with the packages we already have?


I guess I wasn't clear enough in the footnote when I said I would 
disable some features of tlmgr.  What I meant was that I would disable 
the features that deal with package management.  But tlmgr does other 
things that could be useful (like managing default paper size), and I 
would like to make those things work on Cygwin.


Ken


--
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: Don't I get /etc/profile with a fresh installation?

2016-03-20 Thread Warren Young
On Mar 16, 2016, at 2:18 AM, Gerrit Haase  wrote:
> 
> this is not documented, at least
> not where I expected to find the information:
> https://cygwin.com/faq/faq.html#faq.setup.cli

This is “frequently asked”?
--
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: can't get sshd to new Windows 2012 R2 Server to work

2016-03-20 Thread Warren Young
On Mar 15, 2016, at 4:35 PM, Kevin Layer  wrote:
> 
> Cygwin Configuration Diagnostics

Next time, please *attach* this, don’t paste it inline.

(That’s not my idiosyncratic preference, it’s part of the instructions: 
https://cygwin.com/problems.html)

> Running in Terminal Service session

You say you disabled the firewall on the machine you’re working with, but have 
you disabled the firewall on the TS host, too?

Truncated SSH sessions feel like some sort of security thingy to me.

> Output from C:\cygwin\bin\id.exe
> UID: 1049579(layer) GID: 1049089(Domain Users)
> 1049089(Domain Users)   559(Performance Log Users)
> 545(Users)  14(REMOTE INTERACTIVE LOGON)
> 4(INTERACTIVE)  11(Authenticated Users)
> 15(This Organization)   4095(CurrentSession)
> 66048(LOCAL)1054502(domcon2 $ Acronis Remote 
> Users)
> 1055482(CERTSVC_DCOM_ACCESS)401408(Medium Mandatory Level)

I don’t see 544 in there, so this must not be an admin shell.  I believe you 
need to run ssh-host-config as admin for it to do its work correctly.  Without 
those privileges, it can’t set sshd up to run as admin but drop privileges to 
the logged-in user when accepting connections.
--
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: make command fails on cygwin-x86 (cyggmp-10.dll: Loaded to different address)

2016-03-20 Thread Tatsuro MATSUOKA
Dear Achim

>Tatsuro MATSUOKA  yahoo.co.jp> writes:
>>  The last step of setup seem to be autorebase then setup command is the
> easiest way
>>  to use "rebase". Am I right?
> 
> Yes.
>>  After rebase sometime one needs to restart PC. Right?
> 
> No.  You only need to restart if in-use DLL have been replaced during setup.
> Rebase just doesn't do anything for in-use files, so the worst that can
> happen is that you have an incomplete rebase.
> 
Thank you for your kind explanations.

I remember the situation of the Cygwin setup before the issue.
Usually I do not use cygwin process until setup command finished.
However,I have no confidence that I kill all other cygwin-x86 process at that 
time.
I will take care during cygwin setup process.

Regards

Tatsuro 

--
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



[ANNOUNCEMENT] Updated: Perl distributions

2016-03-20 Thread Achim Gratz

The following Perl distributions are updated to the latest version
available on CPAN:

perl-Log-Log4perl-1.47-1
perl-Mojolicious-6.56-1
perl-Scalar-List-Utils-1.44-1
perl-Socket6-0.26-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:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple



2.4-2.5 x64: bash crashes on backticks, gdb crashes on opening core dump

2016-03-20 Thread Ivan Pozdeev

bash

I'm being plagued by these crashes for about half a month now.
Specifically, it cannot run any `configure' script.
The crashes appear to happen in child bash/sh processes launched while 
processing backticks. Other times, commands with stream redirection fail 
silently or produce nothing. Simple commands or very short scripts do 
not fail.


On trying to open `sh.exe.core', gdb 1.10 crashes, too; gdb 1.9 says 
"get_core_register_section: Assertion `core_vec' failed" (see 
attachment). So I'm unable to diagnose bash's problem right now.


At another machine with the same packages, bash does not fail, but gdb's 
problem stands. Already tried reinstalling all the packages `bash' 
depends on and itself to no effect.


gdb
---
I managed to debug the gdb session with VisualGDB (trial).
It turns out, the root cause is that the /bin/sh executable is x64, but 
the core file `sh.exe.core' - of the same executable - has i386 format!

(objdump: <...>sh.exe.core: file format elf32-i386)

And gdb doesn't check that. Created ticket (incl. patch):
https://sourceware.org/bugzilla/show_bug.cgi?id=19834

Now I'm stumped. How can this be?! Does this mean `dumper' is faulty?
If this was normal, gdb would likely be able to process the dumps.

further action
--
Since the crash dump is unusable, I'm now going the only way available, 
checking `dumper''s workings (this needs to be done anyway)


summary
---
Writing this primarily to alert the community of these apparent critical 
bugs.

Hints on where to look inside `dumper' would be more than welcome, too.

--
Regards,
Ivan Pozdeev






$ gdb /bin/sh UU/sh.exe.core
GNU gdb (GDB) Cygwin 7.9.1-1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /bin/sh...(no debugging symbols found)...done.

warning: core file may not match specified executable file.
[New Thread 0x1288]
[New Thread 0x2f38]
/wip/cygport-git/gdb/gdb-7.9.1-1.x86_64/src/gdb-7.9.1/gdb/corelow.c:542: 
internal-error: get_core_register_section: Assertion `core_vec' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

This is a bug, please report it.  For instructions, see:
.

/wip/cygport-git/gdb/gdb-7.9.1-1.x86_64/src/gdb-7.9.1/gdb/corelow.c:542: 
internal-error: get_core_register_section: Assertion `core_vec' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) y
*** starting debugger for pid 6248, tid 9044
*** continuing pid 6248 from debugger call (1)
Aborted (core dumped)


cygcheck.out.gz
Description: application/gzip
--
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: clang copy of limits.h misses NAME_MAX

2016-03-20 Thread Ismail Donmez
Hi,

On Thu, Mar 17, 2016 at 3:11 PM, Hans-Bernhard Bröker
 wrote:
> Hello there,
>
> clang has its own copy of some system headers.  One of those lacks an entry
> that breaks compilation of any program trying to work with directories the
> POSIX way:
>
> $ cat tdirent.c
> #include 
>
> void foo(void)
> {
> return;
> }
>
> $ clang -c tdirent.c
> In file included from tdirent.c:1:
> In file included from /usr/include/dirent.h:6:
> /usr/include/sys/dirent.h:31:15: error: use of undeclared identifier
> 'NAME_MAX'
>   char d_name[NAME_MAX + 1];
>   ^
> 1 error generated.
>
> The same file compiles just fine with GCC.  The problem turns out to be that
> NAME_MAX is defined in  as seen by GCC, but not in the same header
> read by clang.  The culprit is this file:
>
> $ cygcheck -f /usr/lib/clang/3.7.1/include/limits.h
> libclang3.7-3.7.1-1

clangs limits.h has:

#if __STDC_HOSTED__ && __has_include_next()
#include_next 
#endif

So it does depend on system's own limits.h which should have this
definition. And cygwin's /usr/include/limits.h does have NAME_MAX
defined but show its being hidden. Checking the preprocessed source
file might help to see why.

ismail

--
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



X widget question

2016-03-20 Thread Marco Atzeri

I have finally identified where ncview was
segfaulting on X86_64

The solution was to reverse the order of destruction
for a chain of widgets

i=0;
-   while( (w = *(diminfo_row_widget + i++)) != NULL )
-   XtDestroyWidget( w );
+   while( (w = *(diminfo_row_widget + i)) != NULL )
+   i++;
+   while( i>0 ) {
+   i--;
+   XtDestroyWidget( *(diminfo_row_widget + i ));
+   }
 }

that were connected by a vertical constraints:

*(diminfo_row_widget+ll) = XtVaCreateManagedWidget(
   widget_name,
   boxWidgetClass,
   commandcanvas_widget,
   XtNorientation, XtorientHorizontal,
   XtNfromVert, *(diminfo_row_widget + (ll-1)),
   XtNheight, bb_height,
   XtNwidth,  bb_width,
   NULL);

The segfault was inside Xlib when managing the constraints.

As the segfault did not happened on i686, is it possible
that is a race inside Xlib  ?
I have not found in the X Documentation nothing about
requested order of widget destruction in this case.

Thanks in advance
Marco

--
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: Change PS1 when run as administrator

2016-03-20 Thread Erik Soderquist
On Tue, Mar 15, 2016 at 7:19 PM, Warren Young wrote:
>> I'm fairly certain that I have not had this machine that long
>
> The mtimes on those files is as reliable as your system clock, because 
> they’re generated during first install.

Turns out I was wrong, I've had the machine since 2014-12-04 according
to corporate asset management records... cygwin installed the next day
sounds like me.

-- Erik

--
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: [Attn] git maintainer: Remote Code Execution for git < 2.7.1

2016-03-20 Thread Adam Dinwoodie
On Fri, Mar 18, 2016 at 10:41:41AM +0200, Ismail Donmez wrote:
> On Wed, Mar 16, 2016 at 12:50 PM, Adam Dinwoodie  wrote:
> > On Wed, Mar 16, 2016 at 07:43:54AM +0200, Ismail Donmez wrote:
> >> Please see http://www.openwall.com/lists/oss-security/2016/03/15/5 .
> >> Would be nice to update to just released 2.7.3 version.
> >
> > Ack, thanks for the heads up.  I've been holding off on making a release
> > while investigating some test failures, but I'll try to make a new build
> > available either today or tomorrow.
> 
> Now git 2.7.4 is released with more security fixes:
> https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.7.4.txt
> :(

Yes, I spotted that last night.  I needed to do a rebuild anyway, so
I'll build this version.

Adam

--
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



Running texconfig breaks backspace in Bash/MinTTY

2016-03-20 Thread Adam Dinwoodie
Here's an interesting bug: normally in a Bash session in MinTTY,
backspace and Ctrl+H both delete the previous character, as expected.
However, after running texconfig and returning to the shell, both the
backspace key and Ctrl+H appear to just print "^H" to the terminal.

It looks like this is genuinely the terminal trying to render a
backspace character, rather than just backspacing, given the following:

$ printf ^H | xxd
: 08   .

(To get that, I typed "printf {backspace} | xxd".)

It's not clear to me whether this is Bash, MinTTY or texconfig that's
misbehaving.  Ctrl+W to delete a word, Ctrl+R to get (for me) fzf's
history search, and using the up and down arrows to navigate history all
work.  Running Vim, opening a new Bash shell from within the duff one,
or SSHing to another box has Ctrl+H working just fine within that
process, but the bugged behaviour resumes when I return to the original
Bash shell.

Attempting the same thing but using Windows' cmd shell window, by
running cmd, running c:\cygwin64\bin\bash there, configuring PATH to
include /bin, then running texconfig, has Ctrl+H and backspace both
working fine to delete the previous character after texconfig exits.

Redacted cygcheck.out attached.

Cygwin Configuration Diagnostics
Current System Time: Wed Mar 16 12:18:36 2016

Windows 7 Enterprise Ver 6.1 Build 7601 Service Pack 1

Path:   C:\cygwin64\home\add\bin
C:\cygwin64\usr\local\bin
C:\cygwin64\bin
C:\ProgramData\Oracle\Java\javapath
C:\Perl\site\bin
C:\Perl\bin
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0
Z:\bin\wget
C:\program files (x86)\putty
C:\Program Files\TortoiseSVN\bin
C:\Program Files (x86)\Skype\Phone
C:\cygwin64\lib\lapack

Output from C:\cygwin64\bin\id.exe
UID: 1063214(add)
GID: 1049089(Domain Users)
1049089(Domain Users)
545(Users)
4(INTERACTIVE)
66049(CONSOLE LOGON)
11(Authenticated Users)
15(This Organization)
4095(CurrentSession)
66048(LOCAL)
{entries removed}
1056149(All)
{entries removed}

SysDir: C:\Windows\system32
WinDir: C:\Windows

USER = 'add'
PWD = '/home/add'
HOME = '/home/add'

USERDOMAIN_ROAMINGPROFILE = 'DCL'
HOMEPATH = '\Users\add'
_fzf_orig_completion_tee = 'complete -F %s tee #_longopt'
QT_DEVICE_PIXEL_RATIO = 'auto'
APPDATA = 'C:\Users\add\AppData\Roaming'
SSH_AGENT_PID = '15572'
ProgramW6432 = 'C:\Program Files'
HOSTNAME = 'PC5175'
_fzf_orig_completion_diff = 'complete -F %s diff #_longopt'
SHELL = '/bin/bash'
TERM = 'xterm'
PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 60 Stepping 3, GenuineIntel'
PROFILEREAD = 'true'
WINDIR = 'C:\Windows'
_fzf_orig_completion_mv = 'complete -F %s mv #_longopt'
PUBLIC = 'C:\Users\Public'
_fzf_orig_completion_du = 'complete -F %s du #_longopt'
OLDPWD = '/cygdrive/c/Windows/system32'
_fzf_orig_completion_bunzip2 = 'complete -F %s bunzip2 #_filedir_xspec'
ORIGINAL_PATH = 
'/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Perl/site/bin:/cygdrive/c/Perl/bin:/cygdrive/c/Windows/system32:/cygdrive/c/Windows:/cygdrive/c/Windows/System32/Wbem:/cygdrive/c/Windows/System32/WindowsPowerShell/v1.0:/cygdrive/z/bin/wget:/cygdrive/c/program
 files (x86)/putty:/cygdrive/c/Program 
Files/TortoiseSVN/bin:/cygdrive/c/Program Files (x86)/Skype/Phone'
USERDOMAIN = 'DCL'
CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files'
_fzf_orig_completion_less = 'complete -F %s less #_longopt'
OS = 'Windows_NT'
ALLUSERSPROFILE = 'C:\ProgramData'
_fzf_orig_completion_rmdir = 'complete -F %s rmdir #_longopt'
_fzf_orig_completion_head = 'complete -F %s head #_longopt'
_fzf_orig_completion_tail = 'complete -F %s tail #_longopt'
_fzf_orig_completion_svn = 'complete -o default -X 
'@(*/.svn|*/.svn/|.svn|.svn/)' -F %s svn #_svn'
windows_tracing_flags = '3'
_fzf_orig_completion_telnet = 'complete -F %s telnet #_known_hosts'
windows_tracing_logfile = 'C:\BVTBin\Tests\installpackage\csilogfile.log'
VBOX_INSTALL_PATH = 'C:\Program Files\Oracle\VirtualBox\'
!:: = '::\'
LS_COLORS = 
'rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:

[ANNOUNCEMENT] Updated: mc-4.8.16-1

2016-03-20 Thread Marco Atzeri

Version mc-4.8.16-1 of Midnight Commander
has been uploaded for cygwin

CHANGES
This is a upstream bugfix release
https://www.midnight-commander.org/wiki/NEWS-4.8.16

DESCRIPTION
GNU Midnight Commander is a visual file manager. It's a feature rich
full-screen text mode application that allows you to copy, move and
delete files and whole directory trees, search for files and run
commands in the subshell. Internal viewer and editor are included.

HOMEPAGE
http://www.midnight-commander.org/


Regards
Marco Atzeri

If you have questions or comments, please send them to the
cygwin mailing list at: cygwin (at) cygwin (dot) com .

--
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



[ANNOUNCEMENT] Updated: wtf-0.0.4-8

2016-03-20 Thread Marco Atzeri

Version 0.0.4-8 of "wtf" has been uploaded.

wtf translates acronyms and filename suffixes for you.

The wtf program looks-up the definition of a term. It supports a
number of definition sources. In this version they are an acronyms
database and a filename suffixes database.

CHANGES
- Built also for X86_64
- synced the Cygwin acronyms with the webpage
  https://cygwin.com/acronyms/
- synced the acronyms with BSD
  https://sourceforge.net/projects/bsdwtf/

HOMEPAGE
https://sourceforge.net/projects/wtf/


Regards

Marco Atzeri

If you have questions or comments, please send them to the
cygwin mailing list at: cygwin (at) cygwin (dot) com .

--
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: 2.4-2.5 x64: bash crashes on backticks, gdb crashes on opening core dump

2016-03-20 Thread Marco Atzeri

On 20/03/2016 10:05, Ivan Pozdeev wrote:

bash

I'm being plagued by these crashes for about half a month now.
Specifically, it cannot run any `configure' script.
The crashes appear to happen in child bash/sh processes launched while
processing backticks. Other times, commands with stream redirection fail
silently or produce nothing. Simple commands or very short scripts do
not fail.


Any BLODA around ?


On trying to open `sh.exe.core', gdb 1.10 crashes, too; gdb 1.9 says
"get_core_register_section: Assertion `core_vec' failed" (see
attachment). So I'm unable to diagnose bash's problem right now.

At another machine with the same packages, bash does not fail, but gdb's
problem stands. Already tried reinstalling all the packages `bash'
depends on and itself to no effect.

gdb
---
I managed to debug the gdb session with VisualGDB (trial).
It turns out, the root cause is that the /bin/sh executable is x64, but
the core file `sh.exe.core' - of the same executable - has i386 format!
(objdump: <...>sh.exe.core: file format elf32-i386)


Are you sure about the 64 bit dumper ?
https://www.cygwin.com/cygwin-ug-net/dumper.html


--
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



clamav: Request for package update

2016-03-20 Thread Jonathan D Johnston
Attention package clamav maintainer (Reini Urban?)

Usage of freshclam (1) reports that the recommended version of ClamAV is
0.99.1, but the most recent version in https://cygwin.com/packages/ is
0.98.7 .  Version 0.98.7 isn't functional with the current ClamAV
databases.  Can this package be updated?  Thanks!

--
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: Suddenly: Font does not support ANSI character range?

2016-03-20 Thread Thomas Wolff

Am 19.03.2016 um 19:54 schrieb Andrey Tarasevich:

On Sat, Mar 19, 2016 at 11:01 AM, Thomas Wolff  wrote:

Am 19.03.2016 um 18:18 schrieb Andrey Tarasevich:

...
when I attempt to start Cygwin terminal (mintty), I'm immediately
greeted with a message box saying

Lucida Console
Font does not support ANSI character range
...

This is fixed in the uploaded repository. Cygwin package to follow.
Thomas

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


--
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: Running texconfig breaks backspace in Bash/MinTTY

2016-03-20 Thread Ken Brown
On 3/17/2016 7:40 AM, Ken Brown wrote:
> On 3/16/2016 6:11 PM, Thomas Wolff wrote:
>> Am 16.03.2016 um 16:07 schrieb Ken Brown:
>>> On 3/16/2016 10:00 AM, Adam Dinwoodie wrote:
 On Wed, Mar 16, 2016 at 08:34:45AM -0400, Ken Brown wrote:
> On 3/16/2016 7:45 AM, Adam Dinwoodie wrote:
>> Here's an interesting bug: normally in a Bash session in MinTTY,
>> backspace and Ctrl+H both delete the previous character, as expected.
>> However, after running texconfig and returning to the shell, both the
>> backspace key and Ctrl+H appear to just print "^H" to the terminal.
>>
>> It looks like this is genuinely the terminal trying to render a
>> backspace character, rather than just backspacing, given the
>> following:
>>
>>  $ printf ^H | xxd
>>  : 08   .
>>
>> (To get that, I typed "printf {backspace} | xxd".)
>>
>> It's not clear to me whether this is Bash, MinTTY or texconfig that's
>> misbehaving.  Ctrl+W to delete a word, Ctrl+R to get (for me) fzf's
>> history search, and using the up and down arrows to navigate
>> history all
>> work.  Running Vim, opening a new Bash shell from within the duff 
>> one,
>> or SSHing to another box has Ctrl+H working just fine within that
>> process, but the bugged behaviour resumes when I return to the
>> original
>> Bash shell.
>
> I can't reproduce this on my system.  I tried 'texconfig --help' and
> 'texconfig conf'.  What's the precise texconfig command that you
> used?

 I'm just running `texconfig`, with no arguments.  There's a warning
 prompt, that you press Enter to clear, then there's an interactive menu
 that appears -- I'm assuming it's something about that interactive menu
 that's causing the problem.
>>>
>>> In the interactive case, texconfig calls texconfig-dialog, which calls
>>> dialog.
>>>
 Turns out, after some digging, MinTTY's "Keys" > "Backspace sends ^H"
 setting is critical here -- my .minttyrc has `BackspaceSendsBS=yes`, 
 but
 if I remove that line and restart MinTTY, everything works fine.  If I
 add that setting to a fresh Cygwin install that contains only the Base
 packages, texlive-collection-basic, and their dependencies, I can
 reproduce the issue.

 That probably explains why you can't reproduce it, but it still seems
 like a bug -- I wouldn't expect backspace behaviour to change in that
 fashion regardless of that bit of configuration.
>>>
>>> So it appears to be a MinTTY/dialog issue.
>> Checking stty -a before and after texconfig reveals that texconfig
>> mangles the stty erase setting and does not restore it.
>> That is clearly a bug of texconfig.
> 
> I'm not sure how you ruled out dialog as the culprit, but in fact you're 
> right. texconfig-dialog calls 'reset' and 'stty sane' at various places, 
> and that seems to be the problem. I'll report this upstream.

I've done this in http://tug.org/pipermail/tex-live/2016-March/037852.html, 
where you can also see responses by two of the TeX Live developers.

The best long-term solution is to get rid of the need for texconfig by making 
tlmgr work on Cygwin[*].  In the meantime, upstream TeX Live will consider 
patches that make texconfig stop messing with terminal settings.  [If it turns 
out that dialog also messes with terminal settings, then we'll have to find a 
different workaround.]

Here's one possibility:

--- /usr/share/texmf-dist/scripts/texlive/texconfig-dialog.sh.orig  
2015-10-08 16:04:18.0 -0400
+++ /usr/share/texmf-dist/scripts/texlive/texconfig-dialog.sh   2016-03-18 
07:26:50.708149300 -0400
@@ -43,7 +43,7 @@
   rc=$1
   $needsCleanup && test -n "$tmpdir" && test -d "$tmpdir" \
 && { cd / && rm -rf "$tmpdir"; }
-  termCtl reset
+  termCtl clear
   (exit $rc); exit $rc
 }

Adam, please give this a try and let me know if it solves the problem without 
creating new ones.

Ken

[*] tlmgr is currently incompatible with the Cygwin packaging of TeX Live.  
I'll look into fixing this for TeX Live 2016.  I should be able to simply 
disable some features of tlmgr, while retaining those that replace the 
functionality of texconfig.


--
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: git svn -T svn://svn. ...

2016-03-20 Thread Adam Dinwoodie
On Wed, Mar 09, 2016 at 07:46:06PM +, Adam Dinwoodie wrote:
> On Tue, Mar 08, 2016 at 01:32:30PM -0500, cyg Simple wrote:
> > Using the latest production release 2.4.1(1) the command is removing the
> > / after the svn: leaving svn:/svn which isn't correct.  Using
> > 'svn://svn' doesn't help either.
> > 
> > (2) $ git svn init -T 'svn://svn.code.sf.net/p/squirrelmail/code/trunk'
> > E: 'svn:/svn.code.sf.net/p/squirrelmail/code/trunk' is not a complete
> > URL  and a separate URL is not specified
> 
> I'm seeing the same behaviour on local builds of both v2.7.0 and v2.2.0,
> and when using http:// URIs as well as svn:// ones.  Very sad.
> 
> It's not immediately obvious what's going wrong here, and I don't
> currently have much spare time for digging, but I'll add it to my queue
> to investigate the problem / report it upstream to see if anyone else
> has any cunning ideas.

This has now been fixed upstream; the fix should be available from
v2.8.0.

Adam

--
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: ctrl-c doesn't reliably kill ping

2016-03-20 Thread cyg Simple
On 3/15/2016 7:43 AM, Adam Dinwoodie wrote:
> On Tue, Mar 15, 2016 at 02:00:38PM +0300, Andrey Repin wrote:
>> Greetings, Frank Farance!
>>
>>> A little digression, so you understand the background ... The workstation I 
>>> am
>>> doing this from is connected to a Verizon router to their FIOS network.  
>>> Now the
>>> reason I mention this is that the router's DNS (via DHCP to my workstation) 
>>> is
>>> 192.168.1.1, which I presume is forwarded from the router upstream to 
>>> Verizon's
>>> DNS caches.  So if I type the URL http://something.that.doesnt.exist in my 
>>> browser, rather than getting a Hostname Not Found error (at the name 
>>> resolution
>>> level), it actually loads up a page saying "something.that.doesnt.exist" 
>>> isn't
>>> found and then I have a Yahoo set of search results on things matching the 
>>> broken hostname.
>>
>>> So all of this is normal ISP stuff: they actually resolve unknown addresses 
>>> to
>>> their own website (which is 90.242.140.21).
>>
>> This is NOT "normal", this is a violation of protocol.
>> Whoever encounter such behavior should call their ISP and tell them to stop
>> doing it.
> 
> It's both normal and a violation of protocol -- a lot of DNS servers,
> will replace an NXDOMAIN response will "hijack" the query and return
> something that punts the user onto a search page with advertising.
> 

This should probably be moved to cygwin-talk but ...

If a violation becomes normal then it is no longer a violation but an
accepted practiced exception.  Unless a rule is enforced the accepted
practiced exception becomes the rule.

-- 
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



Package choosing algorithm ...

2016-03-20 Thread Houder

Hi Corinna,

A year ago you changed the "package choosing algorithm" ...

https://sourceware.org/ml/cygwin/2015-02/msg00034.html
 - [ANNOUNCEMENT] Updated: setup.exe (Release 2.864) -- by Corinna 
Vinschen

Here C. announces the modification of the "package choosing algorithm"
(and the introduction of the "mirror mode")

When I started setup (2.873) and selected "Download without Installing", 
it
offered me to download version 2.5.0-0.8 of cygwin (installed: 
2.5.0-0.7).


Splendid!

However when I restarted setup and selected "Install from Local 
Directory",

it did NOT offer me to install version 2.5.0-0.8 ...

(Meaning, I had to restart setup AGAIN, and force it to install the last
 version of cygwin - a bit annoying, as you wrote in [1])

Did your modification only apply to the  "Download without Installing" 
part

of setup? (i.e. downloading from internet)

(honestly, I do not remember whether or not setup acted consistently in 
both

 modes after your modification)

Did I miss something?

Regards,

Henri

[1]
https://cygwin.com/ml/cygwin-apps/2015-01/msg00126.html
 - Setup patch to keep test version if test version installed - by 
Corinna

   Vinschen
Start of discussion ...

=

--
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: faster opening Cygwin from Explorer window

2016-03-20 Thread Buchbinder, Barry (NIH/NIAID) [E]
Marco Atzeri sent the following at Friday, March 18, 2016 11:01 AM
>On 18/03/2016 15:43, Nellis, Kenneth wrote:
>> I frequently ping-pong back and forth between working in the Windows
>> and Cygwin environments, needing to keep both Explorer windows and
>> Cygwin PWD focused on the same folder/directory. (I use mintty in
>> Cygwin.)
>>
>> To open an Explorer window to my Cygwin PWD, I can simply type "cygstart .".
>> The reverse is a clumsy bit of typing and mousing: From Cygwin/bash,
>> enter "cd " (but not Return), go to my Explorer window and drag the
>> folder icon from the address bar into the mintty window and press return.
>> I'm looking for a simpler method.
>>
>> My ideal scenario is to right-click in the Explorer window, select the
>> new Cygwin option that I'd like to appear, and this would open a
>> mintty/bash window with PWD set to that Windows folder.
>>
>> Long shot, I know, but if anyone has done this and is willing to share
>> I'd love to hear about it. BTW, I'm using Windows 7 and am current on
>> Cygwin 64-bit.
>
> "Cygwin Prompt Here context menus"
>looks on chere package

For a while recently - and for unknown reasons - the chere menu entries
were not working for me.  I ended up creating a shortcut in my SendTo
folder/menu that would open a bash window in the directory containing
the highlighted file or folder.  Not perfect, but better than nothing.

Target:
C:\cygwin\bin\mintty.exe -e /bin/xhere /bin/bash.exe "%L"
Start in:  [leave blank]

I don't remember whether there might be any customizations in .bashrc
that helped this to work, so YMMV.

BTW, chere is back working for me now.  Don't remember what - if
anything noticeable - changed.

- Barry

--
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



[ANNOUNCEMENT] Updated: mintty 2.3.2

2016-03-20 Thread Thomas Wolff
I have uploaded mintty 2.3.2 with the following changes (same as 
pre-release 2.2.4, plus 3 fixes):


Highlights:
  * Font setup and configuration improvements.
  * Colour schemes / Theme files.
  * GUI configuration of wav file for terminal beep.
  * Startup error handling improvements.

Font configuration:
  * Mintty adjusts row spacing according to the font metrics, to 
compensate for tight or tall spacing of some fonts (e.g. Consolas, 
FreeMono, Monaco). (The RowSpacing value is added to that.)

  * Adjusting font weight selection to available font weights (#520).
  * New option FontWeight supports more specific font weight selection 
(#520).

  * Font selection menu has its own Apply button.
  * Fonts with name problems (long names, #507) can be selected with 
the Apply button.

  * Warnings for font not found or not supporting ANSI character set.
  * Excluding fonts with OEM or SYMBOL charset from font selection menu.
  * Excluding vertical fonts from font selection menu.
  * New option ShowHiddenFonts to offer monospace fonts marked to Hide 
in the menu.

  * Unicode-enabled Font setting (so e.g. mintty -o Font=Sütterlin works).

Themes, Configuration, and Options menu:
  * Colour schemes: New option ThemeFile, configuration also in Options 
menu (~#193).
  * Configuration of .wav bell sounds (option BellFile, #369) in 
Options menu.

  * Resource directory $HOME/.mintty for theme and bell files.
  * Fixed -o settings to also be saved when changed in Options menu.

Keyboard and mouse features:
  * Workaround for occasional Alt state inconsistencies after window 
focus changes (#519).

  * Compose key on wiki pages: replace AllChars with WinCompose.
  * Opening marked "www." addresses also without "http:" prefix (#345).

Start and error handling:
  * Fixed -C/--loadconfig to not overwrite common options in main 
config file.

  * Fixed format substitution for log file in case of excess % conversions.
  * Report full pathname of log file if creation fails.
  * Improved and fixed format of child creation error messages.
  * Improved reporting failed icon loading with non-ANSI icon filenames.

The homepage is at http://mintty.github.io/
It also links to the issue tracker.

--
Thomas

--
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



Is ping only supposed to work for admin accounts?

2016-03-20 Thread Ray Satiro

I just used the cygwin installer to install ping-1.0.2-1.tar.xz but it
doesn't work for limited user accounts:

$ ping google.com
ping: socket: Operation not permitted

  149   29930 [main] ping 11668 dup_ent: duping protoent "icmp", 0xD56580
   46   29976 [main] ping 11668 dup_ent: protoent icmp 0x80039F64 0x1
   21   29997 [main] ping 11668 dup_ent: duped protoent "icmp", 0x80039F50
   21   30018 [main] ping 11668 cygwin_socket: socket (2, 3 (flags 0x0), 1)
--- Process 11668 loaded C:\Windows\SysWOW64\WSHTCPIP.DLL at 73BB
 1084   31102 [main] ping 11668 __set_errno: void
__set_winsock_errno(const char*, int):235 setting errno 1
   37   31139 [main] ping 11668 __set_winsock_errno: cygwin_socket:694
- winsock error 10013 -> errno 1
   57   31196 [main] ping 11668 cygwin_socket: -1 = socket(2, 3 (flags
0x0), 1), errno 1





--
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: 2.4-2.5 x64: bash crashes on backticks, gdb crashes on opening core dump

2016-03-20 Thread Ivan Pozdeev



20.03.2016 15:47, Marco Atzeri пишет:

On 20/03/2016 10:05, Ivan Pozdeev wrote:

bash

I'm being plagued by these crashes for about half a month now.
Specifically, it cannot run any `configure' script.
The crashes appear to happen in child bash/sh processes launched while
processing backticks. Other times, commands with stream redirection fail
silently or produce nothing. Simple commands or very short scripts do
not fail.


Any BLODA around ?
None that I managed to find (checked with AVZ for interceptors, autoruns 
from a boot disk for suspicious entries, procmon for 3rd-party drivers 
in call chain).
There might be something from hardware drivers, but none were installed 
two weeks ago.



On trying to open `sh.exe.core', gdb 1.10 crashes, too; gdb 1.9 says
"get_core_register_section: Assertion `core_vec' failed" (see
attachment). So I'm unable to diagnose bash's problem right now.

At another machine with the same packages, bash does not fail, but gdb's
problem stands. Already tried reinstalling all the packages `bash'
depends on and itself to no effect.

gdb
---
I managed to debug the gdb session with VisualGDB (trial).
It turns out, the root cause is that the /bin/sh executable is x64, but
the core file `sh.exe.core' - of the same executable - has i386 format!
(objdump: <...>sh.exe.core: file format elf32-i386)


Are you sure about the 64 bit dumper ?
https://www.cygwin.com/cygwin-ug-net/dumper.html

There's only one copy on my system and it's a 64-bit exe:
$ which dumper
/usr/bin/dumper
$ cygcheck -f `which dumper`
cygwin-2.4.1-1
$ objdump -h `which dumper` | head
/usr/bin/dumper: file format pei-x86-64
<...>
Already tried reinstalling the package as well as trying other versions 
available (2.3.1 and 2.5.0).
specifying full windows-style path to the exe as `man dumper' says 
doesn't change anything.



--
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



--
Regards,
Ivan


--
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: Is ping only supposed to work for admin accounts?

2016-03-20 Thread Brian Mathis
Yes.  Ping needs admin rights in all operating systems, but they have
various ways to allow access, such as running suid in unix or using a
special API call on Windows.  If you need ping from cygwin, it's best
to rely on the Windows version without installing the cygwin one.

~ Brian

On Sun, Mar 20, 2016 at 5:34 PM, Ray Satiro  wrote:
> I just used the cygwin installer to install ping-1.0.2-1.tar.xz but it
> doesn't work for limited user accounts:
>
> $ ping google.com
> ping: socket: Operation not permitted
>
>   149   29930 [main] ping 11668 dup_ent: duping protoent "icmp", 0xD56580
>46   29976 [main] ping 11668 dup_ent: protoent icmp 0x80039F64 0x1
>21   29997 [main] ping 11668 dup_ent: duped protoent "icmp", 0x80039F50
>21   30018 [main] ping 11668 cygwin_socket: socket (2, 3 (flags 0x0), 1)
> --- Process 11668 loaded C:\Windows\SysWOW64\WSHTCPIP.DLL at 73BB
>  1084   31102 [main] ping 11668 __set_errno: void
> __set_winsock_errno(const char*, int):235 setting errno 1
>37   31139 [main] ping 11668 __set_winsock_errno: cygwin_socket:694
> - winsock error 10013 -> errno 1
>57   31196 [main] ping 11668 cygwin_socket: -1 = socket(2, 3 (flags
> 0x0), 1), errno 1
>
>
>
>
>
> --
> 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
>

--
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