Bug 229637 - Epoch for thunderbird in FC6
Epoch for thunderbird in FC6
Status: CLOSED DUPLICATE of bug 227860
Product: Fedora
Classification: Fedora
Component: thunderbird (Show other bugs)
6
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Gecko Maintainer
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-22 07:48 EST by Andrew C Aitchison
Modified: 2008-08-02 19:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-03-04 15:35:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrew C Aitchison 2007-02-22 07:48:29 EST
Description of problem:

The thunderbird package in FC6 has epoch 0, but the package in updates has
no Epoch at all.

Version-Release number of selected component (if applicable):

thunderbird-0:1.5.0.7-4.fc6.x86_64.rpm
thunderbird-(none):1.5.0.9-7.fc6.x86_64.rpm

Steps to Reproduce:
1. wget
http://download.fedora.redhat.com/pub/fedora/linux/core/6/x86_64/os/Fedora/RPMS/thunderbird-1.5.0.7-4.fc6.x86_64.rpm
 wget
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/6/x86_64/thunderbird-1.5.0.9-7.fc6.x86_64.rpm


2.
rpmquery -p --qf '%{name}-%{epoch}:%{version}-%{release}.%{arch}.rpm\n' thunderbird*
thunderbird-0:1.5.0.7-4.fc6.x86_64.rpm
thunderbird-(none):1.5.0.9-7.fc6.x86_64.rpm

yum is happy that thunderbird-1.5.0.9-7.fc6.x86_64.rpm is newer than
thunderbird-1.5.0.7-4.fc6.x86_64.rpm but I have tools that think that
Epoch 0 is newer than Epoch (none).

Additional info:
Comment 2 Christopher Aillon 2007-03-04 15:35:23 EST
This isn't a bug in thunderbird, really.  Epoch 0 is the same as no epoch.  It
only matters because rpm python bindings are broken and produces the wrong
result for the version comparison.  See the dupe.

*** This bug has been marked as a duplicate of 227860 ***

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