public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: setup 2.891release candidate - please test
Date: Sun, 18 Mar 2018 19:36:00 -0000	[thread overview]
Message-ID: <8adaa9605805e133b7b68ec046862f78@smtp-cloud8.xs4all.net> (raw)
In-Reply-To: <62924e28-4b71-02cc-d4c7-d5fd7e7020f6@dronecode.org.uk>

On Thu, 15 Mar 2018 23:32:15, Jon Turney wrote:
> 
> A new setup release candidate is available at:
> 
>    https://cygwin.com/setup/setup-2.891.x86_64.exe (64 bit version)
>    https://cygwin.com/setup/setup-2.891.x86.exe    (32 bit version)
> 
> Please test and report any problems here.

As requested, I carried out some testing ...

>> uname -a
CYGWIN_NT-6.1 Seven 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin
>> file --version
file-5.30
magic file from /usr/share/misc/magic

>> cd /var/log
>> file setup.log *log-*
setup.log:        ASCII text, with CRLF, CR line terminators <====
setup.log-1.full: ASCII text, with very long lines, with CRLF line terminators
setup.log-2.full: ASCII text, with very long lines, with CRLF line terminators
setup.log-3.full: ASCII text, with very long lines, with CRLF line terminators
setup.log-4.full: ASCII text, with very long lines, with CRLF line terminators
setup.log-5.full: ASCII text, with very long lines, with CRLF line terminators
setup.log-6.full: ASCII text, with very long lines, with CRLF line terminators
setup.log-7.full: ASCII text, with very long lines, with CRLF, CR line terminators <====
setup.log-8.full: ASCII text, with very long lines, with CRLF, CR line terminators <====

>> grep '^M^M' setup.log-8.full
2018/03/18 14:06:50 Problem 1/1
nothing provides liblz4_1 needed by libarchive13-3.3.2-1
Solution 1/1 (default)
  - do not ask to install bsdtar-3.3.2-1
>> # apparently, problem reporting by libsolv causes an additional CR ... why?

Q:

Would it be possible to prevent the additional CR from showing up in the log
file? It is visible when the log file is examined by means of vi(m).

Henri



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

  parent reply	other threads:[~2018-03-18 18:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 23:41 Jon Turney
2018-03-16 22:13 ` Robert Cohen
2018-03-22 21:26   ` Jon Turney
2018-03-23  0:15     ` Robert Cohen
2018-03-17 17:14 ` Steven Penny
2018-03-18 19:36 ` Houder [this message]
2018-03-22 21:48   ` Jon Turney

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=8adaa9605805e133b7b68ec046862f78@smtp-cloud8.xs4all.net \
    --to=houder@xs4all.nl \
    --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).