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
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
