Skip to content
This repository was archived by the owner on May 30, 2023. It is now read-only.

app-admin/logrotate: Correct downstream changes to take effect#1442

Merged
pothos merged 1 commit intomainfrom
kai/logrotate-fix
Nov 23, 2021
Merged

app-admin/logrotate: Correct downstream changes to take effect#1442
pothos merged 1 commit intomainfrom
kai/logrotate-fix

Conversation

@pothos
Copy link
Copy Markdown
Contributor

@pothos pothos commented Nov 22, 2021

By accident the upstream files from the example folder got used,
instead of the downstream files that were added in the files/ folder.
Also, the configuration file didn't get installed.

Use the right paths to install the downstream files.

How to use

Check that logrotate doesn't fail
Pick for flatcar-3066

Testing done

Booted https://bucket.release.flatcar-linux.net/flatcar-jenkins/developer/developer/boards/amd64-usr/2021.11.22+dev-flatcar-master-4222/flatcar_production_image.bin.bz2
and ran sudo systemctl start logrotate.service and systemctl status logrotate.service and it worked: Process: 958 ExecStart=/usr/bin/logrotate /usr/share/logrotate/logrotate.conf (code=exited, status=0/SUCCESS)

Copy link
Copy Markdown
Contributor

@krnowak krnowak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look good, let's wait for CI.

By accident the upstream files from the example folder got used,
instead of the downstream files that were added in the files/ folder.
Also, the configuration file didn't get installed.

Use the right paths to install the downstream files.
@pothos pothos merged commit 308bb7b into main Nov 23, 2021
@pothos pothos deleted the kai/logrotate-fix branch November 23, 2021 13:20
pothos added a commit that referenced this pull request Nov 23, 2021
app-admin/logrotate: Correct downstream changes to take effect
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants