Bug Reporting

Weak dependencies

As there are no rules how to use weak dependencies now and DNF will be the reference implementation of this, we need to know uncommon packagers use cases. If you found that DNF should have proceed the transaction other way, report a bug with:

• "[weak deps]" summary prefix
• command line executed
• post link to custom COPR, so we can reproduce it easily
• write "expected" result

then RPM team decides how DNF should act, change it accordingly and document this case.

Metadata download problem

If an error messages occur during downloading of metadata of repositories or packages, file a bug with:

• "[metadata]" summary prefix
• command line executed
• attach archive of /var/cache/dnf directory

Depsolving problem

When you think DNF pulled in more packages than it should or you see error after these lines:

--> Starting dependency resolution
--> Finished dependency resolution

and you have already tried new switches --allowerasing or --best introduced in DNF, report a bug with:

• "[depsolve]" summary prefix
• command line executed
• attach archive of debugdata (outputs in current directory while using --debugsolver switch within command line)

Some of the depsolving problems are caused by different selection prioritization of provides than in yum. These cases should be resolved on package level by adding weak dependencies.

Note: these bugs will have default priority set to low as it's in 95% not a DNF bug and wastes only time of DNF developers. I would like to encourage all community members to look at these bugs using repoquery and other useful tools to figure out which package to blame. Thanks.

Reporting dependency problems in more detail is on dnf blog.