3:58 a.m.
Hello maintainers!
Let me announce a new release of Mock v5.0 (the chroot build environment
manager for building RPMs).
This release release brings lots of changes, though the one that I'd
like to underline is that we turned --use-bootstrap-image ON by default.
This effectively means that Mock uses Podman to pull the bootstrap image
from image registries (instead of installing it from scratch with `dnf
--installroot`). Thus Podman is now in `Recommends:`, not just
`Suggests:`. Should you have any issues, you can temporarily revert this
change with `--no-bootstrap-image` (--scrub=all first!). Alternatively
set `config_opts["use_bootstrap_image"] = False` in configuration.
Mock 5.0 also stops using '/sbin/useradd' inside the chroot, but uses
'/sbin/useradd --prefix <chroot>' _on host_ to modify the in-chroot
/etc/passwd. This change passed all our testing, but there's a
potential for bugs.
The mock-core-configs-v39 brings also the Fedora 39 configuration as it
is now branched from Rawhide (Rawhide is 40 now in Mock). Several folks
already reported that Fedora Copr builds are broken for
fedora-rawhide-*, sorry for inconveniences. This is being resolved
right now, we are pushing mock-5.0 into the Fedora Copr production.
In case of any trouble, please report issues upstream:
https://github.com/rpm-software-management/mock/issues
Full release notes:
https://rpm-software-management.github.io/mock/Release-Notes-5.0
The updated packages are in Bodhi:
[Fedora 38]: https://bodhi.fedoraproject.org/updates/FEDORA-2023-0ca9df2164
[Fedora 37]: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c65d483a5c
[EPEL 9]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-e03c59145d
[EPEL 8]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-a5c155a6c0
Happy building!
Pavel
10:56 a.m.
On Thu, 2023-08-10 at 10:58 +0200, Pavel Raiskup wrote:
Hello maintainers!
Let me announce a new release of Mock v5.0 (the chroot build environment
manager for building RPMs).
This release release brings lots of changes, though the one that I'd
like to underline is that we turned --use-bootstrap-image ON by default.
This effectively means that Mock uses Podman to pull the bootstrap image
from image registries (instead of installing it from scratch with `dnf
--installroot`). Thus Podman is now in `Recommends:`, not just
`Suggests:`. Should you have any issues, you can temporarily revert this
change with `--no-bootstrap-image` (--scrub=all first!). Alternatively
set `config_opts["use_bootstrap_image"] = False` in configuration.
Unfortunately this seems to be broken on Rawhide, whether you use the
'fedora-40' or 'fedora-rawhide' name:
[adamw@xps13a gnome-shell (rawhide %)]$ mock -r fedora-40-x86_64 --scrub=all
...
[adamw@xps13a gnome-shell (rawhide %)]$ mock -r fedora-40-x86_64 --install nano
...
Start(bootstrap): cleaning package manager metadata
Finish(bootstrap): cleaning package manager metadata
INFO: Using bootstrap image: registry.fedoraproject.org/fedora:rawhide
INFO: Pulling image: registry.fedoraproject.org/fedora:rawhide
ERROR: Command failed:
# podman pull registry.fedoraproject.org/fedora:rawhide
[adamw@xps13a gnome-shell (rawhide %)]$ mock -r fedora-rawhide-x86_64 --scrub=all
...
[adamw@xps13a gnome-shell (rawhide %)]$ mock -r fedora-rawhide-x86_64 --install nano
...
Start(bootstrap): cleaning package manager metadata
Finish(bootstrap): cleaning package manager metadata
INFO: Using bootstrap image: registry.fedoraproject.org/fedora:rawhide
INFO: Pulling image: registry.fedoraproject.org/fedora:rawhide
ERROR: Command failed:
# podman pull registry.fedoraproject.org/fedora:rawhide
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org
https://www.happyassassin.net
11:58 a.m.
On Thu, 2023-08-10 at 08:56 -0700, Adam Williamson wrote:
On Thu, 2023-08-10 at 10:58 +0200, Pavel Raiskup wrote:
> Hello maintainers!
>
> Let me announce a new release of Mock v5.0 (the chroot build environment
> manager for building RPMs).
>
> This release release brings lots of changes, though the one that I'd
> like to underline is that we turned --use-bootstrap-image ON by default.
> This effectively means that Mock uses Podman to pull the bootstrap image
> from image registries (instead of installing it from scratch with `dnf
> --installroot`). Thus Podman is now in `Recommends:`, not just
> `Suggests:`. Should you have any issues, you can temporarily revert this
> change with `--no-bootstrap-image` (--scrub=all first!). Alternatively
> set `config_opts["use_bootstrap_image"] = False` in configuration.
Unfortunately this seems to be broken on Rawhide, whether you use the
'fedora-40' or 'fedora-rawhide' name:
Update: nirik has fixed this for now. We think the Rawhide nightly
script is messing up the registry when it runs, he'll try and fix that
later.
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw(a)fosstodon.org
https://www.happyassassin.net
2:21 p.m.
On Thu, Aug 10, 2023 at 09:58:30AM -0700, Adam Williamson wrote:
On Thu, 2023-08-10 at 08:56 -0700, Adam Williamson wrote:
> On Thu, 2023-08-10 at 10:58 +0200, Pavel Raiskup wrote:
> > Hello maintainers!
> >
> > Let me announce a new release of Mock v5.0 (the chroot build environment
> > manager for building RPMs).
> >
> > This release release brings lots of changes, though the one that I'd
> > like to underline is that we turned --use-bootstrap-image ON by default.
> > This effectively means that Mock uses Podman to pull the bootstrap image
> > from image registries (instead of installing it from scratch with `dnf
> > --installroot`). Thus Podman is now in `Recommends:`, not just
> > `Suggests:`. Should you have any issues, you can temporarily revert this
> > change with `--no-bootstrap-image` (--scrub=all first!). Alternatively
> > set `config_opts["use_bootstrap_image"] = False` in configuration.
>
> Unfortunately this seems to be broken on Rawhide, whether you use the
> 'fedora-40' or 'fedora-rawhide' name:
Update: nirik has fixed this for now. We think the Rawhide nightly
script is messing up the registry when it runs, he'll try and fix that
later.
And I think thats now fixed (was some leftover armhfp stuff. ;)
kevin
6:31 p.m.
Will the current fixes allow test installations of the workspaces.iso? True Ivan test
using the everything.iso, but we do want the installation programs to work fully
What is stopping workspace installs is: gnome.display.manager
Sent from Yahoo Mail on Android
On Thu, Aug 10, 2023 at 3:22 p.m., Kevin Fenzi<kevin(a)scrye.com> wrote: On Thu,
Aug 10, 2023 at 09:58:30AM -0700, Adam Williamson wrote:
On Thu, 2023-08-10 at 08:56 -0700, Adam Williamson wrote:
> On Thu, 2023-08-10 at 10:58 +0200, Pavel Raiskup wrote:
> > Hello maintainers!
> >
> > Let me announce a new release of Mock v5.0 (the chroot build environment
> > manager for building RPMs).
> >
> > This release release brings lots of changes, though the one that I'd
> > like to underline is that we turned --use-bootstrap-image ON by default.
> > This effectively means that Mock uses Podman to pull the bootstrap image
> > from image registries (instead of installing it from scratch with `dnf
> > --installroot`). Thus Podman is now in `Recommends:`, not just
> > `Suggests:`. Should you have any issues, you can temporarily revert this
> > change with `--no-bootstrap-image` (--scrub=all first!). Alternatively
> > set `config_opts["use_bootstrap_image"] = False` in configuration.
>
> Unfortunately this seems to be broken on Rawhide, whether you use the
> 'fedora-40' or 'fedora-rawhide' name:
Update: nirik has fixed this for now. We think the Rawhide nightly
script is messing up the registry when it runs, he'll try and fix that
later.
And I think thats now fixed (was some leftover armhfp stuff. ;)
kevin
2:30 p.m.
Kevin Fenzi venit, vidit, dixit 2023-08-10 21:21:59:
On Thu, Aug 10, 2023 at 09:58:30AM -0700, Adam Williamson wrote:
> On Thu, 2023-08-10 at 08:56 -0700, Adam Williamson wrote:
> > On Thu, 2023-08-10 at 10:58 +0200, Pavel Raiskup wrote:
> > > Hello maintainers!
> > >
> > > Let me announce a new release of Mock v5.0 (the chroot build environment
> > > manager for building RPMs).
> > >
> > > This release release brings lots of changes, though the one that I'd
> > > like to underline is that we turned --use-bootstrap-image ON by default.
> > > This effectively means that Mock uses Podman to pull the bootstrap image
> > > from image registries (instead of installing it from scratch with `dnf
> > > --installroot`). Thus Podman is now in `Recommends:`, not just
> > > `Suggests:`. Should you have any issues, you can temporarily revert this
> > > change with `--no-bootstrap-image` (--scrub=all first!). Alternatively
> > > set `config_opts["use_bootstrap_image"] = False` in
configuration.
> >
> > Unfortunately this seems to be broken on Rawhide, whether you use the
> > 'fedora-40' or 'fedora-rawhide' name:
>
> Update: nirik has fixed this for now. We think the Rawhide nightly
> script is messing up the registry when it runs, he'll try and fix that
> later.
And I think thats now fixed (was some leftover armhfp stuff. ;)
Is this supposed to work now?
With mock-5.0-1.fc38.noarch and after scrubbing, the image is pulled but
then not used because it is "not marked ready" (rawhide, f39, f38). Am I
holding it wrong?
```
Start(bootstrap): cleaning package manager metadata
Finish(bootstrap): cleaning package manager metadata
INFO: Using bootstrap image: registry.fedoraproject.org/fedora:38
INFO: Pulling image: registry.fedoraproject.org/fedora:38
INFO: Copy content of container registry.fedoraproject.org/fedora:38 to
/var/lib/mock/fedora-38-x86_64-bootstrap/root
INFO: mounting registry.fedoraproject.org/fedora:38 with podman image mount
INFO: image registry.fedoraproject.org/fedora:38 as
/var/lib/containers/storage/overlay/5eb2e729c16708697e84f3cf2648d1ff3f2ce56f2f1eceb0289b226bc96b061a/merged
INFO: umounting image registry.fedoraproject.org/fedora:38
(/var/lib/containers/storage/overlay/5eb2e729c16708697e84f3cf2648d1ff3f2ce56f2f1eceb0289b226bc96b061a/merged)
with
podman image umount
INFO: Package manager dnf detected and used (fallback)
INFO: Bootstrap image not marked ready
Start(bootstrap): installing dnf tooling
```
and then dnf builds the chroot.
Michael
4:27 a.m.
Dne 14. 08. 23 v 21:30 Michael J Gruber napsal(a):
Is this supposed to work now?
With mock-5.0-1.fc38.noarch and after scrubbing, the image is pulled but
then not used because it is "not marked ready" (rawhide, f39, f38). Am I
holding it wrong?
1) When image is not marked ready then it is still used. Only additional packages are
installed into chroot when image
is unpacked. It is still faster than installing whole chroot using DNF.
2) Only RHEL images has all packages installed by default:
https://github.com/rpm-software-management/mock/commit/e7139e1ce10198066b...
Other images does not have necessary tools installed.
I do not expect that default Fedora images will have all packages installed by default. It
does not make sense.
This is targeted for teams that do frequent builds and they can prepare the image tuned
for their needs and mark it as
ready. It will significantly lower the time before mock starts rpmbuild.
--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
3:30 a.m.
On neděle 20. srpna 2023 11:27:44 CEST Miroslav Suchý wrote:
Dne 14. 08. 23 v 21:30 Michael J Gruber napsal(a):
> Is this supposed to work now?
>
> With mock-5.0-1.fc38.noarch and after scrubbing, the image is pulled but
> then not used because it is "not marked ready" (rawhide, f39, f38). Am I
> holding it wrong?
1) When image is not marked ready then it is still used. Only
additional packages are installed into chroot when image is
unpacked. It is still faster than installing whole chroot using
DNF.
2) Only RHEL images has all packages installed by default:
https://github.com/rpm-software-management/mock/commit/e7139e1ce10198066b...
Other images does not have necessary tools installed.
I do not expect that default Fedora images will have all packages
installed by default. It does not make sense.
This is targeted for teams that do frequent builds and they can prepare
the image tuned for their needs and mark it as ready. It will
significantly lower the time before mock starts rpmbuild.
Well, in what shape is our "layered image" build system? Aren't we able
to create a new official image say `fedora-mock-bootstrap:<FEDORA_VERSION>`
that would be automatically built (ideally at least as frequently as the
base image is)? This way we could optimize fedora builds for everyone.
Pavel
2:48 p.m.
On Tue, Oct 03, 2023 at 10:30:45AM +0200, Pavel Raiskup wrote:
Well, in what shape is our "layered image" build system? Aren't we able
Terrible, and going to be decomissioned after f39 release. ;)
But if you mean base images... those are fine.
to create a new official image say
`fedora-mock-bootstrap:<FEDORA_VERSION>`
that would be automatically built (ideally at least as frequently as the
base image is)? This way we could optimize fedora builds for everyone.
Yes, we could. Just wouldn't be a layer, it would be it's own image.
kevin
4:24 p.m.
On úterý 3. října 2023 21:48:24 CEST Kevin Fenzi wrote:
On Tue, Oct 03, 2023 at 10:30:45AM +0200, Pavel Raiskup wrote:
>
> Well, in what shape is our "layered image" build system? Aren't we
able
Terrible, and going to be decomissioned after f39 release. ;)
But if you mean base images... those are fine.
I fear that doing this as additional full Fedora image would be a waste
of space in the Fedora registry? Or not? We basically need the base
image + python3-dnf-plugins-core:
Installing:
python3-dnf-plugins-core noarch 4.4.2-1.fc39 rawhide
293 k
Installing dependencies:
dbus-libs x86_64 1:1.14.10-1.fc40 rawhide
155 k
fonts-filesystem noarch 1:2.0.5-12.fc39 rawhide
8.2 k
js-jquery noarch 3.7.1-1.fc40 rawhide
169 k
python3-dateutil noarch 1:2.8.2-10.fc39 rawhide
355 k
python3-dbus x86_64 1.3.2-4.fc39 rawhide
157 k
python3-distro noarch 1.8.0-6.fc39 rawhide
49 k
python3-six noarch 1.16.0-12.fc39 rawhide
41 k
python3-systemd x86_64 235-5.fc39 rawhide
107 k
web-assets-filesystem noarch 5-20.fc39 rawhide
7.9 k
Installing weak dependencies:
python-systemd-doc x86_64 235-5.fc39 rawhide
75 k
For DNF5 images (41+), I hope we can put the dnf5-plugins
(dnf-plugins-core alternative in c++) directly into the base image since
it has no additional deps.
> to create a new official image say
`fedora-mock-bootstrap:<FEDORA_VERSION>`
> that would be automatically built (ideally at least as frequently as the
> base image is)? This way we could optimize fedora builds for everyone.
Yes, we could. Just wouldn't be a layer, it would be it's own image.
Do we have some HOWTO document how to start? I suppose I have to
provide a kickstart file in fedora-kickstarts.git? Would the image be
built automatically/when? :-)
Pavel
kevin
12:43 p.m.
On Wed, Oct 04, 2023 at 11:24:15PM +0200, Pavel Raiskup wrote:
On úterý 3. října 2023 21:48:24 CEST Kevin Fenzi wrote:
> On Tue, Oct 03, 2023 at 10:30:45AM +0200, Pavel Raiskup wrote:
> >
> > Well, in what shape is our "layered image" build system? Aren't
we able
>
> Terrible, and going to be decomissioned after f39 release. ;)
>
> But if you mean base images... those are fine.
I fear that doing this as additional full Fedora image would be a waste
of space in the Fedora registry? Or not? We basically need the base
image + python3-dnf-plugins-core:
Yes, it would be a lot of wasted space/duplication. ;(
Installing:
python3-dnf-plugins-core noarch 4.4.2-1.fc39 rawhide
293 k
Installing dependencies:
dbus-libs x86_64 1:1.14.10-1.fc40 rawhide
155 k
fonts-filesystem noarch 1:2.0.5-12.fc39 rawhide
8.2 k
js-jquery noarch 3.7.1-1.fc40 rawhide
169 k
python3-dateutil noarch 1:2.8.2-10.fc39 rawhide
355 k
python3-dbus x86_64 1.3.2-4.fc39 rawhide
157 k
python3-distro noarch 1.8.0-6.fc39 rawhide
49 k
python3-six noarch 1.16.0-12.fc39 rawhide
41 k
python3-systemd x86_64 235-5.fc39 rawhide
107 k
web-assets-filesystem noarch 5-20.fc39 rawhide
7.9 k
Installing weak dependencies:
python-systemd-doc x86_64 235-5.fc39 rawhide
75 k
For DNF5 images (41+), I hope we can put the dnf5-plugins
(dnf-plugins-core alternative in c++) directly into the base image since
it has no additional deps.
So, what do you need out of there? builddep? or?
> > to create a new official image say
`fedora-mock-bootstrap:<FEDORA_VERSION>`
> > that would be automatically built (ideally at least as frequently as the
> > base image is)? This way we could optimize fedora builds for everyone.
>
> Yes, we could. Just wouldn't be a layer, it would be it's own image.
Do we have some HOWTO document how to start? I suppose I have to
provide a kickstart file in fedora-kickstarts.git? Would the image be
built automatically/when? :-)
I'm not convinced this is worth it... especially if dnf5 will mean it
doesn't matter anymore and currently it just means people have to
download a few packages at the start of a build.
I guess I would say a f40 change and with that discussion all the
details would be worked out. Is it release blocking? Does it need to be
advertised anywhere on websites? etc...
kevin
226
days inactive
283
days old
10 comments
6 participants
participants (6)
-
Adam Williamson -
Kevin Fenzi -
Leslie Satenstein -
Michael J Gruber -
Miroslav Suchý -
Pavel Raiskup