Fedora 22 Repositories contain Fedora 21 Packages?

[Sumit Bhardwaj]

Hi All,

I have a fresh installation of Fedora 22 RC1 with all the extra stuff I 
needed installed. Today I was going through the list of packages 
installed on my system and was a little bit surprised to find some 
packages ending in "fc21" in their names. Now, for an upgraded system 
that might happen, but on a clean install, why I am getting FC21 packages?

Because per my understanding, for any branched release, packages are 
completely rebuilt. Then how did this happen?

More to the point, do I have to care about or do something about these? 
Will these be auto upgraded later with their FC22 counterparts?

BTW, below is the list of those packages:

nodejs-lru-cache-2.3.0-5.fc21.noarch
nodejs-cryptiles-0.2.2-2.fc21.noarch
python-pyasn1-0.1.7-4.fc21.noarch
nodejs-assert-plus-0.1.4-2.fc21.noarch
nodejs-cookie-jar-0.3.0-3.fc21.noarch
mono-extras-2.10.8-7.fc21.x86_64
foomatic-db-filesystem-4.0-44.20140707.fc21.noarch
unoconv-0.6-11.fc21.noarch
atom-0.200.0-0.1.fc21.x86_64
nodejs-block-stream-0.0.7-2.fc21.noarch
nodejs-sha-1.2.1-2.fc21.noarch
nodejs-async-0.2.10-2.fc21.noarch
nodejs-couch-login-0.1.18-2.fc21.noarch
mono-mvc-2.10.8-7.fc21.x86_64
nodejs-opener-1.3.0-9.fc21.noarch
pysvn-1.7.6-10.fc21.x86_64
python3-decorator-3.4.0-5.fc21.noarch
system-config-users-docs-1.0.9-7.fc21.noarch
nodejs-graceful-fs-2.0.0-4.fc21.noarch
nodejs-once-1.1.1-7.fc21.noarch
nodejs-tunnel-agent-0.3.0-3.fc21.noarch
nodejs-glob-3.2.6-2.fc21.noarch
npm-1.3.6-6.fc21.noarch
python-mechanize-0.2.5-8.fc21.noarch
alacarte-3.11.91-2.fc21.noarch
color-filesystem-1-15.fc21.noarch
zd1211-firmware-1.4-10.fc21.noarch
ipw2200-firmware-3.1-10.fc21.noarch
jcodings-1.0.9-7.fc21.noarch
docbook-dtds-1.0-63.fc21.noarch
python3-canberra-0-0.6.git65c3b3f.fc21.noarch
nautilus-python-1.1-7.fc21.x86_64
opera-29.0.1795.60-0.fc21.x86_64
python-tempita-0.5.1-8.fc21.noarch
system-config-samba-1.2.100-3.fc21.noarch
python-smmap-0.8.1-8.fc21.noarch
nodejs-hoek-0.9.1-3.fc21.noarch
nodejs-npmlog-0.0.4-3.fc21.noarch
nodejs-delayed-stream-0.0.5-7.fc21.noarch
nodejs-github-url-from-git-1.1.1-4.fc21.noarch
nodejs-node-uuid-1.4.1-2.fc21.noarch
nodejs-mute-stream-0.0.4-2.fc21.noarch
monodoc-2.10.8-7.fc21.x86_64
nodejs-read-installed-0.2.4-3.fc21.noarch
nodejs-lockfile-0.4.2-2.fc21.noarch
itstool-2.0.2-2.fc21.noarch
lua-json-1.3.2-3.fc21.noarch
foomatic-db-ppds-4.0-44.20140707.fc21.noarch
atmel-firmware-1.3-13.fc21.noarch
python3-humanize-0.5-6.fc21.noarch
words-3.0-23.fc21.noarch
ozon-repos-21-5.fc21.noarch
odfpy-0.9.6-2.fc21.noarch
docbook-style-xsl-1.78.1-3.fc21.noarch
docbook-utils-0.6.14-38.fc21.noarch
system-config-samba-docs-1.0.9-7.fc21.noarch
GitPython-0.3.2-0.7.RC1.fc21.noarch
nodejs-fstream-0.1.24-2.fc21.noarch
nodejs-tar-0.1.18-2.fc21.noarch
nodejs-ansi-0.2.1-2.fc21.noarch
nodejs-cmd-shim-1.1.0-5.fc21.noarch
nodejs-form-data-0.1.1-2.fc21.noarch
nodejs-oauth-sign-0.3.0-3.fc21.noarch
nodejs-npm-registry-client-0.2.28-2.fc21.noarch
mono-wcf-2.10.8-7.fc21.x86_64
web-assets-filesystem-5-2.fc21.noarch
nodejs-init-package-json-0.0.10-3.fc21.noarch
nodejs-npm-user-validate-0.0.3-3.fc21.noarch
python-pexpect-3.1-3.fc21.noarch
basesystem-10.0-10.fc21.noarch
gnome-video-effects-0.4.1-2.fc21.noarch
sgabios-bin-0.20110622svn-7.fc21.noarch
python3-beaker-1.5.4-10.fc21.noarch
python3-progress-1.2-4.fc21.noarch
sound-theme-freedesktop-0.8-4.fc21.noarch
python-ply-3.4-7.fc21.noarch
jnr-constants-0.8.4-6.fc21.noarch
jnr-unixsocket-0.2-5.fc21.noarch
jzlib-1.1.3-2.fc21.noarch
docbook-style-dsssl-1.79-20.fc21.noarch
gl-manpages-1.1-9.20140424.fc21.noarch
nodejs-osenv-0.0.3-7.fc21.noarch
nodejs-mime-1.2.11-2.fc21.noarch
mono-core-2.10.8-7.fc21.x86_64
nodejs-nopt-2.1.2-2.fc21.noarch
geany-themes-1.24-2.fc21.noarch
nodejs-packaging-7-2.fc21.noarch
nodejs-ctype-0.5.3-5.fc21.noarch
nodejs-proto-list-1.2.2-7.fc21.noarch
mono-data-sqlite-2.10.8-7.fc21.x86_64
nodejs-forever-agent-0.5.0-3.fc21.noarch
mono-data-2.10.8-7.fc21.x86_64
nodejs-promzard-0.2.0-8.fc21.noarch
mono-nunit-2.10.8-7.fc21.x86_64
nodejs-fstream-npm-0.1.5-3.fc21.noarch
nodejs-chmodr-0.1.0-6.fc21.noarch
fontpackages-filesystem-1.44-10.fc21.noarch
rootfiles-8.1-17.fc21.noarch
python-ntplib-0.3.2-3.fc21.noarch
chmlib-0.40-10.fc21.x86_64
python-paste-1.7.5.1-11.20111221hg1498.fc21.noarch
system-config-date-1.10.7-2.fc21.noarch
python-docutils-0.12-0.2.20140510svn7747.fc21.noarch
python-html5lib-0.999-5.fc21.noarch
nodejs-slide-1.1.5-2.fc21.noarch
nodejs-abbrev-1.0.4-8.fc21.noarch
nodejs-combined-stream-0.0.4-5.fc21.noarch
nodejs-normalize-package-data-0.2.1-2.fc21.noarch
nodejs-json-stringify-safe-5.0.0-3.fc21.noarch
mono-winfx-2.10.8-7.fc21.x86_64
nodejs-read-1.0.5-2.fc21.noarch
mono-devel-2.10.8-7.fc21.x86_64
nodejs-fstream-ignore-0.0.7-3.fc21.noarch
nodejs-editor-0.0.4-4.fc21.noarch
python-cssutils-0.9.9-5.fc21.noarch
xorg-x11-drv-vmmouse-13.0.0-13.fc21.x86_64
b43-openfwwf-5.2-11.fc21.noarch
foomatic-db-4.0-44.20140707.fc21.noarch
ipw2100-firmware-1.3-17.fc21.noarch
poppler-sharp-0.0.3-6.fc21.noarch
bytelist-1.0.8-9.fc21.noarch
d-feet-0.3.9-1.fc21.noarch
xorg-x11-proto-devel-7.7-12.fc21.noarch
python-beaker-1.5.4-10.fc21.noarch
nodejs-mkdirp-0.3.5-5.fc21.noarch
python-ecdsa-0.11-3.fc21.noarch
nodejs-ini-1.1.0-5.fc21.noarch
nodejs-retry-0.6.0-7.fc21.noarch
nodejs-sntp-0.2.4-3.fc21.noarch
nodejs-asn1-0.1.11-5.fc21.noarch
nodejs-npmconf-0.1.3-2.fc21.noarch
nodejs-aws-sign-0.3.0-3.fc21.noarch
mono-winforms-2.10.8-7.fc21.x86_64
nodejs-minimatch-0.2.12-4.fc21.noarch
po-debconf-1.0.16-4.nmu2.fc21.noarch
nodejs-archy-0.0.2-10.fc21.noarch
python-feedparser-5.1.3-7.fc21.noarch
paktype-naskh-basic-fonts-4.1-4.fc21.noarch
redhat-menus-12.0.2-8.fc21.noarch
nodejs-semver-2.1.0-3.fc21.noarch
nodejs-which-1.0.5-10.fc21.noarch
nodejs-config-chain-1.1.7-3.fc21.noarch
nodejs-sigmund-1.0.0-7.fc21.noarch
nodejs-child-process-close-0.1.1-4.fc21.noarch
python-dns-1.11.1-4.fc21.noarch
jnr-x86asm-1.0.2-5.fc21.noarch
pdfmod-0.9.1-8.fc21.noarch
joda-time-2.3-2.tzdata2013g.fc21.noarch
ghostscript-fonts-5.50-33.fc21.noarch
system-config-date-docs-1.0.12-2.fc21.noarch
python-beautifulsoup4-4.3.2-3.fc21.noarch
nodejs-rimraf-2.2.2-2.fc21.noarch
nodejs-chownr-0.0.1-11.fc21.noarch
libcue-1.4.0-4.fc21.x86_64
python-pyasn1-modules-0.1.7-4.fc21.noarch
nodejs-read-package-json-1.1.3-2.fc21.noarch
python-BeautifulSoup-3.2.1-8.fc21.noarch
telepathy-filesystem-0.0.2-7.fc21.noarch
rubypick-1.1.1-2.fc21.noarch
python-decorator-3.4.0-5.fc21.noarch
comps-extras-23-2.fc21.noarch
nodejs-boom-0.4.2-4.fc21.noarch
nodejs-hawk-1.0.0-2.fc21.noarch
pytz-2012d-7.fc21.noarch
nodejs-http-signature-0.10.0-5.fc21.noarch
nodejs-request-2.25.0-2.fc21.noarch
mono-web-2.10.8-7.fc21.x86_64
nodejs-uid-number-0.0.3-9.fc21.noarch

Thanks.

[Josh Boyer]

On Fri, May 22, 2015 at 3:40 PM, Sumit Bhardwaj
 wrote:
> Hi All,
>
> I have a fresh installation of Fedora 22 RC1 with all the extra stuff I
> needed installed. Today I was going through the list of packages installed
> on my system and was a little bit surprised to find some packages ending in
> "fc21" in their names. Now, for an upgraded system that might happen, but on
> a clean install, why I am getting FC21 packages?
>
> Because per my understanding, for any branched release, packages are
> completely rebuilt. Then how did this happen?

This is not always the case.  There was no mass rebuild for Fedora 22.
> More to the point, do I have to care about or do something about these? Will
> these be auto upgraded later with their FC22 counterparts?

No, you don't have to care about them.  They will be upgraded if and
when they are upgraded and built as updates for f22.

josh

[Matthew Miller]

On Sat, May 23, 2015 at 01:10:21AM +0530, Sumit Bhardwaj wrote:
> Because per my understanding, for any branched release, packages are
> completely rebuilt. Then how did this happen?

Simple: we didn't do a mass rebuild this time around.
> More to the point, do I have to care about or do something about
> these? Will these be auto upgraded later with their FC22
> counterparts?

If and only if they're updated.
> BTW, below is the list of those packages:

List more with `dnf list|grep fc21`. :) There are some 5000 packages
which weren't rebuilt at some point during the cycle. The vast majority
of these are noarch packages.

[Kevin Fenzi]

On Sat, 23 May 2015 01:10:21 +0530
Sumit Bhardwaj  wrote:
> Hi All,
>
> I have a fresh installation of Fedora 22 RC1 with all the extra stuff
> I needed installed. Today I was going through the list of packages 
> installed on my system and was a little bit surprised to find some 
> packages ending in "fc21" in their names. Now, for an upgraded system 
> that might happen, but on a clean install, why I am getting FC21
> packages?
>
> Because per my understanding, for any branched release, packages are 
> completely rebuilt. Then how did this happen?

There was no mass rebuild for f22. There was not time in the schedule
to do it and still release around when we wanted to.

Additionally, there's aways some few packages that fail to rebuild in
the mass rebuild but yet continue to work fine. So, on any release you
could see packages from older versions, it's nothing to worry about.
> More to the point, do I have to care about or do something about
> these? Will these be auto upgraded later with their FC22 counterparts?

No. No need to worry. When/if they need an update for some reason, they
would be built with a newer version and you would update.

kevin

[Sumit Bhardwaj]

Thanks a lot for the quick clarifications Matthew, Kevin and Josh! This 
is why I love Fedora project, the most awesome community we have! :)

Regards,
Sumit Bhardwaj

On Saturday 23 May 2015 01:16 AM, Kevin Fenzi wrote:
> On Sat, 23 May 2015 01:10:21 +0530
> Sumit Bhardwaj  wrote:
> > Hi All,
> >
> > I have a fresh installation of Fedora 22 RC1 with all the extra stuff
> > I needed installed. Today I was going through the list of packages
> > installed on my system and was a little bit surprised to find some
> > packages ending in "fc21" in their names. Now, for an upgraded system
> > that might happen, but on a clean install, why I am getting FC21
> > packages?
> >
> > Because per my understanding, for any branched release, packages are
> > completely rebuilt. Then how did this happen?
>
> There was no mass rebuild for f22. There was not time in the schedule
> to do it and still release around when we wanted to.
>
> Additionally, there's aways some few packages that fail to rebuild in
> the mass rebuild but yet continue to work fine. So, on any release you
> could see packages from older versions, it's nothing to worry about.
> > More to the point, do I have to care about or do something about
> > these? Will these be auto upgraded later with their FC22 counterparts?
>
> No. No need to worry. When/if they need an update for some reason, they
> would be built with a newer version and you would update.
>
> kevin

[Emmanuel Seyman]

* Sumit Bhardwaj [23/05/2015 01:10] :
>                    Now, for an upgraded system that might happen, but on
>
> a clean install, why I am getting FC21 packages?

If these packages have not been rebuilt since f22 was forked from rawhide, the
f21 package is the most recent one there is. As such, they are the ones included.
> Because per my understanding, for any branched release, packages are
> completely rebuilt.

This isn't the case. We've had mass rebuilds in the past but no such thing
happened during the f22 developement period.
> More to the point, do I have to care about or do something about these?

No.
>                                                                     Will
>
> these be auto upgraded later with their FC22 counterparts?

No.

Emmanuel