Hi,
I just gave fedup a try and found myself confronted with this:
# yum update ...
# fedup --network 22 ... WARNING: potential problems with upgrade sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) requires sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) ... WARNING: problems were encountered during transaction test: broken dependencies sqlitebrowser-3.6.0-1.fc22.x86_64 requires sqlitebrowser-3.6.0-1.fc22.x86_64
?!?
Ralf
On 05/08/2015 06:32 AM, Ralf Corsepius wrote:
Hi,
I just gave fedup a try and found myself confronted with this:
# yum update ...
# fedup --network 22 ... WARNING: potential problems with upgrade sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) requires sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) ... WARNING: problems were encountered during transaction test: broken dependencies sqlitebrowser-3.6.0-1.fc22.x86_64 requires sqlitebrowser-3.6.0-1.fc22.x86_64
See also https://bugzilla.redhat.com/show_bug.cgi?id=1214931, for a similar message about
WARNING: potential problems with upgrade yum-3.4.3-152.fc20.noarch (replaced by yum-3.4.3-505.fc22.noarch) requires yum-3.4.3-152.fc20.noarch (replaced by yum-3.4.3-505.fc22.noarch)
On 05/08/2015 04:57 PM, Eric Blake wrote:
On 05/08/2015 06:32 AM, Ralf Corsepius wrote:
Hi,
I just gave fedup a try and found myself confronted with this:
# yum update ...
# fedup --network 22 ... WARNING: potential problems with upgrade sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) requires sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) ... WARNING: problems were encountered during transaction test: broken dependencies sqlitebrowser-3.6.0-1.fc22.x86_64 requires sqlitebrowser-3.6.0-1.fc22.x86_64
See also https://bugzilla.redhat.com/show_bug.cgi?id=1214931, for a similar message about
WARNING: potential problems with upgrade yum-3.4.3-152.fc20.noarch (replaced by yum-3.4.3-505.fc22.noarch) requires yum-3.4.3-152.fc20.noarch (replaced by yum-3.4.3-505.fc22.noarch)
In my case, my guess is the origin of the breakdown is a side effect of the f22 repo currently being in a broken state:
Proof: On an up2date fc22 system:
# dnf install sqlitebrowser Error: nothing provides libqhexedit-qt5.so.1()(64bit) needed by sqlitebrowser-3.6.0-1.fc22.x86_64
Apparently sqlitebrowser was pushed to the repos, but not the necessarily required qhexedit2-qt5-libs-0.6.6-1.fc23.x86_64 (which provides ibqhexedit-qt5.so.1).
Nevertheless the WARNING above seems just broken.
Ralf
Hi,
I just gave fedup a try and found myself confronted with this:
# yum update ...
# fedup --network 22 ... WARNING: potential problems with upgrade sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) requires sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) ... WARNING: problems were encountered during transaction test: broken dependencies sqlitebrowser-3.6.0-1.fc22.x86_64 requires sqlitebrowser-3.6.0-1.fc22.x86_64
?!?
Unfortunately, broken dependencies occur almost every time you use fedup, especially before final release. It's because it uses "update" instead of "distro-sync" mode [1]. If there are no serious breakages (regarding core system packages), just perform the upgrade and then run "dnf distro-sync" in the upgraded system to fix it.
Of course, it's great if you file tickets in bugzilla against those broken packages.
On 05/11/2015 09:09 AM, Kamil Paral wrote:
Hi,
I just gave fedup a try and found myself confronted with this:
# yum update ...
# fedup --network 22 ... WARNING: potential problems with upgrade sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) requires sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) ... WARNING: problems were encountered during transaction test: broken dependencies sqlitebrowser-3.6.0-1.fc22.x86_64 requires sqlitebrowser-3.6.0-1.fc22.x86_64
?!?
Unfortunately, broken dependencies occur almost every time you use fedup, especially before final release.
I know. I have been complaing about this release process *defect* ever since Fedora exists.
It's because it uses "update" instead of "distro-sync" mode [1].
Well, I do not think this reasoning applies in this case:
Both packages in question are provided through the f22 repos:
https://dl.fedoraproject.org/pub/fedora/linux/development/22/x86_64/os/Packa...
https:dl.fedoraproject.org/pub/fedora/linux/development/22/x86_64/os/Packages/q/qhexedit2-qt5-libs-0.6.6-1.fc22.x86_64.rpm
It's just that fedup fails handling them miserably (== bug #1), producing bogus error messages (== bug #2).
Ralf
On 05/08/2015 02:32 PM, Ralf Corsepius wrote:
Hi,
I just gave fedup a try and found myself confronted with this:
# yum update ...
The situation has worsened: ,,, WARNING: potential problems with upgrade 4:texlive-luatex-bin-svn31084.0-7.1.20140525_r34255.fc21.x86_64 (no replacement) requires poppler-0.26.2-9.fc21.x86_64 (replaced by poppler-0.30.0-3.fc22.x86_64) sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) requires sqlitebrowser-3.5.1-1.fc21.x86_64 (replaced by sqlitebrowser-3.6.0-1.fc22.x86_64) 4:texlive-pdftex-bin-svn30845.0-7.1.20140525_r34255.fc21.x86_64 (no replacement) requires poppler-0.26.2-9.fc21.x86_64 (replaced by poppler-0.30.0-3.fc22.x86_64) ... WARNING: problems were encountered during transaction test: broken dependencies sqlitebrowser-3.6.0-1.fc22.x86_64 requires sqlitebrowser-3.6.0-1.fc22.x86_64 texlive-luatex-bin-4:svn31084.0-7.1.20140525_r34255.fc21.x86_64 requires poppler-0.26.2-9.fc21.x86_64 texlive-pdftex-bin-4:svn30845.0-7.1.20140525_r34255.fc21.x86_64 requires poppler-0.26.2-9.fc21.x86_64 ...
Ralf
On Thu, 2015-05-14 at 08:31 +0200, Ralf Corsepius wrote:
On 05/08/2015 02:32 PM, Ralf Corsepius wrote:
Hi,
I just gave fedup a try and found myself confronted with this:
# yum update ...
The situation has worsened: ,,, WARNING: potential problems with upgrade 4:texlive-luatex-bin-svn31084.0-7.1.20140525_r34255.fc21.x86_64 (no replacement) requires poppler-0.26.2-9.fc21.x86_64 (replaced by poppler-0.30.0-3.fc22.x86_64)
https://admin.fedoraproject.org/updates/FEDORA-2015-7564/texlive-2014 -8.20140525_r34255.fc22 was pushed stable five days ago (05-10) and looks like it should resolve this: it requires the same soname as the current poppler package provides. It sounds like your repositories are somehow out of date?
On 05/15/2015 10:51 PM, Adam Williamson wrote:
On Thu, 2015-05-14 at 08:31 +0200, Ralf Corsepius wrote:
On 05/08/2015 02:32 PM, Ralf Corsepius wrote:
Hi,
I just gave fedup a try and found myself confronted with this:
# yum update ...
The situation has worsened: ,,, WARNING: potential problems with upgrade 4:texlive-luatex-bin-svn31084.0-7.1.20140525_r34255.fc21.x86_64 (no replacement) requires poppler-0.26.2-9.fc21.x86_64 (replaced by poppler-0.30.0-3.fc22.x86_64)
https://admin.fedoraproject.org/updates/FEDORA-2015-7564/texlive-2014 -8.20140525_r34255.fc22 was pushed stable five days ago (05-10) and looks like it should resolve this: it requires the same soname as the current poppler package provides. It sounds like your repositories are somehow out of date?
Well, quite likely, but not deliberately. AFAICT, there had been broken F22 pushes and quite a few broken/out-of-sync F22 EU mirrors, this week.
Also, FWIW, I have been facing these issues on 3 machines with fully updated F21. From this, I conclude likely is a systematic problem and not a "random repository hick-up"
This is what I am observing on 2 of these boxes right now:
# yum update ... No packages marked for update
# fedup --network 22 WARNING: potential problems with upgrade firefox-38.0-4.fc21.x86_64 (no replacement) requires libicu-52.1-6.fc21.x86_64 (replaced by libicu-54.1-1.fc22.x86_64) ... WARNING: problems were encountered during transaction test: broken dependencies firefox-38.0-4.fc21.x86_64 requires libicu-52.1-6.fc21.x86_64 ...
IMO, today's case seems to be caused by an inconsistency between the Fedora 21 and Fedora 22 repos. This would be the classic design flaw in fedora's release process during this phase of release preps (fc21's firefox is newer than fc22's, but fc21's firefox depends on older libs)
Ralf