From: Jon Turney <jon.turney@dronecode.org.uk>
To: Houder <houder@xs4all.nl>, The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: setup 2.891release candidate - please test
Date: Thu, 22 Mar 2018 21:48:00 -0000 [thread overview]
Message-ID: <40ae5a91-02e9-36ce-6ebf-ff96f014edb5@dronecode.org.uk> (raw)
In-Reply-To: <8adaa9605805e133b7b68ec046862f78@smtp-cloud8.xs4all.net>
On 18/03/2018 18:23, Houder wrote:
>
>>> cd /var/log
>>> file setup.log *log-*
[...]
>
>>> 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).
It looks like this is just a bug (we are logging the string after it's
had the line terminators turned into CRLF for putting into a Windows
text box, but the logging mechanism expects LF line terminators)
Thanks for testing, and thanks for pointing this out.
--
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:[~2018-03-22 21:31 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
2018-03-22 21:48 ` Jon Turney [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=40ae5a91-02e9-36ce-6ebf-ff96f014edb5@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=houder@xs4all.nl \
/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).