Re: [ANNOUNCEMENT] Updated: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1

[Steven Penny]

On Wed, 18 Jan 2017 00:02:37, "Larry Hall (Cygwin)" wrote:
> Whoa!  While I agree there has been some very negatively charged comments
> coming from Steven in this thread, I don't think we need to start finding
> fault with everything he says and does relative to it.  It's perfectly
> fine for him, or anyone else for that matter, to monitor a thread or this
> list in whatever form works for them.  In this case, Steven corrected the
> problem when it was pointed out to him that his method was breaking
> threading.  That's a perfectly acceptable response and all we can ask of
> him in that regard.  There's no need to go looking for fault in that.

Thanks. I was put off by Eric at first, as it seemed he wanted me to do
everything, and I was not looking forward to fixing a low level bug like this.
Still am not.

> Let's try to keep this thread productive and moving forward.  While I
> would say, in my estimation, it got off to a rocky start, I think the
> recent exchange between Steven and Eric has done allot to track the
> problem and to scale back the negative comments.  Let's try to keep the
> thread moving forward on both fronts.

I would like to keep this productive; my next step is to try to unpack that
large commit, while also helping Eric to reproduce.

On Tue, 17 Jan 2017 21:09:33, Doug Henderson wrote:
> I find it despicable that you want us to participating in solving a
> problem you encountered, but seem unwilling to subscribe so you can
> participate in solving problems that the rest of us encounter.

I am going to keep my response here civil, with repsect to Larry. I would like
you to know that I have answered more Cygwin questions on Stack Overflow than
anyone on the site:

http://stackoverflow.com/tags/cygwin/topusers

No, I am no subscribed to this list, but the point of my script is to allow me
to reply without subscribing. I can reply to any threads, not just my own.


--
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: [ANNOUNCEMENT] Updated: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1

[Larry Hall (Cygwin)]

On 01/17/2017 11:09 PM, Doug Henderson wrote:

On 17 January 2017 at 20:55, Steven Penny  wrote:

On Tue, 17 Jan 2017 20:08:17, Eric Blake wrote:

[again, your email client likes to break threading, so I nearly missed
this one]


Sorry about that, I wrote my own client so that I could reply without
subscribing:


I find it despicable that you want us to participating in solving a
problem you encountered, but seem unwilling to subscribe so you can
participate in solving problems that the rest of us encounter.

I feel that you are using false pretenses to use our time to think
about your problem and offer solutions, if we can, without
reciprocating.

Shame on you.


Whoa!  While I agree there has been some very negatively charged comments
coming from Steven in this thread, I don't think we need to start finding
fault with everything he says and does relative to it.  It's perfectly
fine for him, or anyone else for that matter, to monitor a thread or this
list in whatever form works for them.  In this case, Steven corrected the
problem when it was pointed out to him that his method was breaking
threading.  That's a perfectly acceptable response and all we can ask of
him in that regard.  There's no need to go looking for fault in that.

Let's try to keep this thread productive and moving forward.  While I
would say, in my estimation, it got off to a rocky start, I think the
recent exchange between Steven and Eric has done allot to track the
problem and to scale back the negative comments.  Let's try to keep the
thread moving forward on both fronts.


--
Larry

_

A: Yes.

Q: Are you sure?

A: Because it reverses the logical flow of conversation.

Q: Why is top posting annoying in email?


--
Larry

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
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: [ANNOUNCEMENT] Updated: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1

[Doug Henderson]

On 17 January 2017 at 20:55, Steven Penny  wrote:
> On Tue, 17 Jan 2017 20:08:17, Eric Blake wrote:
>> [again, your email client likes to break threading, so I nearly missed
>> this one]
>
> Sorry about that, I wrote my own client so that I could reply without
> subscribing:

I find it despicable that you want us to participating in solving a
problem you encountered, but seem unwilling to subscribe so you can
participate in solving problems that the rest of us encounter.

I feel that you are using false pretenses to use our time to think
about your problem and offer solutions, if we can, without
reciprocating.

Shame on you.

Doug

--
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: [ANNOUNCEMENT] Updated: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1

[Steven Penny]

On Tue, 17 Jan 2017 20:08:17, Eric Blake wrote:
> [again, your email client likes to break threading, so I nearly missed
> this one]

Sorry about that, I wrote my own client so that I could reply without
subscribing:

http://github.com/svnpenn/a/blob/master/etc/mailing-list.awk

I switched the "In-Reply-To" header to "References", hopefully that will fix it.

> Are you building readline from source each step of the bisection?

Yes.

> are you applying all the downstream cygwin patches each build, or just using
> the stock upstream sources?

The latter.

> Normally, I _don't_ run anything under cmd.exe (all my use of cygwin is
> under mintty), so I need a lot of hand-holding to reproduce anything in
> your setup, in particular how you are even getting extended characters
> to print (what locales and/or window settings you have to set).

1. You must run as a login shell, i.e. "bash -l"

2. You must have in /etc/profile, .profile or similar:

LANG=en_US.UTF-8


--
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: ssh-host-config: patch fix debug option + broken for me on Vista (non-domain)

[Shaddy Baddah]

Hi,

On 18/01/17 14:34, Shaddy Baddah wrote:

First please find attached a simple patch that fixes a problem I
encountered running ssh-host-config with the --debug option.



Also, it'd be nice if an enhancement was made to protect the privacy of
silly people.

--
Regards,
Silly person



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

ssh-host-config: patch fix debug option + broken for me on Vista (non-domain)

[Shaddy Baddah]

Hi,

First please find attached a simple patch that fixes a problem I
encountered running ssh-host-config with the --debug option.

Pretty simple. Without redirecting the output of csih_stacktrace() to
stderr, then (3.5.4) Command Substitution of functions that call it will
run into problems. And the one that I encountered was this one:

cygwin-service-installation-helper.sh:1147:csih_mktemp ()
cygwin-service-installation-helper.sh:1148:{
cygwin-service-installation-helper.sh:1149:  csih_stacktrace "${@}"
cygwin-service-installation-helper.sh:1150:  $_csih_trace
cygwin-service-installation-helper.sh:1152:  local __umask=$(umask)
cygwin-service-installation-helper.sh:1153:  local rval
cygwin-service-installation-helper.sh:1154:  local tmpdir
cygwin-service-installation-helper.sh:1156: 
tmpdir=$(csih_writable_tmpdir) || return 1

cygwin-service-installation-helper.sh:1158:  umask 0077
cygwin-service-installation-helper.sh:1159:  /usr/bin/mktemp 
--tmpdir="${tmpdir}" "$@"


tmpdir will be filled with stacktrace output from the
csih_writable_tmpdir() call, and mktemp will fail.

Further, there is definitely a bug, at least for me, with running
ssh-host-config on Vista (32 bit, but that shouldn't matter) in a
non-domain environment.

The script obviously confuses the form of username construct to use at
various points. I encounter the following error:

*** Info: This script plans to use 'cyg_server'.
*** Info: 'cyg_server' will only be used by registered services.
no
*** Query: Create new privileged user account 'LIBRA-VW\cyg_server' 
(Cygwin name: 'libra-vw+cyg_server')? (yes/no) yes
*** Info: Please enter a password for new user libra-vw+cyg_server. 
Please be sure
*** Info: that this password matches the password rules given on your 
system.

*** Info: Entering no password will exit the configuration.
*** Query: Please enter the password:
*** Query: Reenter:

*** Info: User 'libra-vw+cyg_server' has been created with password 
'melum0m0'.

*** Info: If you change the password, please remember also to change the
*** Info: password for the installed services which use (or will soon use)
*** Info: the 'libra-vw+cyg_server' account.

passwd: unknown user libra-vw+cyg_server
*** Warning: Setting password expiry for user 'libra-vw+cyg_server' failed!
*** Warning: Please check that password never expires or set it to your 
needs.

No user or group 'libra-vw+cyg_server' known.
*** Warning: Assigning the appropriate privileges to user 
'libra-vw+cyg_server' failed!

*** ERROR: There was a serious problem creating a privileged user.
yes
*** Warning: Expected privileged user 'libra-vw+cyg_server' does not exist.
*** Warning: Defaulting to 'SYSTEM'

*** Info: The sshd service has been installed under the LocalSystem
*** Info: account (also known as SYSTEM). To start the service now, call
*** Info: `net start sshd' or `cygrunsrv -S sshd'.  Otherwise, it
*** Info: will start automatically after the next reboot.

*** Warning: Host configuration exited with 1 errors or warnings!
*** Warning: Make sure that all problems reported are fixed,
*** Warning: then re-run ssh-host-config.


And I'm sure the problem is that this well-intended change to the script
fails on the assumption that LOGONSERVER is always populated. It isn't
for me on Vista.

cygwin-service-installation-helper.sh:2884:  # This test succeeds on 
domain member machines only, not on DCs.
cygwin-service-installation-helper.sh:2885:  if [ 
"${COMPUTERNAME,,*}" != "${LOGONSERVER,,*}" \
cygwin-service-installation-helper.sh:2886:-a "${LOGONSERVER}" 
!= "MicrosoftAccount" ]

cygwin-service-installation-helper.sh:2887:  then
cygwin-service-installation-helper.sh:2888: # Lowercase of USERDOMAIN
cygwin-service-installation-helper.sh:2889: 
csih_PRIVILEGED_USERNAME="${COMPUTERNAME,,*}+${username}"

cygwin-service-installation-helper.sh:2890:  fi
cygwin-service-installation-helper.sh:2891:fi

I fixed this by modifying the test to check LOGONSERVER is not empty:

if [ -n "${LOGONSERVER}" -a "...

Can this be fixed in the next release?

--
Regards,
Shaddy


--- cygwin-service-installation-helper.sh.orig	2015-10-28 20:23:49.0 +1100
+++ cygwin-service-installation-helper.sh	2017-01-18 14:04:40.856126700 +1100
@@ -384,7 +384,7 @@
   fi
 n=$(($n-1))
 done
-echo -e "${_csih_STACKTRACE_STR} ${val} ${@}"
+echo -e "${_csih_STACKTRACE_STR} ${val} ${@}" 1>&2
   fi
 } # === End of csih_stacktrace() === #
 readonly -f csih_stacktrace


--
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: "Copy until full" tool

[Doug Henderson]

On 17 January 2017 at 01:57, Andrea Venturoli  wrote:
>
> Hello.
>
> I've got a 2TB backup HD which is filled with several copies (at different 
> times) of the same data; in other words, I could have the following 
> directories:
>
> Data20170117
> Data20170110
> Data20170103
> ...
> Data20161220
> User20170117
> User20170110
> User20170103
> ...
> User20161220
> DB20170117
> DB20170110
> DB20170103
> ...
> DB20161220
>
>
>
> Now I periodically need to copy this HD to another one, which is, alas, only 
> 1TB.
> So I'd like to only transfer the most recent copies, either until the disk is 
> full or by specifying a number of "copies" to keep. Of course the older ones 
> should be deleted.
>
> Think rsync (which I've been using extensibly), but with a size barrier.


This is not specifically a cygwin solution, but I am using it with my
cygwin installation as well as interesting parts of my windows
installation.

Restic is a program that does backups right.

home page: https://restic.github.io/
documentation: https://restic.readthedocs.io/en/latest/
source: https://github.com/restic/restic

Read the home page. I think it meets its design goals very well.

HTH,
Doug


-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.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: [ANNOUNCEMENT] Updated: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1

[Eric Blake]

[again, your email client likes to break threading, so I nearly missed
this one]

On 01/17/2017 06:36 PM, Steven Penny wrote:
> On Mon, 16 Jan 2017 19:32:19, Steven Penny wrote:
>> I did another bisect on the readline-7.0-testing branch and came up with 
>> this:
>> ef27d114778ffef483ed2746603f9487f880edbd is the first bad commit
>> commit ef27d114778ffef483ed2746603f9487f880edbd
>> Author: Chet Ramey 
>> Date:   Thu Jul 9 16:28:21 2015 -0400
>> readline-7.0-alpha distribution
> 

Are you building readline from source each step of the bisection? And
are you applying all the downstream cygwin patches each build, or just
using the stock upstream sources? (The cygwin patches can be found in
/usr/src if you use setup.exe to download the sources)

> This still works on Linux, even with libreadline7.

Linux doesn't have a cmd.exe.  And in mintty, I'm having no problems
entering extended characters (well, there, ALT-6-6 gives 'B' as in
ASCII, but ALT-2-3-4 gives 'ê' instead of 'Ω', while ALT-+-2-3-4 gives
'Ω', but at least input isn't silently dropped).  So I really think this
is an issue with interacting with the native windows console (which is
cygwin's domain), and not with the input being fed to readline (readline
is reading the terminal presented by cygwin, but it is cygwin that is
interpreting the console's reaction to keypresses in a way that is
converted to what cygwin apps think is a normal terminal).

Another thing I tried: running bash in mintty, this command:
 printf $'\u66\u3a9'
outputs 'fΩ' (correct, since hex 66 is 'f', while decimal 66 is 'B').
But while running bash directly from cmd.exe, the same command results
in 'f\u03A9'.  It's as if bash has determined (from locale?) that the
current character set is not Unicode, and therefore outputs an escape
sequence instead of the UTF-8 sequence.  So next I tried
LANG=en_US.UTF-8. After that, the printf produced the results I got in
mintty, but ALT-2-3-4 caused \316 to be output.

Normally, I _don't_ run anything under cmd.exe (all my use of cygwin is
under mintty), so I need a lot of hand-holding to reproduce anything in
your setup, in particular how you are even getting extended characters
to print (what locales and/or window settings you have to set).

> Chet is refusing to address
> the issue:
> 
> http://lists.gnu.org/archive/html/bug-readline/2017-01/msg1.html

I didn't even know bug-readline existed (all the readline bug reports
I've seen over the years have been addressed to bug-bash); I'm
subscribed now.  But Chet is right that it is probably a Cygwin problem,
and not a readline problem.

> 
> So it looks like we will need a Cygwin specific patch?

Well, first someone has to get to the real root cause. Since I have been
unable to reproduce it, and I don't have much free time to devote to it,
I don't know when that will be.

-- 
Eric Blake   eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org



signature.asc
Description: OpenPGP digital signature

Re: [ANNOUNCEMENT] Updated: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1

[Eric Blake]

[your email client tends to break threading, which is making it VERY
hard to follow your multiple replies]

On 01/13/2017 08:46 AM, Eric Blake wrote:
> On 01/12/2017 11:05 PM, Steven Penny wrote:
>> On Tue, 3 Jan 2017 10:34:01, "Eric Blake (cygwin)" wrote:
>>> The releases of readline 7.0.1-1 and bash 4.4.5-1, which have been
>>> experimental for a few weeks, have now been promoted to current.
>>
>> Note that new version of libreadline7 breaks interactive non ASCII input. 
>> Please
>> see:
>>
>> http://cygwin.com/ml/cygwin/2017-01/msg00066.html
>>
>> downgrading to the following versions fixes the problem:
>>
>> - libreadline7-6.3.8
>> - bash-4.3.48

So far, I'm unable to reproduce your issue.  Here's what I've tried:

In a clean windows VM, I've opened up cmd.exe, and verified that
ALT-2-3-4 generates 'Ω' (so my default locale encodings and font in that
screen do what you describe).  Likewise, ALT-6-6 generates 'B'.  From
there, I created a test directory with JUST the following files:

bash.exe from bash-4.3.48-8
cyg{history,readline7}.dll from libreadline-6.3.8-1
cyg{gcc_s-1,iconv-2,intl-8,ncursesw-10,win1}.dll from current setup.exe

and verified that it was sufficient to start up the older bash in the
same cmd.exe window (invoking .\bash).  Once that version of bash is up
and running, ALT-6-6 types 'B', but ALT-2-3-4 types nothing.

Based on your description, you said the older combination lets things
through.  Are you sure you didn't also downgrade cygwin1.dll?  At this
point, I'm inclined to think the problem is in cygwin1.dll and not
libreadline7.

-- 
Eric Blake   eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org



signature.asc
Description: OpenPGP digital signature

[ANNOUNCEMENT] mingw64-{i686,x86_64}-{headers,runtime,winpthreads}-5.0.1-1 (x86/x86_64)

[JonY]

I have just updated the mingw-w64 headers, runtime, and winpthreads to
5.0.1-1.

mingw64-*-headers-5.0.1-1
mingw64-*-runtime-5.0.1-1
mingw64-*-winpthreads-5.0.1-1

The cross compiler can produce Win32 and Win64 native binaries. As a
cross compiler, you may use --host=i686-w64-mingw32 or
--host=x86_64-w64-mingw32 for autotools based source packages to build
for Windows.

  *** 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.com  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.




signature.asc
Description: OpenPGP digital signature

Re: [PATCH cygport] Use compressed empty archives for empty packages

[Yaakov Selkowitz]

On 2016-06-26 07:26, Jon Turney wrote:

Using a compressed empty file instead of a compressed archive means these
files need to be treated specially throughout the entire package pipeline.


I suppose you have tested this with calm, so I pushed it to master.

--
Yaakov

mingw64-{i686,x86_64}-{headers,runtime,winpthreads}-5.0.1-1 (x86/x86_64)

[JonY]

I have just updated the mingw-w64 headers, runtime, and winpthreads to
5.0.1-1.

mingw64-*-headers-5.0.1-1
mingw64-*-runtime-5.0.1-1
mingw64-*-winpthreads-5.0.1-1

The cross compiler can produce Win32 and Win64 native binaries. As a
cross compiler, you may use --host=i686-w64-mingw32 or
--host=x86_64-w64-mingw32 for autotools based source packages to build
for Windows.

  *** 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.com  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.




signature.asc
Description: OpenPGP digital signature

Re: Cygwin 2.6.1 32-bit post install failed by /usr/bin/perl.exe

[Katsumi Yamaoka]

On Mon, 16 Jan 2017 18:57:51 +0100, Achim Gratz wrote:
> Katsumi Yamaoka writes:
>> Run setup-x86.exe for full install excluding *x86_64* modulues.

> You do not want a full Cygwin install.  In particular, you do not want a
> full installl for Cygwin 32bit.

Yes, I know I overdo or am greedy.  So, I tried minimal install,
that is:

Stop cygwin
cd c:\
ren cygwin cygwin.cur
Run setup-x86.exe with the default configuration, plus Emacs,
Perl, X11, and some required dependencies.

It finished with no problem and main commands work fine.  Oh!

>> However, the post install didn't seem to end.  At that time, ps
>> on mintty showed a lot of defunct perl processes.  Then I tried
>> replacing /usr/bin/perl.exe with the one I built from the source
>> one and a half years ago.

> You've run out of address space to rebase to and now perl (which comes
> pretty late in the rebase sequence) collides with something else on your
> system or maybe even the Cygwin heap.

I see.  But the current 32-bit full-install seems to work (I
haven't tested everything, though).  Does it mean only a space,
that is comparable to the one perl and possibly a few modules
occupy, exceeds the limit?  Moreover, is there no way to know
how many space exceeds the limit, before installing?  I won't do
it even if it exists if it is hard to me, though.

Anyway, it's handy that everything is close at hand. ;)

>> It did the trick!  Now new cygwin is running with no problem!

> No it doesn't and it never will given that you did a full install.
> Please do a fresh install with only the packages that you need.  If you
> select too many packages you will likely need to switch to a 3GB
> userVM address space even then.  You are much better off using a 64bit
> Cygwin if you're using a 64bit Windows version.

Ok, I will try negotiating with boss for a 64-bit machine at the
next opportunity.  This is an office pc.

Thank you very much for your help.
Regards,


--
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: [ANNOUNCEMENT] Updated: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1

[Steven Penny]

On Mon, 16 Jan 2017 19:32:19, Steven Penny wrote:
> I did another bisect on the readline-7.0-testing branch and came up with this:
> ef27d114778ffef483ed2746603f9487f880edbd is the first bad commit
> commit ef27d114778ffef483ed2746603f9487f880edbd
> Author: Chet Ramey 
> Date:   Thu Jul 9 16:28:21 2015 -0400
> readline-7.0-alpha distribution

On Linux readline is 2 packages:

libreadline7 = 7.0
libreadline6 = 6.3

Using:

- Debian 8.7.1
- http://packages.debian.org/stretch/libreadline7

For the test in question, GREEK CAPITAL LETTER OMEGA U+03A9, you do:

Ctrl + Shift + U, release, 3a9, Enter

This still works on Linux, even with libreadline7. Chet is refusing to address
the issue:

http://lists.gnu.org/archive/html/bug-readline/2017-01/msg1.html

So it looks like we will need a Cygwin specific 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: sincerely beg your help!!! for getting version 2.6.0-1

[sun zheng]

hi Repin/team

thanks for your reply!


i also tried to install at c:/cygwin64
and the cygwin version is also 2.6.1-1

it is not due to my install method. i just mean that i am using the latest 
setupexe, so the version is 2.6.1-1.
and what i need is how to install 2.6.0-1 currently? 
or can you send me some dll to replace so that i can get "2.6.0-1" using 
"cygcheck -c cygwin"?

please help me!!!


发自我的 iPhone

> 在 2017年1月18日，01:25，Andrey Repin  写道：
> 
> Greetings, sun zheng!
> 
>> installed cygwin using setup_64.exe from your website in my personal
>> pc, and provide the folder c:\program files\cygwin64
> 
> Root directory with space or other ambiguous character may cause
> interoperability issues.
> 
>> to our security
>> team for scanning and confirming. they will re-package using this
>> folder.
> 
> Repackaging an installed Cygwin release may also cause issues.
> Please refer to http://cygwin.com/faq/#faq.using.fixing-fork-failures f.e.
> 
> 
> -- 
> With best regards,
> Andrey Repin
> Tuesday, January 17, 2017 20:19:42
> 
> Sorry for my terrible english...
> 

--
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: cygcheck (64&32) output contains DOS line terminators

[cyg Simple]

On 1/17/2017 4:44 PM, Nellis, Kenneth (Conduent) wrote:
> From: Brian Inglis 
>> On 2017-01-17 13:21, Marco Atzeri wrote:
>>> On 17/01/2017 21:00, Brian Inglis wrote:
 All cygcheck output seems to have DOS line terminators in both
 Cygwin 64 & 32.
 Is this by design or just because it's a native Windows app?
>>> second one
>>
>> So by accident rather than intent?
>> Could that be easily changed to be more Cygwin-like?
>> Or would it involve more difficult changes to a lower level API?
>>
 It's annoying in command lines and scripts to have to strip the \r.
> 
> I agree. Despite the fact that it's a "Windows app", the fact remains
> that it is installed in /usr/bin, so its clear intent is to be run
> from the Cygwin command line.  --Ken Nellis
> 

Anyone willing to write a patch to set the output to binary mode instead
of text mode?

-- 
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: [PATCH] src_postinst.cygpart: Sanitize binary data in bash command subst

[Yaakov Selkowitz]

On 2016-12-16 15:09, Eric Blake wrote:

On 12/16/2016 02:40 PM, Eric Blake wrote:

bash 4.4 now warns about skipping NUL bytes in $(command), since
command substitution is only well-formed for commands that output
text, but NUL bytes are not text.  Silence the warning by removing
NUL bytes from the stream before bash can see them.


And of course, reading this in isolation, we could shave a process or
two by merging the two case statements into one, if you want to go one
step further as a micro-optimization:


Squashed and pushed.  Thanks,

--
Yaakov

RE: cygcheck (64&32) output contains DOS line terminators

[Nellis, Kenneth (Conduent)]

From: Brian Inglis 
> On 2017-01-17 13:21, Marco Atzeri wrote:
> > On 17/01/2017 21:00, Brian Inglis wrote:
> >> All cygcheck output seems to have DOS line terminators in both
> >> Cygwin 64 & 32.
> >> Is this by design or just because it's a native Windows app?
> > second one
> 
> So by accident rather than intent?
> Could that be easily changed to be more Cygwin-like?
> Or would it involve more difficult changes to a lower level API?
> 
> >> It's annoying in command lines and scripts to have to strip the \r.

I agree. Despite the fact that it's a "Windows app", the fact remains
that it is installed in /usr/bin, so its clear intent is to be run
from the Cygwin command line.  --Ken Nellis

Re: cygcheck (64&32) output contains DOS line terminators

[Brian Inglis]

On 2017-01-17 13:21, Marco Atzeri wrote:
> On 17/01/2017 21:00, Brian Inglis wrote:
>> All cygcheck output seems to have DOS line terminators in both
>> Cygwin 64 & 32.
>> Is this by design or just because it's a native Windows app?
> second one

So by accident rather than intent?
Could that be easily changed to be more Cygwin-like?
Or would it involve more difficult changes to a lower level API?

>> It's annoying in command lines and scripts to have to strip the \r.

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

Re: cygcheck (64&32) output contains DOS line terminators

[Marco Atzeri]

On 17/01/2017 21:00, Brian Inglis wrote:

All cygcheck output seems to have DOS line terminators in both Cygwin 64 & 32.
Is this by design or just because it's a native Windows app?


second one

Regards
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

cygcheck (64&32) output contains DOS line terminators

[Brian Inglis]

All cygcheck output seems to have DOS line terminators in both Cygwin 64 & 32.
Is this by design or just because it's a native Windows app?
It's annoying in command lines and scripts to have to strip the \r.

$ cygcheck -f /bin/find | cat -A
findutils-4.6.0-1^M$

$ cygcheck -p findutils > t; cat -A t
Found 7 matches for findutils^M$
busybox-debuginfo-1.23.2-1 - busybox-debuginfo: Debug info for busybox 
(installed binaries and support files)^M$
findutils-debuginfo-4.5.12-1 - findutils-debuginfo: Debug info for findutils 
(installed binaries and support files)^M$
findutils-debuginfo-4.6.0-1 - findutils-debuginfo: Debug info for findutils 
(installed binaries and support files)^M$
findutils-4.5.12-1 - findutils: Utilities for finding files--find, xargs, 
locate, updatedb (installed binaries and support files)^M$
findutils-4.5.12-1-src - findutils: Utilities for finding files--find, xargs, 
locate, updatedb (source code)^M$
findutils-4.6.0-1 - findutils: Utilities for finding files--find, xargs, 
locate, updatedb (installed binaries and support files)^M$
findutils-4.6.0-1-src - findutils: Utilities for finding files--find, xargs, 
locate, updatedb (source code)^M$

$ cygcheck --version
cygcheck (cygwin) 2.6.1
System Checker for Cygwin
Copyright (C) 1998 - 2016 Cygwin Authors
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ uname -srvmo
CYGWIN_NT-10.0 2.6.1(0.305/5/3) 2016-12-16 11:55 x86_64 Cygwin

$ uname -srvmo
CYGWIN_NT-10.0-WOW 2.6.1(0.305/5/3) 2016-12-16 11:50 i686 Cygwin

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

RE: separating cygcheck -f package name from version

[Nellis, Kenneth (Conduent)]

From: Brian Inglis
> 
> $ fgrep "$(cygcheck -f /usr/bin/find | sed 's/\r$//').tar." \
>   /etc/setup/installed.db | cut -d' ' -f1
> findutils
> 
> OR
> 
> $ fgrep "$(cygcheck -f /usr/bin/find | d2u).tar." \
>   /etc/setup/installed.db | cut -d' ' -f1
> findutils
> 
> cygcheck -f outputs DOS lines with \r which need stripped as
> shown, using sed (Base), d2u, or your choice of available tool.

Excellent! Thank you! --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: separating cygcheck -f package name from version

[Brian Inglis]

On 2017-01-17 12:01, Nellis, Kenneth (Conduent) wrote:
> I want to be able to extract a package's name from its version
> information output by cygcheck -f. For many packages it is 
> easy: just strip off after the first hyphen; for example:
> 
> $ cygcheck -f /usr/bin/find
> findutils-4.6.0-1
> $ cygcheck -f /usr/bin/find | cut -d- -f1
> findutils
> $
> 
> But, then there are cases where both the package name and the
> version have multiple hyphens:
> 
> $ cygcheck -f /usr/share/man/man3p/wcstoimax.3p
> man-pages-posix-2013-a-1
> $ cygcheck -c man-pages-posix
> Cygwin Package Information
> Package  VersionStatus
> man-pages-posix  2013-a-1   OK
> $
> 
> So, looking for ideas how best to do this.

$ fgrep "$(cygcheck -f /usr/bin/find | sed 's/\r$//').tar." \
/etc/setup/installed.db | cut -d' ' -f1
findutils

OR 

$ fgrep "$(cygcheck -f /usr/bin/find | d2u).tar." \
/etc/setup/installed.db | cut -d' ' -f1
findutils

cygcheck -f outputs DOS lines with \r which need stripped as 
shown, using sed (Base), d2u, or your choice of available tool.

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

Re: sincerely beg your help!!! for getting version 2.6.0-1

[Brian Inglis]

On 2017-01-17 10:25, Andrey Repin wrote:
>> installed cygwin using setup_64.exe from your website in my personal
>> pc, and provide the folder c:\program files\cygwin64
> Root directory with space or other ambiguous character may cause
> interoperability issues.
>> to our security
>> team for scanning and confirming. they will re-package using this
>> folder.
> Repackaging an installed Cygwin release may also cause issues.
> Please refer to http://cygwin.com/faq/#faq.using.fixing-fork-failures f.e.

It's the org's problem if they want to spend a lot of time and money 
packaging a frequently updated non-Windows install process, which is a 
Unix-distro-like rolling upgrade. 
If they are taking on the role of a distro they should really be 
packaging each package install, with its dependencies, separately, 
like any other downstream, and doing their own setup.

If they were smarter, they'd just package Setup with a fixed mirror, 
or maintain their own local mirror, and package updating from that 
mirror using Setup, maybe even become and offer a public Cygwin mirror?

It's the requesters' and packagers' problems to read and understand 
the Setup process, FAQ, and postinstall scripts - probably why it 
takes 2 months - getting some random Windows package scripter to 
understand a Unix-like net install of packages and dependencies 
- and stuff that into an msi that works reliably under SCCM.

Get them to start packaging the current release and upgrades right away, 
otherwise something else may have changed by the time they start!

And they should always be packaging installs using the defaults, like 
C:\Cygwin64 not %ProgramFiles%, if they want to avoid problems with 
users running programs and scripts.

Quite a few Windows packages still want their own directory under root, 
as they prioritize their own stable approach over MS Windows approaches.
Easier for the little guys with simple products, and the big guys making 
lots of millions mainly on Windows, but lots of others go their own way.
Following "standards" is all very well, but what product manager is going 
to be able to get signoff on spending a year and $1M or more to change 
a complex working product and install process to the MS approach?
Product users don't care as long as the result works on their desktops, 
and they won't notice or pay more for a Windows logo - that only "benefits" 
the marketing department, so they should be footing the bill for making 
and testing the product conforms.

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

separating cygcheck -f package name from version

[Nellis, Kenneth (Conduent)]

I want to be able to extract a package's name from its version
information output by cygcheck -f. For many packages it is 
easy: just strip off after the first hyphen; for example:

$ cygcheck -f /usr/bin/find
findutils-4.6.0-1
$ cygcheck -f /usr/bin/find | cut -d- -f1
findutils
$

But, then there are cases where both the package name and the
version have multiple hyphens:

$ cygcheck -f /usr/share/man/man3p/wcstoimax.3p
man-pages-posix-2013-a-1
$ cygcheck -c man-pages-posix
Cygwin Package Information
Package  VersionStatus
man-pages-posix  2013-a-1   OK
$

So, looking for ideas how best to do this.

--Ken Nellis

--
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: sincerely beg your help!!! for getting version 2.6.0-1

[Achim Gratz]

sun zheng writes:
> i was requesting to install cygwin 2.6.0-1 in my company's pc since
> this is the latest version. due to security checking, it takes nearly
> 2 months for me to get the approval of this version.

If that's a requirement, you will need to provide a local mirror with
the exact state of packages that your security check is goint to vet.

> fortunately, it finally goes to packaging process. while this step, i
> installed cygwin using setup_64.exe from your website in my personal
> pc, and provide the folder c:\program files\cygwin64 to our security
> team for scanning and confirming. they will re-package using this
> folder.

You don't want to install into %PROGRAM_FILES% or WIndows' folder
virtualization will play bad tricks on you if you ever try to write to
anywhere inside that installation directory.  You also don't want to
package up an installation to install on further machines, instead
you'll need to do an installation on each machine.

> all is done. but when it goes to version-confirming process. i am crazy!!!
> i use "cygcheck -c cygwin" to check version, but it shows "2.6.1-1"
>
> then i went back to your website main page. it shows 2.6.1-1 as the
> latest version. i really really want to cry

Well, at the moment you can still select the previous version from setup
and have a reasonable chance of everything working correctly.  But
Cygwin really is a rolling distribution, so your security process is
fundamentally at odds with how it is updated.


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: sincerely beg your help!!! for getting version 2.6.0-1

[Andrey Repin]

Greetings, sun zheng!

> installed cygwin using setup_64.exe from your website in my personal
> pc, and provide the folder c:\program files\cygwin64

Root directory with space or other ambiguous character may cause
interoperability issues.

> to our security
> team for scanning and confirming. they will re-package using this
> folder.

Repackaging an installed Cygwin release may also cause issues.
Please refer to http://cygwin.com/faq/#faq.using.fixing-fork-failures f.e.


-- 
With best regards,
Andrey Repin
Tuesday, January 17, 2017 20:19:42

Sorry for my terrible english...


--
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: irssi-1.0.0-1

[Marco Atzeri]

New version `1.0.0-1
  irssi
  irssi-devel
have been uploaded.

CHANGES
This is a new upstream release focused on bug fix.
 https://irssi.org/2017/01/05/irssi-1.0.0-released/

full list of changes
 https://github.com/irssi/irssi/releases

DESCRIPTION
Irssi is a terminal based IRC client for UNIX systems.
It also supports SILC and ICB protocols via plugins.


HOMEPAGE
 http://www.irssi.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

Re: sincerely beg your help!!! for getting version 2.6.0-1

[Marco Atzeri]

On 17/01/2017 15:09, Nellis, Kenneth (Conduent) wrote:

From: Marco Atzeri

On 17/01/2017 13:42, sun zheng wrote:

hi team,




As cygwin is a rolling distribution you can consider

http://www.fruitbat.org/Cygwin/timemachine.html#AHEM

for an installation frozen in time.

Regards
Marco


Maybe I'm missing something because I'm confused why Marco is suggesting
timemachine when setup.exe still offers version 2.6.0-1. Just click on
the package in the New column until it shows your version, then proceed
with the installation.

--Ken Nellis



Hi Ken,
two reasons:

- he could need to install again sometime in the future,
and than going back will not work.

- some packages could use new features added by 2.6.1
  and it will be a mess to understand which packages must be
  downgraded.

Regards
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: sincerely beg your help!!! for getting version 2.6.0-1

[Nellis, Kenneth (Conduent)]

From: Marco Atzeri [mailto:marco.atz...@gmail.com]
> On 17/01/2017 13:42, sun zheng wrote:
> > hi team,
> >
> > sorry for troubling. but
> >
> > currently i am facing a big problem:
> > i was requesting to install cygwin 2.6.0-1 in my company's pc since
> > this is the latest version. due to security checking, it takes nearly
> > 2 months for me to get the approval of this version.
> > fortunately, it finally goes to packaging process. while this step, i
> > installed cygwin using setup_64.exe from your website in my personal
> > pc, and provide the folder c:\program files\cygwin64 to our security
> > team for scanning and confirming. they will re-package using this
> > folder.
> >
> > all is done. but when it goes to version-confirming process. i am
> crazy!!!
> > i use "cygcheck -c cygwin" to check version, but it shows "2.6.1-1"
> >
> > then i went back to your website main page. it shows 2.6.1-1 as the
> > latest version. i really really want to cry
> >
> >
> > i do not want to take another 2 months for requesting the new 2.6.1-1
> > version approval!!!
> 
> we will have a (or more) new version in two months
> 
> 
> > !
> > PLEASE HELP ME!!!
> >
> > 1. how can i install 2.6.0-1?? can you send me the setup_64.exe for
> > this version??
> > 2. if cannot install 2.6.0-1 vir setup_64.exe. can you send me the dll
> > files to replace in folder "c:\program files\cygwin64", so that i can
> > get "2.6.0-1" using "cygcheck -c cygwin" ???
> >
> > !
> >
> > this really matters!! i beg your help!!!
> > waiting for your response eagerly...
> >
> 
> As cygwin is a rolling distribution you can consider
> 
> http://www.fruitbat.org/Cygwin/timemachine.html#AHEM
> 
> for an installation frozen in time.
> 
> Regards
> Marco

Maybe I'm missing something because I'm confused why Marco is suggesting 
timemachine when setup.exe still offers version 2.6.0-1. Just click on 
the package in the New column until it shows your version, then proceed 
with the installation.

--Ken Nellis

Re: sincerely beg your help!!! for getting version 2.6.0-1

[Marco Atzeri]

On 17/01/2017 13:42, sun zheng wrote:

hi team,

sorry for troubling. but

currently i am facing a big problem:
i was requesting to install cygwin 2.6.0-1 in my company's pc since
this is the latest version. due to security checking, it takes nearly
2 months for me to get the approval of this version.
fortunately, it finally goes to packaging process. while this step, i
installed cygwin using setup_64.exe from your website in my personal
pc, and provide the folder c:\program files\cygwin64 to our security
team for scanning and confirming. they will re-package using this
folder.

all is done. but when it goes to version-confirming process. i am crazy!!!
i use "cygcheck -c cygwin" to check version, but it shows "2.6.1-1"

then i went back to your website main page. it shows 2.6.1-1 as the
latest version. i really really want to cry


i do not want to take another 2 months for requesting the new 2.6.1-1
version approval!!!


we will have a (or more) new version in two months



!
PLEASE HELP ME!!!

1. how can i install 2.6.0-1?? can you send me the setup_64.exe for
this version??
2. if cannot install 2.6.0-1 vir setup_64.exe. can you send me the dll
files to replace in folder "c:\program files\cygwin64", so that i can
get "2.6.0-1" using "cygcheck -c cygwin" ???

!

this really matters!! i beg your help!!!
waiting for your response eagerly...



As cygwin is a rolling distribution you can consider

http://www.fruitbat.org/Cygwin/timemachine.html#AHEM

for an installation frozen in time.

Regards
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

sincerely beg your help!!! for getting version 2.6.0-1

[sun zheng]

hi team,

sorry for troubling. but

currently i am facing a big problem:
i was requesting to install cygwin 2.6.0-1 in my company's pc since
this is the latest version. due to security checking, it takes nearly
2 months for me to get the approval of this version.
fortunately, it finally goes to packaging process. while this step, i
installed cygwin using setup_64.exe from your website in my personal
pc, and provide the folder c:\program files\cygwin64 to our security
team for scanning and confirming. they will re-package using this
folder.

all is done. but when it goes to version-confirming process. i am crazy!!!
i use "cygcheck -c cygwin" to check version, but it shows "2.6.1-1"

then i went back to your website main page. it shows 2.6.1-1 as the
latest version. i really really want to cry


i do not want to take another 2 months for requesting the new 2.6.1-1
version approval!!!

!
PLEASE HELP ME!!!

1. how can i install 2.6.0-1?? can you send me the setup_64.exe for
this version??
2. if cannot install 2.6.0-1 vir setup_64.exe. can you send me the dll
files to replace in folder "c:\program files\cygwin64", so that i can
get "2.6.0-1" using "cygcheck -c cygwin" ???

!

this really matters!! i beg your help!!!
waiting for your response eagerly...




Regards,
Jerry

--
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: gawk-4.1.4-2

[Corinna Vinschen]

I've updated the gawk package to 4.1.4-2.

This is a bugfix release.  It adds all post-release patches from the
gawk 4.1.4 stable branch.  This should especially fix
https://cygwin.com/ml/cygwin/2017-01/msg00115.html


Have fun,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Developercygwin AT cygwin DOT com
Red Hat, Inc.

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

Updated: gawk-4.1.4-2

[Corinna Vinschen]

I've updated the gawk package to 4.1.4-2.

This is a bugfix release.  It adds all post-release patches from the
gawk 4.1.4 stable branch.  This should especially fix
https://cygwin.com/ml/cygwin/2017-01/msg00115.html


Have fun,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Developercygwin AT cygwin DOT com
Red Hat, Inc.

Re: Windows 10 Insider Preview OS Build 15007.1000: Couldn't compute FAST_CWD pointer

[Corinna Vinschen]

On Jan 17 03:12, Jim Reisert AD1C wrote:
> I just upgraded my Windows 10 Home 64-bit installation to the latest
> Windows Insider preview version:
> 
> Version: 1607
> OS Build:  15007.1000
> 
> I'm now getting this warning from Cygwin, but only in a CMD window
> (not XWin).  It doesn't seem to affect anything negatively.
> cygcheck.out attached (I got the FAST_CWD warning three times during
> the generation of the file):
> 
> C:\Users\jjrei>uname -a
> 
> Cygwin WARNING:
>   Couldn't compute FAST_CWD pointer.  This typically occurs if you're using
>   an older Cygwin version on a newer Windows.  Please update to the latest
>   available Cygwin version from https://cygwin.com/.  If the problem persists,
>   please see https://cygwin.com/problems.html

Try the latest developer snapshot from https://cygwin.com/snapshots/


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat


signature.asc
Description: PGP signature

"Copy until full" tool

[Andrea Venturoli]

Hello.

I've got a 2TB backup HD which is filled with several copies (at 
different times) of the same data; in other words, I could have the 
following directories:


Data20170117
Data20170110
Data20170103
...
Data20161220
User20170117
User20170110
User20170103
...
User20161220
DB20170117
DB20170110
DB20170103
...
DB20161220



Now I periodically need to copy this HD to another one, which is, alas, 
only 1TB.
So I'd like to only transfer the most recent copies, either until the 
disk is full or by specifying a number of "copies" to keep. Of course 
the older ones should be deleted.


Think rsync (which I've been using extensibly), but with a size barrier.



I could try and write my custom script, but I'd hate to reinvent the wheel.
Does such a tool already exist in Cygwin?
Failing that, somewhere else?

Bonus for retrieving the original data via FTP, but that's not required.

 bye & Thanks
av.

--
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: [ANNOUNCEMENT] Updated: shutdown 2.0-1

[Frank Fesevur]

2017-01-16 18:52 GMT+01:00 Achim Gratz:
> There is a build or packaging error somewhere with the 64bit version:
> the shutdown.exe delivered with the x86_64 package is in fact a 32bit
> executable that refuses to work in 64bit Cygwin.  Can you please correct
> and re-release the package?

Thanks for spotting.

There was a problem in the Makefile. I will re-release the package ASAP.

Regards,
Frank

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