On Sunday 29 June 2008, Philip Webb wrote:
Doesn't that give you a huge world file ...
No: of course, I 'emerge -1' when the pkg is not marked 'W/S' in my
pkg.ref. Currently, 'world' lists 97 pkgs ; pkg.ref lists 513
pkgs.
OK, that would work.
I suppose I don't stand much chance of
080628 Neil Bothwick wrote:
On Sat, 28 Jun 2008 14:57:05 -0400, Philip Webb wrote:
the problem with 'emerge world' (without '-p') is
the user hands over control of his machine to an unreliable automaton,
No one has ever suggested that you run emerge world without -p or -a.
Damage caused by
On Saturday 28 June 2008, Philip Webb wrote:
your manually maintained log is entirely redundant if you emerge
Genlop
How so ? -- the site given by 'eix genlop' simply goes on re Perl.
emerge genlop.
When it runs it essentially parses /var log/emerge.log and gives output
like so:
Sat
On Sunday 29 June 2008, Philip Webb wrote:
Anyway, I continue to recommend my own approach to everyone,
while knowing full well they (like me) will go on in their own way
(grin).
Doesn't that give you a huge world file and no easy way to identify
redundant and unused libs?
--
Alan McKinnon
080629 Alan McKinnon wrote:
Doesn't that give you a huge world file ...
No: of course, I 'emerge -1' when the pkg is not marked 'W/S' in my pkg.ref.
Currently, 'world' lists 97 pkgs ; pkg.ref lists 513 pkgs.
... and no easy way to identify redundant and unused libs?
This is clear when a
080628 William Kenworthy top-posted (ugh!):
On Fri, 2008-06-27 at 12:41 -0700, Grant wrote:
Lately it seems like a new problem pops up every day
and every time I try to do something new it doesn't work.
Anybody else experiencing that lately?
My Gentoo systems get this way for one of two
On Saturday 28 June 2008, Philip Webb wrote:
'emerge world' is the source of many problems regularly reported
here.
Do you mean 'emerge world enter' as opposed to the much more
sensible 'emerge -p world', examine output for problems, consider each
update, examine USE flag changes for impact,
On 28 Jun 2008, at 03:47, Kevin O'Gorman wrote:
On Fri, Jun 27, 2008 at 3:23 PM, Grant [EMAIL PROTECTED] wrote:
| I think it could be the pick-and-mix approach to keywording, I
use pure
| ~amd64 on my desktop and laptop and the only problems I've had
recently
| turned out to be a
Alan McKinnon wrote on 28/06/08 08:54:
The ~x86 branch seems to have settled into not-so-cutting-edge anymore,
quite similar to what other distros release - Ubuntu for examples.
x86 seems to be taking it's lead lately from Debian :-)
Would it were so!
tcp-wrappers bug 158306, opened on
so, have you asked to become its maintainer to fix the bugs?
--
gentoo-user@lists.gentoo.org mailing list
On Sat, 28 Jun 2008 08:50:07 +0200, Alan McKinnon wrote:
Do you think I might have swung from being waay too verbose to
being waay too brief?
Do you want the long answer or the short answer? ;-)
--
Neil Bothwick
When puns are outlawed only outlaws will have puns.
signature.asc
Volker Armin Hemmann wrote on 28/06/08 14:12:
so, have you asked to become its maintainer to fix the bugs?
Lacking the necessary skills, no.
--
gentoo-user@lists.gentoo.org mailing list
Grant wrote:
| I think it could be the pick-and-mix approach to keywording, I use pure
| ~amd64 on my desktop and laptop and the only problems I've had recently
| turned out to be a corrupt root filesystem.
|
| yeah, mixing isn't good. Pure systems are way more stable.
Now that's an
080628 Neil Bothwick wrote:
On Sat, 28 Jun 2008 02:53:53 -0400, Philip Webb wrote:
'emerge world' is the source of many problems regularly reported here.
No, it's changing package versions that breaks a working system,
whether this is a result of running 'emerge world'
or updating the guilty
080628 Philip Webb wrote:
I've been doing it this way for nearly 8 years
Of course, I mean nearly 5 years .
--
,,
SUPPORT ___//___, Philip Webb : [EMAIL PROTECTED]
ELECTRIC /] [] [] [] [] []| Centre for Urban
On Sat, 28 Jun 2008 14:57:05 -0400, Philip Webb wrote:
No, the problem with 'emerge world' (without '-p') is
that the user hands over control of his machine to an unreliable
automaton,
No one has ever suggested that you run emerge world without -p or -a.
Damage caused by using a tool badly
Lately it seems like a new problem pops up every day and every time I
try to do something new it doesn't work. Anybody else experiencing
that lately?
- Grant
--
gentoo-user@lists.gentoo.org mailing list
On Friday 27 June 2008, Grant wrote:
Lately it seems like a new problem pops up every day and every time I
try to do something new it doesn't work. Anybody else experiencing
that lately?
No.
--
Alan McKinnon
alan dot mckinnon at gmail dot com
--
gentoo-user@lists.gentoo.org mailing list
Grant wrote:
Lately it seems like a new problem pops up every day and every time I
try to do something new it doesn't work. Anybody else experiencing
that lately?
- Grant
Rock solid.
--Joshua Doll
--
gentoo-user@lists.gentoo.org mailing list
On Freitag, 27. Juni 2008, Grant wrote:
Lately it seems like a new problem pops up every day and every time I
try to do something new it doesn't work. Anybody else experiencing
that lately?
- Grant
a botched gcc-upgrade/clean cycle damaged gcc beyond repair - but that was
easily solved by
Grant,
I've had a lot of problems lately upgrading ~arch and masked packages. This
is expected (obviously) but 99% of the time I am able to fix them myself
without going through support resources.
If you're using any that are ~arch and in packages.mask perhaps that is why
you're having problems
Grant,
I've had a lot of problems lately upgrading ~arch and masked packages. This
is expected (obviously) but 99% of the time I am able to fix them myself
without going through support resources.
If you're using any that are ~arch and in packages.mask perhaps that is why
you're having
Grant ha scritto:
Lately it seems like a new problem pops up every day and every time I
try to do something new it doesn't work. Anybody else experiencing
that lately?
- Grant
Yes. Looks like my Gentoo box is rotting these days, but most probably
it's me not having time at all to iron out
On Fri, 27 Jun 2008 14:09:16 -0700, Grant wrote:
I think you're right Brian. Of course, this is nobody's fault but
mine for using ~amd64 packages, but I only pull those in if I feel I
have to. Quite a few of them now though. Does it seem like ~arch
packages have been more difficult lately?
On Fri, 27 Jun 2008 22:01:10 +0200, Alan McKinnon wrote:
Lately it seems like a new problem pops up every day and every time I
try to do something new it doesn't work. Anybody else experiencing
that lately?
No.
How can you be so certain that not one of the thousands of Gentoo users
On Fri, Jun 27, 2008 at 4:41 PM, Grant [EMAIL PROTECTED] wrote:
Lately it seems like a new problem pops up every day and every time I
try to do something new it doesn't work. Anybody else experiencing
that lately?
After almost 8 months withtou an upgrade, I finally decided to go on
with it,
b.n. wrote:
Grant ha scritto:
Lately it seems like a new problem pops up every day and every time I
try to do something new it doesn't work. Anybody else experiencing
that lately?
- Grant
Yes. Looks like my Gentoo box is rotting these days, but most probably
it's me not having time at all
On Freitag, 27. Juni 2008, Neil Bothwick wrote:
On Fri, 27 Jun 2008 14:09:16 -0700, Grant wrote:
I think you're right Brian. Of course, this is nobody's fault but
mine for using ~amd64 packages, but I only pull those in if I feel I
have to. Quite a few of them now though. Does it seem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Volker Armin Hemmann wrote:
| On Freitag, 27. Juni 2008, Neil Bothwick wrote:
| I think it could be the pick-and-mix approach to keywording, I use pure
| ~amd64 on my desktop and laptop and the only problems I've had recently
| turned out to be a
| I think it could be the pick-and-mix approach to keywording, I use pure
| ~amd64 on my desktop and laptop and the only problems I've had recently
| turned out to be a corrupt root filesystem.
|
| yeah, mixing isn't good. Pure systems are way more stable.
Now that's an interesting idea.
On Friday 27 June 2008, Grant wrote:
| I think it could be the pick-and-mix approach to keywording, I use
| pure ~amd64 on my desktop and laptop and the only problems I've had
| recently turned out to be a corrupt root filesystem.
|
| yeah, mixing isn't good. Pure systems are way more
My Gentoo systems get this way for one of two reasons:
Some config files get overwritten (make.conf was one time ) by accident
and a few packages get installed with the wrong build settings causing
random grief
system inconsistency, mainly with libraries. revdep-rebuild may or may
not help - if
32 matches
Mail list logo