Bug 1710756 - Cannot upgrade from Fedora 29 to 30 (ekiga and boost-signals)
Summary: Cannot upgrade from Fedora 29 to 30 (ekiga and boost-signals)
Keywords:
Status: CLOSED DUPLICATE of bug 1674843
Alias: None
Product: Fedora
Classification: Fedora
Component: ekiga
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1674843
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-16 09:15 UTC by Milan Crha
Modified: 2019-05-16 14:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-16 13:44:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Milan Crha 2019-05-16 09:15:20 UTC
I tried to upgrade from Fedora 29 to Fedora 30 and it fails on package conflicts. One problem being ekiga and boost-signals. The terminal output:

# dnf system-upgrade download --refresh --releasever=30
Before you continue ensure that your system is fully upgraded by running "dnf --refresh upgrade". Do you want to continue [y/N]: y
Fedora Modular 30 - x86_64                    25 kB/s |  25 kB     00:00    
Fedora Modular 30 - x86_64 - Updates          21 kB/s |  23 kB     00:01    
Fedora Modular 30 - x86_64 - Updates          92 kB/s | 236 kB     00:02    
Fedora 30 - x86_64 - Updates                  24 kB/s |  22 kB     00:00    
Fedora 30 - x86_64                            34 kB/s |  25 kB     00:00    
Error: 
 Problem 1: problem with installed package ekiga-4.0.1-42.fc29.x86_64
  - package ekiga-4.0.1-42.fc29.x86_64 requires libboost_signals.so.1.66.0()(64bit), but none of the providers can be installed
  - boost-signals-1.66.0-14.fc29.x86_64 does not belong to a distupgrade repository
....
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages)

Comment 1 Milan Crha 2019-05-16 09:19:24 UTC
(There had been reported two problems, the second is bug #1710759.)

Comment 2 Jonathan Wakely 2019-05-16 12:55:47 UTC
The ekiga package needs to be fixed or retired, this is not a boost problem.

Comment 3 Robert Scheck 2019-05-16 13:31:06 UTC
I'm already working on this, I've a working Ekiga build locally, but some crashes when calling or being called (which seem to be related to newer GCC optimizations, e.g. bug #1696458).

Comment 4 Milan Crha 2019-05-16 13:44:35 UTC
Aha, my fault. I kind of expected that ekiga has its f30 build, been made as part of the mass rebuild, but I only now realized that its f30 build failed and does not exist:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1186090

I though that the boost forgot to add some obsolete or something like that for the removed package. Badly deciphered message on my side. Again, I'm sorry, my fault.

I'm closing this bug to avoid duplicates.

*** This bug has been marked as a duplicate of bug 1674843 ***

Comment 5 Jonathan Wakely 2019-05-16 13:58:04 UTC
I did forget to add the Obsoletes to boost (that was Bug 1706079) but it's not the problem here, and wouldn't have helped.

Comment 6 Milan Crha 2019-05-16 14:03:25 UTC
> it's not the problem here, and wouldn't have helped.

Yes, I know, I understood as soon as you pointed to the right thing. I just misread the error message before and made some guesses, instead of being sure. I'm sorry.


Note You need to log in before you can comment on or make changes to this bug.