Bug 505726 - cronie package older than in F10 update repository
Summary: cronie package older than in F10 update repository
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cronie
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Marcela Mašláňová
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-13 09:16 UTC by Milan Kerslager
Modified: 2009-06-16 06:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-16 06:37:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Milan Kerslager 2009-06-13 09:16:14 UTC
Please provide updaed cronie package to be ahead of F10 update repository:

F10: cronie-1.2-8.fc10
F11: cronie-1.2-7.fc11

This issue do not breaks functionality as bug #504980, anaconda handle this smoothly. Just manual update through yum does not work.

Comment 1 Milan Kerslager 2009-06-13 09:18:34 UTC
To detect after update from F10 to F11, issue command:

package-cleanup --orphans

How to workaround this problem in F11:

rpm -Uvh --oldpackage http://download.fedora.redhat.com/pub/fedora/linux/releases/11/Fedora/x86_64/os/Packages/cronie-1.2-7.fc11.x86_64.rpm

Comment 2 Milan Kerslager 2009-06-13 09:20:10 UTC
Above command should be on one line or you have to download package 
cronie-1.2-7.fc11.x86_64.rpm manually and then use:

rpm -Uvh --oldpackage cronie-1.2-7.fc11.x86_64.rpm

Comment 3 Milan Kerslager 2009-06-13 09:23:35 UTC
Sorry. This works for x86_64 only. If you have i386 package, download it from http://download.fedora.redhat.com/pub/fedora/linux/releases/11/Fedora/i386/os/Packages/cronie-1.2-7.fc11.i386.rpm.

Command to check own version (check line with "installed" keyword on right):

yum list cronie

Comment 4 Marcela Mašláňová 2009-06-16 06:37:27 UTC
This was already fixed https://admin.fedoraproject.org/updates/F11/FEDORA-2009-6365
I moved it to stable updates, so it should be all right in few days.


Note You need to log in before you can comment on or make changes to this bug.