Log everything related to package listing and build tagging done by admin users via --force flag.
Fixes: https://pagure.io/koji/issue/1930
rebased onto 3906eaa052fe60eb7326b0ab35b750449797c823
I don't know if we want to require folks needing #1930 to crank logging up to DEBUG.
DEBUG
Overrides are hypothetically rare, but I guess in a mass tagging operation they might not be.
@mikem - other option is plugin hook + message via proton or mail. Anything else?
Or dou you mean just upgrading to INFO? (done)
rebased onto c1a4b5edd5b239c763dd30c38c3fdb14a20b7497
just upgrading to INFO?
yeah, that's what I was getting at. thanks :smile:
Metadata Update from @tkopecek: - Pull-request tagged with: testing-ready
rebased onto ad0fb667d90a5b6a7ccb57f9089ff03097ba0c11
1 new commit added
fix logging package name
Metadata Update from @jcupova: - Pull-request tagged with: testing-done
Commit 336c3ba5 fixes this pull-request
Pull-Request has been merged by tkopecek
pretty please pagure-ci rebuild
Log everything related to package listing and build tagging done by
admin users via --force flag.
Fixes: https://pagure.io/koji/issue/1930