From: Marco Atzeri <marco.atzeri@gmail.com>
To: Ian Lambert <ian.lambert_42@yahoo.com>, cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: lapack-3.7.0-1
Date: Thu, 12 Jan 2017 11:59:00 -0000 [thread overview]
Message-ID: <f869b6dd-2bf6-5f67-9e32-23a5fb5762c3@gmail.com> (raw)
In-Reply-To: <E80262C8-FC62-4B45-8BA5-4E50FE412DA0@yahoo.com>
On 11/01/2017 21:29, Ian Lambert wrote:
> On January 11, 2017 3:41:42 AM EST, Marco Atzeri wrote:
>> To: cygwin-announce@cygwin.com
>> Subject: Updated: lapack-3.7.0-1
>>
>> New versions lapack-3.7.0-1 of
>>
>> lapack (source)
>> liblapack0
>> liblapack-devel
>> liblapack-doc
>>
>> are available in the Cygwin distribution, 32 and 64 bit :
>>
>
> Is anyone else having problems with ...-Doc hanging with a pop-up, "unable to extract /use/share/man/man3/zhbev.3.gz. The file is in use or some other error occurred. Please stop all cygwin processes and select retry or select continue to go on anyway (the file will be updated after a reboot)."
> ?
>
> Then when I hit continue, setup hangs there until hitting cancel. I've tried a few times, uninstall and reinstall.
>
The files uploaded seem fine.
Can you check the one you downloaded with
tar -tf liblapack-doc-3.7.0-1.tar.xz
If damaged, remove it and try to download it again
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
next prev parent reply other threads:[~2017-01-12 11:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 10:08 Marco Atzeri
2017-01-11 20:30 ` Ian Lambert via cygwin
2017-01-12 11:59 ` Marco Atzeri [this message]
2017-04-26 1:12 ` Erik Bray
2017-04-26 23:18 ` Marco Atzeri
[not found] <126582986.1855303.1484238675795.ref@mail.yahoo.com>
2017-01-12 16:31 ` Ian Lambert via cygwin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f869b6dd-2bf6-5f67-9e32-23a5fb5762c3@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=ian.lambert_42@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).