On Mon, Jul 27, 2015 at 08:48:08PM +0200, Lennart Poettering wrote:
On Tue, 21.07.15 03:27, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
[resending with the right systemd-devel address, sorry for that]
Here are some thoughts on offline updates resulting from testing
the new
On Mon, 27.07.15 19:37, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
OK, I think we're pretty much in agreement. I'd like to take the opportunity
to convert the wiki page to a man page. It would be easier to discuss
and track changes then. ?
I'd document systemd behaviour, apis and
On Tue, 21.07.15 03:27, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
[resending with the right systemd-devel address, sorry for that]
Here are some thoughts on offline updates resulting from testing
the new dnf fedup plugin developed by Will Woods
On Tue, 2015-07-21 at 03:27 +, Zbigniew Jędrzejewski-Szmek wrote:
fedup-system-upgrade.service uses an additional flag file which is
checked with ConditionPathExists so it will not run if 'dnf fedup
reboot'
did not create the flag, even if we go into system-upgrade.target.
On Tue, Jul 21, 2015 at 03:00:39PM -0400, Will Woods wrote:
On Tue, 2015-07-21 at 03:27 +, Zbigniew Jędrzejewski-Szmek wrote:
fedup-system-upgrade.service uses an additional flag file which is
checked with ConditionPathExists so it will not run if 'dnf fedup
reboot'
did not create
[resending with the right systemd-devel address, sorry for that]
Here are some thoughts on offline updates resulting from testing
the new dnf fedup plugin developed by Will Woods
[https://github.com/wgwoods/dnf-plugin-fedup].
I ran an update using dnf fedup and it works (or would have worked, if
