8:19 a.m.
Am I the only one having this problem? I don't know exactly when it started
but all of a sudden all of the log output has DOS line endings and it's
very annoying. I have to run dox2unix on the logs to make them readable.
Thanks,
Richard
9:06 a.m.
On 1/30/20 9:19 AM, Richard Shaw wrote:
Am I the only one having this problem? I don't know exactly when
it started but all of a sudden all of the log output has DOS line endings and it's
very annoying. I have to run dox2unix on the logs to make them readable.
I am seeing that too, and you are right - it is very annoying.
Steve
9:34 a.m.
On Thu, Jan 30, 2020 at 7:21 AM Richard Shaw <hobbes1069(a)gmail.com> wrote:
Am I the only one having this problem? I don't know exactly when
it started but all of a sudden all of the log output has DOS line endings and it's
very annoying. I have to run dox2unix on the logs to make them readable.
It's even worse than that. Some of the lines have DOS line endings
and others have Unix line endings. In a recent root.log, for example,
the file starts off with Unix line endings, and then ...
DEBUG util.py:427: Unsharing. Flags: 1073741824
DEBUG util.py:427: Unsharing. Flags: 134217728
DEBUG util.py:598: Updating / installing...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That line is the first one with DOS line endings. That continues until....
DEBUG util.py:598: warning: group jjames does not exist - using root
DEBUG util.py:744: Child return code was: 0
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That line switches back to Unix line endings.
This pattern continues for the rest of the file. Whenever the two
"Unsharing" lines (with Unix line endings) show up, the very next line
has a DOS line ending and that persists until a "Child return code"
line, which again has a Unix line ending.
In build.log, the first few lines dealing with systemd-nspawn have
Unix line endings, then these lines have DOS line endings:
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1580256000
Wrote: /builddir/build/SRPMS/foo-1.0-1.fc32.src.rpm
As before the subsequent "Child return code" line returns to Unix line
endings. The next "Building target platforms" line switches back to
DOS line endings again, and that persists until the next "Child return
code" line.
--
Jerry James
http://www.jamezone.org/
12:02 p.m.
On Thu, 2020-01-30 at 08:19 -0600, Richard Shaw wrote:
Am I the only one having this problem? I don't know exactly when
it
started but all of a sudden all of the log output has DOS line
endings and it's very annoying. I have to run dox2unix on the logs to
make them readable.
I have the same question redirecting to buildsys Mailing list
Thanks,
Richard
_______________________________________________devel mailing list --
devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
--
Sérgio M. B.
7:44 p.m.
On Thu, Jan 30, 2020 at 06:02:33PM +0000, Sérgio Basto wrote:
On Thu, 2020-01-30 at 08:19 -0600, Richard Shaw wrote:
> Am I the only one having this problem? I don't know exactly when it
> started but all of a sudden all of the log output has DOS line
> endings and it's very annoying. I have to run dox2unix on the logs to
> make them readable.
I have the same question redirecting to buildsys Mailing list
Is this in local mock? Or koji? builds? Or both?
kevin
7:52 p.m.
On Thu, Jan 30, 2020 at 7:51 PM Kevin Fenzi <kevin(a)scrye.com> wrote:
On Thu, Jan 30, 2020 at 06:02:33PM +0000, Sérgio Basto wrote:
> On Thu, 2020-01-30 at 08:19 -0600, Richard Shaw wrote:
> > Am I the only one having this problem? I don't know exactly when it
> > started but all of a sudden all of the log output has DOS line
> > endings and it's very annoying. I have to run dox2unix on the logs to
> > make them readable.
>
> I have the same question redirecting to buildsys Mailing list
Is this in local mock? Or koji? builds? Or both?
Only in local mock as far as I know but browsers may not care...
Thanks,
Richard
11:05 p.m.
On Friday, January 31, 2020 2:44:21 AM CET Kevin Fenzi wrote:
On Thu, Jan 30, 2020 at 06:02:33PM +0000, Sérgio Basto wrote:
> On Thu, 2020-01-30 at 08:19 -0600, Richard Shaw wrote:
> > Am I the only one having this problem? I don't know exactly when it
> > started but all of a sudden all of the log output has DOS line
> > endings and it's very annoying. I have to run dox2unix on the logs to
> > make them readable.
>
> I have the same question redirecting to buildsys Mailing list
Is this in local mock? Or koji? builds? Or both?
Probably only local mock. Copr has a hotfix for this for a few days now,
and Koji uses --old-chroot.
That said, it is probably this issue:
https://github.com/rpm-software-management/mock/issues/432
which means that the trigger is updated systemd:
https://github.com/systemd/systemd/commit/de40a3037
This should be fixed in mock 'devel' branch, and it is soon to be released
(or try 'dnf copr enable @mock/mock'). Work-around is to explicitly use
--old-chroot.
Pavel
1549
days inactive
1550
days old
6 comments
6 participants
participants (6)
-
Jerry James -
Kevin Fenzi -
Pavel Raiskup -
Richard Shaw -
Steven A. Falco -
Sérgio Basto