bodhi: stop using pyramid_sawing in stg #2664

Open
mattia wants to merge 1 commit from bodhi-sawing into main
Contributor

pyramid_sawing is dead upstream and I want to get rid of it's usage in Bodhi.
We currently load the logging configuration from an external file, I'd like to test moving the configuration within the main config file. This only applies to staging.

Signed-off-by: Mattia Verga mattia.verga@tiscali.it

pyramid_sawing is dead upstream and I want to get rid of it's usage in Bodhi. We currently load the logging configuration from an external file, I'd like to test moving the configuration within the main config file. This only applies to staging. Signed-off-by: Mattia Verga <mattia.verga@tiscali.it>
First-time contributor
Build succeeded. https://fedora.softwarefactory-project.io/zuul/buildset/52f1bf91458946248c657c749fd01e7c - [fi-ansible-lint-diff ](https://fedora.softwarefactory-project.io/zuul/build/b6e8433c49634f86860719aad82f9a81) : SUCCESS in 2m 31s - [fi-yamllint-diff ](https://fedora.softwarefactory-project.io/zuul/build/c16f62d34a2345968f06980cd78be1eb) : SUCCESS in 2m 11s
This pull request is broken due to missing fork information.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin bodhi-sawing:bodhi-sawing
git checkout bodhi-sawing

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git checkout main
git merge --no-ff bodhi-sawing
git checkout bodhi-sawing
git rebase main
git checkout main
git merge --ff-only bodhi-sawing
git checkout bodhi-sawing
git rebase main
git checkout main
git merge --no-ff bodhi-sawing
git checkout main
git merge --squash bodhi-sawing
git checkout main
git merge --ff-only bodhi-sawing
git checkout main
git merge bodhi-sawing
git push origin main
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/ansible#2664
No description provided.