Bug 723348 - Thunderbird-lightning update won't install
Summary: Thunderbird-lightning update won't install
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird-lightning
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 723707 724913 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-19 20:18 UTC by Jonathan Ryshpan
Modified: 2011-07-22 16:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-21 21:34:47 UTC
Type: ---


Attachments (Terms of Use)

Description Jonathan Ryshpan 2011-07-19 20:18:31 UTC
Description of problem: 
Lightening update is present in repo, but can't be installed because of a missing requirement.


Version-Release number of selected component (if applicable):
thunderbird-lightning-1.0-0.44.b3pre.fc15.x86_64


How reproducible:
Always.


Steps to Reproduce:
1. Attempt udate

  
Actual results:
Error box containing this message:
thunderbird-lightning-1.0-0.44.b3pre.fc15.x86_64 requires thunderbird >= 5.0 : Success - empty transaction


Expected results:
Update succeeds.


Additional info:

Comment 1 Jerry Amundson 2011-07-20 00:56:19 UTC
me too.
# yum update
Loaded plugins: langpacks, presto, refresh-packagekit
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package thunderbird-lightning.i686 0:1.0-0.41.b3pre.fc15 will be updated
---> Package thunderbird-lightning.i686 0:1.0-0.44.b3pre.fc15 will be an update
--> Processing Dependency: thunderbird >= 5.0 for package: thunderbird-lightning-1.0-0.44.b3pre.fc15.i686
--> Finished Dependency Resolution
Error: Package: thunderbird-lightning-1.0-0.44.b3pre.fc15.i686 (updates)
           Requires: thunderbird >= 5.0
           Installed: thunderbird-3.1.11-1.fc15.i686 (@updates)
               thunderbird = 3.1.11-1.fc15
           Available: thunderbird-3.1.10-1.fc15.i686 (fedora)
               thunderbird = 3.1.10-1.fc15
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Comment 2 Jerry Amundson 2011-07-21 15:21:18 UTC
Switching components, in the hope that someone takes notice.

Comment 3 Jerry Amundson 2011-07-21 20:30:10 UTC
I erase'd the existing pacakges, and installed from koji instead :
thunderbird-5.0-1.fc15.x86_64
thunderbird-lightning-1.0-0.44.b3pre.fc15.x86_64

That's working well.

Comment 4 Orion Poplawski 2011-07-21 21:34:47 UTC
https://fedorahosted.org/rel-eng/ticket/4828

Not really something to be fixed here.

Comment 5 Jerry Amundson 2011-07-22 03:23:28 UTC
(In reply to comment #4)
> https://fedorahosted.org/rel-eng/ticket/4828
> 
> Not really something to be fixed here.

I disagree. It's a problem facing the end-user, and this is where end-users are directed to for reporting problems. I'll continue in Bug #723707.

Comment 6 Orion Poplawski 2011-07-22 13:11:29 UTC
What I mean is that there is nothing I can do at the moment.  We're waiting for a new update push to fix the situation, but everything is in place at the moment.

Comment 7 Orion Poplawski 2011-07-22 13:12:53 UTC
*** Bug 723707 has been marked as a duplicate of this bug. ***

Comment 8 Orion Poplawski 2011-07-22 15:10:50 UTC
*** Bug 724913 has been marked as a duplicate of this bug. ***

Comment 9 Victor Hahn 2011-07-22 16:19:32 UTC
In wonder how incompatible packages entered the stable tree in the first place...?

Orion, you mean we're waiting for Thunderbird 5 to be packages and approved for stable?

Comment 10 Orion Poplawski 2011-07-22 16:29:16 UTC
Two updates for thunderbird were pushed at the same time - one for 3.1.1, one for 5.0.  The 3.1.1 won out.  We are waiting for the Fedora release team to push a new set of updates for F15.  Normally this happens once a day, but due to bugs in the update management software, this hasn't happened since the 18th.


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