Bug 2143030

Description of problem:
When trying to update moodle in F37 using dnf, I get file conflict errors.

Version-Release number of selected component (if applicable):
moodle-4.0.5-1.fc37.noarch

How reproducible:
every time

Steps to Reproduce:
1.  Have moodle and php-google-apiclient installed
2.  Try to update to moodle-4.0.5-1.fc37.noarch
3.

Actual results:
r: Transaction test error:
file /var/www/moodle/web/lib/google/src/Google/Http/REST.php from install of moodle-4.0.5-1.fc37.noarch conflicts with file from package php-google-apiclient1-1.1.7-14.fc36.noarch
file /var/www/moodle/web/lib/google/src/Google/IO/Curl.php from install of moodle-4.0.5-1.fc37.noarch conflicts with file from package php-google-apiclient1-1.1.7-14.fc36.noarch
file /var/www/moodle/web/lib/google/src/Google/IO/Stream.php from install of moodle-4.0.5-1.fc37.noarch conflicts with file from package php-google-apiclient1-1.1.7-14.fc36.noarch
file /var/www/moodle/web/lib/google/src/Google/Signer/P12.php from install of moodle-4.0.5-1.fc37.noarch conflicts with file from package php-google-apiclient1-1.1.7-14.fc36.noarch
file /var/www/moodle/web/lib/google/src/Google/Verifier/Pem.php from install of moodle-4.0.5-1.fc37.noarch conflicts with file from package php-google-apiclient1-1.1.7-14.fc36.noarch

Expected results:
moodle updates

Additional info:

I don't know which package is at fault, but it was a moodle update that triggered the file conflict, so I posted the bug to moodle.

Not about moodle, but this kind of error is easily prevented.  rpm has two options, -q and --filesbypkg that lists all the files in a package.  If the file names (with path) for every fedora package were put in a database as primary key, the build system would only have to get the package list, run some sequel queries against all the file names possible, and ensure that there wasn't a conflict before pushing the package to testing.  Since it seems so obvious, I am guessing that it needs someone knowledgeable of the packaging application to implement it, fingers on the keyboard.  I suppose because it happens so infrequently, it isn't worth the effort.