On Sat, Feb 4, 2023 at 3:33 AM ToddAndMargo via users users@lists.fedoraproject.org wrote:
On 2/4/23 00:05, Samuel Sieb wrote:
On 2/3/23 21:32, ToddAndMargo via users wrote:
On 2/3/23 20:10, Go Canes wrote:
On Fri, Feb 3, 2023 at 10:11 PM Todd Zullinger tmz@pobox.com wrote:
This is not the way I've ever seen excludepkgs used or documented. The man page states:
excludepkgs list Exclude packages of this repository, speciā fied by a name or a glob and separated by a comma, from all operations. Can be disabled using --disableexcludes command line switch. Defaults to [].
Put them all together, not a bunch of different definitions.
Note: "separated by a comma" - the commented-out lines were separated by spaces (I assume these were failed attempts).
excludepkgs=wine*,resolvconf,systemd-resolved
Did work. I missed what Samuel's said.
This is a regression from Fedora 36. I updates the bug report.
It might be a change, but it's not a regression. It's clearly documented in the man page.
Where in the man page does it say you can only have one entry, so cram it all on the same line?
I don't see the discussion in the dnf(8) man page after a quick read. And in particular, the discussion under PACKAGE FILTERING.[1]
I think the use of multiple excludepkgs is intuitive. Each time you want to pin a package, you add an excludepkgs. When you no longer want to pin a package, you delete the particular excludepkgs. I also understand the usage may be one excludepkgs with commas separating a list of package names. That makes sense, too.
I think this is probably a documentation bug. You should file a bug report at https://bugzilla.redhat.com/ .
Jeff