On Tue, 1 Apr 2008 20:40:44 -0400, Walter Dnes wrote:
I figure that an older version of program x should
not be considered as a block to a newer version of program x. Isn't
that the whole point of --update?
It is, but the way portage updates packages is to install the new version
and then
I had interpreted the error message to read that some other package
required = openmotif-2.3.0
On Tue, Apr 01, 2008 at 08:53:48PM +0200, Alan McKinnon wrote
What's confusing about that? The reason is in the ebuild for
x11-libs/openmotif-2.3.0-r1 where it's configured to not co-exist with
On Wednesday 02 April 2008, Walter Dnes wrote:
To fix: unmerge the existing openmotif, merge the new one
But, but, but... isn't the whole point of --update --world to
*UPDATE* to the latest available version? Why is it that openmotif
requires *MANUALLY* deleting the old version, when 99%
On Tuesday 01 April 2008, Walter Dnes wrote:
I'm updating my newer machine (the hot-backup). Last time was in
mid-February. After doing an emerge --sync and updating portage, I'm
getting a mysterious message at the end of...
emerge --pretend --deep --update --world x
...namely...
On Tue, Apr 01, 2008 at 05:48:22AM +0200, Volker Armin Hemmann wrote
emerge unmerge openmotif
emerge openmotif
Thanks; it worked. Actually, I unmerged openmotif, and then went
right to the update of world. I misread the diagnostic message...
=x11-libs/openmotif-2.3.0 (is blocking
On Mittwoch, 2. April 2008, Walter Dnes wrote:
On Tue, Apr 01, 2008 at 05:48:22AM +0200, Volker Armin Hemmann wrote
emerge unmerge openmotif
emerge openmotif
Thanks; it worked. Actually, I unmerged openmotif, and then went
right to the update of world. I misread the diagnostic
Walter Dnes wrote:
On Tue, Apr 01, 2008 at 05:48:22AM +0200, Volker Armin Hemmann wrote
emerge unmerge openmotif
emerge openmotif
Thanks; it worked. Actually, I unmerged openmotif, and then went
right to the update of world. I misread the diagnostic message...
On Wednesday 02 April 2008, Walter Dnes wrote:
...as saying that some other program required a version of openmotif
which was = 2.3.0. I figure that an older version of program x
should not be considered as a block to a newer version of program
x. Isn't that the whole point of --update?
It
On Dienstag, 1. April 2008, Walter Dnes wrote:
I'm updating my newer machine (the hot-backup). Last time was in
mid-February. After doing an emerge --sync and updating portage, I'm
getting a mysterious message at the end of...
emerge --pretend --deep --update --world x
...namely...
9 matches
Mail list logo
