libxxhash-devel 0.8.0 has a broken .pc pkg-config file
Hi, borgbackup developer here. Just wanted to note that you still have the broken 0.8.0 in cygwin and it would be nice to have that updated to >= 0.8.1 (which has the missing version number in the .pc file already fixed). I noticed it because it does not get auto-discovered by the borg build process due to that. Cheers, Thomas -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: rebase-4.4.3-1 regression: Too many DLLs for available address space
On 01/11/2018 01:32 PM, Christian Franke wrote: > After 4.4.3-1 upgrade, rebase always fails on 32- and 64-bit Cygwin: > > $ rebase -s -T /var/cache/rebase/rebase_all > rebase: Too many DLLs for available address space: Cannot allocate memory Confirmed, I suddenly had the same issue. > A downgrade to 4.4.2-1 fixes the problem. Also confirmed, thanks for the hint - 4.4.2 works fine. -- GPG ID: 9F88FB52FAF7B393 GPG FP: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393 -- 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: borgbackup test fail on cygwin (only) - cygwin pipe issues?
On 01/13/2017 07:18 PM, Thomas Waldmann wrote: > It was a bug in our code that was triggered frequently by the small > cygwin pipe buffer size of only 64kiB. > > borgbackup fix/workaround see there: > > https://github.com/borgbackup/borg/pull/2032 > > It (almost?) never happened on other OSes, due to their bigger buffers. Hmm, the last phrase seems not to be the real reason why it worked there, but rather that neither Linux nor *BSD ever do partial writes on blocking pipes. So, should cygwin also behave that ^^^ way on blocking pipes? -- 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: borgbackup test fail on cygwin (only) - cygwin pipe issues?
It was a bug in our code that was triggered frequently by the small cygwin pipe buffer size of only 64kiB. borgbackup fix/workaround see there: https://github.com/borgbackup/borg/pull/2032 It (almost?) never happened on other OSes, due to their bigger buffers. Note: It would be nice to have bigger pipe buffers on cygwin, for performance reasons. -- 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: borgbackup test fail on cygwin (only) - cygwin pipe issues?
>> https://github.com/borgbackup/borg/issues/1268 > > Are your pipe handles in open in binary mode or text mode? You should > always ensure they are in binary mode. That was my first idea also. https://github.com/borgbackup/borg/blob/1.0.9/borg/remote.py#L188 this is the place where the ssh subprocess is forked and the pipes are set up. There is nothing special about binary mode there, but as mentioned in that ticket, I just tried it out to send binary data over such pipes and it worked: https://github.com/borgbackup/borg/issues/1268#issuecomment-239923192 (that \n should get modified to \r\n if in text mode, but it got through "as is") -- GPG ID: 9F88FB52FAF7B393 GPG FP: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393 -- 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
borgbackup test fail on cygwin (only) - cygwin pipe issues?
Hi, borgbackup uses a RPC protocol via a ssh pipe to implement client/server communication. borg client --pipe-- ssh --tcp-- sshd --pipe-- borg serve This works very reliable, we have tests running on linux, freebsd, netbsd, openbsd, OS X. It even works on win10 linux subsystem. But on Cygwin, only the local tests work, but the remote tests (which need the pictured ssh pipe) fail or hang. When trying to find out what's going wrong, I noticed corrupted data coming over the pipe. I've found some other pipe issues on the cygwin mailing list, maybe this is related? Our issue about this: https://github.com/borgbackup/borg/issues/1268 Note: I am one of the borgbackup developers, but I am not a windows developer (and I personally don't use windows or cygwin except for testing borgbackup on this platform). What I could offer is to run the tests on a fixed version. Thanks for looking into this, 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
