[ANNOUNCEMENT] Updated: w32api-3.13-1

I've made a new version of the w32api available for download. A list of what has changed can be found here: http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/w32api/ChangeLog?rev=1.980&cvsroot=src To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web pag

Re: all files seems to be owned by the actual user

Matthias Meyer wrote: > Another strangely effect is that "ls -alnh /" lists all files as owned by > the actual user. > If I do that as another user the files will also be listet as owned by him, > the user who runs the ls. > > What is the reason for that? You instructed Cygwin to not read or wri

all files seems to be owned by the actual user

Hi, I define CYGWIN=nontsec as global environment variable. After reboot I install the cygwin-setup-2.602.exe. I only add rsync to the pre selected modules. Then I logged in into the cygwin bash (by using the icon on the desktop) There I tried "rsync -a /cygdrive/c/work /cygdrive/c/backup" All fil

Re: cygport and gpg

On 12/6/2008 12:19 PM, Brian Dessent wrote: It appears that in recent versions (0.9.1 and on) of cygport, failure to verify has been made informational and not fatal. But trunk versions of cygport are for cygwin 1.7 only so it looks like 1.5 will only ever see 0.4.x. Anyway, it's just a script.

Re: cygport and gpg

Ken Brown wrote: > I don't use gpg, but a look at the documentation suggests that I'm > supposed to import a public key. Should the key have been included with > the source package? I didn't see it there. No, keys are available from keyservers. You ought to be able to import it automatically w

cygport and gpg

I'm trying to rebuild a cygwin package in order to diagnose some problems with it, but cygport fails because gpg can't verify the signature: gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information gpg: Signature made Tue Feb 27 17:48:23 2007 EST us

Re: Setup.exe: all files in one common directory? (not per-server)

2008/12/6 sowiso <[EMAIL PROTECTED]>: > > F:\CygwinInstall\release. That would be the sh*t.. And *all* packages > going in there. And one setup.ini. That's the best solution IMHO. Use NTFS junctions. Once you see you have to use a different server, quit setup, go to the newly created Release dir,