I think you're right about that. Can I configure eclean to wait a
certain number of days since a package was removed before cleaning it?
Even if I only run it once per week, it could remove a package that
was updated yesterday that I find out I need tomorrow.
- Grant
-t,
On Wed, 12 Dec 2012 08:05:24 +0200, Alan McKinnon wrote:
is run every morning with my first cup of coffee. If something were
changed or left off that alias do you suppose this mysterious
@preserved-rebuild would be run?
No, you would likely never see it. Your alias runs revdep-rebuild,
On Tue, 11 Dec 2012 07:36:10 -0600, Bruce Hill wrote:
After using Gentoo for close to two years, the only time/place I've
ever even seen @preserved-rebuild is in this thread. Yet you say,
Portage will warn you when the set is [it] non-empty, telling you to
run emerge @preserved-rebuild.
Can I recapitulate the routine? So it should be something like that:
layman -S
emerge --sync
emerge -DuN world
emerge @preserved-rebuild
emerge --depclean
revdep-rebuild
eclean distfiles -t=2w
eclean packages -t=2w
dispatch-conf
elogv
Right? But this script could not be run automatically because
On Wed, Dec 12, 2012 at 08:05:24AM +0200, Alan McKinnon wrote:
Of course, all this assumes that your version of portage supports
@preserved-rebuild
To use it, you simply notice the portage message right at the end of an
emerge and run emerge @preserved-rebuild - it's just a regular emerge
On Sun, Dec 09, 2012 at 04:48:24PM +, Neil Bothwick wrote:
workstation ~ # emerge -a @preserved-rebuild
emerge: 'preserved-rebuild' is an empty set
emerge: no targets left after set expansion
So you have nothing that needs rebuilding. Portage will warn you when the
set it
On Tue, 11 Dec 2012 07:36:10 -0600, Bruce Hill wrote:
So you have nothing that needs rebuilding. Portage will warn you when
the set is non-empty, telling you to run emerge @preserved-rebuild.
There is no need to run it at any other time.
After using Gentoo for close to two years, the
On 12/11/2012 08:36 AM, Bruce Hill wrote:
On Sun, Dec 09, 2012 at 04:48:24PM +, Neil Bothwick wrote:
workstation ~ # emerge -a @preserved-rebuild
emerge: 'preserved-rebuild' is an empty set
emerge: no targets left after set expansion
So you have nothing that needs rebuilding. Portage
On Tue, 11 Dec 2012 07:36:10 -0600
Bruce Hill da...@happypenguincomputers.com wrote:
On Sun, Dec 09, 2012 at 04:48:24PM +, Neil Bothwick wrote:
workstation ~ # emerge -a @preserved-rebuild
emerge: 'preserved-rebuild' is an empty set
emerge: no targets left after set expansion
On Tue, 4 Dec 2012 16:30:33 -0800
Grant emailgr...@gmail.com wrote:
My unattended daily system maintenance procedure is like this:
layman -S
emerge --sync
emerge -pvDuN world
emerge -pv --depclean
eclean -p distfiles
eclean -p packages
And then attended like this:
emerge -DuN world
On Sat, Dec 08, 2012 at 05:20:36PM -0600, Dale wrote:
That's been my experience too. I run @preserved-rebuild when it tells
me to but revdep-rebuild rarely finds anything. Thing is, it has a time
or two. It is best to run revdep-rebuild and be sure than not to and
run the risk of not
On Sun, 9 Dec 2012 07:18:42 -0600, Bruce Hill wrote:
What is @preserved-rebuild ?
It is a portage set, hence the @ prefix, containing packages that need to
be rebuilt in order to link them against the installed versions of
libraries.
workstation ~ # emerge -a @preserved-rebuild
emerge:
On Sun, Dec 09, 2012 at 04:48:24PM +, Neil Bothwick wrote:
What is @preserved-rebuild ?
It is a portage set, hence the @ prefix, containing packages that need to
be rebuilt in order to link them against the installed versions of
libraries.
workstation ~ # emerge -a
On Sun, 9 Dec 2012 11:01:37 -0600, Bruce Hill wrote:
What is @preserved-rebuild ?
It is a portage set, hence the @ prefix, containing packages that
need to be rebuilt in order to link them against the installed
versions of libraries.
workstation ~ # emerge -a
On Fri, 7 Dec 2012 16:56:18 -0800, Grant wrote:
@preserved-rebuild is getting very good at what it does lately
(supported in all recent portage version including stable IIRC), as is
--depclean, so revdep-rebuild seldom finds anything to do these days.
If revdep-rebuild does everything
On Fri, 7 Dec 2012 16:56:18 -0800
Grant emailgr...@gmail.com wrote:
My unattended daily system maintenance procedure is like this:
layman -S
emerge --sync
emerge -pvDuN world
emerge -pv --depclean
eclean -p distfiles
eclean -p packages
And then attended like this:
The logic is:
Rebuild busted packages that portage already knows about
(@preserved-rebuild), then get rid of oudated packages and finally
revdep-rebuild to fix anything that --depclean broke.
@preserved-rebuild is getting very good at what it does lately
(supported in all
On Sat, 8 Dec 2012 13:07:28 -0800
Grant emailgr...@gmail.com wrote:
So they are not really the same thing at all.I'm not saying they're
the same, I'm saying it looks like @preserved-rebuild does a subset
of the things revdep-rebuild does. Why run @preserved-rebuild
followed by
So they are not really the same thing at all.I'm not saying they're
the same, I'm saying it looks like @preserved-rebuild does a subset
of the things revdep-rebuild does. Why run @preserved-rebuild
followed by revdep-rebuild if the end result is the same as running
revdep-rebuild?
I think you're right about that. Can I configure eclean to wait a
certain number of days since a package was removed before cleaning it?
Even if I only run it once per week, it could remove a package that
was updated yesterday that I find out I need tomorrow.
- Grant
-t,
On Sat, 8 Dec 2012 13:54:25 -0800
Grant emailgr...@gmail.com wrote:
So they are not really the same thing at all.I'm not saying
they're the same, I'm saying it looks like @preserved-rebuild
does a subset of the things revdep-rebuild does. Why run
@preserved-rebuild followed by
On Sat, 8 Dec 2012 13:54:25 -0800, Grant wrote:
Got it. So @preserved-rebuild is meant to be a replacement for
revdep-rebuild
No, it is a means of preventing the problems that revdep-rebuild fixes.
If revdep-rebuild were a medicine, @preserved-rebuild would be a vaccine.
Which you choose to
Neil Bothwick wrote:
On Sat, 8 Dec 2012 13:54:25 -0800, Grant wrote:
Got it. So @preserved-rebuild is meant to be a replacement for
revdep-rebuild
No, it is a means of preventing the problems that revdep-rebuild fixes.
If revdep-rebuild were a medicine, @preserved-rebuild would be a
Grant wrote:
I think you're right about that. Can I configure eclean to wait a
certain number of days since a package was removed before cleaning it?
Even if I only run it once per week, it could remove a package that
was updated yesterday that I find out I need tomorrow.
-
On Saturday 08 December 2012 22:49:50 Neil Bothwick wrote:
... revdep-rebuild is still useful as a fallback, but the main reason
I run it from my weekly system check script is as a sanity check. It
rarely finds anything.
Not quite never, though. I still find it useful.
--
Rgds
Peter
BTW, what should I do about this:
# revdep-rebuild -p
* Configuring search environment for revdep-rebuild
* Checking reverse dependencies
* Packages containing binaries and libraries broken by a package
update
* will be emerged.
* Collecting system binaries and libraries
Dale wrote:
That's been my experience too. I run @preserved-rebuild when it tells
me to but revdep-rebuild rarely finds anything. Thing is, it has a
time or two. It is best to run revdep-rebuild and be sure than not to
and run the risk of not being able to boot or some other problem that
The first depclean is redundant, you haven't updated anything so it
won't
show anything useful. I only run depclean and revdep-rebuild weekly,I
don't see a need to routinely do it more often, especially on slower
systems. I do run eix-update and eix-update-remote after my daily
My unattended daily system maintenance procedure is like this:
layman -S
emerge --sync
emerge -pvDuN world
emerge -pv --depclean
eclean -p distfiles
eclean -p packages
And then attended like this:
revdep-rebuild
etc-update
elogv
emerge --depclean
eclean distfiles
I run depclean about once a month after a large update, usually KDE, qt
or something like that. I sync and update about twice a week. I try to
time mine to hit those important updates to things like KDE or
something. I'm actually waiting on KDE 4.9.4 to hit the tree now. It
should be
On Tue, 4 Dec 2012 16:30:33 -0800
Grant emailgr...@gmail.com wrote:
My unattended daily system maintenance procedure is like this:
layman -S
emerge --sync
emerge -pvDuN world
emerge -pv --depclean
eclean -p distfiles
eclean -p packages
And then attended like this:
revdep-rebuild
Grant wrote:
I think you're right about that. Can I configure eclean to wait a
certain number of days since a package was removed before cleaning it?
Even if I only run it once per week, it could remove a package that
was updated yesterday that I find out I need tomorrow.
-
On Tue, 4 Dec 2012 20:04:30 -0800, Grant wrote:
The first depclean is redundant, you haven't updated anything so it
won't
show anything useful. I only run depclean and revdep-rebuild weekly,I
don't see a need to routinely do it more often, especially on slower
systems. I do run
Why with the pretend option? Checking to see if it's needed?
Connected by DROID on Verizon Wireless
-Original message-
From: Grant emailgr...@gmail.com
To: Gentoo mailing list gentoo-user@lists.gentoo.org
Sent: Wed, Dec 5, 2012 00:34:37 GMT+00:00
Subject: [gentoo-user] System
Grant wrote:
My unattended daily system maintenance procedure is like this:
layman -S
emerge --sync
emerge -pvDuN world
emerge -pv --depclean
eclean -p distfiles
eclean -p packages
And then attended like this:
emerge -DuN world
revdep-rebuild
etc-update
elogv
emerge --depclean
Grant emailgr...@gmail.com wrote:
My unattended daily system maintenance procedure is like this:
layman -S
emerge --sync
emerge -pvDuN world
emerge -pv --depclean
eclean -p distfiles
eclean -p packages
And then attended like this:
emerge -DuN world
revdep-rebuild
etc-update
On Dec 5, 2012 7:34 AM, Grant emailgr...@gmail.com wrote:
My unattended daily system maintenance procedure is like this:
layman -S
emerge --sync
emerge -pvDuN world
emerge -pv --depclean
eclean -p distfiles
eclean -p packages
And then attended like this:
emerge -DuN world
On Tue, Dec 04 2012, Pandu Poluan wrote:
On Dec 5, 2012 7:34 AM, Grant emailgr...@gmail.com wrote:
My unattended daily system maintenance procedure is like this:
layman -S
emerge --sync
emerge -pvDuN world
emerge -pv --depclean
eclean -p distfiles
eclean -p packages
And then attended
Pandu Poluan wrote:
There's an incantation that makes emerge download the source files but
don't actually emerge them, yet. Will save a lot of time during
attended sessions if your Internet connection is kind of not fast.
Can someone help me refresh my mind?
Rgds,
That would be the -f
My unattended daily system maintenance procedure is like this:
layman -S
emerge --sync
emerge -pvDuN world
emerge -pv --depclean
eclean -p distfiles
eclean -p packages
And then attended like this:
emerge -DuN world
revdep-rebuild
etc-update
elogv
emerge --depclean
My unattended daily system maintenance procedure is like this:
layman -S
emerge --sync
emerge -pvDuN world
emerge -pv --depclean
eclean -p distfiles
eclean -p packages
And then attended like this:
emerge -DuN world
revdep-rebuild
etc-update
elogv
emerge --depclean
eclean distfiles
Grant wrote:
I think you're right about that. Can I configure eclean to wait a
certain number of days since a package was removed before cleaning it?
Even if I only run it once per week, it could remove a package that
was updated yesterday that I find out I need tomorrow.
- Grant
-t,
I think you're right about that. Can I configure eclean to wait a
certain number of days since a package was removed before cleaning it?
Even if I only run it once per week, it could remove a package that
was updated yesterday that I find out I need tomorrow.
- Grant
-t,
43 matches
Mail list logo
