[fedora-kickstarts] branch master updated (363a8c6 -> eae92c2)
by pagure@pagure.io
This is an automated email from the git hooks/post-receive script.
puiterwijk pushed a change to branch master
in repository fedora-kickstarts.
from 363a8c6 Use the fedora-release-container package to get the release version
add eae92c2 Update ostree repo url from atomic/repo/ to ostree/repo
No new revisions were added by this update.
Summary of changes:
fedora-atomic.ks | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
5 years, 2 months
[fedora-kickstarts] branch f28 updated (d8c1268 -> ab0f966)
by pagure@pagure.io
This is an automated email from the git hooks/post-receive script.
kevin pushed a change to branch f28
in repository fedora-kickstarts.
from d8c1268 Use coreutils instead of coreutils-single in containers.
add ab0f966 Use the fedora-release-container package to get the release version
No new revisions were added by this update.
Summary of changes:
fedora-docker-common.ks | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
5 years, 2 months
[fedora-kickstarts] branch f29 updated (96e4175 -> 776ba20)
by pagure@pagure.io
This is an automated email from the git hooks/post-receive script.
kevin pushed a change to branch f29
in repository fedora-kickstarts.
from 96e4175 Use the fedora-release-container package in container images
add 776ba20 Use the fedora-release-container package to get the release version
No new revisions were added by this update.
Summary of changes:
fedora-docker-common.ks | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
5 years, 2 months
[fedora-kickstarts] branch master updated (e168b19 -> 363a8c6)
by pagure@pagure.io
This is an automated email from the git hooks/post-receive script.
kevin pushed a change to branch master
in repository fedora-kickstarts.
from e168b19 Install the anaconda-live package on the live image
add 363a8c6 Use the fedora-release-container package to get the release version
No new revisions were added by this update.
Summary of changes:
fedora-container-common.ks | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
5 years, 2 months
[fedora-kickstarts] branch master updated (ffd90db -> e168b19)
by pagure@pagure.io
This is an automated email from the git hooks/post-receive script.
kevin pushed a change to branch master
in repository fedora-kickstarts.
from ffd90db IoT: Fixes and updates for IoT
add e168b19 Install the anaconda-live package on the live image
No new revisions were added by this update.
Summary of changes:
fedora-live-base.ks | 1 +
1 file changed, 1 insertion(+)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
5 years, 2 months
[fedora-kickstarts] branch master updated: IoT: Fixes and updates for IoT
by pagure@pagure.io
This is an automated email from the git hooks/post-receive script.
pbrobinson pushed a commit to branch master
in repository fedora-kickstarts.
The following commit(s) were added to refs/heads/master by this push:
new ffd90db IoT: Fixes and updates for IoT
ffd90db is described below
commit ffd90dbee1cd54ef4f6c611bcf644b400bd5ad70
Author: Peter Robinson <pbrobinson(a)fedoraproject.org>
AuthorDate: Tue Feb 5 18:06:35 2019 +0000
IoT: Fixes and updates for IoT
---
fedora-iot.ks | 14 +++++---------
1 file changed, 5 insertions(+), 9 deletions(-)
diff --git a/fedora-iot.ks b/fedora-iot.ks
index d2ba26a..7374cc7 100644
--- a/fedora-iot.ks
+++ b/fedora-iot.ks
@@ -24,7 +24,7 @@ autopart --nohome --noswap --type=plain
# Equivalent of %include fedora-repo.ks
# Pull from the ostree repo that was created during the compose
-ostreesetup --nogpg --osname=fedora-iot --remote=fedora-iot --url=https://kojipkgs.fedoraproject.org/compose/iot/repo/ --ref=fedora/29/${basearch}/iot
+ostreesetup --nogpg --osname=fedora-iot --remote=fedora-iot --url=https://kojipkgs.fedoraproject.org/compose/iot/repo/ --ref=fedora/devel/${basearch}/iot
reboot
@@ -44,19 +44,19 @@ fi
# Set the origin to the "main ref", distinct from /updates/ which is where bodhi writes.
# We want consumers of this image to track the two week releases.
-ostree admin set-origin --index 0 fedora-iot https://kojipkgs.fedoraproject.org/iot/29/ "fedora/29/${arch}/iot"
+ostree admin set-origin --index 0 fedora-iot https://dl.fedoraproject.org/iot/repo/ "fedora/devel/${arch}/iot"
# Make sure the ref we're supposedly sitting on (according
# to the updated origin) exists.
-ostree refs "fedora-iot:fedora/29/${arch}/iot" --create "fedora-iot:fedora/29/${arch}/iot"
+ostree refs "fedora-iot:fedora/devel/${arch}/iot" --create "fedora-iot:fedora/devel/${arch}/iot"
# Remove the old ref so that the commit eventually gets cleaned up.
-ostree refs "fedora-iot:fedora/29/${arch}/iot" --delete
+ostree refs "fedora-iot:fedora/devel/${arch}/iot" --delete
# delete/add the remote with new options to enable gpg verification
# and to point them at the cdn url
ostree remote delete fedora-iot
-ostree remote add --set=gpg-verify=true --set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-primary fedora-iot 'https://dl.fedoraproject.org/iot/repo/'
+ostree remote add --set=gpg-verify=true --set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-iot-2019 fedora-iot 'https://dl.fedoraproject.org/iot/repo/'
# We're gettin a stray console= from somewhere, work around it
rpm-ostree kargs --delete=console=tty0
@@ -108,10 +108,6 @@ rm -f /etc/sysconfig/network-scripts/ifcfg-ens3
echo "Adding Developer Mode GRUB2 menu item."
/usr/libexec/atomic-devmode/bootentry add
-# Disable network service here, as doing it in the services line
-# fails due to RHBZ #1369794
-/sbin/chkconfig network off
-
# Anaconda is writing an /etc/resolv.conf from the install environment.
# The system should start out with an empty file, otherwise cloud-init
# will try to use this information and may error:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
5 years, 2 months