Is it a bug in DNF or a fault by maintainer?

[Christopher Meng]

Hi all,

As mostly described in the bug[1], I encountered upgrade path issue
from 26 to rawhide, which has been here for a long time preventing a
complete update without manual exclusion.

DNF in my computer says:

# dnf update catfish* 1>/dev/null

 Problem: cannot install both catfish-common-1.4.2-2.fc28.3.noarch and
catfish-common-1.4.2-2.fc26.2.noarch
  - package catfish-1.4.2-2.fc26.2.noarch requires catfish-common =
1.4.2-2.fc26.2, but none of the providers can be installed
  - cannot install the best update candidate for package
catfish-common-1.4.2-2.fc26.2.noarch
  - problem with installed package catfish-1.4.2-2.fc26.2.noarch

While maintainer said:

$ rpmdev-vercmp 1.4.2-2.fc28.3 1.4.2-2.fc26.2
1.4.2-2.fc28.3 > 1.4.2-2.fc26.2

Both are demonstrably true.

Should I report a bug against DNF now?

[1]---https://bugzilla.redhat.com/show_bug.cgi?id=1514296

Yours sincerely,
Christopher Meng

[Matthew Miller]

On Fri, Nov 17, 2017 at 09:59:17PM +0800, Christopher Meng wrote:
>  As mostly described in the bug[1], I encountered upgrade path issue
>  from 26 to rawhide, which has been here for a long time preventing a
>  complete update without manual exclusion.
>  DNF in my computer says:
>  # dnf update catfish* 1>/dev/null 
Does this error happen if you update _everything_, not just "catfish*"?
What if you explicitly say "dnf update catfish catfish-common
catfish-python3"? 

If that fails, this sounds like a DNF bug.

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Christopher Meng]

On 11/17/17, Matthew Miller <mattdm(a)fedoraproject.org&gt; wrote:
>  Does this error happen if you update _everything_, not just
> "catfish*"?
>  What if you explicitly say "dnf update catfish catfish-common
>  catfish-python3"? 
If I update Everything, DNF will automatically exclude catfish since
it cannot satisfy the dependencies.

>  If that fails, this sounds like a DNF bug. 
It's not that kind error which occurs during transaction explicitly,
DNF is at least a little bit smart to prevent it from happening.

Yours sincerely,
Christopher Meng

[Sérgio Basto]

On Sun, 2017-11-19 at 18:10 +0800, Christopher Meng wrote:
>  On 11/17/17, Matthew Miller <mattdm(a)fedoraproject.org&gt; wrote:
>  > Does this error happen if you update _everything_, not just
>  > "catfish*"?
>  > What if you explicitly say "dnf update catfish catfish-common
>  > catfish-python3"?
>  
>  If I update Everything, DNF will automatically exclude catfish since
>  it cannot satisfy the dependencies. 
try: dnf update --best 

>  > If that fails, this sounds like a DNF bug.
>   
I bet it is more a issue in provides/obsoletes of catfish

>  It's not that kind error which occurs during transaction
> explicitly,
>  DNF is at least a little bit smart to prevent it from happening.
>  
>  Yours sincerely,
>  Christopher Meng
>  _______________________________________________
>  devel mailing list -- devel(a)lists.fedoraproject.org
>  To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org 
-- 
Sérgio M. B.

[Mamoru TASAKA]

Christopher Meng wrote on 11/17/2017 10:59 PM:
>  Hi all,
>  
>  As mostly described in the bug[1], I encountered upgrade path issue
>  from 26 to rawhide, which has been here for a long time preventing a
>  complete update without manual exclusion.
>  
>  DNF in my computer says:
>  
>  # dnf update catfish* 1>/dev/null
>  
>    Problem: cannot install both catfish-common-1.4.2-2.fc28.3.noarch and
>  catfish-common-1.4.2-2.fc26.2.noarch
>     - package catfish-1.4.2-2.fc26.2.noarch requires catfish-common =
>  1.4.2-2.fc26.2, but none of the providers can be installed
>     - cannot install the best update candidate for package
>  catfish-common-1.4.2-2.fc26.2.noarch
>     - problem with installed package catfish-1.4.2-2.fc26.2.noarch
>  
>  While maintainer said:
>  
>  $ rpmdev-vercmp 1.4.2-2.fc28.3 1.4.2-2.fc26.2
>  1.4.2-2.fc28.3 > 1.4.2-2.fc26.2
>  
>  Both are demonstrably true.
>  
>  Should I report a bug against DNF now?
>  
>  [1]---https://bugzilla.redhat.com/show_bug.cgi?id=1514296
>   
Ah, turned out that this is due to python2- automated namespace
change bug introduced by 318a44255dec768ddcd4762a2669c239cde15312
during https://fedoraproject.org/wiki/FinalizingFedoraSwitchtoPython3

Looks like automated renaming script failed to check
Provides / Obsoletes correctly.

Regards,
Mamoru