View previous topic :: View next topic |
Author |
Message |
Sadako Advocate
Joined: 05 Aug 2004 Posts: 3792 Location: sleeping in the bathtub
|
Posted: Sat Aug 18, 2007 5:40 pm Post subject: New udev/device mapper blocking problem |
|
|
I just updated udev to 114-r1 yesterday (from 111-r3).
I --sync'd today, and I get the following; Code: | # emerge -p udev
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] sys-fs/udev-114-r1 USE="(-selinux)" 0 kB
[blocks B ] <sys-fs/device-mapper-1.02.19-r1 (is blocking sys-fs/udev-114-r1)
# emerge -p device-mapper
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] sys-fs/device-mapper-1.02.19 USE="(-selinux)" 0 kB
[blocks B ] <sys-fs/device-mapper-1.02.19-r1 (is blocking sys-fs/udev-114-r1)
# emerge -p =udev-114
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild UD] sys-fs/udev-114 [114-r1] USE="(-selinux)" 0 kB
[blocks B ] <sys-fs/device-mapper-1.02.19-r1 (is blocking sys-fs/udev-114, sys-fs/udev-114-r1) |
It's only device-mapper-1.02.19-r1 which is supposed to be blocked, which I've never had installed, so I don't understand this.
I added =sys-fs/device-mapper-1.02.19-r1 to /etc/portage/package.mask.
I have a feeling it will sort itself out if I unmerge and then emerge -1 udev, but I'd like to understand what the problem is.
Is this what happens when changes are made to ebuilds without a revision bump? _________________ "You have to invite me in" |
|
Back to top |
|
|
Rob1n l33t
Joined: 29 Nov 2003 Posts: 714 Location: Cambridge, UK
|
Posted: Sat Aug 18, 2007 6:27 pm Post subject: |
|
|
I'd guess this is related to changing ebuild without version bumping, yes. From the looks of it they've changed the udev ebuild to require a newer version of device-mapper than you have installed. Ss the output you pasted from after you added the mask for device-mapper? Otherwise I would've thought it would allow the upgrade. Anyway, I'd recommend removing this mask and upgrading device-mapper (if this fails then you may need to uninstall device-mapper & then install the new version). |
|
Back to top |
|
|
Sadako Advocate
Joined: 05 Aug 2004 Posts: 3792 Location: sleeping in the bathtub
|
Posted: Sat Aug 18, 2007 6:36 pm Post subject: |
|
|
Rob1n wrote: | I'd guess this is related to changing ebuild without version bumping, yes. From the looks of it they've changed the udev ebuild to require a newer version of device-mapper than you have installed. Ss the output you pasted from after you added the mask for device-mapper? Otherwise I would've thought it would allow the upgrade. Anyway, I'd recommend removing this mask and upgrading device-mapper (if this fails then you may need to uninstall device-mapper & then install the new version). | That's just the thing, it was like this before the mask.
I masked it in an effort to resolve the issue. _________________ "You have to invite me in" |
|
Back to top |
|
|
Rob1n l33t
Joined: 29 Nov 2003 Posts: 714 Location: Cambridge, UK
|
Posted: Sat Aug 18, 2007 7:27 pm Post subject: |
|
|
Odd that it's not trying to install the new version of device-mapper - you could try doing "emerge =sys-fs/device-mapper-1.02.19-r1" to force this. |
|
Back to top |
|
|
Sadako Advocate
Joined: 05 Aug 2004 Posts: 3792 Location: sleeping in the bathtub
|
Posted: Sat Aug 18, 2007 7:34 pm Post subject: |
|
|
Rob1n wrote: | Odd that it's not trying to install the new version of device-mapper - you could try doing "emerge =sys-fs/device-mapper-1.02.19-r1" to force this. |
Code: | # emerge -p =sys-fs/device-mapper-1.02.19-r1
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] sys-fs/device-mapper-1.02.19-r1 [1.02.19] USE="(-selinux)" 0 kB
[blocks B ] <sys-fs/device-mapper-1.02.19-r1 (is blocking sys-fs/udev-114-r1) |
_________________ "You have to invite me in" |
|
Back to top |
|
|
Rob1n l33t
Joined: 29 Nov 2003 Posts: 714 Location: Cambridge, UK
|
Posted: Sat Aug 18, 2007 7:49 pm Post subject: |
|
|
Hopeless wrote: |
Code: | # emerge -p =sys-fs/device-mapper-1.02.19-r1
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] sys-fs/device-mapper-1.02.19-r1 [1.02.19] USE="(-selinux)" 0 kB
[blocks B ] <sys-fs/device-mapper-1.02.19-r1 (is blocking sys-fs/udev-114-r1) |
|
Gah - guess you'll have to uninstall device-mapper first, then install the new version |
|
Back to top |
|
|
stigger n00b
Joined: 12 Aug 2007 Posts: 13
|
Posted: Sun Aug 19, 2007 11:30 am Post subject: |
|
|
Rob1n wrote: | Gah - guess you'll have to uninstall device-mapper first, then install the new version |
i had the same problem and this is solve it. thanks. |
|
Back to top |
|
|
gzunk Tux's lil' helper
Joined: 31 Aug 2003 Posts: 149 Location: Dunblane, Scotland
|
Posted: Sun Aug 19, 2007 1:28 pm Post subject: |
|
|
I have the same problem. Does anybody think that upgrading the device mapper will mess up my LVM2 installation? _________________ Intel Core 2 Quad Q9650 | Asus P5K | 8GB DDR-2 800
Sapphire Radeon 4870 X2 | 30" Samsung SM305T+
(4xSATA) 3 TB | 2 x DVD+-RW DL (Pioneer 112D 115D)
Logitech X-530 5.1 | DiNovo Edge | MX Revolution |
|
Back to top |
|
|
Carlo Developer
Joined: 12 Aug 2002 Posts: 3356
|
Posted: Sun Aug 19, 2007 3:06 pm Post subject: Re: New udev/device mapper blocking problem |
|
|
Hopeless wrote: | It's only device-mapper-1.02.19-r1 which is supposed to be blocked, which I've never had installed, so I don't understand this. |
No it is every version < device-mapper-1.02.19-r1 that is blocking. Remove your pointless local mask, unmerge device-mapper, then emerge udev and device-mapper. And please read the documentation of Portage, so you're aware of what the operators in front of an ebuild atom mean. _________________ Please make sure that you have searched for an answer to a question after reading all the relevant docs. |
|
Back to top |
|
|
Sadako Advocate
Joined: 05 Aug 2004 Posts: 3792 Location: sleeping in the bathtub
|
Posted: Sun Aug 19, 2007 3:42 pm Post subject: Re: New udev/device mapper blocking problem |
|
|
Carlo wrote: | No it is every version < device-mapper-1.02.19-r1 that is blocking. Remove your pointless local mask, unmerge device-mapper, then emerge udev and device-mapper. And please read the documentation of Portage, so you're aware of what the operators in front of an ebuild atom mean. |
Actually, I understand the meaning operators of the operators just fine, I just misread it (never even noticed the bloody '<').
But still, Code: | # emerge -p device-mapper
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] sys-fs/device-mapper-1.02.19-r1 [1.02.19] USE="(-selinux)" 0 kB
[blocks B ] <sys-fs/device-mapper-1.02.19-r1 (is blocking sys-fs/udev-114-r1) |
_________________ "You have to invite me in" |
|
Back to top |
|
|
Arfrever Bodhisattva
Joined: 29 Apr 2006 Posts: 2463 Location: 異世界
|
Posted: Sun Aug 19, 2007 4:09 pm Post subject: |
|
|
You didn't unmerge "device-mapper".
Perduodu linkėjimus
Arfrever |
|
Back to top |
|
|
Sadako Advocate
Joined: 05 Aug 2004 Posts: 3792 Location: sleeping in the bathtub
|
Posted: Sun Aug 19, 2007 4:15 pm Post subject: |
|
|
Arfrever wrote: | You didn't unmerge "device-mapper".
Perduodu linkėjimus |
I shouldn't have to.
Anyway, I couldn't find a polish -> english translator, what "perduodu linkėjimus" mean? _________________ "You have to invite me in" |
|
Back to top |
|
|
Arfrever Bodhisattva
Joined: 29 Apr 2006 Posts: 2463 Location: 異世界
|
Posted: Sun Aug 19, 2007 4:32 pm Post subject: |
|
|
Hopeless wrote: | Arfrever wrote: | You didn't unmerge "device-mapper". |
|
Sometimes it is necessary, e. g. to prevent files collision with other packages. In this case newer "udev" can't work with older "device-mapper", so "<device-mapper-1.02.19-r1" is blocked.
Hopeless wrote: | Anyway, I couldn't find a polish -> english translator, what "perduodu linkėjimus" mean? |
Tai neyra lenkiškai.
Perduodu linkėjimus
Arfrever |
|
Back to top |
|
|
MacTuitui n00b
Joined: 10 Oct 2003 Posts: 53
|
|
Back to top |
|
|
jman451 n00b
Joined: 25 May 2005 Posts: 5
|
Posted: Sun Nov 11, 2007 12:34 am Post subject: |
|
|
So for anyone who still comes across this problem, this is exactly what I did to solve it on my machine
Code: | emerge =sys-fs/device-mapper-1.02.19-r1
emerge -u sys-fs/udev
emerge -u sys-fs/device-mapper |
|
|
Back to top |
|
|
audiodef Watchman
Joined: 06 Jul 2005 Posts: 6639 Location: The soundosphere
|
Posted: Sat Apr 26, 2008 12:20 am Post subject: |
|
|
I had this conflict when emerging Gnome on a new system. What worked for me was to first emerge udev, then emerge Gnome. After reading this thread, and before emerging Gnome, I checked and saw that I could then emerge device-mapper alone, without conflict, if I wanted to. |
|
Back to top |
|
|
|