Re: dnf-4.19.0 without filelists in Rawhide soon

Yep, this is a topic for potential improvement. Currently, there's a simple file path detection, like "arg[0] == '/' || (arg[0] == '*' && arg[1] == '/')", and filelists are always additionally downloaded in such cases. The situation aligns with dnf5 at the moment, and there's already a tracking

Re: dnf-4.19.0 without filelists in Rawhide soon

/usr/bin/BINARYNAME is part of the primary metadata AFAIK Vít Dne 14. 02. 24 v 10:49 Jan Kolarik napsal(a): Hi Marcin, > So no more "dnf install /usr/bin/BINARYNAME" in default setup? In the case where a file path argument is provided to dnf, it will automatically attempt to download the

Re: dnf-4.19.0 without filelists in Rawhide soon

Hi Marcin, > So no more "dnf install /usr/bin/BINARYNAME" in default setup? In the case where a file path argument is provided to dnf, it will automatically attempt to download the missing filelists metadata. Sorry, I forgot to explicitly mention this use case. Jan On Wed, Feb 14, 2024 at

Re: dnf-4.19.0 without filelists in Rawhide soon

W dniu 9.02.2024 o 14:02, Jan Kolarik pisze: Just a heads up that a new DNF version (4.19.0) is on its way to Rawhide and is expected to land within the next several hours. This update brings a system-wide change related to not

Re: dnf-4.19.0 without filelists in Rawhide soon

Dne 09. 02. 24 v 16:29 Florian Weimer napsal(a): What's the impact on mock and older chroots? Just use bootstrap chroot? Yes, in rawhide if you build package for older chroot, you will have to use bootstrap chroot. It is enabled by default. You will have problems if you disabled it manually.

Re: dnf-4.19.0 without filelists in Rawhide soon

Hi Florian, What's the impact on mock and older chroots? Just use bootstrap chroot? I don't expect any issues with existing environments. If the filelists metadata is already present on the system, DNF simply won't load them by default now. Or are you referring to something else? Regards, Jan

Re: dnf-4.19.0 without filelists in Rawhide soon

* Jan Kolarik: > From a Fedora user perspective, there won't be any changes in the way > you operate the DNF package manager. The only difference is that > typically there will be less metadata downloaded. Since all packages > in Fedora should have already eliminated file dependencies requiring