 |
 |
 |
 |
| F16 Development This section archived once F16 reached final release. |
4th March 2010, 07:47 PM
|
 |
Registered User
|
|
Join Date: Sep 2009
Posts: 1,409
 
|
|
|
Ignore yum list extras?
I'm curious how to handle the output of "yum list extras." I get the following:
Code:
[gene@Mobile-PC ~]$ yum list extras
Loaded plugins: fastestmirror, presto, protect-packages, refresh-packagekit, remove-with-leaves,
: show-leaves, verify
Extra Packages
alsa-lib.x86_64 1.0.22-2.fc12 @updates/12
evolution-data-server.x86_64 2.29.91-1.fc13 @updates-testing/13
glibc.x86_64 2.11.90-14 @updates-testing/13
glibc-common.x86_64 2.11.90-14 @updates-testing/13
glibc-devel.x86_64 2.11.90-14 @updates-testing/13
glibc-headers.x86_64 2.11.90-14 @updates-testing/13
gnome-shell.x86_64 2.28.1-0.2.20100128git @/gnome-shell-2.28.1-0.2.20100128git.x86_64
gpm-libs.x86_64 1.20.6-9.fc12 @updates/12
iptstate.x86_64 2.2.2-4.fc12 @updates/12
jre.x86_64 1.6.0_18-fcs installed
kernel.x86_64 2.6.33-0.52.rc8.git6.fc13 @updates-testing/13
kernel.x86_64 2.6.33-1.fc13 @updates-testing/13
kernel-doc.noarch 2.6.32.8-48.rc2.fc12 @/kernel-doc-2.6.32.8-48.rc2.fc12.noarch/12
krb5-auth-dialog.x86_64 0.13-2.fc12 @anaconda-InstallationRepo-200911081904.x86_64/12
libdvdcss.x86_64 1.2.10-1 @livna/12
libsepol.x86_64 2.0.41-3.fc13 @updates-testing/13
mplayer-codecs.x86_64 3:20061022-1 @/mplayer-codecs-20061022-1.x86_64/12
mplayer-codecs-extra.x86_64 3:20061022-1 @/mplayer-codecs-extra-20061022-1.x86_64/12
neon.x86_64 0.29.3-1.fc12 @updates/12
nscd.x86_64 2.11.90-14 @updates-testing/13
paktype-fonts-common.noarch 2.0-5.fc12 @anaconda-InstallationRepo-200911081904.x86_64/12
plymouth.x86_64 0.8.0-0.20100225.1.fc13 @updates-testing/13
plymouth-core-libs.x86_64 0.8.0-0.20100225.1.fc13 @updates-testing/13
plymouth-gdm-hooks.x86_64 0.8.0-0.20100225.1.fc13 @updates-testing/13
plymouth-graphics-libs.x86_64 0.8.0-0.20100225.1.fc13 @updates-testing/13
plymouth-plugin-label.x86_64 0.8.0-0.20100225.1.fc13 @updates-testing/13
plymouth-plugin-two-step.x86_64 0.8.0-0.20100225.1.fc13 @updates-testing/13
plymouth-scripts.x86_64 0.8.0-0.20100225.1.fc13 @updates-testing/13
plymouth-system-theme.x86_64 0.8.0-0.20100225.1.fc13 @updates-testing/13
plymouth-theme-charge.x86_64 0.8.0-0.20100225.1.fc13 @updates-testing/13
plymouth-utils.x86_64 0.8.0-0.20100225.1.fc13 @updates-testing/13
policycoreutils.x86_64 2.0.79-2.fc13 @updates-testing/13
policycoreutils-gui.x86_64 2.0.79-2.fc13 @updates-testing/13
policycoreutils-python.x86_64 2.0.79-2.fc13 @updates-testing/13
pulseaudio.x86_64 0.9.21-6.fc13 @updates-testing/13
pulseaudio-gdm-hooks.x86_64 0.9.21-6.fc13 @updates-testing/13
pulseaudio-libs.x86_64 0.9.21-6.fc13 @updates-testing/13
pulseaudio-libs-glib2.x86_64 0.9.21-6.fc13 @updates-testing/13
pulseaudio-module-bluetooth.x86_64
0.9.21-6.fc13 @updates-testing/13
pulseaudio-module-gconf.x86_64 0.9.21-6.fc13 @updates-testing/13
pulseaudio-module-x11.x86_64 0.9.21-6.fc13 @updates-testing/13
pulseaudio-utils.x86_64 0.9.21-6.fc13 @updates-testing/13
selinux-policy.noarch 3.7.10-4.fc13 @updates-testing/13
selinux-policy-targeted.noarch 3.7.10-4.fc13 @updates-testing/13
From reading the yum man page, these packages aren't in rawhide yet, but I'm guessing some of them are being updated in the F12 & F13 repos. Is it safe to assume they'll end up in rawhide at the appropriate time?
dd_wizard
Last edited by dd_wizard; 5th March 2010 at 01:19 AM.
|
4th March 2010, 09:55 PM
|
 |
Registered User
|
|
Join Date: Aug 2006
Location: /dev/realm/{Abba,Carpenters,...stage}
Posts: 3,286
|
|
|
IIRC testing/development happens in rawhide, then fixes are backported to stable releases. F13 is a branch if I understood it right, still buggy and needing a lot of work prior to being released. Anything coming from F12 and below should be considered obsolete in respect to F13 or F14, so I don't see how anything deemed stable could land in rawhide.
|
4th March 2010, 10:48 PM
|
|
Registered User
|
|
Join Date: Sep 2009
Posts: 1,409
|
|
|
After doing some exploring with yum, I see how it's working. Those packages are installed on my machine, but not in rawhide, yet. For example, I picked up alsa-lib.x86_64, release 1.0.22-2.fc12 from updates/12. However, the rawhide repo has release 1.0.22-1.fc13. The glibc release 2.11.90-14 on my machine came from updates-testing/13 but rawhide still has release 2.11.90-12. So rawhide can be somewhat out of sync with an existing release that upgrades to rawhide.
dd_wizard
|
4th March 2010, 11:05 PM
|
|
Registered User
|
|
Join Date: Aug 2006
Location: /dev/realm/{Abba,Carpenters,...stage}
Posts: 3,286
|
|
|
dd_wizard, rawhide means F14 for now. At least, that's my understanding of it. And you're talking about F13 packages.
|
4th March 2010, 11:22 PM
|
|
Registered User
|
|
Join Date: Sep 2009
Posts: 1,409
|
|
|
I'm talking about F14, rawhide. Upgrading to F13 when it was rawhide left a few F12 packages around. And upgrading to F14 rawhide left some F12 and F13 packages. Currently, the rawhide repo has older versions of these packages than the F12 and F13 repos had prior to the upgrade to F14 rawhide. I could downgrade to rawhide at this point, or just wait for rawhide to catch up.
dd_wizard
|
4th March 2010, 11:29 PM
|
|
Registered User
|
|
Join Date: Aug 2006
Location: /dev/realm/{Abba,Carpenters,...stage}
Posts: 3,286
|
|
|
Erm, OK, it was a misunderstanding on my part.
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
 Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Current GMT-time: 01:17 (Saturday, 25-05-2013)
|
|
 |
 |
 |
 |
|
|
