Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1154973 - thunderbird-lightning blocking upgrade to RHEL6.6, needs update
Summary: thunderbird-lightning blocking upgrade to RHEL6.6, needs update
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: thunderbird-lightning
Version: el6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-21 07:32 UTC by bugreports2005
Modified: 2014-11-12 23:13 UTC (History)
4 users (show)

Fixed In Version: thunderbird-lightning-3.3-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-12 23:13:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description bugreports2005 2014-10-21 07:32:11 UTC 
Description of problem:

RHEL6.6 arrived with thunderbird 31, with which EPEL thunderbird-lightning is incompatible. This blocks upgrade.

Could a compatible thunderbird-lightning be built for RHEL6.6?

Version-Release number of selected component (if applicable):
2.6.5-2.el6.x86_64


How reproducible:
Try to upgrade RHEL6.5 to 6.6 with thunderbird-enigmail installed

Steps to Reproduce:
1. yum update
2.
3.


Actual results:

Error: Package: thunderbird-lightning-2.6.5-2.el6.x86_64 (@epel_rhel6_ws_x86_64)
           Requires: thunderbird < 25.0
           Removing: thunderbird-24.8.0-1.el6_5.x86_64 (@rhel-x86_64-workstation-6)
               thunderbird = 24.8.0-1.el6_5
           Updated By: thunderbird-31.2.0-3.el6_6.x86_64 (rhel-x86_64-workstation-6)


Expected results:

Complete!


Additional info:
Comment 1 Oliver Ilian 2014-10-24 08:17:52 UTC 
do we have any ETA for the update, as my users are getting a bit impatient :).

Is there any way we can help?
Comment 2 Fedora Update System 2014-10-24 14:50:07 UTC 
thunderbird-lightning-3.3-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/thunderbird-lightning-3.3-1.el6
Comment 3 Galen Seitz 2014-10-27 23:04:12 UTC 
Where can I find the testing package?  I tried the following command, per the epel wiki (https://fedoraproject.org/wiki/EPEL/testing) but it did not find the package:
sudo yum install thunderbird-lightning --enablerepo=epel-testing

I thought I might find it at http://dl.fedoraproject.org/pub/epel/testing/6/x86_64/, but it's not there either.  Obviously I'm not looking in the correct place, as I see that Oliver has apparently tested the package.
Comment 4 Oliver Ilian 2014-10-27 23:09:34 UTC 
Hi Galen, 

I used the rpm from: http://koji.fedoraproject.org/koji/buildinfo?buildID=587067

So far the package is only requested to go into epel testing, and there for not available in the repo right now. 

Hope that helps to test. 

Cheers Oliver
Comment 5 Orion Poplawski 2014-10-28 00:54:37 UTC 
The update has not yet been pushed to testing yet, so you'll need to pull it from koji until it is.
Comment 6 Fedora Update System 2014-10-28 11:02:17 UTC 
Package thunderbird-lightning-3.3-1.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing thunderbird-lightning-3.3-1.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-3624/thunderbird-lightning-3.3-1.el6
then log in and leave karma (feedback).
Comment 7 Fedora Update System 2014-11-12 23:13:35 UTC 
thunderbird-lightning-3.3-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.