Re: File permissions different inside and outside cygwin root
(Sorry I cannot reply directly to the previous email I just subscribed to the list, I am quoting from the list archive) (from the archive - permissions inside and outside of /cygwin get messed up) I think this is *THE* cause of my problems. My question is how do I turn this of 100% totally - and completely? How it is effecting me: In my case, I *OFTEN* edit source code using ‘emacs-w32’ under cygwin. and often refer to files via a filename like this /cygdrive/c/some/path/foo.c Sadly what happens in the end is, the ACL gets set to the point where I cannot edit source files. Another common example is this: Step 1: On Linux - create a “tar.gz” of a source directory. tar cfz foo.tar.gz somedirectory (In my case, it is an open source package that *must* build under both cygwin and linux) I need to move the code back and forth - to make sure my changes don’t break things Step 2: Pull that tar file over to Cygwin (I use cygwin64) Step 3: Unpack the tar.gz file using CYGWIN tar xfz foo.bar.tz Step 4: I specifically use “emacs-w32” - to edit the source code. It seems that *randomly* the ACL gets totally bunkered Maybe there is a method to this madness, but I can’t figure out the exact sequence I am *NOT* building or doing this under any Cygwin mount I should not need to, and I should not be required to I specifically use: /cygdrive/c/some/path/ **NOTE** This does not *require* the ‘tar-copy’ method Using CYGWIN - I “git clone” some repository and edit the files in the standard way It seems to be more predominant when I copy via TAR across systems. Result: I can no longer edit my source code. I would end up having to “right click” permissions and fix things using windows tools It seems the ACLs are totally messed up Bottom line, my expected behavior I should be able to use a simple editor - i.e.: Emacs-w32 I should be able to edit a source code file When I save the source code file - the permissions *before* and *after* should be identical They are not, permissions are totally messed up. What ever I am seeing, it is fundamentally broken. -Duane. -- 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
tmux 2.x performance regression when switching windows
Hello,
I noticed moving between tmux windows became much slower since 2.0.x when
running some applications in the windows. The problems disappear if I move back
to 1.9. To reproduce:
- Cygwin: CYGWIN_NT-6.1-WOW PMD 2.0.2(0.287/5/3) 2015-05-08 17:03 i686 Cygwin,
Win7 64 bits.
- Start tmux and create two windows.
- In one of the windows, execute the following Go program (natively compiled,
Go 1.4.2 64-bits):
package main
import (
fmt
time
)
func main() {
for i := 0; ; i++ {
fmt.Println(i)
time.Sleep(500*time.Millisecond)
}
}
- Try switching between windows
KO = it eventually succeeds but lags a lot. With 1.9, the switch is immediate.
--
Patrick Mézard
--
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
Help on patching xdvipdfmx in texlive
Hi, I can't use CID-keyed fonts (SourceHanSans) with xelatex but find a solution. (http://tug.org/pipermail/xetex/2014-July/025387.html) The solution need to patch xdvipdfmx and the patch could be found in ``` https://gist.github.com/jjgod/c1194a9b371848aaa746 ``` There is not patched xdvipdfmx binary file for cygwin. How can I get source and apply patches? Or could Ken help to patch it? 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
cygport upload: patch for openssh 6.8p1
Since the latest update to openssh, ssh-keygen's output format for key
fingerprints has changed. The default hash algorithm is now base64-encoded
SHA256 instead of MD5, and the hash name precedes its value, like
SHA256:lvRrjAXmEhzDp5kQqzelsei8s5hXJ+zLaqJ2yiGXmYc
This breaks the current logic for detecting key fingerprints in cygport's
lib/pkg_upload.cygpart. The attached patch fixes the problem. (You might know
a more precise regex for the base64-encoded hash value than I do. I couldn't
find any documentation of it anywhere, and just settled for
SHA256:.{44}
)
Andrew
pkg_upload_key_fingerprint.patch
Description: Binary data
Re: Help on patching xdvipdfmx in texlive
That's okay. I would wait. Thanks! On Mon, May 25, 2015 at 12:38 AM, Ken Brown kbr...@cornell.edu wrote: On 5/24/2015 12:30 PM, Arthur Tu wrote: Hi, I can't use CID-keyed fonts (SourceHanSans) with xelatex but find a solution. (http://tug.org/pipermail/xetex/2014-July/025387.html) The solution need to patch xdvipdfmx and the patch could be found in ``` https://gist.github.com/jjgod/c1194a9b371848aaa746 ``` There is not patched xdvipdfmx binary file for cygwin. How can I get source and apply patches? Or could Ken help to patch it? How urgent is this? I'll be releasing TeX Live 2015 in about a month. It will include a lot of bug fixes for xdvipdfmx. 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 -- 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: Help on patching xdvipdfmx in texlive
On 5/24/2015 12:30 PM, Arthur Tu wrote: Hi, I can't use CID-keyed fonts (SourceHanSans) with xelatex but find a solution. (http://tug.org/pipermail/xetex/2014-July/025387.html) The solution need to patch xdvipdfmx and the patch could be found in ``` https://gist.github.com/jjgod/c1194a9b371848aaa746 ``` There is not patched xdvipdfmx binary file for cygwin. How can I get source and apply patches? Or could Ken help to patch it? How urgent is this? I'll be releasing TeX Live 2015 in about a month. It will include a lot of bug fixes for xdvipdfmx. 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: BUILD_ISO.bat
On 5/24/2015 12:01 AM, Justin Scott wrote: Couldn't compute FAST_CWD pointer. Dear Justin, your is probably the shortest version I ever see of the same problem report. The most ineffective I should also say. So I will repeat the usual disclaimer: The package you are using (what ever it is, I have no clue) is likely using a cygwin utility called rsync. It seems whoever provide it is bundling and old version of the cygwin kernel. Our answer is always : update to the last version, this problem was solved around one year ago... Solution for you : contact who distribute it and report the problem, we can do nothing for you. Additional suggestion: before writing on a mailing list it is worth to look for previous message with the same problem. http://lmgtfy.com/?q=FAST_CWD 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
[ANNOUNCEMENT] Updated: dos2unix 7.2.2-1
CHANGES SINCE LAST RELEASE: === New upstream release. * Fix: Fixed symlink support on FreeBSD. * Fix: Skip GB18030 test on FreeBSD. * Fix: When conversion of an UTF-16 file with binary symbols was forced, null characters were not written in the output. * Fix: Check UTF-16 input for invalid surrogate pairs. homepage: http://waterlan.home.xs4all.nl/dos2unix.html license: 2-clause BSD (FreeBSD) -- Erwin Waterlander http://waterlan.home.xs4all.nl/ -- 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: Perl distributions
Achim Gratz writes: I just realized that the 64bit distribution has a perl-Term-ReadKey package that should have been obsoleted by perl-TermReadkey (sans the hyphen). Can somebody please move the directory perl-Term-ReadKey into perl-TermReadkey so I can create and install the obsoletion package? Ping? Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
perl-5.22.0-RC2 / Perl distributions
I've built perl-5.22.0-RC2 and bootstrapped the Perl distributions for
Cygwin (well, most of them -- I will send another ITA for some
additional ones I've hat to build later). It doesn't make much sense to
try a test release on sourceware, so I've uploaded to my own server,
which you can use (in addition to) the normal package archive(s):
setup-{x86,x86_64}.exe -XOs http://cygwin.stromeko.net/
Let me know if anything is missing.
The release of Perl 5.22.0 is still scheduled for June 1st. Now that
I've bootstrapped another set of packages should be ready in about a day
or two I think, so a Cygwin release beginning of June might be in the
cards. Switching to the new Perl version will require that _all_ other
Perl distributions be re-packaged, so anything I didn't build will have
to be ready at the same time. Please build and test your Perl
distribution packages with RC2 so that the final build will go smooth.
If you've rather had me build your packages instead (aside from the ones
mentioned above), let me know.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: perl-5.22.0-RC2 / Perl distributions
On 5/24/2015 4:02 PM, Achim Gratz wrote:
I've built perl-5.22.0-RC2 and bootstrapped the Perl distributions for
Cygwin (well, most of them -- I will send another ITA for some
additional ones I've hat to build later). It doesn't make much sense to
try a test release on sourceware, so I've uploaded to my own server,
which you can use (in addition to) the normal package archive(s):
setup-{x86,x86_64}.exe -XOs http://cygwin.stromeko.net/
Let me know if anything is missing.
The latest version of Biber requires autovivification, XML::Writer, and
Text::Roman. And Test::Difference is required for running the tests. Can you
add those?
Here's a trickier one: Biber wants Unicode::Normalize, version = 1.17. There's
a comment that says 1.18 removes XS and is too slow. I'm not sure what to do
about that. Any advice?
Thanks.
Ken
