If you update your Fedora 22 install using DNF on the command line, you may notice that some of the packages that are downloaded and installed still have the release label of
in the package name. For example, if you install or update GitPython on Fedora 22, you will get the following package:
GitPython-0.3.2-0.7.RC1.fc21.noarch.rpm
While some other packages have the
label, like the main git package:
git-2.4.0-1.fc22.x86_64.rpm
.. and this is perfectly all right. Usually, for a new release, the entire Fedora package set is rebuilt. This time around, however, there wasn’t enough time in the Fedora 22 cycle for this “mass rebuild” as it’s called. These packages from Fedora 21 will not cause any issues in your Fedora 22 installations at all. So, if you do run dnf commands and notice these in the transactions, please do not let them worry you.
If you do have questions, please ask the community at http://ask.fedoraproject.org!
Poster
Just like every other release of Fedora ever.
Matthew Miller
Well, before F21, no releases contained fc21 packages. 🙂
But, yes, it’s fairly common for this to happen. However, it’s also the case that for the last few releases we’ve done a mass rebuild, and this is the first in a while where we didn’t, so a number of newer Fedora users were alarmed.
Nick N
So let’s just call this release F21.2 then?
patrick
Does this update include support for this bluetooth adapter?
0bda:b728 Realtek Semiconductor Corp.
Sponge Bob
I upgraded using fedup without an issue. But when I woke up in the morning, the screen is blank but the system isn’t hang. I had to press the power switch. It’s been a while since this behavior last occurred, I think FC10.
Toma
Btw. Why are the packages are still called fc22 resp. fc21. Why not f22? Fedora core is gone for a while now!