We don't create a repo during this pungi run. We need to pull
from a repo that was already created.
This was a copy/paste error from f6e7f69.
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
The nightly scripts try to send an announcement about compose starting.
As this happens before Pungi even started, the compose ID is not known
and can not be included in the message. The message about starting rsync
sent later will contain the ID correctly.
Without the json defined there is a traceback in the cron output, but
the errors are not logged anywhere else (but don't actually block
anything in the compose process).
Relates: https://pagure.io/pungi/issue/698
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
Since we are currently building atomic host media every night using
the cloud variant then we need to add ostree-support group if we
want to pull in new ostree tools into the ISO installer images.
Signed-off-by: Dusty Mabe <dusty@dustymabe.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>
The script gets a label as a command line argument, and this is manually
handled by adding it as `--label=$1` to the pungi-koji command. We
should not add this argument to another time.
This avoid problem with Pungi 4.1.17 which reports an error when seeing
unknown arguments (which were silently ignored before).
Fixes: https://pagure.io/pungi/issue/682
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
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>
There were a lot of changes to f25 fedora-cloud.conf (like
removing calls to create atomic artifacts) that were not in
master. Updating it here and pointing to f26.
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>
Go ahead and update the fedora-atomic.conf so that when it gets
branched it will have the override already in there.
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>
In koji there are ova-options and also factory-parameters.
We can pass ova-options to koji and also factory-parameters
but we can't pass ova-options as a factory-parameter. We just
need to pass in the vagrant_sync_directory as a factory
parameter.
Fixes https://pagure.io/atomic-wg/issue/181
Signed-off-by: Dusty Mabe <dusty@dustymabe.com>
