Bug 1023940 - thunderbird-lightning-gdata
Summary: thunderbird-lightning-gdata
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird-lightning
Version: 20
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: 2013-10-28 11:53 UTC by Matthias Runge
Modified: 2013-10-28 11:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-28 11:58:05 UTC
Type: Bug


Attachments (Terms of Use)

Description Matthias Runge 2013-10-28 11:53:24 UTC
Description of problem:
tb-lightning-gdata is not installable on top of tb-lightning:

[mrunge@turing ~]$ sudo yum install thunderbird-lightning-gdata
Loaded plugins: langpacks, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package thunderbird-lightning-gdata.x86_64 0:0.18-5.fc20 will be installed
--> Processing Dependency: thunderbird-lightning(x86-64) = 1.9.1-5.fc20 for package: thunderbird-lightning-gdata-0.18-5.fc20.x86_64
--> Finished Dependency Resolution
Error: Package: thunderbird-lightning-gdata-0.18-5.fc20.x86_64 (euler-releases)
           Requires: thunderbird-lightning(x86-64) = 1.9.1-5.fc20
           Installed: thunderbird-lightning-2.6-1.fc20.x86_64 (@euler-updates-testing)
               thunderbird-lightning(x86-64) = 2.6-1.fc20
           Available: thunderbird-lightning-1.9.1-5.fc20.x86_64 (euler-releases)
               thunderbird-lightning(x86-64) = 1.9.1-5.fc20
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

[mrunge@turing ~]$ rpm -q thunderbird-lightning
thunderbird-lightning-2.6-1.fc20.x86_64

It looks like patches from rawhide were not merged into f20?

Comment 1 Matthias Runge 2013-10-28 11:58:05 UTC
na! scratch that please! Something wrong with my mirror config here.


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