On Friday 26 February 2010 18:47:40 Alex Schuster wrote:
> > What's a suitable substitute?
>
> Whatever you like. Just edit the MERGETOOL definition in /etc/cfg-
> update.conf:
>
> # +--+
> # | MERGETOOL \
> #
> ++---
> +
Peter Humphrey writes:
> I'm still using etc-update, which seems adequate except when squid is
> upgraded, but I thought I'd try cfg-update. Problem though: it demands
> dev-util/xxdiff which doesn't exist. What's a suitable substitute?
Whatever you like. Just edit the MERGETOOL definition in /et
On Sunday 14 February 2010 11:32:12 Neil Bothwick wrote:
> On Sun, 14 Feb 2010 12:03:40 +0100, Volker Armin Hemmann wrote:
> > > On a more serious note, conf-update automatically merges trivial
> > > changes, so any configs you ran at the default, which is probably
> > > the majority, won't be flag
On Montag 22 Februar 2010, daid kahl wrote:
> >> > > > On a more serious note, conf-update automatically merges trivial
> >> > > > changes, so any configs you ran at the default, which is probably
> >> > > > the majority, won't be flaged at all.
> >> > >
> >> > > so does cfg-update
> >> >
> >
>> > > > On a more serious note, conf-update automatically merges trivial
>> > > > changes, so any configs you ran at the default, which is probably the
>> > > > majority, won't be flaged at all.
>> > >
>> > > so does cfg-update
>> >
>> > Every now and then, someone mentions cfg-update - usuall
On Sat, 2010-02-20 at 12:08 +, Mick wrote:
> On Sunday 14 February 2010 11:32:12 Neil Bothwick wrote:
> > On Sun, 14 Feb 2010 12:03:40 +0100, Volker Armin Hemmann wrote:
> > > > On a more serious note, conf-update automatically merges trivial
> > > > changes, so any configs you ran at the defau
On Sat, 20 Feb 2010 12:08:05 +, Mick wrote:
> > I expect that if I were still using etc-update or dispatch-conf I
> > would welcome it with open arms though.
>
> You make me feel out of touch with Gentoo! Is dispatch-conf and
> etc-update that bad then?
They're not bad in that they do the
On Samstag 20 Februar 2010, Mick wrote:
> On Sunday 14 February 2010 11:32:12 Neil Bothwick wrote:
> > On Sun, 14 Feb 2010 12:03:40 +0100, Volker Armin Hemmann wrote:
> > > > On a more serious note, conf-update automatically merges trivial
> > > > changes, so any configs you ran at the default, whi
On Sunday 14 February 2010 11:32:12 Neil Bothwick wrote:
> On Sun, 14 Feb 2010 12:03:40 +0100, Volker Armin Hemmann wrote:
> > > On a more serious note, conf-update automatically merges trivial
> > > changes, so any configs you ran at the default, which is probably the
> > > majority, won't be flag
On Sun, 14 Feb 2010 12:03:40 +0100, Volker Armin Hemmann wrote:
> > On a more serious note, conf-update automatically merges trivial
> > changes, so any configs you ran at the default, which is probably the
> > majority, won't be flaged at all.
>
> so does cfg-update
Every now and then, so
On Sonntag 14 Februar 2010, Neil Bothwick wrote:
> On Sun, 14 Feb 2010 08:01:50 +0200, Alan McKinnon wrote:
> > > > The OP then doesn't have to deal with 600+ conf-update complaints
> > >
> > > Run conf-update and press a then d :)
> >
> > But I'm a paranoid snarky old git and that doesn't work f
On Sun, 14 Feb 2010 08:01:50 +0200, Alan McKinnon wrote:
> > > The OP then doesn't have to deal with 600+ conf-update complaints
> >
> > Run conf-update and press a then d :)
>
> But I'm a paranoid snarky old git and that doesn't work for me!
But d rejects all the changes, leaving your own
On Saturday 13 February 2010 22:43:39 Neil Bothwick wrote:
> On Sat, 13 Feb 2010 09:28:57 +0200, Alan McKinnon wrote:
> > > /etc/ is CONFIG_PROTECTed, so emerge -e world will do just what the OP
> > > wants, rebuild everything without touching the configs.
> > >
> > > Of course, a backup of /etc i
On Saturday 13 February 2010 19:51:05 Alan Mackenzie wrote:
> Thanks! In the end, I just used the gcc I had on the system anyway; it
> wasn't broken. I first did 'emerge -e gcc', which took an hour, then did
> 'emerge -e world', which took ~2 hours 30 mins.
>
> I was being a bit paranoid. The r
On Sat, 13 Feb 2010 09:28:57 +0200, Alan McKinnon wrote:
> > /etc/ is CONFIG_PROTECTed, so emerge -e world will do just what the OP
> > wants, rebuild everything without touching the configs.
> >
> > Of course, a backup of /etc is always a handy thing to have around
> > anyway,
>
> For this ca
On 13 Feb 2010, at 17:51, Alan Mackenzie wrote:
...
There was that apocryphal tale of the origianl Unix hacker who
hardwired
a backdoor login into the system, and hacked cc to _keep_ inserting
the
backdoor each time the system was built, and to keep this hack in cc
each
time cc was compil
Hi, Alan,
On Sat, Feb 13, 2010 at 09:27:15AM +0200, Alan McKinnon wrote:
> On Friday 12 February 2010 21:55:29 Alan Mackenzie wrote:
> > As reported in other threads, my new PC had a broken RAM stick in it.
> > As a result, an unknown proportion of installed binaries are flaky.
> > One non-functi
On Saturday 13 February 2010 00:52:32 Neil Bothwick wrote:
> On Fri, 12 Feb 2010 13:21:18 -0800, Kyle Bader wrote:
> > >> Has anybody any other tips to offer me for this operation?
> > >
> > > tar up /etc.
> >
> > Make sure the tar can extract on another system. Backups that haven't
> > been tes
On Friday 12 February 2010 21:55:29 Alan Mackenzie wrote:
> Hi, Gentoo!
>
> As reported in other threads, my new PC had a broken RAM stick in it.
> As a result, an unknown proportion of installed binaries are flaky. One
> non-functioning binary is probably GCC.
>
> What I'd like to do is reinsta
"equery check package" compares current with the as installed checksum
(or something like that!) for the packages files.
emerge -ep world > a
edit "a" to add "equery check " before each package name
run "sh a > b" and got hrough the list in b to see whats broke - lots of
debris - config files etc
On Fri, 12 Feb 2010 13:21:18 -0800, Kyle Bader wrote:
> >> Has anybody any other tips to offer me for this operation?
> >
> > tar up /etc.
>
> Make sure the tar can extract on another system. Backups that haven't
> been tested are not backups! :D
/etc/ is CONFIG_PROTECTed, so emerge -e worl
>> Has anybody any other tips to offer me for this operation?
>
> tar up /etc.
Make sure the tar can extract on another system. Backups that haven't
been tested are not backups! :D
--
Kyle
On Freitag 12 Februar 2010, Alan Mackenzie wrote:
> Hi, Gentoo!
>
> As reported in other threads, my new PC had a broken RAM stick in it.
> As a result, an unknown proportion of installed binaries are flaky. One
> non-functioning binary is probably GCC.
>
> What I'd like to do is reinstall every
Hi, Gentoo!
As reported in other threads, my new PC had a broken RAM stick in it.
As a result, an unknown proportion of installed binaries are flaky. One
non-functioning binary is probably GCC.
What I'd like to do is reinstall every binary, yet without erasing any
configuration info, whose creat
24 matches
Mail list logo