fd424757a6
It was an oversight during v2 development for dib to start providing dib-run-parts. The intention was for dib to use a vendored dib-run-parts directly from $_LIB and have no dependencies on dib-utils at all. By exporting dib-run-parts, we created an unintentional conflict with the dib-utils package which provides the same script. Tools that depend on dib-utils are unaffected by this (os-refresh-config). The only tool that installs diskimage-builder and then assumes dib-run-parts is available in the path is instack. I have proposed Ibfe972208df40fa092b11b5419043524c903f1b4 to modify that to use our internal version. Change-Id: I149c345d38d761a49b3a6ccc4833482f09f1cd05
9 lines
No EOL
397 B
YAML
9 lines
No EOL
397 B
YAML
---
|
|
deprecations:
|
|
- |
|
|
dib no longer exports ``dib-run-parts``. Adding this was an
|
|
oversight made during v2 development, since ``dib-utils`` already
|
|
provides this. The ``dib-run-parts`` used internally
|
|
(``diskimage_builder/lib/dib-run-parts``) is not intended to be
|
|
used by external tools. If you require ``dib-run-parts``, you
|
|
should install the ``dib-utils`` package. |