spins May 2015

spins@lists.fedoraproject.org

19 participants
39 discussions

[spin-kickstarts/f22] design-suite: fixes correct name of page icons
by Luya Tshimbalanga 15 May '15

15 May '15

commit b8947535a21cd021d57d380399b045748ce2e271 Author: Luya Tshimbalanga <luya(a)fedoraproject.org> Date: Fri May 15 14:51:06 2015 -0700 design-suite: fixes correct name of page icons fedora-live-design_suite.ks | 11 +++++------ 1 files changed, 5 insertions(+), 6 deletions(-) --- diff --git a/fedora-live-design_suite.ks b/fedora-live-design_suite.ks index 01bc7ca..1ecd2d7 100644 --- a/fedora-live-design_suite.ks +++ b/fedora-live-design_suite.ks @@ -110,9 +110,9 @@ cat >> /usr/share/applications/fedora-design-suite.desktop << FOE Name=Design Suite Info GenericName=About Design Suite Comment=Wiki page of Design Suite -Name=About Design Team -GenericName=About Design Team -Comment=Wiki page of Design Team +Name=About Design Suite +GenericName=About Design Suite +Comment=Wiki page of Design Suite Exec=xdg-open http://fedoraproject.org/wiki/Design_Suite Type=Application Icon=applications-internet @@ -125,8 +125,8 @@ cat >> /usr/share/applications/fedora-design-team.desktop << FOE [Desktop Entry] Name=Design Team Info GenericName=About Design Team -Name=About Design Suite -GenericName=About Design Suite Wiki Page +Name=About Design Team +GenericName=About Design Team Wiki Page Comment=Wiki page of Design Team Exec=xdg-open http://fedoraproject.org/wiki/Design Type=Application @@ -139,4 +139,3 @@ chmod a+x /usr/share/applications/fedora-design-team.desktop glib-compile-schemas /usr/share/glib-2.0/schemas %end -

1 0

[spin-kickstarts] docker: Use bootloader --none to work around Anaconda regression
by Colin Walters 15 May '15

15 May '15

commit 4dc7946ad46869e3b78231ed11b0436d14456be8 Author: Colin Walters <walters(a)verbum.org> Date: Fri May 15 17:35:52 2015 -0400 docker: Use bootloader --none to work around Anaconda regression We were getting grub2 in the base image again. Apparently for a while Anaconda has supported a cleaner syntax for this, and since it fixes the bug, let's use it. https://bugzilla.redhat.com/show_bug.cgi?id=1222132 fedora-docker-base.ks | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) --- diff --git a/fedora-docker-base.ks b/fedora-docker-base.ks index c9da8f2..07d3049 100644 --- a/fedora-docker-base.ks +++ b/fedora-docker-base.ks @@ -16,7 +16,7 @@ # cmdline -bootloader --location=none +bootloader --disabled timezone --isUtc --nontp Etc/UTC rootpw --lock --iscrypted locked user --name=none

1 0

[spin-kickstarts] cloud-atomic-vagrant: Set root's password to vagrant too
by Colin Walters 13 May '15

13 May '15

commit ed4f6a9e883a080e4ba55d83b801ae68b9af98e5 Author: Colin Walters <walters(a)verbum.org> Date: Wed May 13 17:33:07 2015 -0400 cloud-atomic-vagrant: Set root's password to vagrant too This matches the Base box, and is standard per the Vagrant Base Box guidelines: http://docs.vagrantup.com/v2/boxes/base.html https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2015-May… fedora-cloud-atomic-vagrant.ks | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) --- diff --git a/fedora-cloud-atomic-vagrant.ks b/fedora-cloud-atomic-vagrant.ks index b91c01f..5f5d8ff 100644 --- a/fedora-cloud-atomic-vagrant.ks +++ b/fedora-cloud-atomic-vagrant.ks @@ -6,6 +6,7 @@ services --disabled=cloud-init,cloud-init-local,cloud-config,cloud-final user --name=vagrant --password=vagrant +rootpw vagrant %post --erroronfail

1 0

[spin-kickstarts/f22] design-suite: fixes documentation links only for f22
by Luya Tshimbalanga 12 May '15

12 May '15

commit 72a583d4a493907dbf643c8c6069d340c40d8218 Author: Luya Tshimbalanga <luya(a)fedoraproject.org> Date: Tue May 12 10:13:44 2015 -0700 design-suite: fixes documentation links only for f22 fedora-live-design_suite.ks | 1 - 1 files changed, 0 insertions(+), 1 deletions(-) --- diff --git a/fedora-live-design_suite.ks b/fedora-live-design_suite.ks index 0ffc64f..01bc7ca 100644 --- a/fedora-live-design_suite.ks +++ b/fedora-live-design_suite.ks @@ -113,7 +113,6 @@ Comment=Wiki page of Design Suite Name=About Design Team GenericName=About Design Team Comment=Wiki page of Design Team ->>>>>>> d4d001c54999e8f5401ca3f7b5d9b6a2d0132093 Exec=xdg-open http://fedoraproject.org/wiki/Design_Suite Type=Application Icon=applications-internet

1 0

Cinnamon Spin
by Dan Book 11 May '15

11 May '15

Hello, I would like to submit a Cinnamon spin for review and possible inclusion in future Fedora releases, though I am sure it is too late to include in F22. It is a spin simply using the Cinnamon desktop environment group, and I have been working with the Cinnamon maintainers to fix any issues that have come up in F21 or F22 beta. The proposed spin page is here: https://fedoraproject.org/wiki/Cinnamon_Spin The kickstart files are available in this repository: https://github.com/Grinnz/spin-kickstart-cinnamon I have uploaded ISOs for both F21 and F22 beta here: http://grinnz.com/public/spins-cinnamon -Dan

2 6

cleanup of spins process
by Dennis Gilmore 07 May '15

07 May '15

Since the Spins process has fallen down and there has not been a spins SIG meeting in years that I know of. I think we should update https://fedoraproject.org/wiki/Spins_Process to point people to the Fedora Change process and just use that for the addition of new spins. ensuring that kickstarts are reviewed by at least one non owner before being pulled in. Thoughts, objections or counter proposals? Dennis

6 11

[spin-kickstarts/f21] docker: Don't use a hardcoded root password
by Colin Walters 06 May '15

06 May '15

commit e9241770840e672e838a1aa1d1c38cebabe62d0a Author: Colin Walters <walters(a)verbum.org> Date: Tue Dec 16 16:26:01 2014 -0500 docker: Don't use a hardcoded root password Best practice is to use unprivileged service daemons inside Docker containers. But with this hardcoded root password, in the case of remote code execution, an attacker could trivially escalate their privileges to root/uid 0. And while that's uid 0 inside a container, that's a much larger attack surface. Instead, do the same thing we're doing for the Cloud images: lock the root password, create a user to make Anaconda happy, then delete the user in %post. https://bugzilla.redhat.com/show_bug.cgi?id=1175997 Conflicts: fedora-docker-base.ks fedora-docker-base.ks | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) --- diff --git a/fedora-docker-base.ks b/fedora-docker-base.ks index 78e5b93..eda9b21 100644 --- a/fedora-docker-base.ks +++ b/fedora-docker-base.ks @@ -6,7 +6,8 @@ cmdline bootloader --location=none timezone America/New_York --isUtc --nontp -rootpw --plaintext qweqwe +rootpw --lock --iscrypted locked +user --name=none keyboard us firewall --disable @@ -31,6 +32,9 @@ yum # Set the language rpm nodocs transaction flag persistently in the # image yum.conf and rpm macros +# remove the user anaconda forces us to make +userdel -r none + LANG="en_US" echo "%_install_lang $LANG" > /etc/rpm/macros.image-language-conf

1 0

[spin-kickstarts/f22] docker: Don't use a hardcoded root password
by Colin Walters 06 May '15

06 May '15

commit 7a6f83699b918c5c1a9f2218fbdda974f09b3675 Author: Colin Walters <walters(a)verbum.org> Date: Tue Dec 16 16:26:01 2014 -0500 docker: Don't use a hardcoded root password Best practice is to use unprivileged service daemons inside Docker containers. But with this hardcoded root password, in the case of remote code execution, an attacker could trivially escalate their privileges to root/uid 0. And while that's uid 0 inside a container, that's a much larger attack surface. Instead, do the same thing we're doing for the Cloud images: lock the root password, create a user to make Anaconda happy, then delete the user in %post. https://bugzilla.redhat.com/show_bug.cgi?id=1175997 fedora-docker-base.ks | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) --- diff --git a/fedora-docker-base.ks b/fedora-docker-base.ks index 907667b..c9da8f2 100644 --- a/fedora-docker-base.ks +++ b/fedora-docker-base.ks @@ -18,7 +18,8 @@ cmdline bootloader --location=none timezone --isUtc --nontp Etc/UTC -rootpw --plaintext qweqwe +rootpw --lock --iscrypted locked +user --name=none keyboard us zerombr @@ -44,6 +45,9 @@ dnf-yum # https://fedorahosted.org/fesco/ticket/1312#comment:29 # Set the language rpm nodocs transaction flag persistently in the # image yum.conf and rpm macros +# remove the user anaconda forces us to make +userdel -r none + LANG="en_US" echo "%_install_lang $LANG" > /etc/rpm/macros.image-language-conf

1 0

[spin-kickstarts] docker: Don't use a hardcoded root password
by Colin Walters 06 May '15

06 May '15

commit 6ba647a663f09da4ba740eb99733a39cba58d204 Author: Colin Walters <walters(a)verbum.org> Date: Tue Dec 16 16:26:01 2014 -0500 docker: Don't use a hardcoded root password Best practice is to use unprivileged service daemons inside Docker containers. But with this hardcoded root password, in the case of remote code execution, an attacker could trivially escalate their privileges to root/uid 0. And while that's uid 0 inside a container, that's a much larger attack surface. Instead, do the same thing we're doing for the Cloud images: lock the root password, create a user to make Anaconda happy, then delete the user in %post. https://bugzilla.redhat.com/show_bug.cgi?id=1175997 fedora-docker-base.ks | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) --- diff --git a/fedora-docker-base.ks b/fedora-docker-base.ks index 907667b..c9da8f2 100644 --- a/fedora-docker-base.ks +++ b/fedora-docker-base.ks @@ -18,7 +18,8 @@ cmdline bootloader --location=none timezone --isUtc --nontp Etc/UTC -rootpw --plaintext qweqwe +rootpw --lock --iscrypted locked +user --name=none keyboard us zerombr @@ -44,6 +45,9 @@ dnf-yum # https://fedorahosted.org/fesco/ticket/1312#comment:29 # Set the language rpm nodocs transaction flag persistently in the # image yum.conf and rpm macros +# remove the user anaconda forces us to make +userdel -r none + LANG="en_US" echo "%_install_lang $LANG" > /etc/rpm/macros.image-language-conf

1 0

[spin-kickstarts/f22] kde: drop plasma-netbook hack
by Rex Dieter 05 May '15

05 May '15

commit 76d2df7147508c5af5437ae92bee249d628c67b6 Author: Rex Dieter <rdieter(a)math.unl.edu> Date: Tue May 5 12:06:24 2015 -0500 kde: drop plasma-netbook hack plasma-netbook no longer exists fedora-live-kde-base.ks | 5 ----- 1 files changed, 0 insertions(+), 5 deletions(-) --- diff --git a/fedora-live-kde-base.ks b/fedora-live-kde-base.ks index f4d3219..0179924 100644 --- a/fedora-live-kde-base.ks +++ b/fedora-live-kde-base.ks @@ -101,11 +101,6 @@ KRES_EOF chown -R liveuser:liveuser /home/liveuser/ restorecon -R /home/liveuser/ -# small hack to enable plasma-netbook workspace on boot -if strstr "\`cat /proc/cmdline\`" netbook ; then - mv /usr/share/autostart/plasma-desktop.desktop /usr/share/autostart/plasma-netbook.desktop - sed -i 's/desktop/netbook/g' /usr/share/autostart/plasma-netbook.desktop -fi EOF %end

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

spins May 2015