On Sun, Sep 1, 2013 at 10:30 PM, Robert Pendell wrote:
> Which mirror did you try? Did you try another mirror? I just checked
> my private mirror and it shows fine.
I primarily use ftp.heanet.ie, but I tried mirrors.kernel.org and a
couple random mirrors, all of them show the same problem. For e
On Sun, Sep 1, 2013 at 5:38 PM, nu774 wrote:
> Same experience here.
> I once pushed "continue" on the "incomplete download" error dialog by
> mistake, that resulted in uninstalling of the selected packages for updates,
> including cygwin (except for cygwin1.dll).
Did the same thing, in my case e
On Mon, Sep 28, 2009 at 11:42 PM, Kevin Holleran wrote:
> I am building a new laptop and was wondering if there was a way I
> could copy some ini or setup file from cygwin to the new one so that
> the cygwin installer would install the same packages as opposed to
> having to go through and tweak t
On Mon, Aug 10, 2009 at 8:40 PM, Corinna
Vinschen wrote:
> That's a bug in perl. There are other OSes out there which have
> root-like permissions for non-0 uids. Perl should use the access()
> function to check for read/write/execute permissions, which always
> returns the correct result indepen
On Mon, Aug 10, 2009 at 8:11 PM, Alexey Borzenkov wrote:
> Anyway, it means there is a bug in perl, because on Linux:
On second though, it is actually bug in Cygwin. Programs and libraries
expect superuser behavior only when user id is zero, which is clearly
not the case in Cygwin 1.7. I th
On Mon, Aug 10, 2009 at 5:25 PM, Corinna
Vinschen wrote:
> That's a bug in your testsuite. I assume you're running the tests as
> administrator, right? Administrators have the right to write to all
> files, even R/O files, according to POSIX rules. Your test would fail
> on Linux as well, if you
Hi,
$ echo foo >test.txt
$ chmod 0444 test.txt
$ echo bar >test.txt
This succeeds, even though the file is readonly, and permissions don't
allow writing to the file. What's even stranger is that other programs
(i.e. Notepad and other editors) can't write to this file, because
there are no writing
On Tue, Aug 4, 2009 at 1:30 PM, Alexey Borzenkov wrote:
> I just noticed that for several cygwin1.dll versions git svn is not
> working. Here's the repo I can reproduce it with and cygcheck -s -r:
Ok, I did a fresh minimal install on a clean Windows XP at home and
the bug doesn't
On Thu, Aug 6, 2009 at 10:04 AM, Reini Urban wrote:
> peflagsall maybe?
Does it even apply on Windows XP? I thought ASLR is a Vista feature.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
U
I just noticed that for several cygwin1.dll versions git svn is not
working. Here's the repo I can reproduce it with and cygcheck -s -r:
http://kitsu.ru/cygwin17-psyco2-git.tar.bz2
http://kitsu.ru/cygwin17-psyco2-cygcheck.log.gz
aborzen...@ng-ws0212 /cygdrive/d/Alex/_work/git-tracking/psyco/psyco
On Wed, Jun 3, 2009 at 6:27 PM, Corinna Vinschen
wrote:
> What's left as questionable is the LANG=C default case. Due to the
> discussion from the last month we now use UTF-8 as default encoding,
> because it's the only encoding which covers all (valid) characters.
> Sure, we could also convert t
On Sun, May 31, 2009 at 6:36 PM, Roger Head wrote:
> U... e no, no, that's too easy. There must be a harder way to do
> it.
As an alternative you can try looking into my
http://git.kitsu.ru/mine/shell-wrapper.git (use snapshot link for
topmost commit if you don't have git and don't k
On Sat, May 30, 2009 at 1:21 AM, Edward Lam wrote:
> Here's some more investigation:
[...]
> So note that even when I'm seems to be an UNICODE-AWARE child process, I'm
> still getting a truncated command line. In fact, call GetCommandLineW()
> directly seems to give a truncated command line
> as w
On Sat, May 30, 2009 at 1:04 AM, Edward Lam wrote:
> Alexey Borzenkov wrote:
>> It might be safe for you, but not for other people. If you have a
>> Russian default codepage and ever need to work with chineese/japanese
>> filenames and cygwin uses default codepage for filesys
On Sat, May 30, 2009 at 12:10 AM, Edward Lam wrote:
> Thanks for explaining the UTF8 changes in cygwin 1.7. However, the decision
> to use UTF-8 for the C locale is questionable.
Not at all, because utf-8, as far as I understand, is used for
communication with the system in this context, and does
On Fri, May 29, 2009 at 8:22 PM, Edward Lam wrote:
> I think there is still a bug here? I set LANG=C, then shouldn't be just NOT
> doing any encoding, thus work? If I do this on Linux, it works. If I use a
> cygwin compiled app, it also works.
On Linux, internally, system uses multibyte strings (
On Thu, May 28, 2009 at 7:28 PM, Edward Lam wrote:
> PS. In case you haven't noticed, copyright.txt is not a long file. It
> consists of a single byte, 0xA9.
Did you try utf-8 encoding copyright.txt? Perhaps your locale is utf-8
and the encoder fails.
--
Unsubscribe info: http://cygwin.com/
On Sat, May 16, 2009 at 2:51 AM, Brian Mathis wrote:
> What I have done is associate files with a .sh extension to run the
> bash.exe file. Works for me, but I'm not sure if it pulls in all the
> environment variables - but I don't need them.
If you ever need those environment variables, take a
On Fri, May 15, 2009 at 1:30 PM, Alexey Borzenkov wrote:
> And I found why. It appears that there's a bug in printf with %ls that
> will refuse to print the string completely if the wide string for %ls
> cannot be represented in current charset.
[...]
> Prints nothing, i.e.
On Fri, May 15, 2009 at 11:43 AM, Alexey Borzenkov wrote:
> I'm in a domain at work and previously used mkpasswd -d and mkgroup -d
> to populate /etc/passwd and /etc/group files. Unfortunately, we mostly
> use Russian versions of Windows (especially on servers) here and most
>
I'm in a domain at work and previously used mkpasswd -d and mkgroup -d
to populate /etc/passwd and /etc/group files. Unfortunately, we mostly
use Russian versions of Windows (especially on servers) here and most
built-in user and group names (like Administrator, Domain Users, etc.)
are localized. W
There is something strange going on with national characters in
directory names when using Cygwin 1.7 with UTF-8. Here's a sample
session:
# test.rb
# -*- coding: utf-8 -*-
filename = File.expand_path("test.txt")
puts filename
puts File.open(filename) { |f| f.read }
# test.txt
This is a test
C:\
Hi everyone,
I wonder if nobody noticed this yet, but since Asciidoc 8.2.3 git manpages are
broken in regard that gitlink macro is not handled correctly, and what you see
when issuing git --help is a lot of [1], [2], [3], etc that are completely
unreadable. I found this offending line in asciidoc.
23 matches
Mail list logo
