On 31 Aug 2008, at 09:04, Mick wrote:
...
When I tried I got:
$ eix -Iu --only-names
app-arch/lzma-utils
dev-libs/libsigc++
media-plugins/gst-plugins-x
media-plugins/gst-plugins-xvideo
sys-apps/hdparm
sys-kernel/gentoo-sources
virtual/perl-Test-Harness
However, when I run emerge -upDv --with-d
On Tuesday 02 September 2008, Neil Bothwick wrote:
> On Mon, 1 Sep 2008 23:57:03 +0200, Sebastian Günther wrote:
> > But it is a *negativ* condition: portage is not depending on pycrypto
> > if and only if the build useflag is specified, which noone should
> > specify.
>
> portage depends on >=pyth
On Mon, 1 Sep 2008 23:57:03 +0200, Sebastian Günther wrote:
> But it is a *negativ* condition: portage is not depending on pycrypto
> if and only if the build useflag is specified, which noone should
> specify.
portage depends on >=python-2.5 or pycrypto.
> So --depclean should not consider it t
* Neil Bothwick ([EMAIL PROTECTED]) [01.09.08 23:14]:
> On Mon, 1 Sep 2008 11:49:36 +0100, Mick wrote:
>
>
> > It tells me to remove dev-python/pycrypto, when portage seems to depend
> > on it:
> >
> > # equery depends dev-python/pycrypto
> > [ Searching for packages depending on dev-pytho
On Mon, 1 Sep 2008 11:49:36 +0100, Mick wrote:
> No! --depclean is evil! :)) (and/or my system is borked).
Neither.
> It tells me to remove dev-python/pycrypto, when portage seems to depend
> on it:
>
> # equery depends dev-python/pycrypto
> [ Searching for packages depending on dev-py
* Mick ([EMAIL PROTECTED]) [01.09.08 20:22]:
>
> Where should I look?
>
An emerge --info is a start..
> >
> > with emerge -n hdparm you can add it.
>
> Sure, but I had emerged (many years ago) so it should be in there, right?
>
Not necessarily, maybe you unmerged the package which required i
On Monday 01 September 2008, Sebastian Günther wrote:
> * Mick ([EMAIL PROTECTED]) [01.09.08 19:35]:
> >
> > No! --depclean is evil! :)) (and/or my system is borked).
>
> Your system is borked! ;-)
That's what I fear. :(
> > It tells me to remove dev-python/pycrypto, when portage seems to de
* Mick ([EMAIL PROTECTED]) [01.09.08 19:35]:
> On Sunday 31 August 2008, Neil Bothwick wrote:
> > On Sun, 31 Aug 2008 09:04:03 +0100, Mick wrote:
> > > $ eix -Iu --only-names
> > > app-arch/lzma-utils
> > > dev-libs/libsigc++
> > > media-plugins/gst-plugins-x
> > > media-plugins/gst-plugins-xvideo
On Sunday 31 August 2008, Neil Bothwick wrote:
> On Sun, 31 Aug 2008 09:04:03 +0100, Mick wrote:
> > $ eix -Iu --only-names
> > app-arch/lzma-utils
> > dev-libs/libsigc++
> > media-plugins/gst-plugins-x
> > media-plugins/gst-plugins-xvideo
> > sys-apps/hdparm
> > sys-kernel/gentoo-sources
> > virtu
On 31 Aug 2008, at 09:05, David Sveningsson wrote:
Stroller skrev:
On 30 Aug 2008, at 21:19, Alan McKinnon wrote:
...
In retrospect, it would probably have been quicker if you went the
long way
round:
emerge -e world
Tried it. Kept dying and leaving a number of packages that I just
couldn'
On Sun, 31 Aug 2008 09:04:03 +0100, Mick wrote:
> $ eix -Iu --only-names
> app-arch/lzma-utils
> dev-libs/libsigc++
> media-plugins/gst-plugins-x
> media-plugins/gst-plugins-xvideo
> sys-apps/hdparm
> sys-kernel/gentoo-sources
> virtual/perl-Test-Harness
>
> However, when I run emerge -upDv --wit
On Saturday 30 August 2008, Neil Bothwick wrote:
> On Sat, 30 Aug 2008 05:10:27 +0100, Stroller wrote:
> > It just seems more effective than `emerge -D
> > world` - that seems to miss many packages.
>
> The packages is misses are either build-time dependencies, so don't need
> updating, or are not
Stroller skrev:
>
> On 30 Aug 2008, at 21:19, Alan McKinnon wrote:
>> ...
>> In retrospect, it would probably have been quicker if you went the
>> long way
>> round:
>>
>> emerge -e world
>
> Tried it. Kept dying and leaving a number of packages that I just
> couldn't build.
>
> Stroller.
>
>
On 30 Aug 2008, at 21:19, Alan McKinnon wrote:
...
In retrospect, it would probably have been quicker if you went the
long way
round:
emerge -e world
Tried it. Kept dying and leaving a number of packages that I just
couldn't build.
Stroller.
On Saturday 30 August 2008 16:59:02 Stroller wrote:
> but when I
> had the libexpat.so.0 error the only thing that worked (having
> followed a number of different advices posted here) was to rebuild
> EVERY outdated package on my system - a total numbering in the region
> of 250. I wouldn't
On Saturday 30 August 2008 16:59:02 Stroller wrote:
> On 30 Aug 2008, at 13:56, Alan McKinnon wrote:
> > The main reason these packages are behind at all is that they are
> > usually
> > build dependencies, not run dependencies. They will only be updated
> > with
> > emerge -uD when something that
On Sat, 30 Aug 2008 05:10:27 +0100, Stroller wrote:
> It just seems more effective than `emerge -D
> world` - that seems to miss many packages.
The packages is misses are either build-time dependencies, so don't need
updating, or are not dependencies of anything in world and would be
removed by
On 30 Aug 2008, at 13:56, Alan McKinnon wrote:
The main reason these packages are behind at all is that they are
usually
build dependencies, not run dependencies. They will only be updated
with
emerge -uD when something that depends on them is rebuilt.
To avoid this, use 'emerge --with-bde
On Saturday 30 August 2008 06:10:27 Stroller wrote:
> First question: is 'emerge -1 `eix -Iu --only-names`' a useful
> command for updating packages not in the world file? Or is this usage
> of mine to be avoided? It just seems more effective than `emerge -D
> world` - that seems to miss many
Hi there,
I recently got bitten by the libexpat.so.0 error - for me I
discovered this some considerable months after everyone else on the
list, not because I don't update often (perhaps once or twice every
few weeks) but, I think, because my machines are servers and I don't
have that many
20 matches
Mail list logo
