| 1 |
At Sat, 03 Jun 2006 22:56:21 +0930 Raymond Lewis Rebbeck <dystopianray@×××××.com> wrote: |
| 2 |
|
| 3 |
> On Saturday, 3 June 2006 22:48, Allan Gottlieb wrote: |
| 4 |
>> When doing an |
| 5 |
>> |
| 6 |
>> emerge --tree --ask --verbose --newuse --update --deep world |
| 7 |
>> |
| 8 |
>> I received the following error |
| 9 |
>> |
| 10 |
>> These are the packages that I would merge, in reverse order: |
| 11 |
>> |
| 12 |
>> Calculating world dependencies ...done! |
| 13 |
>> [blocks B ] sys-apps/utempter (is blocking |
| 14 |
>> sys-libs/libutempter-1.1.2.1) [ebuild U ] x11-terms/xterm-207-r1 [207] |
| 15 |
>> -Xaw3d +doc -toolbar +truetype +unicode 727 kB [ebuild N ] |
| 16 |
>> sys-libs/libutempter-1.1.2.1 21 kB |
| 17 |
>> |
| 18 |
>> Total size of downloads: 749 kB |
| 19 |
>> |
| 20 |
>> !!! Error: The above package list contains packages which cannot be |
| 21 |
>> installed !!! on the same system. |
| 22 |
>> |
| 23 |
>> I *thought* I knew what to do when such a blockage occurs. I |
| 24 |
>> |
| 25 |
>> 1. did a quickpge utempter (for safety) |
| 26 |
>> |
| 27 |
>> 2. unmerged utempter |
| 28 |
>> |
| 29 |
>> 3. emerged libutempter |
| 30 |
>> |
| 31 |
>> 4. re-emerged utempter (from the portage tree not /usr/portage/packages) |
| 32 |
>> |
| 33 |
>> No errors were reported during any of these 4 steps. But now an |
| 34 |
>> emerge world reports |
| 35 |
>> |
| 36 |
>> Calculating world dependencies ...done! |
| 37 |
>> [blocks B ] sys-apps/utempter (is blocking |
| 38 |
>> sys-libs/libutempter-1.1.2.1) [nomerge ] x11-terms/xterm-207-r1 |
| 39 |
>> -Xaw3d +doc -toolbar +truetype +unicode [nomerge ] |
| 40 |
>> sys-libs/libutempter-1.1.2.1 |
| 41 |
>> |
| 42 |
>> Total size of downloads: 0 kB |
| 43 |
>> |
| 44 |
>> !!! Error: The above package list contains packages which cannot be |
| 45 |
>> installed !!! on the same system. |
| 46 |
>> |
| 47 |
>> Reading the ebuilds I can see the problem. |
| 48 |
>> |
| 49 |
>> * both: PROVIDE="virtual/utempter" |
| 50 |
>> |
| 51 |
>> * libutempter demands exclusivity: DEPEND="!virtual/utempter" |
| 52 |
>> |
| 53 |
>> So they really do block. Which one am I supposed to keep and which |
| 54 |
>> one should I unmerge ... |
| 55 |
>> |
| 56 |
>> ... and how should I have figured this out? |
| 57 |
>> |
| 58 |
>> What is the correct procedure when a blockage is encountered? Should |
| 59 |
>> I write a wiki page with this information? |
| 60 |
>> |
| 61 |
>> thanks, |
| 62 |
>> allan |
| 63 |
> |
| 64 |
> There was a blog entry on planet gentoo recently about this: |
| 65 |
> |
| 66 |
> http://planet.gentoo.org/developers/seemant/2006/06/02/utemptations_with_xterm |
| 67 |
> |
| 68 |
> It looks like you have to unmerge utempter and then emerge libutempter and |
| 69 |
> rebuild xterm. |
| 70 |
> |
| 71 |
> -- |
| 72 |
> Raymond Lewis Rebbeck |
| 73 |
|
| 74 |
Thanks for the pointer. It is just what I needed. |
| 75 |
|
| 76 |
(I reorganized your response into bottom-posting style, which I |
| 77 |
believe is the convention for this group). |
| 78 |
|
| 79 |
So this utmpter/libutmpter appears to be a special case where the |
| 80 |
normal |
| 81 |
|
| 82 |
unmerge A |
| 83 |
merge B |
| 84 |
merge A |
| 85 |
|
| 86 |
is wrong. |
| 87 |
|
| 88 |
thanks again, |
| 89 |
allan |
| 90 |
-- |
| 91 |
gentoo-user@g.o mailing list |
Archives