View previous topic :: View next topic |
Author |
Message |
drwook Veteran
Joined: 30 Mar 2005 Posts: 1324 Location: London
|
Posted: Sat Dec 08, 2012 10:14 am Post subject: udev / hwids file clash |
|
|
Hi,
Suspect a few people have hit this as I just did, so just thought I'd post a quick note for any newer users... the latest (~) hwids installs some files that were in udev, leading to a merge failure due to file collision.
if you've been hit by this and aren't sure how to proceed, I'd suggest upgrading udev first. Since hwids is in the DEPEND, you can't use emerge (as it'll try to pull in hwids first), so you'll need to do ebuild {path to the udev ebuild} merge. once that's complete you can carry on as normal.
Ideally I personally think hwids should be in RDEPEND not DEPEND, since hwids isn't needed by udev at build time AFAIK. But I don't think portage would handle that as I'd hope anyway (i.e. by building/merging 'out of order') |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21602
|
Posted: Sat Dec 08, 2012 5:40 pm Post subject: |
|
|
I think the dependency resolver is (or at least, should be) good enough that if udev has RDEPEND on hwids and hwids has RDEPEND !<=udev-old, then it will recognize the need to upgrade udev before it can install the new hwids. |
|
Back to top |
|
|
drwook Veteran
Joined: 30 Mar 2005 Posts: 1324 Location: London
|
Posted: Sat Dec 08, 2012 5:51 pm Post subject: |
|
|
Yeah I was going to test that then submit a bug if it did resolve, but as I didn't see anyone moaning in the forums I presumed few had been caught by it. Also as I'm running portage 2.2 I suppose my test wouldn't be all that valid for stable users either. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21602
|
Posted: Sat Dec 08, 2012 8:51 pm Post subject: |
|
|
Yes, stable users may have a different resolver algorithm. However, I think it is likely quite similar, and you could post the changes here with a request for someone on Portage 2.1 to try it. The changes should be easy to test and should fail safely if not supported on Portage 2.1, so finding a volunteer should be easy. |
|
Back to top |
|
|
|