fixup doubled-logs by predictable bootstrap resultdir (GH#539, #1805631)
fix --chain --isolation=simple with external URLs (GH#542)
option --orphanskill fixed for --isolation=simple --bootstrap-chroot
orphan processes are now also killed "postyum", right after the installation
trasactions are executed to also kill daemons started from scriptlets (GH#183)
EL7 fix - use 'private' mount option for <bootsrap_root>/<root>, not 'rprivate'
ceanup rpmdb before checking installed packages (fixes builds against target
chroots that have different rpmdb backend, e.g. SQLite on F33+)
mock-core-configs-32.6-1
the site-defaults.cfg file moved from mock to mock-core-configs
new option config_opts['isolation'], obsoletes 'use_nspawn'
declare minimal version of mock, and set this to v2.2 as we use the new
'isolation' config option now, and we provide site-defaults.cfg file
specify amazonlinux bootstrap image, to fix --use-bootstrap-image
allow to replace mock-core-configs by packages that 'Provides: mock-configs'
Using [1] as test source RPM. I get the following log message:
Can not load RPM file: /var/lib/mock/epel-8-x86_64/result/python3-distroinfo-0.3.2-2.el8.noarch.rpm.
Could not open: /var/lib/mock/epel-8-x86_64/result/python3-distroinfo-0.3.2-2.el8.noarch.rpm
WARNING: Failed install built packages
As a workaround, I can use --no-bootstrap-chroot, but the default configuration is broken.
Using [1] as test source RPM. I get the following log message:
Can not load RPM file: /var/lib/mock/epel-8-x86_64/result/python3-distroinfo-0.3.2-2.el8.noarch.rpm.
Could not open: /var/lib/mock/epel-8-x86_64/result/python3-distroinfo-0.3.2-2.el8.noarch.rpm
WARNING: Failed install built packages
As a workaround, I can use --no-bootstrap-chroot, but the default configuration is broken.
@jpena, thanks for the update. Please use --no-bootstrap-chroot if you want to
use --postinstall. The --postinstall option is not yet fixed, and fix will be in v2.3
hopefully. I don't want to skip the update only because of this small problem
(ie fedora got the updates, and nobody noticed this so far).
@jpena, thanks for the update. Please use --no-bootstrap-chroot if you want to
use --postinstall. The --postinstall option is not yet fixed, and fix will be in v2.3
hopefully. I don't want to skip the update only because of this small problem
(ie fedora got the updates, and nobody noticed this so far).
@jpena, thanks for the update. Please use --no-bootstrap-chroot if you want to
use --postinstall. The --postinstall option is not yet fixed, and fix will be in v2.3
hopefully. I don't want to skip the update only because of this small problem
(ie fedora got the updates, and nobody noticed this so far).
Meh, yeah, bodhi sucks these days :-( anyways, since the negative karma turned off the
auto push - I will very likely push the update to stable anyways once it is in 30 days of
testing. Unless some much more serious problems appear.
This update has been submitted for stable by praiskup.
This update has been submitted for testing by praiskup.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted mock-2.0-2.el8, and has inherited its bugs and notes.
This update's test gating status has been changed to 'ignored'.
praiskup edited this update.
praiskup edited this update.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
praiskup edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by praiskup.
This update has been pushed to testing.
praiskup edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by praiskup.
praiskup edited this update.
praiskup edited this update.
This update's test gating status has been changed to 'greenwave_failed'.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Installs correctly. Works correctly for me.
Installs correctly. Works correctly for me.
This update can be pushed to stable now if the maintainer wishes
I have an issue with this version, when building a package with --postinstall. In that case, mock fails to find the built package. For example:
$ mock --rebuild -r epel-8-x86_64 --postinstall python-distroinfo-0.3.2-2.el8.src.rpm
Using [1] as test source RPM. I get the following log message:
Can not load RPM file: /var/lib/mock/epel-8-x86_64/result/python3-distroinfo-0.3.2-2.el8.noarch.rpm. Could not open: /var/lib/mock/epel-8-x86_64/result/python3-distroinfo-0.3.2-2.el8.noarch.rpm WARNING: Failed install built packages
As a workaround, I can use --no-bootstrap-chroot, but the default configuration is broken.
Would it help if I open an issue on GitHub or BZ?
[1] - https://kojipkgs.fedoraproject.org//packages/python-distroinfo/0.3.2/2.el8/src/python-distroinfo-0.3.2-2.el8.src.rpm
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
I have an issue with this version, when building a package with --postinstall. In that case, mock fails to find the built package. For example:
$ mock --rebuild -r epel-8-x86_64 --postinstall python-distroinfo-0.3.2-2.el8.src.rpm
Using [1] as test source RPM. I get the following log message:
Can not load RPM file: /var/lib/mock/epel-8-x86_64/result/python3-distroinfo-0.3.2-2.el8.noarch.rpm. Could not open: /var/lib/mock/epel-8-x86_64/result/python3-distroinfo-0.3.2-2.el8.noarch.rpm WARNING: Failed install built packages
As a workaround, I can use --no-bootstrap-chroot, but the default configuration is broken.
Would it help if I open an issue on GitHub or BZ?
[1] - https://kojipkgs.fedoraproject.org//packages/python-distroinfo/0.3.2/2.el8/src/python-distroinfo-0.3.2-2.el8.src.rpm
Sorry for the double-comment, it looked like the Bodhi UI tricked me.
@jpena, thanks for the update. Please use
--no-bootstrap-chroot
if you want to use--postinstall
. The--postinstall
option is not yet fixed, and fix will be in v2.3 hopefully. I don't want to skip the update only because of this small problem (ie fedora got the updates, and nobody noticed this so far).Thanks for the upstream report: https://github.com/rpm-software-management/mock/issues/564
@jpena, thanks for the update. Please use
--no-bootstrap-chroot
if you want to use--postinstall
. The--postinstall
option is not yet fixed, and fix will be in v2.3 hopefully. I don't want to skip the update only because of this small problem (ie fedora got the updates, and nobody noticed this so far).Thanks for the upstream report: https://github.com/rpm-software-management/mock/issues/564
@jpena, thanks for the update. Please use
--no-bootstrap-chroot
if you want to use--postinstall
. The--postinstall
option is not yet fixed, and fix will be in v2.3 hopefully. I don't want to skip the update only because of this small problem (ie fedora got the updates, and nobody noticed this so far).Thanks for the upstream report: https://github.com/rpm-software-management/mock/issues/564
Meh, yeah, bodhi sucks these days :-( anyways, since the negative karma turned off the auto push - I will very likely push the update to stable anyways once it is in 30 days of testing. Unless some much more serious problems appear.
This update has been submitted for stable by praiskup.
This update has been pushed to stable.