Off a fresh install of F20 because upgrade did not work spectacularly, I noticed that there are a number of F19 packages (including some from rpmfusion) on my machine.
a52dec.x86_64 0.7.4-18.fc19 @rpmfusion-free bouncycastle-tsp.noarch 1.46-6.fc19 @fedora emacs-common-ess.noarch 12.09-3.fc19 @fedora emacs-ess.noarch 12.09-3.fc19 @fedora gstreamer-plugins-espeak.x86_64 0.4.0-2.fc19 @fedora/$releasever lame-libs.x86_64 3.99.5-2.fc19 @rpmfusion-free libdca.x86_64 0.0.5-7.fc19 @rpmfusion-free libmad.x86_64 0.15.1b-16.fc19 @rpmfusion-free pdftk.x86_64 1.44-11.fc19 @fedora pymetar.noarch 0.14-9.fc19 @fedora vcdimager.x86_64 0.7.24-6.fc19 @rpmfusion-free vcdimager-libs.x86_64 0.7.24-6.fc19 @rpmfusion-free
Why so? I especially care about emacs-common, emacs-ess and pdftk and the compat-gcc-***
Thanks, Ranjan
On 12/18/2013 10:42 PM, Ranjan Maitra wrote:
Off a fresh install of F20 because upgrade did not work spectacularly, I noticed that there are a number of F19 packages (including some from rpmfusion) on my machine.
That just means that there's not a newer version available. Fedora doesn't do a mass repackaging for every version, and that's a Good Thing. Imagine how much more you'd need to download for an upgrade if they did.
On Wed, 18 Dec 2013 22:46:07 -0800 Joe Zeff joe@zeff.us wrote:
On 12/18/2013 10:42 PM, Ranjan Maitra wrote:
Off a fresh install of F20 because upgrade did not work spectacularly, I noticed that there are a number of F19 packages (including some from rpmfusion) on my machine.
That just means that there's not a newer version available. Fedora doesn't do a mass repackaging for every version, and that's a Good Thing. Imagine how much more you'd need to download for an upgrade if they did.
I am not sure I know why it is a good or bad thing. Seems to me that it would make sense is a context where we would not have to upgrade at all, which is what would happen if we just had a rolling release model....
Thanks for the clarification!
Best, Ranjan
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On Thu, 19 Dec 2013 01:16:03 -0600 Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
which is what would happen if we just had a rolling
release model....
That was argued to death on @devel it lost
On 19.12.2013 07:46, Joe Zeff wrote:
On 12/18/2013 10:42 PM, Ranjan Maitra wrote:
Off a fresh install of F20 because upgrade did not work spectacularly, I noticed that there are a number of F19 packages (including some from rpmfusion) on my machine.
That just means that there's not a newer version available. Fedora doesn't do a mass repackaging for every version, and that's a Good Thing. Imagine how much more you'd need to download for an upgrade if they did.
That just means that someone haven done his job or there was an error during package rebuild which hasn't been fixed yet (correct me if I'm wrong but there is something like mass rebuild in Fedora).
Please file bugzilla report against this packages but excluding that from rpmfussion.
Mateusz Marzantowicz
On Thu, 19 Dec 2013 11:17:46 +0100 Mateusz Marzantowicz mmarzantowicz@osdf.com.pl wrote: ownload for an upgrade if they did.
That just means that someone haven done his job or there was an error during package rebuild which hasn't been fixed yet (correct me if I'm wrong but there is something like mass rebuild in Fedora).
Please file bugzilla report against this packages but excluding that from rpmfussion.
Wrong, yum update was used (check earlier threads from op) yum distro-sync is your friend.
On Thu, 19 Dec 2013 10:22:14 +0000 Frank Murphy frankly3d@gmail.com wrote:
On Thu, 19 Dec 2013 11:17:46 +0100 Mateusz Marzantowicz mmarzantowicz@osdf.com.pl wrote: ownload for an upgrade if they did.
That just means that someone haven done his job or there was an error during package rebuild which hasn't been fixed yet (correct me if I'm wrong but there is something like mass rebuild in Fedora).
Please file bugzilla report against this packages but excluding that from rpmfussion.
Wrong, yum update was used (check earlier threads from op) yum distro-sync is your friend.
Actually not in this case. It was a clean install.
Thanks, Ranjan
-- Regards, Frank www.frankly3d.com
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On Thu, 19 Dec 2013 07:36:39 -0600 Ranjan Maitra maitra.mbox.ignored@inbox.com wrote:
Actually not in this case. It was a clean install.
I would still run "yum --releasever=20 distro-sync --skip-broken"
On 12/19/13 21:36, Ranjan Maitra wrote:
On Thu, 19 Dec 2013 10:22:14 +0000 Frank Murphy frankly3d@gmail.com wrote:
On Thu, 19 Dec 2013 11:17:46 +0100 Mateusz Marzantowicz mmarzantowicz@osdf.com.pl wrote: ownload for an upgrade if they did.
That just means that someone haven done his job or there was an error during package rebuild which hasn't been fixed yet (correct me if I'm wrong but there is something like mass rebuild in Fedora).
Please file bugzilla report against this packages but excluding that from rpmfussion.
Wrong, yum update was used (check earlier threads from op) yum distro-sync is your friend.
Actually not in this case. It was a clean install.
As previously pointed out, there is nothing to be concerned about. There are cases where a package is not rebuilt to fc20. If you look at the Packages directory in the F20 DVD you'd find....
dbus-java-2.7-12.fc19.x86_64.rpm gstreamer-plugins-espeak-0.4.0-2.fc19.x86_64.rpm keybinder-0.3.0-2.fc19.x86_64.rpm liblqr-1-0.4.1-5.fc19.x86_64.rpm rubygem-therubyracer-0.11.0-2.fc19.x86_64.rpm
and I would expect there to be others in the repos for things not on the DVD.
On 19.12.2013 11:22, Frank Murphy wrote:
On Thu, 19 Dec 2013 11:17:46 +0100 Mateusz Marzantowicz mmarzantowicz@osdf.com.pl wrote: ownload for an upgrade if they did.
That just means that someone haven done his job or there was an error during package rebuild which hasn't been fixed yet (correct me if I'm wrong but there is something like mass rebuild in Fedora).
Please file bugzilla report against this packages but excluding that from rpmfussion.
Wrong, yum update was used (check earlier threads from op) yum distro-sync is your friend.
How yum distro-sync command is related to availability of package in software repositories? Packages are either there or not regardless of command you issued locally to install/update them.
It's also worth noting that it might be important to have packages for exact distro release because of changes in run time environment, build system and other policies from one Fedora release to another. Package from fc17 may work well in fc20 but I don't think it's encouraged behavior.
Mateusz Marzantowicz
On Thu, 19 Dec 2013 15:18:18 +0100 Mateusz Marzantowicz mmarzantowicz@osdf.com.pl wrote:
On 19.12.2013 11:22, Frank Murphy wrote:
On Thu, 19 Dec 2013 11:17:46 +0100 Mateusz Marzantowicz mmarzantowicz@osdf.com.pl wrote: ownload for an upgrade if they did.
That just means that someone haven done his job or there was an error during package rebuild which hasn't been fixed yet (correct me if I'm wrong but there is something like mass rebuild in Fedora).
Please file bugzilla report against this packages but excluding that from rpmfussion.
Wrong, yum update was used (check earlier threads from op) yum distro-sync is your friend.
How yum distro-sync command is related to availability of package in software repositories? Packages are either there or not regardless of command you issued locally to install/update them.
Because it will pull in the packages available for that release. Regardless whther NVR is higher\lower. yum update will not.
maintainers can pull out of mass rebuilds and build when they are ready.