Hold until the change has been submitted and accepted.

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/9ab85c37c56849248759604e708fc6c1

• validate : SUCCESS in 2m 23s

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/36885621da7b47999178f99801731425

• validate : SUCCESS in 3m 21s

Hold until the change has been accepted.

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/bf3fa4363b924d5093f1a16ecdd13d60

• validate : SUCCESS in 2m 59s

Shouldn't this skip the script if the output file already exists?

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/bb1cf56652034ac697ae752dcd4c05ea

• validate : SUCCESS in 2m 44s

The post process scripts in those manifests are run as part of the rpm-ostree compose, so this only impacts the content of the ostree commit, not the content of /etc as configured by users on their systems.

ostree will do a three-way diff on update on actual systems with the content of /etc: https://ostreedev.github.io/ostree/atomic-upgrades/#assembling-a-new-deployment-directory

As we don't ship such a file for now in any package, we don't really need to check if it exists.

Build succeeded.
https://fedora.softwarefactory-project.io/zuul/buildset/95f08c268cb94fceb6cbf3ab04b6fa3e

• validate : SUCCESS in 2m 51s

Merging now that the change has been accepted by FESCo.

Does this mechanism
- detect low battery state
- pause on metered connection
- limit update priority so it doesnt run under high load

? If yes or no, are these things specific to the software stores used?

So if a change would help, would this be done upstream?

With a systemd service these things can be done in a single service file, and work desktop independent.

You should file bugs upstream to Plasma Discover in KDE's bugzilla.