Some x86_64 users wish to install ibus-gtk3.i686 and ibus-gtk2.i686
in the multilib systems but ibus.i686 is not required now.
The users could install them with `dnf install ibus-gtk3.i686` when
those modules are added to multilib_whitelist.
https://pagure.io/releng/issue/7937
Signed-off-by: Takao Fujiwara <tfujiwar@redhat.com>
There are several recommends packages that aren't getting installed in
Silverblue because the workstation comps group doesn't include them.
One of these is slirp4netns which is needed for rootless containers
using podman.
Since we are thinking about removing the separate Workstation repo
anyway[1], then maybe we can just move SB over to the Everything repo.
[1] https://pagure.io/releng/issue/7403
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
dnf does not use these, but mdapi does, so it's worth it to us to
just keep shipping them for now at least until mdapi has some other
way to get repodata.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This will ensure that the OSTrees get generated on each compose
so that the media created will match the version numbers of the
OSTree inside.
The caveat is that there can be empty commits that do happen.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
We need to stop building repos and install media for the *Cloud* variant
because the only consumers of those repos/install media is the cloud
base images that could easily be built with the Everything repo/install
media. This commit removes the cloud variant (as it was previously
known) and then renames the CloudImages variant to 'Cloud'.
Summary:
- Cloud now becomes an empty variant (no repos, no install media)
- CloudImages variant goes away
- Cloud image builds use Everything repo/install media
- Atomic image builds use Everything install tree
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
In the output we will now put the AtomicHost cloud images under
the AtomicHost/ directory instead of in CloudImages.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
Move Atomic to AtomicHost and WorkstationOstree to
AtomicWorkstation. This is mostly to make things align
more with the names of the things we actually put out.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
Pulling these packages into Modular content is probably not the right
thing to do. The config should only list variants that get traditional
content.
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
Since we now include modular content, we need to tell Pungi where to get
information about them from.
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
Some newer subvariants / loadouts were missing from the
substitution list. This updates it, alphabetizes it, corrects
the indentation, and adds a better comment about what it's for.
Note https://pagure.io/koji/pull-request/817 , corresponding
pull request for Koji.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
With Fedora 27, s390x composes (Server and Everything) are
part of primary compose. It will be nice to have atomic, cloud
and docker composes available for s390x too.
Signed-off-by: Sinny Kumari <sinny@redhat.com>
By FESCo decision all Java packages are exempt from multilib.
See: https://pagure.io/fesco/issue/961
Signed-off-by: Mikolaj Izdebski <mizdebsk@redhat.com>
This should cause the compose to contain all the previous content plus a
separate Modular variant with packages specified by list of modules in
variants file.
The final layout of the compose should be like this:
compose/Everything/$arch/os/
compose/Modular/$arch/os/
Relates: https://pagure.io/releng/issue/7227
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
- change comps_file setting in the fedora.conf to use the new scm_dict
type from the latest pungi release
- remove the make step from the nightly shell script
Signed-off-by: Robert Marshall <rmarshall@redhat.com>
This will enable the optimizations landed in
https://github.com/rhinstaller/anaconda/pull/1119
to avoid lots of HTTP requests when installing the cloud images.
Signed-off-by: Colin Walters <walters@verbum.org>
Creating the image requires running lorax. There is however already one
lorax instance being run in the buildinstall phase. When the second one
runs, it overwrites the outputs from first one and people expecting to
boot netinst over PXE are instead getting ostree workstation.
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1477916
Relates: https://pagure.io/pungi/issue/695
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
See https://pagure.io/pungi/pull-request/727
Once that is merged, released, and deployed, this change will let us see
New and Fascinating Details about the compose process.
Signed-off-by: Ralph Bean <rbean@redhat.com>
Since not all builds are signed with f28 key yet, we will use f27 key
also and once everything is signed with f28 then we will remove f27 key
Signed-off-by: Mohan Boddu <mboddu@redhat.com>
It's failing on ppc64le, we're at 87% on x86_64. There's really no reason not to
bump this to give ourselves some room at least on 64 bit architectures.
Signed-off-by: Colin Walters <walters@verbum.org>
To match up with the Addition of Container Minimal and the renaming
of dist-git namespace to Container, rename the Docker Variant to
Container
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
Currently the l10n support is moved to a single calligra-l10n package
(which is a subpackage of calligra itself) as opposed to previously
separate calligra-l10n package with a separate subpackage for each
language (which is now retired).
Due `greedy_method = "build"` the l10n subpackage will be pulled into
the compose if some package from the same build gets in (i.e. the main
calligra package required by comps).
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
Since we pull from ostree repos it doesn't really make
sense to provide a yum "repo" to the image build in pungi.
Removing it since it could be confusing to have it there.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
Add new ostree_install_repo and ostree_update_repo vars so that we
can tell lorax where to pull from during the pungi compose and also
where to configure an installed system to pull from. i.e. where a
user is going to pull from over time.
This is related to https://pagure.io/fedora-lorax-templates/pull-request/19
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
These options used to be required in pungi < 4.1.14, but now they have
default values that happen to be the same as what Fedora uses. No need
to specify them anymore.
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
Koji added the ability to set livemedia and image builds to
fail on some arches, the compose configs should be updated to use
that feature and able to identify the blocking artifacts and on what
arches.
Signed-off-by: Mohan Boddu <mboddu@redhat.com>
We have decided [1] that we want to have more meaningful versions
for ostree commits and the resulting images. One way to do this
is to have the ostree version match the version from the compose ID.
Pungi recently [2] gained support for embedding the label from the
compose into the ostree commit version. This change takes advantage
of that work to embed a more meaninful version.
[1] https://pagure.io/atomic-wg/issue/229
[2] https://pagure.io/pungi/pull-request/592
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
For the cloud base image there is no need to override the default
vagrant sync location. /vagrant/ works just fine and is what people
expect.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
