Skip to content

[WIP] Automatic upgrades - #24

Open
sbrl wants to merge 1 commit into
masterfrom
automatic-upgrades
Open

[WIP] Automatic upgrades#24
sbrl wants to merge 1 commit into
masterfrom
automatic-upgrades

Conversation

@sbrl

@sbrl sbrl commented Jun 6, 2018

Copy link
Copy Markdown
Member

This PR will look at enabling automatic upgrades for the Freeside machines.

@sbrl

sbrl commented Jun 6, 2018

Copy link
Copy Markdown
Member Author

Following the guide here: https://paulmellorsblog.wordpress.com/2017/10/11/unattended-upgrades/

....we need to update /etc/dnf/automatic.conf automagically.

@Epictek

Epictek commented Jun 23, 2018

Copy link
Copy Markdown
Contributor

@sbrl this will need to be updated for fabric2, if you need assistance with this let me know :)

@sbrl

sbrl commented Jun 23, 2018

Copy link
Copy Markdown
Member Author

Erm right, @Epictek. So there are 2 files now. What I've got already needs to go in the install one right?

@Epictek

Epictek commented Jun 23, 2018

Copy link
Copy Markdown
Contributor

Since it's more of a configuration change rather than an application install putting it in desktop/conf.py is probably best.

@sbrl

sbrl commented Jun 24, 2018

Copy link
Copy Markdown
Member Author

@Epictek .....but we install packages here? I'm confused 😕

@Epictek

Epictek commented Jun 24, 2018

Copy link
Copy Markdown
Contributor

install.py is more for installing user applications, whereas conf.py is more about configuring. There is no change apart from the name scheme (desktop.conf.dnf-automatic) so whichever you feel is more appropriate. IMO it fits better in conf.py

@sbrl

sbrl commented Jun 25, 2018

Copy link
Copy Markdown
Member Author

....so something can either be in install or conf, but not both?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants