Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 399263 - media-tv/linuxtv-dvb-headers-5 not synchronized with current kernel sources
Summary: media-tv/linuxtv-dvb-headers-5 not synchronized with current kernel sources
Status: RESOLVED DUPLICATE of bug 399161
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Television related Applications in Gentoo's Portage
URL: http://gentoo-portage.com/media-tv/li...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-18 08:27 UTC by Ladislav Zitka
Modified: 2012-01-22 18:59 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ladislav Zitka 2012-01-18 08:27:12 UTC
After today sync and update world: emerge --update --deep --newuse --ask --verbose world

I got this warning
WARNING: One or more updates have been skipped due to a dependency conflict:

sys-kernel/linux-headers:0

  (sys-kernel/linux-headers-3.1::gentoo, ebuild scheduled for merge) conflicts with
    <sys-kernel/linux-headers-3.0 required by (media-tv/linuxtv-dvb-headers-5::gentoo, installed)

But the ebuild at http://gentoo-portage.com/media-tv/linuxtv-dvb-headers seems to be configured to depend on 3.0 and higher, so why there appears the warning?

Reproducible: Always

Steps to Reproduce:
1. emerge --sync
2. emerge --update --deep --newuse --ask --verbose world
Actual Results:  
WARNING: One or more updates have been skipped due to a dependency conflict:

sys-kernel/linux-headers:0

  (sys-kernel/linux-headers-3.1::gentoo, ebuild scheduled for merge) conflicts with
    <sys-kernel/linux-headers-3.0 required by (media-tv/linuxtv-dvb-headers-5::gentoo, installed)

Expected Results:  
No warning regarding this package.
Comment 1 Christian Ruppert (idl0r) gentoo-dev 2012-01-22 18:59:40 UTC

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