Re: Cygwin 2.6.0 Fork issue

[Brian Inglis]

On 2016-12-07 22:37, Rashi Singhal wrote:
> I am using cygwin 2.6.0 (32 bit) version with Actian Pervasive
> version 12.
> We have a program which will call fork() and in child process
> Btrieve file is getting opened.
> While using latest version of cygwin, file open call is not working
> Its not opening file nor displaying any error.
> Could you please help me on this .

With some information to go on, someone on the list may be able to 
help you.

Please read the contents of the web page at the link below and 
follow the instructions: 

> Problem reports:   http://cygwin.com/problems.html

Attach the text from cygcheck -svr, a Simple Test Case minimal source 
program, which when run demonstrates the problem, and the output from 
that test run, and/or the log from a gdb session, and/or the output 
from strace, running the Simple Test Case minimal source program, 
demonstrating the problem.

As the problem is a file open, you may also want to add the output 
from running ls -l, stat, getfacl, and icacls on the file, as file 
open problems often result from permissions issues, so it is also 
important to run cygcheck, tests, and file info using the same 
environment and credentials as when the problem occurs.

-- 
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: [ANNOUNCEMENT] llvm 3.8.1-1

[Yaakov Selkowitz]

On 2016-12-07 17:57, Roger Pack wrote:

Awesome. I tried building 3.9.0 today and ran into

llvm-3.9.0.src/lib/Support/Unix/Signals.inc:418:5: error: ‘Dl_info’
was not declared in this scope
 Dl_info dlinfo;


Already fixed upstream:

http://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Support/Unix/Signals.inc?r1=282919=283427


then when I kind of worked around that by modifying Signals.cpp and
change it to include windows.inc


Ouch.  That's certainly not going to give you the desired results.

I plan to look at rebasing sometime after 3.9.1 is out.

--
Yaakov

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

Cygwin 2.6.0 Fork issue

[Rashi Singhal]

Hi,

I am using cygwin 2.6.0 (32 bit) version with Actian Pervasive version 12.

We have a program which will call fork() and in child process Btrieve
file is getting opened.

While using latest version of cygwin, file open call is not working ,
Its not opening file nor displaying any error.

Could you please help me on this .

Regards,
Rashi

--
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: Installer names not meaningful enough

[Brian Inglis]

On 2016-12-07 15:06, Erik Soderquist wrote:
> On Wed, Dec 7, 2016 at 4:57 PM, Brian Inglis wrote:
> 
>> Use wget -N to prevent duplicate downloads when the name, date, and
>> size don't change.
> 
> That only works if I am downloading to the same location/name as the
> source is

You can use e.g. wget -N -P /var/cache/ with URIs for multiple individual 
files and their detached .sigs: e.g. some of setup_x86{,_64}.exe{,.sig}
setup.ini{,.xz,bz2}{,.sig}, then after gpg --verify, cp -pu to where 
you want to use or store them, appending a release number if you want, 
as described in earlier posts.

-- 
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: [ANNOUNCEMENT] llvm 3.8.1-1

[Roger Pack]

On 7/21/16, Yaakov Selkowitz  wrote:
> The following packages have been uploaded to the Cygwin distribution:
>
> * llvm-3.8.1-1
> * llvm-doc-3.8.1-1
> * libllvm3.8-3.8.1-1
> * libllvm-devel-3.8.1-1

Awesome. I tried building 3.9.0 today and ran into

llvm-3.9.0.src/lib/Support/Unix/Signals.inc:418:5: error: ‘Dl_info’
was not declared in this scope
 Dl_info dlinfo;

then when I kind of worked around that by modifying Signals.cpp and
change it to include windows.inc

at link time I end up with this:

Linking CXX executable ../../bin/llvm-tblgen.exe
CMakeFiles/obj.llvm-tblgen.dir/TableGen.cpp.o: In function `main':
/home/packrd/llvm/llvm-3.9.0.src/utils/TableGen/TableGen.cpp:188:
undefined reference to
`llvm::sys::PrintStackTraceOnErrorSignal(llvm::StringRef, bool)'


Any hints/suggestions there?
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

Re: Problem with chdir and GetCurrentDirectory on Windows 2016

[Dipak Gaigole]

>>
>> So in this situation, is it possible to get the cwd value as
>> "/cygdrive/c/temp/appdir/bin" using some cygwin API?
>
> No, it is generally not possible to get the POSIX path to anything in
> the cygwin root (/) tree to be prefixed by the /cygdrive prefix. The
> /cygdrive prefix exists solely to resolve paths that are outside of /,
> so paths inside that tree don't need the /cygdrive prefix.
>
This path is also displayed to the enduser at different places. So our
requirement is to always get a path in the /cygdrive/ prefix format
irrespective of whether it is inside the cygwin root (/) or outside of
/.

--
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: Problem with chdir and GetCurrentDirectory on Windows 2016

[Eric Blake]

On 12/07/2016 04:22 PM, Dipak Gaigole wrote:

> C:\Temp\appdir>.\test_cwd.exe "bin"
> chdir (bin) reuturned <0>
> GetCurrentDirectory returned , ret = <18>
> getcwd returned , ret = 
> 
> C:\Temp\appdir>
> ##
> Please note that I have the cygwin1.dll in the "C:\Temp\appdir"
> directory. So after changing the directory to "bin", the getcwd()
> returned "/appdir/bin". And our requirement was to get
> "/cygdrive/c/temp/appdir/bin", so the GetCurrentDirectory() approach
> was used.

If you want to convert a POSIX name to the corresponding Windows name,
chdir() and getcwd() is not the best approach; and
chdir()/GetCurrentDirectory() is the wrong approach.  Instead, either
call out to the 'cygpath' utility, or use the cygwin_conv_path() API
(https://cygwin.com/cygwin-api/func-cygwin-conv-path.html) (which is
what 'cygpath' uses under the hood).

> 
> So in this situation, is it possible to get the cwd value as
> "/cygdrive/c/temp/appdir/bin" using some cygwin API?

No, it is generally not possible to get the POSIX path to anything in
the cygwin root (/) tree to be prefixed by the /cygdrive prefix. The
/cygdrive prefix exists solely to resolve paths that are outside of /,
so paths inside that tree don't need the /cygdrive prefix.

But you seem to be asking the wrong question.  If the only reason you
want a "/cygdrive/c" prefix is so that you can supply textual conversion
of "/cygdrive/c" to "c:\", then it seems like your question is really
"how do I convert the POSIX path name given by getcwd() into the
corresponding Windows directory, if one exists".  Then you don't need to
do ANY post-processing of the string, because cygwin will have already
handed you the fully-converted name, by using cygwin_conv_path() correctly.

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



signature.asc
Description: OpenPGP digital signature

RE: permission question

[Michel LaBarre]

> -Original Message-
> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
> Behalf Of Greg Freemyer
> Sent: December-07-16 5:08 PM
> To: brian.ing...@systematicsw.ab.ca; cygwin@cygwin.com
> Subject: Re: permission question
> 
> If I'm going to relegate rsync to the trash bin due to it not
> supporting Windows permissions well enough to be useful, I've got
> other Windows recursive copy tools I use that don't preserve
> permissions either.
> 
> I can't tell you how much I love Windows security permissions.  :(
> 
> In the mean time I have a huge number of folders now on my destination
> drive I need to delete.  (over a million files it seems).
> 
> Neither cygwin, nor windows says I have permission to delete them.
> 
> Any idea how I can do it short of reformating.


You should be able to take ownership recursively of the offending files and 
then remove them.
(Right click - Security => Advanced => Owner Tab => Edit (you may be prompted 
by UAC for admin credentials) => Other users or groups => pick one
Don't forget to select "Replace owner on subcontainers and objects".  In a 
separate step, reset the permissions recursively to get full control, then 
delete everything.)

By the way, did you ever try to setup fstab to apply noacl to default mounts 
before doing your rsynch?
I wonder if that would have reduced your problems.


> 
> Thanks
> Greg
> --
> Greg Freemyer
> 
> 
> On Wed, Dec 7, 2016 at 3:39 PM, Brian Inglis
>  wrote:
> > On 2016-12-07 13:12, Erik Soderquist wrote:
> >>> I really like cygwin and have used it for a decade plus.  Only in the
> >>> last year or 18-months have I noticed significant permission issues
> >>> that slow down my workflow.
> >>>
> >>> Copying these folders/files from one drive to another is a task I'd
> >>> like to accomplish, but even more importantly I'd like to understand
> >>> how to work with permissions in cygwin.  As it is, I'm concerned I
> >>> will have to leave cygwin behind and I don't want to do that.
> >>
> >> I've been a Windows and Linux admin for years, and Windows
> permissions
> >> can be a pain, but can also be very granular.
> >>
> >> What I normally do for something like this is use robocopy's "backup
> mode"
> >> switch to bypass permissions on the source entirely and intentionally not
> >> copy the permissions to the destination, then set up the permissions I
> want
> >> on the destination after the copy is complete.
> >>
> >> The "backup mode" option requires either backup operator or local admin
> >> permissions to use.
> >
> > Concur and recommend for local copies:
> >
> > robocopy src dst /s /sl /xj /copyall /zb /nfl /ndl /np /mt:8 /r:0 /w:0
> >
> > to copy non-empty directories; keep winsymlinks as is; skip junctions;
> > all info; backup fallback; no file, directory, or progress logging;
> > 8 threads, no retries, no waits: use /copy (like cp -p) instead of
> > /copyall to skip security info.
> >
> > --
> > 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
> >
> 
> --
> 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: permission question

[Erik Soderquist]

On Wed, Dec 7, 2016 at 5:08 PM, Greg Freemyer  wrote:
> If I'm going to relegate rsync to the trash bin due to it not
> supporting Windows permissions well enough to be useful, I've got
> other Windows recursive copy tools I use that don't preserve
> permissions either.

I still use rsync in cygwin, just not on things that have "separate"
windows permissions

> I can't tell you how much I love Windows security permissions.  :(

Same!

> In the mean time I have a huge number of folders now on my destination
> drive I need to delete.  (over a million files it seems).
>
> Neither cygwin, nor windows says I have permission to delete them.
>
> Any idea how I can do it short of reformating.

This will obliterate the permissions, so you are aware up front...

In the Windows security dialog, go to advanced --> owner, and forcibly
take recursive ownership of the tree.  On annything you do not have
access to, Windows should prompt you to overwrite the security so you
do have access.  Local Admin is required to be able to do this.

-- Erik

--
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: Problem with chdir and GetCurrentDirectory on Windows 2016

[Dipak Gaigole]

>> I am facing a very strange problem with chdir and GetCurrentDirectory.
>
> Not strange at all.  The two are incompatible.  When writing Cygwin
> programs, stick to the POSIX-y interface, NOT the windows interface.
>
>> After calling chdir (), the call to GetCurrentDirectory () returns
>
> chdir() is POSIX, and the POSIX counterpart is getcwd(), which will
> return the right value always.  GetCurrentDirectory() is the windows
> API, which may or may not have a sane value at any given time, but more
> often than not does NOT match the value in getcwd(), and that is by
> design - because the Cygwin notion of the working directory is more
> powerful than the windows notion of the working directory, and it is
> just too expensive for cygwin to try and always keep windows up-to-date
> with the current directory when there are times that you can be in a
> cygwin directory that has no windows counterpart.
>

That perfectly explains the reason behind the behavior I am facing.

> Again, DON'T use windows API calls from a cygwin program, use POSIX
> calls instead. You WANT to use getcwd() here.
>

I dig into the source code history and found that windows APIs are
used to make some use case work. Here is the simple usecase:
##
C:\Temp\appdir>dir
 Volume in drive C is C_Drive
 Volume Serial Number is DE87-B7F1

 Directory of C:\Temp\appdir

12/08/2016  03:24 AM  .
12/08/2016  03:24 AM  ..
12/08/2016  03:18 AM  bin
11/13/2014  08:15 PM 3,247,117 cygwin1.dll
12/08/2016  03:06 AM   567 test_cwd.c
12/08/2016  03:12 AM   387,593 test_cwd.exe
   3 File(s)  3,635,277 bytes
   3 Dir(s)  27,981,082,624 bytes free

C:\Temp\appdir>.\test_cwd.exe "bin"
chdir (bin) reuturned <0>
GetCurrentDirectory returned , ret = <18>
getcwd returned , ret = 

C:\Temp\appdir>
##
Please note that I have the cygwin1.dll in the "C:\Temp\appdir"
directory. So after changing the directory to "bin", the getcwd()
returned "/appdir/bin". And our requirement was to get
"/cygdrive/c/temp/appdir/bin", so the GetCurrentDirectory() approach
was used.

So in this situation, is it possible to get the cwd value as
"/cygdrive/c/temp/appdir/bin" using some cygwin API?

Thanks,
Dipak

--
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: permission question

[Greg Freemyer]

If I'm going to relegate rsync to the trash bin due to it not
supporting Windows permissions well enough to be useful, I've got
other Windows recursive copy tools I use that don't preserve
permissions either.

I can't tell you how much I love Windows security permissions.  :(

In the mean time I have a huge number of folders now on my destination
drive I need to delete.  (over a million files it seems).

Neither cygwin, nor windows says I have permission to delete them.

Any idea how I can do it short of reformating.

Thanks
Greg
--
Greg Freemyer


On Wed, Dec 7, 2016 at 3:39 PM, Brian Inglis
 wrote:
> On 2016-12-07 13:12, Erik Soderquist wrote:
>>> I really like cygwin and have used it for a decade plus.  Only in the
>>> last year or 18-months have I noticed significant permission issues
>>> that slow down my workflow.
>>>
>>> Copying these folders/files from one drive to another is a task I'd
>>> like to accomplish, but even more importantly I'd like to understand
>>> how to work with permissions in cygwin.  As it is, I'm concerned I
>>> will have to leave cygwin behind and I don't want to do that.
>>
>> I've been a Windows and Linux admin for years, and Windows permissions
>> can be a pain, but can also be very granular.
>>
>> What I normally do for something like this is use robocopy's "backup mode"
>> switch to bypass permissions on the source entirely and intentionally not
>> copy the permissions to the destination, then set up the permissions I want
>> on the destination after the copy is complete.
>>
>> The "backup mode" option requires either backup operator or local admin
>> permissions to use.
>
> Concur and recommend for local copies:
>
> robocopy src dst /s /sl /xj /copyall /zb /nfl /ndl /np /mt:8 /r:0 /w:0
>
> to copy non-empty directories; keep winsymlinks as is; skip junctions;
> all info; backup fallback; no file, directory, or progress logging;
> 8 threads, no retries, no waits: use /copy (like cp -p) instead of
> /copyall to skip security info.
>
> --
> 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
>

--
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: Installer names not meaningful enough

[Erik Soderquist]

On Wed, Dec 7, 2016 at 4:57 PM, Brian Inglis wrote:

> Use wget -N to prevent duplicate downloads when the name, date,
> and size don't change.

That only works if I am downloading to the same location/name as the source is

-- Erik

--
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: Installer names not meaningful enough

[Brian Inglis]

On 2016-12-07 14:40, Erik Soderquist wrote:
> On Thu, Dec 1, 2016 at 7:18 AM, Lee Dilkie wrote:
>> I'd agree that adding "cygwin" to the setup program would be nice
>> but it's certainly not the windows "way", lots of programs use just
>> "setup.exe".
> 
> I don't recall "the Windows way" being a goal of Cygwin.
> 
>> Versioning can't be added to the file name because the setup
>> program itself isn't versioned, or at least isn't the same version
>> as the cygwin you are installing... the cygwin version come from
>> the servers...
> 
> Yes, the setup program is versioned, and will complain about being 
> outdated on its own anytime it sees a setup.ini that reports a newer 
> version of the setup program exists.
> 
> I've often wondered why the setup program doesn't include its
> version number in the name like ever other package does, for
> example: openssh-7.3p1-2.tar.xz
> 
> On my own systems, I download the setup program and check its
> version, then rename the file myself to include the version number. I
> know I would greatly appreciate the setup version number in the file
> name, and suspect this could be accomplished without breaking the
> existing scripted downloads by having setup.exe and setup_x64.exe be
> symlinks to whatever the current version is. Having the version
> number of the setup program thus available could also prevent a lot
> of duplicate downloads. I know I would look at the version number
> before downloading rather than download and then compare to what I
> have.

Use wget -N to prevent duplicate downloads when the name, date, 
and size don't change.

-- 
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: Installer names not meaningful enough

[Erik Soderquist]

On Thu, Dec 1, 2016 at 7:18 AM, Lee Dilkie wrote:
> I'd agree that adding "cygwin" to the setup program would be nice but it's
> certainly not the windows "way", lots of programs use just "setup.exe".

I don't recall "the Windows way" being a goal of Cygwin.

> Versioning can't be added to the file name because the setup program itself
> isn't versioned, or at least isn't the same version as the cygwin you are
> installing... the cygwin version come from the servers...

Yes, the setup program is versioned, and will complain about being
outdated on its own anytime it sees a setup.ini that reports a newer
version of the setup program exists.

I've often wondered why the setup program doesn't include its version
number in the name like ever other package does, for example:
openssh-7.3p1-2.tar.xz

On my own systems, I download the setup program and check its version,
then rename the file myself to include the version number.  I know I
would greatly appreciate the setup version number in the file name,
and suspect this could be accomplished without breaking the existing
scripted downloads by having setup.exe and setup_x64.exe be symlinks
to whatever the current version is.  Having the version number of the
setup program thus available could also prevent a lot of duplicate
downloads.  I know I would look at the version number before
downloading rather than download and then compare to what I have.

-- Erik

--
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: Installer names not meaningful enough

[Brian Inglis]

On 2016-12-07 07:46, Ian Lambert wrote:
> On December 7, 2016 4:57:02 AM EST, Duncan Roe wrote:
>> On Tue, Dec 06, 2016 at 10:11:42AM +0100, Gerrit Haase wrote:
>>> 2016-12-01 11:51 GMT+01:00 Roberto Ríos Gallardo says:
 Please give the installers more meaningful names. In
 particular, make sure "cygwin" is part of it.
 "setup-x86_64.exe" is not very obvious. A version number would
 be nice too.
>>> The version is part of setup.ini in the header:
>>> # This file was automatically generated at 2016-12-05 09:43:16 UTC.
>>> #
>>> # If you edit it, your edits will be discarded next time the file is
>>> # generated.  See http://cygwin.com/setup.html for details.
>>> release: cygwin
>>> arch: x86_64
>>> setup-timestamp: 1480930996
>>> setup-version: 2.876
>>> ...
>> Where is setup.ini?
> $ locate setup.ini
> /cygwin-install/path/ftp.some.mirror/x86_64/setup.ini

More generally, without locate installed or updated, 
you can find it quickly with: 

$ grep -A1 '^last-cache$' /etc/setup/setup.rc
last-cache
C:/cygwin-package-cache

at: 

$ ls $(cygpath $(sed '0,/^last-cache$/d;q' 
/etc/setup/setup.rc))/?*tp%3a%2f%2f*cygwin*%2f/x86*/setup.ini

giving: 

$ grep '^setup-version:\s' $(cygpath $(sed '0,/^last-cache$/d;q' 
/etc/setup/setup.rc))/?*tp%3a%2f%2f*cygwin*%2f/x86*/setup.ini
setup-version: 2.876

or: 

$ sed '/^setup-version:\s/!d;s///' $(cygpath $(sed '0,/^last-cache$/d;q' 
/etc/setup/setup.rc))/?*tp%3a%2f%2f*cygwin*%2f/x86*/setup.ini
2.876

Unwrap commands if required to copy and paste.

-- 
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: Problem with chdir and GetCurrentDirectory on Windows 2016

[Eric Blake]

On 12/07/2016 02:23 PM, Dipak Gaigole wrote:
> Hello,
> 
> I am facing a very strange problem with chdir and GetCurrentDirectory.

Not strange at all.  The two are incompatible.  When writing Cygwin
programs, stick to the POSIX-y interface, NOT the windows interface.

> After calling chdir (), the call to GetCurrentDirectory () returns

chdir() is POSIX, and the POSIX counterpart is getcwd(), which will
return the right value always.  GetCurrentDirectory() is the windows
API, which may or may not have a sane value at any given time, but more
often than not does NOT match the value in getcwd(), and that is by
design - because the Cygwin notion of the working directory is more
powerful than the windows notion of the working directory, and it is
just too expensive for cygwin to try and always keep windows up-to-date
with the current directory when there are times that you can be in a
cygwin directory that has no windows counterpart.


> Administrator@windows2k16vika /cygdrive/c/src
> $ cat test_cwd.c
> #include 
> #include 
> #include 

Any code that does this is already suspect.

> 
> #define BUF_SIZE 512
> 
> int main()
> {
> int ret;
> char *dir;
> char dirname [BUF_SIZE];
> 
> dir = "/cygdrive/c/Program Files";
> ret = chdir (dir);
> fprintf (stderr, "chdir (%s) reuturned <%d>\n", dir, ret);
> 
> ret = GetCurrentDirectory(BUF_SIZE, dirname);

Again, DON'T use windows API calls from a cygwin program, use POSIX
calls instead. You WANT to use getcwd() here.

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



signature.asc
Description: OpenPGP digital signature

Re: Problem with chdir and GetCurrentDirectory on Windows 2016

[Dipak Gaigole]

> GetCurrentDirectory failed with ERROR_INVALID_HANDLE.  As a result the
> buffer was not populated.  What is in dirname[] is stack garbage.

As per the documentation of GetCurrentDirectory(), "If the function
succeeds, the return value specifies the number of characters that are
written to the buffer, not including the terminating null character."
So if I am not wrong, the return value 6 indicates the number of
characters written to the buffer.

Here is the output of the same program on my windows 7 system:
Administrator@W-WIN7-56 /cygdrive/c/temp
$ ./test_cwd.exe
chdir (/cygdrive/c/Program Files) reuturned <0>
GetCurrentDirectory returned , ret = <16>
getcwd returned , ret = 

Administrator@W-WIN7-56 /cygdrive/c/temp
$



On Thu, Dec 8, 2016 at 1:53 AM, Dipak Gaigole  wrote:
> Hello,
>
> I am facing a very strange problem with chdir and GetCurrentDirectory.
> After calling chdir (), the call to GetCurrentDirectory () returns
> wrong value. I tested this on Windows 7 and Windows 2016. It is
> working fine on Windows 7 whereas wrong values are returned on Windows
> 2016. I guess we should see the same behavior on Windows 10 (client
> version of Windows 2016) as well.
>
> #
> Administrator@windows2k16vika /cygdrive/c/src
> $ cygcheck.exe -c cygwin
> Cygwin Package Information
> Package  VersionStatus
> cygwin   1.7.33-1   OK
>
> Administrator@windows2k16vika /cygdrive/c/src
> $ uname -a
> CYGWIN_NT-10.0-WOW6 windows2k16vika 1.7.33-2(0.280/5/3) 2014-11-13
> 15:45 i686 Cygwin
>
> Administrator@windows2k16vika /cygdrive/c/src
> $ cat test_cwd.c
> #include 
> #include 
> #include 
>
> #define BUF_SIZE 512
>
> int main()
> {
> int ret;
> char *dir;
> char dirname [BUF_SIZE];
>
> dir = "/cygdrive/c/Program Files";
> ret = chdir (dir);
> fprintf (stderr, "chdir (%s) reuturned <%d>\n", dir, ret);
>
> ret = GetCurrentDirectory(BUF_SIZE, dirname);
> if (ret)
> fprintf (stderr, "GetCurrentDirectory returned <%s>, ret =
> <%d>\n", dirname, ret);
>
> dir = getcwd (dirname, BUF_SIZE);
> fprintf (stderr, "getcwd returned <%s>, ret = <%s>\n", dirname, dir);
>
> return 0;
> }
>
> Administrator@windows2k16vika /cygdrive/c/src
> $ gcc -g -Wall -lKernel32 test_cwd.c  -o test_cwd
>
> Administrator@windows2k16vika /cygdrive/c/src
> $ ./test_cwd.exe
> chdir (/cygdrive/c/Program Files) reuturned <0>
> GetCurrentDirectory returned , ret = <6>
> getcwd returned , ret = 
>
> Administrator@windows2k16vika /cygdrive/c/src
> $
> #
>
> Has anyone noticed such behavior on Windows 10 or 2016? Any
> suggestions, pointers?
>
> Thanks,
> Dipak

--
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] Perl distributions

[Achim Gratz]

The following Perl distributions have been updated to their latest
version available from CPAN:

x86/x86_64
--
perl-Cpanel-JSON-XS-3.0225-1
perl-Crypt-OpenSSL-DSA-0.18-1
perl-DBD-SQLite-1.52-1
perl-DBD-mysql-4.041-1
perl-JSON-XS-3.03-1
perl-Unicode-Collate-1.19-1

noarch
--
perl-Business-ISMN-1.131-1
perl-CPAN-Meta-Check-0.014-1
perl-HTML-Formatter-2.16-1
perl-IO-Socket-SSL-2.039-1
perl-Log-Log4perl-1.48-1
perl-Module-ScanDeps-1.23-1
perl-Mojolicious-7.11-1
perl-PAR-1.013-1
perl-Pod-Simple-3.35-1
perl-Test-Simple-1.302067-1
perl-YAML-1.20-1

NOTE

perl-JSON-XS has been patched to restore limited functionality with Perl
ithreads that was removed intentionally by upstream with version 3.00.
This is likely to break again in the future in less easily-fixable ways
and you are advised to install and use perl-JSON-MaybeXS (this is a
drop-in replacement for JSON that automatically choses an available XS
module) and perl-Cpanel-JSON-XS (if you need the better XS performace).

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

--
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] Perl distributions

[Achim Gratz]

The following Perl distributions have been updated to their latest
version available from CPAN:

x86/x86_64
--
perl-Cpanel-JSON-XS-3.0225-1
perl-Crypt-OpenSSL-DSA-0.18-1
perl-DBD-SQLite-1.52-1
perl-DBD-mysql-4.041-1
perl-JSON-XS-3.03-1
perl-Unicode-Collate-1.19-1

noarch
--
perl-Business-ISMN-1.131-1
perl-CPAN-Meta-Check-0.014-1
perl-HTML-Formatter-2.16-1
perl-IO-Socket-SSL-2.039-1
perl-Log-Log4perl-1.48-1
perl-Module-ScanDeps-1.23-1
perl-Mojolicious-7.11-1
perl-PAR-1.013-1
perl-Pod-Simple-3.35-1
perl-Test-Simple-1.302067-1
perl-YAML-1.20-1

NOTE

perl-JSON-XS has been patched to restore limited functionality with Perl
ithreads that was removed intentionally by upstream with version 3.00.
This is likely to break again in the future in less easily-fixable ways
and you are advised to install and use perl-JSON-MaybeXS (this is a
drop-in replacement for JSON that automatically choses an available XS
module) and perl-Cpanel-JSON-XS (if you need the better XS performace).

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

Re: permission question

[Brian Inglis]

On 2016-12-07 13:12, Erik Soderquist wrote:
>> I really like cygwin and have used it for a decade plus.  Only in the
>> last year or 18-months have I noticed significant permission issues
>> that slow down my workflow.
>>
>> Copying these folders/files from one drive to another is a task I'd
>> like to accomplish, but even more importantly I'd like to understand
>> how to work with permissions in cygwin.  As it is, I'm concerned I
>> will have to leave cygwin behind and I don't want to do that.
> 
> I've been a Windows and Linux admin for years, and Windows permissions
> can be a pain, but can also be very granular.
> 
> What I normally do for something like this is use robocopy's "backup mode"
> switch to bypass permissions on the source entirely and intentionally not
> copy the permissions to the destination, then set up the permissions I want
> on the destination after the copy is complete.
> 
> The "backup mode" option requires either backup operator or local admin
> permissions to use.

Concur and recommend for local copies:

robocopy src dst /s /sl /xj /copyall /zb /nfl /ndl /np /mt:8 /r:0 /w:0

to copy non-empty directories; keep winsymlinks as is; skip junctions; 
all info; backup fallback; no file, directory, or progress logging; 
8 threads, no retries, no waits: use /copy (like cp -p) instead of 
/copyall to skip security info.

-- 
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: Problem with chdir and GetCurrentDirectory on Windows 2016

[Jeffrey Altman]

On 12/7/2016 3:23 PM, Dipak Gaigole wrote:
> GetCurrentDirectory returned , ret = <6>

GetCurrentDirectory failed with ERROR_INVALID_HANDLE.  As a result the
buffer was not populated.  What is in dirname[] is stack garbage.

My guess is that /cygdrive/c/Program Files is not associated with a
device or if it associated with a NTFS device the driver doesn't know
how to match /cygdrive with a valid path.

Jeffrey Altman




smime.p7s
Description: S/MIME Cryptographic Signature

Problem with chdir and GetCurrentDirectory on Windows 2016

[Dipak Gaigole]

Hello,

I am facing a very strange problem with chdir and GetCurrentDirectory.
After calling chdir (), the call to GetCurrentDirectory () returns
wrong value. I tested this on Windows 7 and Windows 2016. It is
working fine on Windows 7 whereas wrong values are returned on Windows
2016. I guess we should see the same behavior on Windows 10 (client
version of Windows 2016) as well.

#
Administrator@windows2k16vika /cygdrive/c/src
$ cygcheck.exe -c cygwin
Cygwin Package Information
Package  VersionStatus
cygwin   1.7.33-1   OK

Administrator@windows2k16vika /cygdrive/c/src
$ uname -a
CYGWIN_NT-10.0-WOW6 windows2k16vika 1.7.33-2(0.280/5/3) 2014-11-13
15:45 i686 Cygwin

Administrator@windows2k16vika /cygdrive/c/src
$ cat test_cwd.c
#include 
#include 
#include 

#define BUF_SIZE 512

int main()
{
int ret;
char *dir;
char dirname [BUF_SIZE];

dir = "/cygdrive/c/Program Files";
ret = chdir (dir);
fprintf (stderr, "chdir (%s) reuturned <%d>\n", dir, ret);

ret = GetCurrentDirectory(BUF_SIZE, dirname);
if (ret)
fprintf (stderr, "GetCurrentDirectory returned <%s>, ret =
<%d>\n", dirname, ret);

dir = getcwd (dirname, BUF_SIZE);
fprintf (stderr, "getcwd returned <%s>, ret = <%s>\n", dirname, dir);

return 0;
}

Administrator@windows2k16vika /cygdrive/c/src
$ gcc -g -Wall -lKernel32 test_cwd.c  -o test_cwd

Administrator@windows2k16vika /cygdrive/c/src
$ ./test_cwd.exe
chdir (/cygdrive/c/Program Files) reuturned <0>
GetCurrentDirectory returned , ret = <6>
getcwd returned , ret = 

Administrator@windows2k16vika /cygdrive/c/src
$
#

Has anyone noticed such behavior on Windows 10 or 2016? Any
suggestions, pointers?

Thanks,
Dipak

--
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: permission question

[Erik Soderquist]

> I really like cygwin and have used it for a decade plus.  Only in the
> last year or 18-months have I noticed significant permission issues
> that slow down my workflow.
>
> Copying these folders/files from one drive to another is a task I'd
> like to accomplish, but even more importantly I'd like to understand
> how to work with permissions in cygwin.  As it is, I'm concerned I
> will have to leave cygwin behind and I don't want to do that.

I've been a Windows and Linux admin for years, and Windows permissions
can be a pain, but can also be very granular.

What I normally do for something like this is use robocopy's "backup mode"
switch to bypass permissions on the source entirely and intentionally not
copy the permissions to the destination, then set up the permissions I want
on the destination after the copy is complete.

The "backup mode" option requires either backup operator or local admin
permissions to use.

-- Erik

--
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: grep-2.27-1

[Eric Blake (cygwin)]

A new release of grep, 2.27-1, has been uploaded and will soon reach a
mirror near you; leaving the previous version at 2.25-1.

NEWS:
=
This is a new upstream release.  For more details on grep, see the
documentation in /usr/share/doc/grep/.

DESCRIPTION:

GNU Grep searches one or more input files for lines containing a match
to a specified patter.  By default, Grep outputs the matching lines.
The GNU implementation includes several useful extensions over POSIX.

UPDATE:
===
To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system. Save it and run setup, answer the questions and pick up 'grep'
in the 'Base' category (it should already be selected).

DOWNLOAD:
=
Note that downloads from cygwin.com aren't allowed due to bandwidth
limitations.  This means that you will need to find a mirror which has
this update, please choose the one nearest to you:
http://cygwin.com/mirrors.html

QUESTIONS:
==
If you want to make a point or ask a question the Cygwin mailing list is
the appropriate place.

-- 
Eric Blake
volunteer cygwin grep package maintainer

For more details on this list (including unsubscription), see:
http://sourceware.org/lists.html

--
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: permission question

[Greg Freemyer]

On Wed, Dec 7, 2016 at 1:48 PM, Stephen John Smoogen  wrote:
>> I'm tempted to just do a "chmod 755 -R .", but I've just had too many
>> windows permission issues in the last year to start trying things
>> without guidance.
>
> That would probably make things worse. I believe that Windows
> permissions are like attribs in Linux (which moves it into witchcraft
> and sorcery). For dealing with this sort of issue I would look at
> using the xcopy that Glenn from dell mentioned.
>
>> Greg

I really like cygwin and have used it for a decade plus.  Only in the
last year or 18-months have I noticed significant permission issues
that slow down my workflow.

Copying these folders/files from one drive to another is a task I'd
like to accomplish, but even more importantly I'd like to understand
how to work with permissions in cygwin.  As it is, I'm concerned I
will have to leave cygwin behind and I don't want to do that.

Greg
--
Greg Freemyer

--
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: permission question

[Stephen John Smoogen]

On 7 December 2016 at 13:22, Greg Freemyer  wrote:
> On Wed, Dec 7, 2016 at 10:47 AM, Greg Freemyer  
> wrote:
>> I have a USB drive with 100,000's of thousands of files I put on it
>> from one PC.  I've built that dataset up over a couple years.
>>
>> I moved the USB drive to a different PC and I'm trying to rsync it to
>> another drive.
>>
>> 99.9% of the data seems to have made its way from one drive to the other.
>>
>> But I got a few permission denied messages when reading files off of
>> the source drive.
>>
>> I really don't need anything but the equivalent of 666 permissions for
>> the source drive files.
>>
>> I know linux well, but I have screwed up Windows permissions once too often.
>>
>> Is there a command I should run in Windows or cygwin to grant my user
>> read/write permission to all of the files?
>>
>> Or I can parse the rsync log file I created and look for the handful
>> of files that failed with permission denied.
>>
>> Thanks
>
> It's worst than I thought.
>
> I used rsync -avP to make the copy of the folders / files.   (Its
> 2.5TB, so it took all day yesterday to run).
>
> I'm trying now to use "rsync -cvr" to compare the checksums of the
> source / destination and re-copy any that got corrupted.
>
> The trouble is lots of the destination files can't be read due to
> permission issues, so the compare doesn't match and the rsync is
> copying the same files again.
>
> I admit to having little understanding of the Windows / cygwin
> permissions integration.  Or even Windows permissions standalone.  I
> do understand Linux permissions well.
>
> I'm tempted to just do a "chmod 755 -R .", but I've just had too many
> windows permission issues in the last year to start trying things
> without guidance.

That would probably make things worse. I believe that Windows
permissions are like attribs in Linux (which moves it into witchcraft
and sorcery). For dealing with this sort of issue I would look at
using the xcopy that Glenn from dell mentioned.

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



-- 
Stephen J Smoogen.

--
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: permission question

[Greg Freemyer]

On Wed, Dec 7, 2016 at 10:47 AM, Greg Freemyer  wrote:
> I have a USB drive with 100,000's of thousands of files I put on it
> from one PC.  I've built that dataset up over a couple years.
>
> I moved the USB drive to a different PC and I'm trying to rsync it to
> another drive.
>
> 99.9% of the data seems to have made its way from one drive to the other.
>
> But I got a few permission denied messages when reading files off of
> the source drive.
>
> I really don't need anything but the equivalent of 666 permissions for
> the source drive files.
>
> I know linux well, but I have screwed up Windows permissions once too often.
>
> Is there a command I should run in Windows or cygwin to grant my user
> read/write permission to all of the files?
>
> Or I can parse the rsync log file I created and look for the handful
> of files that failed with permission denied.
>
> Thanks

It's worst than I thought.

I used rsync -avP to make the copy of the folders / files.   (Its
2.5TB, so it took all day yesterday to run).

I'm trying now to use "rsync -cvr" to compare the checksums of the
source / destination and re-copy any that got corrupted.

The trouble is lots of the destination files can't be read due to
permission issues, so the compare doesn't match and the rsync is
copying the same files again.

I admit to having little understanding of the Windows / cygwin
permissions integration.  Or even Windows permissions standalone.  I
do understand Linux permissions well.

I'm tempted to just do a "chmod 755 -R .", but I've just had too many
windows permission issues in the last year to start trying things
without guidance.

Greg

--
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: permission question

[Gluszczak, Glenn]

I've found recently while using cp or rsync that the Administrator account 
could not access files or set back permissions for files with System account 
privileges.
I had to resort to xcopy to do things properly.

-Original Message-
From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of 
Greg Freemyer
Sent: Wednesday, December 07, 2016 10:48 AM
To: cygwin@cygwin.com
Subject: permission question

I have a USB drive with 100,000's of thousands of files I put on it from one 
PC.  I've built that dataset up over a couple years.

I moved the USB drive to a different PC and I'm trying to rsync it to another 
drive.

99.9% of the data seems to have made its way from one drive to the other.

But I got a few permission denied messages when reading files off of the source 
drive.

I really don't need anything but the equivalent of 666 permissions for the 
source drive files.

I know linux well, but I have screwed up Windows permissions once too often.

Is there a command I should run in Windows or cygwin to grant my user 
read/write permission to all of the files?

Or I can parse the rsync log file I created and look for the handful of files 
that failed with permission denied.

Thanks
Greg
--
Greg Freemyer

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

permission question

[Greg Freemyer]

I have a USB drive with 100,000's of thousands of files I put on it
from one PC.  I've built that dataset up over a couple years.

I moved the USB drive to a different PC and I'm trying to rsync it to
another drive.

99.9% of the data seems to have made its way from one drive to the other.

But I got a few permission denied messages when reading files off of
the source drive.

I really don't need anything but the equivalent of 666 permissions for
the source drive files.

I know linux well, but I have screwed up Windows permissions once too often.

Is there a command I should run in Windows or cygwin to grant my user
read/write permission to all of the files?

Or I can parse the rsync log file I created and look for the handful
of files that failed with permission denied.

Thanks
Greg
--
Greg Freemyer

--
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: Installer names not meaningful enough

[Ian Lambert]

On December 7, 2016 4:57:02 AM EST, Duncan Roe  
wrote:
>On Tue, Dec 06, 2016 at 10:11:42AM +0100, Gerrit Haase wrote:
>> 2016-12-01 11:51 GMT+01:00 Roberto Ríos Gallardo says:
>> > Please give the installers more meaningful names. In particular,
>make
>> > sure "cygwin" is part of it. "setup-x86_64.exe" is not very
>obvious. A
>> > version number would be nice too.
>>
>> The version is part of setup.ini in the header:
>>
>> # This file was automatically generated at 2016-12-05 09:43:16 UTC.
>> #
>> # If you edit it, your edits will be discarded next time the file is
>> # generated.  See http://cygwin.com/setup.html for details.
>> release: cygwin
>> arch: x86_64
>> setup-timestamp: 1480930996
>> setup-version: 2.876
>> ...
>>
>>
>> Regards,
>> Gerrit
>
>Where is setup.ini?
>

$ locate setup.ini

/cygwin-install/path/ftp.some.mirror/x86_64/setup.ini

Cheers


--
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: make command gives: error while loading shared libraries: ?: cannot open shared object file

[Marco Atzeri]

On 07/12/2016 07:34, Arnaut B wrote:

On Tue, 06 Dec 2016 18:41:25 -0800, Ken Brown  wrote:


On 12/6/2016 6:54 PM, Arnaut B wrote:

Hi All,

After updating cygwin to the latest current release, my "make" command
is broken. It spits the following error:





/usr/bin/cygcrypt-0.dll is provided by the libcrypt0 package.  Try
reinstalling that.

Ken



Thanks. That did it. Wish there was an easier way to get the answer than
going on the mailing list. Is there a command that can check what
package a dll belongs to?



$ cygcheck -p cygcrypt-0.dll
Found 4 matches for cygcrypt-0.dll
crypt-debuginfo-1.3-1 - crypt-debuginfo: Debug info for crypt (installed 
binaries and support files)
crypt-debuginfo-1.4-1 - crypt-debuginfo: Debug info for crypt (installed 
binaries and support files)
libcrypt0-1.3-1 - libcrypt0: Encryption/Decryption utility and library 
(installed binaries and support files)
libcrypt0-1.4-1 - libcrypt0: Encryption/Decryption utility and library 
(installed binaries and support files)



--
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: Installer names not meaningful enough

[Duncan Roe]

On Tue, Dec 06, 2016 at 10:11:42AM +0100, Gerrit Haase wrote:
> 2016-12-01 11:51 GMT+01:00 Roberto Ríos Gallardo says:
> > Please give the installers more meaningful names. In particular, make
> > sure "cygwin" is part of it. "setup-x86_64.exe" is not very obvious. A
> > version number would be nice too.
>
> The version is part of setup.ini in the header:
>
> # This file was automatically generated at 2016-12-05 09:43:16 UTC.
> #
> # If you edit it, your edits will be discarded next time the file is
> # generated.  See http://cygwin.com/setup.html for details.
> release: cygwin
> arch: x86_64
> setup-timestamp: 1480930996
> setup-version: 2.876
> ...
>
>
> Regards,
> Gerrit

Where is setup.ini?

Cheers ... Duncan.

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