diff --git a/mock-core-configs/mock-core-configs.spec b/mock-core-configs/mock-core-configs.spec index 8b9da289d..5fb390f41 100644 --- a/mock-core-configs/mock-core-configs.spec +++ b/mock-core-configs/mock-core-configs.spec @@ -24,7 +24,7 @@ Provides: mock-configs # distribution-gpg-keys contains GPG keys used by mock configs Requires: distribution-gpg-keys >= 1.98 # specify minimal compatible version of mock -Requires: mock >= 5.0 +Requires: mock >= 5.4.post1 Requires: mock-filesystem Requires(post): coreutils diff --git a/releng/release-notes-next/init-and-ownership-problems.bugfix b/releng/release-notes-next/init-and-ownership-problems.bugfix new file mode 100644 index 000000000..d3b9080ac --- /dev/null +++ b/releng/release-notes-next/init-and-ownership-problems.bugfix @@ -0,0 +1,17 @@ +Mock [has been][PR#1322] [fixed][commit#27dde5da] so that it no longer +inadvertently changes the group ownership of the in-chroot $HOME directory +to the wrong group ID. In previous versions of Mock, the group ownership +was changed to the effective group ID of the user on the host that +executed Mock. This could confuse some tools during the build process, as +they might want to create similarly owned files at the `rpmbuild` time +(but that assumption would be incorrect, such GID doesn't exist +in-chroot). Now, Mock changes the files to the `mockbuild:mock` +ownership, where the `mock` group ID is always 135 (the same GID on host +and in-chroot). This matches the effective GID for the `rpmbuild` +process, ensuring that the tools executed during the build process have +full control over such files. + +While on this, Mock was also [optimized][commit#db64d468202] to do this +ownership change before, and only if, the `rpmbuild` process is started +(so e.g. plain `mock --chroot` commands do not touch the file ownership at +all). diff --git a/releng/release-notes-next/mageia-7-eol.config b/releng/release-notes-next/mageia-7-eol.config new file mode 100644 index 000000000..b329a09ca --- /dev/null +++ b/releng/release-notes-next/mageia-7-eol.config @@ -0,0 +1 @@ +Mageia 7 configs [marked as end-of-life][PR#1316]. diff --git a/releng/release-notes-next/mageia-cross-arch.config b/releng/release-notes-next/mageia-cross-arch.config new file mode 100644 index 000000000..61c43c00a --- /dev/null +++ b/releng/release-notes-next/mageia-cross-arch.config @@ -0,0 +1,2 @@ +Mageia config files started using the `{{ repo_arch }}` option to fix the +[cross-arch builds][issue#1317]. diff --git a/releng/release-notes-next/mock-filesystem-deps.bugfix b/releng/release-notes-next/mock-filesystem-deps.bugfix new file mode 100644 index 000000000..80bb45091 --- /dev/null +++ b/releng/release-notes-next/mock-filesystem-deps.bugfix @@ -0,0 +1,3 @@ +The `mock` package has been fixed to depend on precisely the same version +of `mock-filesystem` sub-package (product of the same rpm build). This is +to protect against incompatible Mock sub-package installations. diff --git a/releng/release-notes-next/openmandriva-i686-eol.config b/releng/release-notes-next/openmandriva-i686-eol.config new file mode 100644 index 000000000..3b368343c --- /dev/null +++ b/releng/release-notes-next/openmandriva-i686-eol.config @@ -0,0 +1,2 @@ +The OpenMandriva i686 chroots [have been marked as end-of-life][PR#1315], fixing +[issue#987][] and [issue#1012][]. diff --git a/releng/release-notes-next/percent-interpolation-in-dnf-config.bugfix b/releng/release-notes-next/percent-interpolation-in-dnf-config.bugfix new file mode 100644 index 000000000..2ccde3d4b --- /dev/null +++ b/releng/release-notes-next/percent-interpolation-in-dnf-config.bugfix @@ -0,0 +1,9 @@ +Mock parses the DNF configuration specified in `config_opts["dnf.conf"]` itself +to perform some post-processing tasks, such as bind-mounting the on-host repo +directories into the bootstrap chroot based on this DNF config. In previous +versions of Mock, there was an issue where it failed to parse the DNF config if +some of the DNF options contained the '%' symbol. This was due to Python's +ConfigParser raising an %-interpolation exception that was ignored but Mock, but +resulting in Mock ignoring the rest of the config file and finishing without +performing the mentioned bind-mounts. This bug has been fixed, and the '%' sign +is no longer considered to be a special Python ConfigParser character. diff --git a/releng/release-notes-next/report-file-system-type.feature b/releng/release-notes-next/report-file-system-type.feature index 7d2acfdae..0fde77cee 100644 --- a/releng/release-notes-next/report-file-system-type.feature +++ b/releng/release-notes-next/report-file-system-type.feature @@ -6,7 +6,7 @@ Filesystem Size Used Avail Use% Mou /dev/mapper/luks-3aa4fbe3-5a19-4025-b70c-1d3038b76bd4 399G 9.1G 373G 3% / ~~~ -Newly, also file system type is reported: +Newly, [also file system type is reported][issue#1263]: ~~~ Filesystem Type Size Used Avail Use% Mounted on diff --git a/releng/release-notes-next/use_host_shadow_utils.config b/releng/release-notes-next/use_host_shadow_utils.config index 5ef50b9a1..1ebabd5e5 100644 --- a/releng/release-notes-next/use_host_shadow_utils.config +++ b/releng/release-notes-next/use_host_shadow_utils.config @@ -1,4 +1,4 @@ -Added a config option called "use_host_shadow_utils", to account for situations where +[Added][PR#1283] a config option called "use_host_shadow_utils", to account for situations where users have host shadow-utils configurations that cannot provision or destroy users and groups in the buildroot; one example of this kind of configuration is using FreeIPA-provided subids on the buildhost. The option defaults to True since mock has made a conscious