From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: util-linux package missing usr/bin/script between 2.25 and 2.32
Date: Tue, 05 Mar 2019 13:59:00 -0000 [thread overview]
Message-ID: <06f45cb1-ccc3-50db-5a57-0b9168251671@SystematicSw.ab.ca> (raw)
In-Reply-To: <384FAB28-DA4F-47E0-A378-0467D69358E8@solidrocksystems.com>
On 2019-03-03 14:48, Vince Rice wrote:
>> On Mar 3, 2019, at 3:38 PM, Mason Giles wrote:
>> The /usr/bin/script program seems to have gone missing from the util-linux
>> package somewhere between the 2.25 and 2.32 timeframe.
>> As far as I can tell this program is still included upstream (and the
>> util-linux package still contains its /usr/bin/scriptreplay counterpart).
>> Any ideas what happened here? Is it possible to have this program reinstated?
> A search of the mailing list archives would have found the answer.
> https://cygwin.com/ml/cygwin/2019-02/msg00366.html
Which links to the last package upgrade announcement:
https://cygwin.com/ml/cygwin/2019-01/msg00136.html
which explains the issue: you can upgrade, with script and uuidd
unavailable for now, or downgrade to use the programs.
It's amazing what useful information you can find in package upgrade
announcements if you search for them online, or even just browse recent
cygwin-announce archives:
https://cygwin.com/ml/cygwin-announce/2019-01/msg00017.html
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
prev parent reply other threads:[~2019-03-05 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-03 21:38 Mason Giles
2019-03-03 21:48 ` Vince Rice
2019-03-05 13:59 ` Brian Inglis [this message]
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=06f45cb1-ccc3-50db-5a57-0b9168251671@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.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).