On 03/30/2016 09:11 AM, Jan Zelený wrote:
On 30. 3. 2016 at 06:35:19, Ralf Corsepius wrote:
> On 03/29/2016 07:36 PM, CLOSE Dave wrote:
>> If I run something like, "dnf -y install xxxx", and xxxx is already
>> installed, DNF gives a response like the following.
>>
>> Last metadata expiration check performed 0:00:02 ago on ...
>> Package xxxx is already installed, skipping.
>>
>> ... (long delay, sometimes several minutes) ...
>>
>> Dependencies resolved.
>> Nothing to do.
>> Complete!
>>
>> That is, it works but it takes an unreasonably long time to do so. How
>> can it be that, DNF knows the package is already installed and /still/
>> takes such a long time to decide that dependencies are ok? There aren't
>> any dependencies to resolve!
>
> I've seen and am seeing this happening many times, but I've given up
> complaining about it, because I feel feedback on the numerous defects
> dnf has, is politically unwanted.
Feedback is always welcome, as long as it's constructive and both sides want
to find mutually acceptable solution.
You certainly know that I am tired of hearing
sentences like these. To
me this, are all shallow and weak excuses.
As a German proverb says: "The bucket goes to the well until it breaks".
Now the bucket is broken (read: my patience with dnf and the folks
behind it is finally finished)
I am expecting Red Hat to finally take consequence on dnf and to stop
shipping broken banana SW, such as dnf
Ralf