delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
DomainKey-Signature: | a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:date:from:to:subject:message-id:reply-to | |
:references:mime-version:content-type:in-reply-to; q=dns; s= | |
default; b=ZO0KP2oKd93wO+erjXq7f4boUXgNRmOEnAwnI0Q9YMIdrg/d/LgQT | |
s7LoD4hmhvpGg0mz7LrScMsxp9cUSq6qDSQH+q9s/+g93BJK+eNYwMd7JOqgIjZo | |
jzpUFiUzuvVq9l9o9rLgeZr6yNT19rXSYcQlSreItHtwNBSdCTD60Q= | |
DKIM-Signature: | v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:date:from:to:subject:message-id:reply-to | |
:references:mime-version:content-type:in-reply-to; s=default; | |
bh=DmMdfTSKQm3ga894NmEO/cZQuK0=; b=ARG5ccD+5nl8eZvauGS9v6Ngob9c | |
hiwxRUmBsPkAxsyJ8Y93lEoqI+UAGpbYdG1P8K/j6j3IcAYTasPrAmwncM39/b1T | |
yG6J3BA+GC1KAMFKqFTMmIs0209JvwdnMmxHgG/75KyizlhD78/u9TjLD58qhplc | |
k+xGbvupMXtjGFw= | |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
X-Spam-SWARE-Status: | No, score=-4.4 required=5.0 tests=AWL,BAYES_00,KHOP_PGP_SIGNED autolearn=ham version=3.3.2 |
Date: | Wed, 14 Aug 2013 16:04:15 +0200 |
From: | Corinna Vinschen <corinna-cygwin AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | Re: 64-bit Cygwin installation is missing /usr/bin/lockfile |
Message-ID: | <20130814140415.GJ4315@calimero.vinschen.de> |
Reply-To: | cygwin AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
References: | <CAMCTF-euv+5ZvBWfc8Gv6G4wuEyGH1_guDZPTZQDxD+G4dn6kQ AT mail DOT gmail DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <CAMCTF-euv+5ZvBWfc8Gv6G4wuEyGH1_guDZPTZQDxD+G4dn6kQ@mail.gmail.com> |
User-Agent: | Mutt/1.5.21 (2010-09-15) |
X-Virus-Found: | No |
--SBT+cnFS/G3NVgv4 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Aug 14 09:43, Steve Rowley wrote: > > On 8/13/2013 6:49 PM, Christopher Faylor wrote: > >> On Tue, Aug 13, 2013 at 05:29:46PM -0400, Larry Hall (Cygwin) wrote: > >>> On 8/13/2013 5:01 PM, Steve Rowley wrote: > >>> I just installed 64-bit Cygwin on Win7, and noticed that > >>> /usr/bin/lockfile is missing in my installation. > >>> > >> As always, you can find what package something is in by searching for = it > >> here: <http://cygwin.com/packages/> > >> > >> In the case of lockfile, you can see the results here: > >> <http://cygwin.com/cgi-bin2/package-grep.cgi?grep=3Dusr%2Fbin%2Flockfi= le> > >> > >> However note that, currently, this only searches the 32-bit version of > >> Cygwin. Some packages are still missing from the 64-bit version. > > > > The fact that some packages don't exist yet for 64-bit is something > > that does deserve highlighting. Of course, whether or not the package > > actually exists for 64-bit, the package search will tell you if it > > exists in the 32-bit world, so at least one knows what to look for. > > In this particular case, I did go looking to see if 'procmail' was > > already available for 64-bit. As it turns out, it is. >=20 > Thank you for for the pointer to how to find the Cygwin package > containing a file; that is indeed a useful thing to know. Since > procmail is the home of /usr/bin/lockfile, I reinstalled procmail. >=20 > However, /usr/bin/lockfile is still missing. Unpacking the procmail > 3.22-12 tarball reveals that it contains only the > /usr/share/doc/procmail/ directory, and 4 small documentation files. > The rest of procmail is missing. >=20 > If this is something that will take a while, then perhaps I should go > back to the 32-bit installation so my scripts will work while waiting > for a fix. But as uninstalling and reinstalling a rather large Cygwin > installation is painful, I'd rather not do this if lockfile will be > available in a week or so. >=20 > Does anyone have advice as to whether it's worth waiting vs going back > to 32 bit? It's just a packaging bug. Somehow I tripped over the order of variable evaluation. I'm looking into it and provide a new 64 bit procmail later today. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --SBT+cnFS/G3NVgv4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) iQIcBAEBAgAGBQJSC45fAAoJEPU2Bp2uRE+gAgYP/3Edvd4pPDyaKTbVl6pp2Ya1 79NQbprfHhUkb7W59YElaQRyHNiY3Nms9reu9VR/xUdolyNq217LmCQdhU5J+e3Q mg9JSM3OGj9rhwyDX3YcHMDpk9Jx9IhbTxgZwVaq4OpkH6yVlUyGXWcDEhT9Z2rv N866y9qeAGIYx0qwkVfurFAyTo7OiborGugmyUjQfpbXfPRKLDJDSeJEpDiUYTDF /jUS1hQIBpT7Nn13WvmFOvtKpFBeUHrDK+byvFZQuR67jm7ygV9sS4FrQm9CCy7o M7wuESsLqh5/KbpC6ydkJ0aEGVXLO2AwkZhgmMFN+sIkNowoShDfkQo9kJ5dSbZ9 kb/oFlrkfHV+gAWHdl+kdd8kpLv2IY0tlQg6u604dSHY5tdULIYDq/YwxtvH4toa gV59XOdU/WN4k5X8GhOMjxd7n0/3/NztBkCaZi3+Fk6Wm8RYR1qrwDO/DpN0Zvtb aj/a1O7imrZ8gYkHMjOfN+nF7/DxK8M/BE1dDkaxMckTLsc5+aMKiaLJ5vQyCwoE 6vRi4oX0szuhU9EthAvMCMIdYruwgKcDilsgJc+Da8CSA6YyfnTab/P6KUCZE21t AZtKgMPHzlMJV1N5ZNf3UL+S2qu5vZwI+jVzzgdtc8QWGo9YyPr7cckpopoGRHGy Q9DRI5b1SBNZX0bB0WKg =SNOE -----END PGP SIGNATURE----- --SBT+cnFS/G3NVgv4--
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |