On 2/1/22 12:54 PM, Miro Hrončok wrote:
On 01. 02. 22 18:01, przemek klosowski via devel wrote:


rpm -q -conflicts kicad-6.0.1-4.fc35.x86_64.rpm
kicad-doc < 1:6.0.1-4.fc35
...

When I add the '--best --allowerasing' flags, then I get the desired result:

# dnf update kicad-6.0.1-4.fc35.x86_64.rpm --best --allowerasing
Last metadata expiration check: 0:43:04 ago on Mon 31 Jan 2022 05:06:19 PM EST.
Dependencies resolved.
============================================================================================
  Package            Architecture    Version Repository Size
============================================================================================
Upgrading:
  kicad              x86_64          1:6.0.1-4.fc35 @commandline 90 M
Removing dependent packages:
  kicad-doc          noarch          1:5.1.12-1.fc35 @updates 111 M

Thanks to Steven, Stephen and Miro for finding this solution. Still, having to 
add flags and deleting the existing doc package is not completely 
gruntling---it works, but it's not automatic and, for the future, I am curious 
if there's another way.

Sorry for flogging this fine stallion, but I believe that 'dnf update kicad 
kicad-doc' would have worked (I did check that updating kicad-doc followed by 
updating kicad works). Isn't there some combination of 
Required/Obsoletes/Conflicts/??? to coax dnf to upgrade both packages instead 
of deleting kicad-doc?

This should work without --allowerasing once the packages are actually in a repository. 
"dnf update kicad" will see the newer version of kicad-doc and it will update 
both at the same time.

That is correct.  The --allowerasing only happened because I was testing from a 
local mock build, and deliberately only supplied the main package as part of my 
testing.  You won't have that problem in normal use, once I get Copr to 
complete the build.

However, Copr is being difficult at the moment.  For some reason, the ppc64le 
builders all failed after an hour with:

Connection timed out during banner exchange
Connection to 140.211.168.28 port 22 timed out

Sigh.  The build normally takes over 5 hours.  I'll have to restart it yet 
again.

(Aside: the koji build of KiCad for rawhide went fine, but because KiCad just 
went through a major version change, I have to use Copr for F34/F35.)

        Steve
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to