this is an announcement that KDE SIG has pushed Plasma 5, the next major
version of KDE workspaces, into rawhide as part of the Plasma 5 change for
Fedora 22 .
The upgrade path from KDE 4 should be smooth and doable simply through yum
update without any need for manual intervention, however if you run into any
troubles related to Plasma/KDE we ask you to report them to KDE SIG.
If you want to know more about Plasma 5.2, you can check out the official
release announcement . If you are looking for something more exhausting to
read while you are waiting for yum, you can read Kev Vermette's 10 pages of
Plasma 5.2: Quintessential Breakdown  ;-).
For Fedora 20 and Fedora 21 users, Plasma 5 is still available through
Daniel Vrátil | dvratil(a)redhat.com | dvratil on #kde-devel, #kontact, #akonadi
Software Engineer - KDE Desktop Team, Red Hat Inc.
GPG Key: 0xC59D614F6F4AE348
Fingerprint: 4EC1 86E3 C54E 0B39 5FDD B5FB C59D 614F 6F4A E348
Taskotron doesn't notice if subpackages have been dropped and cause
unresolvable dependencies because they are not obsoleted anywhere.
Examples: jogl2-javadoc, miglayout-examples, glusterfs-regression-tests
rubygem-json-doc, rubygem-rake-doc, and more
Yum is broken in the same way. And by design. When installing a
discontinued subpackage, it happily installs any "old" packages it still
finds in the repos to satisfy dependencies, but it cannot upgrade the
installation afterwards because of unsatisfied deps.
Also a reminder for packagers:
Adhere to Fedora's Packaging Guidelines when removing subpackages!
Add proper Obsoletes tags to your package.
I note the ReplaceYumWithDnf Change page:
says nothing about fedup. However, fedup uses yum:
[adamw@adam fedup (master %)]$ grep -R yum * | wc -l
Has this been considered yet? Should porting fedup to dnf be in the
scope of this Change? Does that affect its practicability for F22?
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
With the new packaging guidelines requiring the setting of a
soname/soversion and referencing the abi-compliance-checker tool I have
completed a first draft of how to check for ABI changes in a package:
Please help by reviewing it for correctness, more so for the WHY than the
HOW. I don't claim to be an expert on ABI/API's.