Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 160811 - Upgrade from FC3 + updates to FC4 doesn't update vixie-cron package
Summary: Upgrade from FC3 + updates to FC4 doesn't update vixie-cron package
Alias: None
Product: Fedora
Classification: Fedora
Component: vixie-cron
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Marcela Mašláňová
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2005-06-17 13:52 UTC by Nils Philippsen
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: vixie-cron-4.1-41.FC4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-08-29 12:53:11 UTC

Attachments (Terms of Use)

Description Nils Philippsen 2005-06-17 13:52:53 UTC
+++ This bug was initially created as a clone of Bug #160808 +++

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524
Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
When upgrading from an updated FC3 to FC4, the vixie-cron package won't get
updated because the RPM release of the FC4 package is lower than that of the
corresponding FC3 update. This is particularly bad because that way the user
misses all the security related goodies coming with gcc4.

Version-Release number of selected component (if applicable):
vixie-cron-4.1-33_FC3, vixie-cron-4.1-33

How reproducible:

Steps to Reproduce:
1. Upgrade an updated FC3 with vixie-cron package to FC4

Actual Results:  vixie-cron package won't get updated

Expected Results:  vixie-cron package gets updated

Additional info:

When using disttags, ensure that the release tag of packages in a released
version of the distribution are always lower than in Rawhide/devel. This can be
achieved e.g. using one of these schemes for the release tag (with %dist being
the distver tag, e.g. "fc3", "fc4" and %rel being the release number to base on):

- the manual way: released distro: "0.%dist.%rel", Rawhide/devel "%rel"
- a variant, based on a distver being defined by the buildsystem (or in the spec
file) for released distro versions but not in Rawhide/devel: "%{?dist:0.%dist.}%rel"

Comment 1 Jason Vas Dias 2005-06-17 19:26:33 UTC
I've now submitted 2:vixie-cron-4.1-FC5_34 and 2:vixie-cron-4.1-FC4_34
An epoch bump was necessary to get them to compare > vixie-cron-4.1-33

Comment 2 Nils Philippsen 2005-06-27 13:38:23 UTC
Hmm, wouldn't it have been sufficient to just do a release bump to 33_FC4 on the
FC4 branch? No need to remove number and dist tag in the release IMO.

Comment 3 Nils Philippsen 2005-06-27 13:52:31 UTC
s/remove/swap/ -- it's too hot here right now.

Comment 4 Marcela Mašláňová 2006-08-29 12:53:11 UTC
All updates has %dist at the end, it has to work now.

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