kolage

Make sure these scenarios are covered: - https://github.com/rpm-software-management/dnf/issues/2031 - https://issues.redhat.com/browse/RHEL-17494 Related PR in libdnf: - https://github.com/rpm-software-management/libdnf/pull/1644.

The current approach to handling deprecated methods has been reported as insufficient by our API clients. Before implementing any changes, we should review existing standards to increase the likelihood of...

After discussing with the RPM team the future of the above mentioned [RPM PR](https://github.com/rpm-software-management/rpm/pull/3083), we concluded that it is not sufficient to solve the issue, as follow-up work in rpm-sequoia...

The file is already in the sources, but I haven't deployed it yet as I wanted to check everything there is valid also for `dnf5`.

> OK, I found the issue, I'm opening a bug report on bugzilla. Thanks! https://bugzilla.redhat.com/show_bug.cgi?id=2275530 Thanks for finding the cause! We'll try to look into it soon.

Also this behavior should be documented in the dnf4 vs dnf5 changes doc.

I was searching for some existing standard related to this topic and found the following link: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html. According to **2. a.**, conforming applications should support both `-xdnf` and `-x dnf`...

Since there has been no feedback for some time, let's finalize our implementation approach. It seems we agree on not supporting the `=` delimiter for short options. If so, we...

Getting back to this. As @kontura mentioned, using the `-q` or `--quiet` option now suppresses the repository metadata update messages. Regarding sending repository metadata update messages to standard output, POSIX...

> This behavior is unexpected and unpleasant to work with. ... snip ... > This is just broken. It's certainly possible to work around the issue, but as multiple people...