particle-os/debian-koji
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix typos

Browse source
This commit is contained in:
Mike McLean 2018-05-09 17:16:31 -04:00
parent 1f8848c372
commit 701f9a9a0e
1 changed files with 6 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/source/release_notes_1.16.rst
View file

@ -95,8 +95,8 @@ If the ``log_timestamps`` option is enabled in ``kojid.conf``, then
the builder will record a separate timestamp file for each log file
in a build.
The filename for the timestamp file is the generated by taking the name
of the log file and appending ``-ts.log``. So ``build.log`` will have a
The filename for the timestamp file is generated by taking the name
of the log file and appending ``-ts.log``. So ``build.log`` will have
timestamp data in ``build.log-ts.log``.
The format of the timestamp log is plain text with each line showing
@ -110,9 +110,10 @@ Builder option: chroot_tmpdir
The new ``chroot_tmpdir`` option controls which directory within buildroots
is used for various temporary data by the Koji builder daemon.
Previously with was hardcoded to ``/builddir/tmp``, which created problems
Previously this was hardcoded to ``/builddir/tmp``, which created problems
with modern versions of mock.
The default value is ``/builddir/tmp``.
The default value is ``/chroot_tmpdir``.
Add internal_dev_setup option to runroot config
@ -249,4 +250,4 @@ The ``migrateImage`` call hub call has been removed.
This call was added in version 1.8 (April 2013)
as a one-time tool for migrating images from the old model (no build entry)
to the new model (image build type). It was only available if the
EnableImageMigration is set on the hub.
EnableImageMigration option was set on the hub.