From 9a78c40d6cada696415886d3ed5276dda8060c91 Mon Sep 17 00:00:00 2001 From: Pavel Raiskup Date: Fri, 15 Sep 2023 11:50:46 +0200 Subject: [PATCH] Mock v5.1 and configs 39.1 Created by commands: /usr/bin/tito tag --use-version=39.1 /usr/bin/tito tag --use-version=5.1 ./releng/generate-release-notes --use-version 5.1 --- .tito/packages/mock | 2 +- .tito/packages/mock-core-configs | 2 +- docs/Release-Notes-5.1.md | 156 ++++++++++++++++++ mock-core-configs/mock-core-configs.spec | 7 +- mock/mock.spec | 5 +- .../bootstrap-image-architecture-check.bugfix | 9 - .../bootstrap-image-fallback.feature | 9 - .../bootstrap-image-language.bugfix | 7 - .../buildroot-affecting-pkg-mgmt.feature.md | 7 - .../release-notes-next/docker-warning.feature | 4 - .../docs-for-config-opts.bugfix | 2 - .../release-notes-next/exit-status-90.feature | 3 - .../hiding-mounts-permissions.bugfix | 5 - .../installed-packages-sorted.feature | 3 - .../nspawn-and-proc-mounted.bugfix | 18 -- .../opensuse-leap-15-3-eol.config | 2 - .../opensuse-leap-15-5.config | 1 - .../orphanskill-br-in-bs.bugfix | 5 - .../package-managers-recommended.feature | 6 - .../podman-image-unmount.bugfix | 2 - .../podman-pull-error-reporting.bugfix | 2 - .../postinstall-exit-status.feature | 5 - .../postyum-called-again.bugfix | 3 - .../proc-filesystems.bugfix | 4 - releng/release-notes-next/rpm-ds.bugfix | 7 - .../scm-int-src-dir.feature | 3 - 26 files changed, 168 insertions(+), 111 deletions(-) create mode 100644 docs/Release-Notes-5.1.md delete mode 100644 releng/release-notes-next/bootstrap-image-architecture-check.bugfix delete mode 100644 releng/release-notes-next/bootstrap-image-fallback.feature delete mode 100644 releng/release-notes-next/bootstrap-image-language.bugfix delete mode 100644 releng/release-notes-next/buildroot-affecting-pkg-mgmt.feature.md delete mode 100644 releng/release-notes-next/docker-warning.feature delete mode 100644 releng/release-notes-next/docs-for-config-opts.bugfix delete mode 100644 releng/release-notes-next/exit-status-90.feature delete mode 100644 releng/release-notes-next/hiding-mounts-permissions.bugfix delete mode 100644 releng/release-notes-next/installed-packages-sorted.feature delete mode 100644 releng/release-notes-next/nspawn-and-proc-mounted.bugfix delete mode 100644 releng/release-notes-next/opensuse-leap-15-3-eol.config delete mode 100644 releng/release-notes-next/opensuse-leap-15-5.config delete mode 100644 releng/release-notes-next/orphanskill-br-in-bs.bugfix delete mode 100644 releng/release-notes-next/package-managers-recommended.feature delete mode 100644 releng/release-notes-next/podman-image-unmount.bugfix delete mode 100644 releng/release-notes-next/podman-pull-error-reporting.bugfix delete mode 100644 releng/release-notes-next/postinstall-exit-status.feature delete mode 100644 releng/release-notes-next/postyum-called-again.bugfix delete mode 100644 releng/release-notes-next/proc-filesystems.bugfix delete mode 100644 releng/release-notes-next/rpm-ds.bugfix delete mode 100644 releng/release-notes-next/scm-int-src-dir.feature diff --git a/.tito/packages/mock b/.tito/packages/mock index 29720b92b..7a34bccaa 100644 --- a/.tito/packages/mock +++ b/.tito/packages/mock @@ -1 +1 @@ -5.0-1 mock/ +5.1-1 mock/ diff --git a/.tito/packages/mock-core-configs b/.tito/packages/mock-core-configs index f9a4d41c2..ba9ed13d2 100644 --- a/.tito/packages/mock-core-configs +++ b/.tito/packages/mock-core-configs @@ -1 +1 @@ -39-1 mock-core-configs/ +39.1-1 mock-core-configs/ diff --git a/docs/Release-Notes-5.1.md b/docs/Release-Notes-5.1.md new file mode 100644 index 000000000..d19a6993c --- /dev/null +++ b/docs/Release-Notes-5.1.md @@ -0,0 +1,156 @@ +--- +layout: default +title: Release Notes - Mock v5.1 and mock-core-configs v39.1 +--- + +Released on 2023-09-15. + + +## New 5.1 features + +- We [implemented a convenience fallback][PR#1200] from **bootstrap-from-image** + to the slower **bootstrap-installed-DNF-from-host** for the cases when Podman + can not be used properly (when container image can not be pulled, image can + not be mounted, image architecture mismatch, Podman is not available or not + working - e.g. if run in non-privileged Docker, etc). + + There's also a new ["podman pull" backoff logic][commit#395fc07f796] that + makes Mock to retry Podman pulling for 120s (default). Feel free to adjust this + timeout by `config_opts["bootstrap_image_keep_getting"]` option. +- Mock [newly logs out][PR#1210] the package management toolset versions (e.g. + version of DNF, RPM, etc.) that is used for the buildroot installation. This + is a feature helping users to diagnose problems with buildroot installation + (minimal buildroot, `BuildRequires`, dynamic build requires, etc.). It might + seem like a trivial addition, but sometimes it isn't quite obvious where the + tooling comes from (is that from host? from bootstrap? was it downloaded + "pre-installed" with bootstrap image?). +- There's a [new "INFO" message][commit#8c7aad5680e8f86] raised when running + Podman in Docker, potentially without `docker run --privileged`. This should + decrease the confusion if Mock subsequently falls-back to non-default + `use_bootstrap_image=False`. See [issue#1184][] for more info. +- New exception `BootstrapError` was invented with (if not caught) returns with + exit status 90. This exception covers problems with the bootstrap chroot + preparation. +- The `package_state.py` plugin has been updated to sort the displayed list of + installed and available packages alphabetically (previously the list of packages + was printed in random order). +- Per [PR#1220][] discussion, Mock package newly `Recommends` having DNF5, DNF and + YUM package managers installed on host. These packages are potentially useful, + at least when the (default) bootstrap preparation mechanism (bootstrap image) + fails and the bootstrap needs to be installed with host's package management. + Previously Mock just "suggested" having them installed, which though used to + have almost zero practical effect (as Suggests are not installed by default). +- Mock now, at least on the best effort basis (if used with + `package_manager=dnf`), ["fails" with exit status 30][issue#42] if it isn't able + to process the `--postinstall` request (i.e. installing the built packages into + the target chroot). Previous Mock versions used to ignore (with warning) the + failed package installation attempts. +- The SCM logic [got a new option][PR#1197] + `config_opts['scm_opts']['int_src_dir']` that instructs Mock to search for + sources in a specified sub-directory. + + +### Bugfixes + +- Some container images Mock is using for initializing bootstrap chroot (e.g. + `centos:7`), do not provide all the needed architectures. Podman [though + silently pulls arch-incompatible + image](https://github.com/containers/podman/issues/19717), which caused + [hard-to-debug build failures](https://github.com/fedora-copr/copr/issues/2875). + Mock 5.1 therefore [implements a new assertion][PR#1199] failing the build + early, before mistakenly trying to run emulated "--forcearch" chroot leading to + failure. The assertion is exposed as a Python library call + `mockbuild.podman:podman_check_native_image_architecture()`. +- When bootstrap chroot is initialized from downloaded container image, it + typically contains `/etc/rpm/macros.image-language-conf` file with locale + filtering of some kind (per defaults from the fedora-kickstarts project). + This bootstrap configuration though affects the buildroot installation + (filtering l11n files from buildroot) and this is sometimes unexpected. + Mock now [automatically removes the macro file][PR#1189], see + [issue#1181][] for more info. +- Manual page has been fixed to better describe the `--config-opts=option=value` + semantics. +- Mock uses `tmpfs` mountpoints in some cases just to hide (on host) some rather + complicated mount structures (done in chroot/separate mount namespace). These + "barrier" mount points though used to have the default `mode=0777` potentially + allowing anyone to accidentally write there and cause e.g. unmount failures. + New Mock [uses `mode=0755`][PR#1213] instead. +- The `systemd-nspawn` utility [v253.9 started + failing](https://github.com/systemd/systemd/issues/29174) with pre-mounted + `/proc` directory (used like `systemd-nspawn -D `). + The resulting Mock error, per several reports like [this + one](https://github.com/fedora-copr/copr/issues/2906), was rather cryptic: + + # /usr/bin/systemd-nspawn -q -M 50743cd0fe0a4142b9b2dbb2c5f8eea6 -D /var/lib/mock/fedora-39-x86_64-bootstrap-1694347273.676351/root + Failed to mount /proc/sys (type n/a) on /proc/sys (MS_BIND ""): Invalid argument + Failed to create /user.slice/user-1000.slice/session-12.scope/payload subcgroup: Structure needs cleaning + + Previous versions of `systemd-nspawn` silently over-mounted the `/proc` + filesystem so Mock simply could _always_ pre-mount `/proc` (with + `--isolation=simple` it is still needed). + + To work-around this problem, new Mock now [stopped "pre-mounting"][PR#1214] + `/proc` directory when `--isolation=nspawn` (default) and the package + management downloaded with bootstrap image is used for **installing packages + into the bootstrap chroot**. +- Mock automatically kills "orphan" processes started in buildroot (unwanted + "daemons"). These are typically started by DNF installation that trigger some + buggy scriptlet. The corresponding code has been [moved][PR#1214] to a better + place which assures that such processes are **always** killed before "buildroot + in bootstrap" recursive bind-mount is unmounted. +- Mock properly dumps Podman's standard error output to logs to allow the user + better diagnose related errors. Per [issue#1191][] report. +- Mock 5.0 release contained a bug causing that `postyum` hooks (in Mock plugins) + were not called. In turn, e.g. `root_cache` locking mechanism [was + broken][issue#1186] causing Mock to wait for the lock unnecessary long. +- Previous version of Mock used to bind-mount `/proc` and `/proc/filesystems` in + wrong order, eventually causing that `/proc/filesystems` was not visible (this + could affect some scriptlests from packages installed into such a chroot). This + [has been fixed now][PR#1214]. +- The `--installdeps foo.spec` feature is implemented using the RPM Python API. + Previously we used the method `hdr.dsFromHeader()` to get the list of + `BuildRequires`. This method has been removed from the Python RPM API (rpm + v4.19) in favor of the long-enough existing `rpm.ds(hdr, ...)` method. Mock + [has started using `rpm.ds()` API call][PR#1223] to fix the [`AttributeError: + 'rpm.hdr' object has no attribute 'dsFromHeader'`][issue#1203] traceback on + newer systems (e.g. Fedora 40+). +- The `--shell` standard output is no longer affected by `podman image unmount` + output executed in the background (prints out the image ID). + + +### mock-core-configs v39.1 changes + +- Mageia 9 to branched (released recently) and Cauldron retargeted to Mageia 10. +- openSUSE Leap 15.3 became end-of-life at the end of 2022 and the corresponding + Mock configuration is now [end-of-life][PR#1175], too. +- openSUSE Leap 15.5 configuration [added][PR#1175]. + + +**Following contributors contributed to this release:** + + * Evan Goode + * Miroslav Suchý + * Neal Gompa + * Pavel Raiskup + * Takuya Wakazono + +Thank you. + +[PR#1200]: https://github.com/rpm-software-management/mock/pull/1200 +[issue#1186]: https://github.com/rpm-software-management/mock/issues/1186 +[PR#1220]: https://github.com/rpm-software-management/mock/pull/1220 +[issue#1203]: https://github.com/rpm-software-management/mock/issues/1203 +[issue#42]: https://github.com/rpm-software-management/mock/issues/42 +[PR#1189]: https://github.com/rpm-software-management/mock/pull/1189 +[issue#1184]: https://github.com/rpm-software-management/mock/issues/1184 +[commit#395fc07f796]: https://github.com/rpm-software-management/mock/commit/395fc07f796 +[PR#1210]: https://github.com/rpm-software-management/mock/pull/1210 +[PR#1197]: https://github.com/rpm-software-management/mock/pull/1197 +[issue#1191]: https://github.com/rpm-software-management/mock/issues/1191 +[PR#1199]: https://github.com/rpm-software-management/mock/pull/1199 +[commit#8c7aad5680e8f86]: https://github.com/rpm-software-management/mock/commit/8c7aad5680e8f86 +[PR#1223]: https://github.com/rpm-software-management/mock/pull/1223 +[issue#1181]: https://github.com/rpm-software-management/mock/issues/1181 +[PR#1213]: https://github.com/rpm-software-management/mock/pull/1213 +[PR#1175]: https://github.com/rpm-software-management/mock/pull/1175 +[PR#1214]: https://github.com/rpm-software-management/mock/pull/1214 diff --git a/mock-core-configs/mock-core-configs.spec b/mock-core-configs/mock-core-configs.spec index 10c9d366f..7037edb8a 100644 --- a/mock-core-configs/mock-core-configs.spec +++ b/mock-core-configs/mock-core-configs.spec @@ -3,7 +3,7 @@ %endif Name: mock-core-configs -Version: 39 +Version: 39.1 Release: 1%{?dist} Summary: Mock core config files basic chroots @@ -144,6 +144,11 @@ fi %ghost %config(noreplace,missingok) %{_sysconfdir}/mock/default.cfg %changelog +* Fri Sep 15 2023 Pavel Raiskup 39.1-1 +- Add openSUSE Leap 15.5 (neal@gompa.dev) +- Move openSUSE Leap 15.3 to EOL (neal@gompa.dev) +- Mageia 9 branched, Mageia Cauldron retargeted to Mageia 10 (neal@gompa.dev) + * Wed Aug 09 2023 Pavel Raiskup 39-1 - new upstream release, per https://rpm-software-management.github.io/mock/Release-Notes-5.0 diff --git a/mock/mock.spec b/mock/mock.spec index 446270456..b11b92591 100644 --- a/mock/mock.spec +++ b/mock/mock.spec @@ -9,7 +9,7 @@ Summary: Builds packages inside chroots Name: mock -Version: 5.0.post1 +Version: 5.1 Release: 1%{?dist} License: GPL-2.0-or-later # Source is created by @@ -275,6 +275,9 @@ pylint-3 py/mockbuild/ py/*.py py/mockbuild/plugins/* || : %dir %{_datadir}/cheat %changelog +* Fri Sep 15 2023 Pavel Raiskup 5.1-1 +- new upstream release, per https://rpm-software-management.github.io/mock/Release-Notes-5.1 + * Wed Aug 09 2023 Pavel Raiskup 5.0-1 - new upstream release, per https://rpm-software-management.github.io/mock/Release-Notes-5.0 diff --git a/releng/release-notes-next/bootstrap-image-architecture-check.bugfix b/releng/release-notes-next/bootstrap-image-architecture-check.bugfix deleted file mode 100644 index b32b5ce0f..000000000 --- a/releng/release-notes-next/bootstrap-image-architecture-check.bugfix +++ /dev/null @@ -1,9 +0,0 @@ -Some container images Mock is using for initializing bootstrap chroot (e.g. -`centos:7`), do not provide all the needed architectures. Podman [though -silently pulls arch-incompatible -image](https://github.com/containers/podman/issues/19717), which caused -[hard-to-debug build failures](https://github.com/fedora-copr/copr/issues/2875). -Mock 5.1 therefore [implements a new assertion][PR#1199] failing the build -early, before mistakenly trying to run emulated "--forcearch" chroot leading to -failure. The assertion is exposed as a Python library call -`mockbuild.podman:podman_check_native_image_architecture()`. diff --git a/releng/release-notes-next/bootstrap-image-fallback.feature b/releng/release-notes-next/bootstrap-image-fallback.feature deleted file mode 100644 index 3ef3a8742..000000000 --- a/releng/release-notes-next/bootstrap-image-fallback.feature +++ /dev/null @@ -1,9 +0,0 @@ -We [implemented a convenience fallback][PR#1200] from **bootstrap installed from -image** to slower **bootstrap installed with host's DNF** for the cases when -Podman can not be used properly (container image can not be pulled, image can -not be mounted, image architecture mismatch, Podman is not available or not -working - e.g. if run in non-privileged Docker, etc). - -There's also a new ["podman pull" backoff logic][commit#395fc07f796] that -makes Mock to retry Podman pulls for 120s by default. Feel free to adjust this -timeout by `config_opts["bootstrap_image_keep_getting"]` option. diff --git a/releng/release-notes-next/bootstrap-image-language.bugfix b/releng/release-notes-next/bootstrap-image-language.bugfix deleted file mode 100644 index 01801733b..000000000 --- a/releng/release-notes-next/bootstrap-image-language.bugfix +++ /dev/null @@ -1,7 +0,0 @@ -When bootstrap chroot is initialized from downloaded container image, it -typically contains `/etc/rpm/macros.image-language-conf` file with locale -filtering of some kind (per defaults from the fedora-kickstarts project). -This bootstrap configuration though affects the buildroot installation -(filtering l11n files from buildroot) and this is sometimes unexpected. -Mock now [automatically removes the macro file][PR#1189], see -[issue#1181][] for more info. diff --git a/releng/release-notes-next/buildroot-affecting-pkg-mgmt.feature.md b/releng/release-notes-next/buildroot-affecting-pkg-mgmt.feature.md deleted file mode 100644 index 696aa34a2..000000000 --- a/releng/release-notes-next/buildroot-affecting-pkg-mgmt.feature.md +++ /dev/null @@ -1,7 +0,0 @@ -Mock [newly logs out][PR#1210] the package management toolset versions (e.g. -version of DNF, RPM, etc.) that is used for the buildroot intallation. This is -a feature helping users to diagnose problems with buildroot installation -(minimal buildroot, `BuildRequires`, dynamic build requires, etc.). It might -seem like a trival addition, but sometimes it isn't quite obvious where the -tooling comes from (is that from host? from bootstrap? was it downloaded -"pre-installed" with bootstrap image?). diff --git a/releng/release-notes-next/docker-warning.feature b/releng/release-notes-next/docker-warning.feature deleted file mode 100644 index 12f04b4f7..000000000 --- a/releng/release-notes-next/docker-warning.feature +++ /dev/null @@ -1,4 +0,0 @@ -There's a [new "INFO" message][commit#8c7aad5680e8f86] raised when running -Podman in Docker, potentially without `docker run --privileged`. This should -decrease the confusion if Mock subsequently falls-back to non-default -`use_bootstrap_image=False`. See [issue#1184][] for more info. diff --git a/releng/release-notes-next/docs-for-config-opts.bugfix b/releng/release-notes-next/docs-for-config-opts.bugfix deleted file mode 100644 index 5d22d52d8..000000000 --- a/releng/release-notes-next/docs-for-config-opts.bugfix +++ /dev/null @@ -1,2 +0,0 @@ -Manual page has been fixed to better describe the `--config-opts=option=value` -semantics. diff --git a/releng/release-notes-next/exit-status-90.feature b/releng/release-notes-next/exit-status-90.feature deleted file mode 100644 index d76f82d8c..000000000 --- a/releng/release-notes-next/exit-status-90.feature +++ /dev/null @@ -1,3 +0,0 @@ -New exception `BootstrapError` was invented with (if not catched) returns with -exit status 90. This exception covers problems with the bootstrap chroot -preparation. diff --git a/releng/release-notes-next/hiding-mounts-permissions.bugfix b/releng/release-notes-next/hiding-mounts-permissions.bugfix deleted file mode 100644 index d806fb38d..000000000 --- a/releng/release-notes-next/hiding-mounts-permissions.bugfix +++ /dev/null @@ -1,5 +0,0 @@ -Mock uses `tmpfs` mountpoints in some cases just to hide (on host) some rather -complicated mount structures (done in chroot/separate mount namespace). These -"barrier" mount points though used to have the default `mode=0777` potentially -allowing anyone to accidentally write there and cause e.g. unmount failures. -New Mock [uses `mode=0755`][PR#1213] instead. diff --git a/releng/release-notes-next/installed-packages-sorted.feature b/releng/release-notes-next/installed-packages-sorted.feature deleted file mode 100644 index c47106091..000000000 --- a/releng/release-notes-next/installed-packages-sorted.feature +++ /dev/null @@ -1,3 +0,0 @@ -The `package_state.py` plugin has been updated to sort the displayed list of -installed and available packages alphabetically (previously the list of packages -was printed in random order). diff --git a/releng/release-notes-next/nspawn-and-proc-mounted.bugfix b/releng/release-notes-next/nspawn-and-proc-mounted.bugfix deleted file mode 100644 index 16f412b0b..000000000 --- a/releng/release-notes-next/nspawn-and-proc-mounted.bugfix +++ /dev/null @@ -1,18 +0,0 @@ -The `systemd-nspawn` utility [v253.9 started -failing](https://github.com/systemd/systemd/issues/29174) with pre-mounted -`/proc` directory (used like `systemd-nspawn -D `). -The resulting Mock error, per several reports like [this -one](https://github.com/fedora-copr/copr/issues/2906), was rather cryptic: - - # /usr/bin/systemd-nspawn -q -M 50743cd0fe0a4142b9b2dbb2c5f8eea6 -D /var/lib/mock/fedora-39-x86_64-bootstrap-1694347273.676351/root - Failed to mount /proc/sys (type n/a) on /proc/sys (MS_BIND ""): Invalid argument - Failed to create /user.slice/user-1000.slice/session-12.scope/payload subcgroup: Structure needs cleaning - -Previous versions of `systemd-nspawn` silently over-mounted the `/proc` -filesystem so Mock simply could _always_ pre-mount `/proc` (with -`--isolation=simple` it is still needed). - -To work-around this problem, new Mock now [stopped "pre-mounting"][PR#1214] -`/proc` directory when `--isolation=nspawn` (default) and the package -management downloaded with bootstrap image is used for **installing packages -into the bootstrap chroot**. diff --git a/releng/release-notes-next/opensuse-leap-15-3-eol.config b/releng/release-notes-next/opensuse-leap-15-3-eol.config deleted file mode 100644 index c1b613c96..000000000 --- a/releng/release-notes-next/opensuse-leap-15-3-eol.config +++ /dev/null @@ -1,2 +0,0 @@ -openSUSE Leap 15.3 became end-of-life at the end of 2022 and the corresponding -Mock configuration is now [end-of-life][PR#1175], too. diff --git a/releng/release-notes-next/opensuse-leap-15-5.config b/releng/release-notes-next/opensuse-leap-15-5.config deleted file mode 100644 index 7ee073ade..000000000 --- a/releng/release-notes-next/opensuse-leap-15-5.config +++ /dev/null @@ -1 +0,0 @@ -openSUSE Leap 15.5 configuration [added][PR#1175]. diff --git a/releng/release-notes-next/orphanskill-br-in-bs.bugfix b/releng/release-notes-next/orphanskill-br-in-bs.bugfix deleted file mode 100644 index 4a7162a82..000000000 --- a/releng/release-notes-next/orphanskill-br-in-bs.bugfix +++ /dev/null @@ -1,5 +0,0 @@ -Mock automatically kills "orphan" processes started in buildroot (unwanted -"daemons"). These are typically started by DNF installation that trigger some -buggy scriptlet. The corresponding code has been [moved][PR#1214] to a better -place which assures that such processes are **always** killed before "buildroot -in bootstrap" recursive bind-mount is unmounted. diff --git a/releng/release-notes-next/package-managers-recommended.feature b/releng/release-notes-next/package-managers-recommended.feature deleted file mode 100644 index 026e91722..000000000 --- a/releng/release-notes-next/package-managers-recommended.feature +++ /dev/null @@ -1,6 +0,0 @@ -Per [PR#1220][] discussion, Mock package newly `Recommends` having DNF5, DNF and -YUM package managers installed on host. These packages are potentially useful, -at least when the (default) bootstrap preparation mechansim (bootstrap image) -fails and the bootstrap needs to be installed with host's package management. -Previously Mock just "suggested" having them installed, which though used to -have almost zero practical effect (as Suggests are not installed by default). diff --git a/releng/release-notes-next/podman-image-unmount.bugfix b/releng/release-notes-next/podman-image-unmount.bugfix deleted file mode 100644 index a2f037fac..000000000 --- a/releng/release-notes-next/podman-image-unmount.bugfix +++ /dev/null @@ -1,2 +0,0 @@ -The `--shell` standard output is no longer affected by `podman image unmount` -output executed in the background (prints out the image ID). diff --git a/releng/release-notes-next/podman-pull-error-reporting.bugfix b/releng/release-notes-next/podman-pull-error-reporting.bugfix deleted file mode 100644 index cb1f234b7..000000000 --- a/releng/release-notes-next/podman-pull-error-reporting.bugfix +++ /dev/null @@ -1,2 +0,0 @@ -Mock properly dumps Podman's standard error output to logs to allow the user -better diagnose related errors. Per [issue#1191][] report. diff --git a/releng/release-notes-next/postinstall-exit-status.feature b/releng/release-notes-next/postinstall-exit-status.feature deleted file mode 100644 index e88fac6a9..000000000 --- a/releng/release-notes-next/postinstall-exit-status.feature +++ /dev/null @@ -1,5 +0,0 @@ -Mock now, at least on the best effort basis (if used with -`package_manager=dnf`), ["fails" with exit status 30][issue#42] if it isn't able -to process the `--postinstall` request (ie. installing the built packages into -the target chroot). Previous Mock versions used to ignore (with warning) the -failed package installation attempts. diff --git a/releng/release-notes-next/postyum-called-again.bugfix b/releng/release-notes-next/postyum-called-again.bugfix deleted file mode 100644 index fe37bd74e..000000000 --- a/releng/release-notes-next/postyum-called-again.bugfix +++ /dev/null @@ -1,3 +0,0 @@ -Mock 5.0 release contained a bug causing that `postyum` hooks (in Mock plugins) -were not called. In turn, e.g. `root_cache` locking mechanism [was -broken][issue#1186] causing Mock to wait for the lock unnecessary long. diff --git a/releng/release-notes-next/proc-filesystems.bugfix b/releng/release-notes-next/proc-filesystems.bugfix deleted file mode 100644 index 723f37c0c..000000000 --- a/releng/release-notes-next/proc-filesystems.bugfix +++ /dev/null @@ -1,4 +0,0 @@ -Previous version of Mock used to bind-mount `/proc` and `/proc/filesystems` in -wrong order, eventually causing that `/proc/filesystems` was not visible (this -could affect some scriptlests from packages installed into such a chroot). This -[has been fixed now][PR#1214]. diff --git a/releng/release-notes-next/rpm-ds.bugfix b/releng/release-notes-next/rpm-ds.bugfix deleted file mode 100644 index dc1ba78ae..000000000 --- a/releng/release-notes-next/rpm-ds.bugfix +++ /dev/null @@ -1,7 +0,0 @@ -The `--installdeps foo.spec` feature is implemented using the RPM Python API. -Previously we used the method `hdr.dsFromHeader()` to get the list of -`BuildRequires`. This method has been removed from the Python RPM API (rpm -v4.19) in favor of the long-enough existing `rpm.ds(hdr, ...)` method. Mock -[has started using `rpm.ds()` API call][PR#1223] to fix the [`AttributeError: -'rpm.hdr' object has no attribute 'dsFromHeader'`][issue#1203] traceback on -newer systems (e.g. Fedora 40+). diff --git a/releng/release-notes-next/scm-int-src-dir.feature b/releng/release-notes-next/scm-int-src-dir.feature deleted file mode 100644 index 26fea2b6b..000000000 --- a/releng/release-notes-next/scm-int-src-dir.feature +++ /dev/null @@ -1,3 +0,0 @@ -The SCM logic [got a new option][PR#1197] -`config_opts['scm_opts']['int_src_dir']` that instructs Mock to search for -sources in a specified sub-directory.