[gentoo-amd64] problem after emerge --update world

[gentoo-amd64] problem after emerge --update world

[Mark]

I'm having a problem after I did emerge --update world last night.
After it finished, it said 75 files  in /etc needed updating. OK, I've
seen this before and have made mistakes with it. So this time, I
copied all of /etc to /home/mark/etc.old, and then ran etc-update. I
then let it auto merge everything and rebooted.

At this point, KDE would not start. Instead, I got a generic-looking
X11 screen, and had no mouse. So I did Ctrl+Alt+F1 and got back to a
cmd line. Then I copied everything back from /etc.old back to its
original place in /etc and rebooted again.

Now, KDE starts, and I have a normal login screen. However, when I log
in, KDE hangs on "Initializing Peripherals". Eventually, the KDE
startup screen goes away, and I'm left with a blank screen except for
my background, but no desktop icons.

Any idea how to fix this? Thanks
-- 
Mark
[unwieldy legal disclaimer would go here - feel free to type your own]

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] problem after emerge --update world

[Steffen Jobbagy-Felso]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This may sound harsh, but don't use automerge. Portage/etc-update cannot
possibly know about every config change you (or the ebuilds) can make. I assume
etc-update (rightly) doesn't even attempt this and merges based on string
analysis without thought as to what the settings actually mean, leading to breakage.

If you never touched a file it's probably save to just overwrite the existing
one. You always have the backup in case it wasn't save ;)
That's how I do it anyways.

On a different if related topic, I'd recommend running
emerge -DuapvN world
instead of emerge --update world (aka emerge -u world)
That stands for:
- --deep (update dependencies as well and not just packages you explicitly
installed)
- --update
- --ask
- --verbose (shows USE flags and download size)
- --newuse (recompiles packages whose USE flags changed, shown by a * next to the
flag in the output of av)

Steffen

Mark wrote:
> I'm having a problem after I did emerge --update world last night.
> After it finished, it said 75 files  in /etc needed updating. OK, I've
> seen this before and have made mistakes with it. So this time, I
> copied all of /etc to /home/mark/etc.old, and then ran etc-update. I
> then let it auto merge everything and rebooted.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC47gwDPBy+6JbS7oRAgmaAJ96/GbAPEH0iEdTFvrUqe21l8WhqACeNZDY
GSYJzMXyioRenEAv183kxPU=
=9M7K
-----END PGP SIGNATURE-----
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] problem after emerge --update world

[Mark]

Understood - I'll take that approach next time. Any idea how I can get
back to normal now though? Thanks

On 7/24/05, Steffen Jobbagy-Felso <steffen@liquidcomputing.co.uk> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> This may sound harsh, but don't use automerge. Portage/etc-update cannot
> possibly know about every config change you (or the ebuilds) can make. I assume
> etc-update (rightly) doesn't even attempt this and merges based on string
> analysis without thought as to what the settings actually mean, leading to breakage.
> 
> If you never touched a file it's probably save to just overwrite the existing
> one. You always have the backup in case it wasn't save ;)
> That's how I do it anyways.
> 
> On a different if related topic, I'd recommend running
> emerge -DuapvN world
> instead of emerge --update world (aka emerge -u world)
> That stands for:
> - --deep (update dependencies as well and not just packages you explicitly
> installed)
> - --update
> - --ask
> - --verbose (shows USE flags and download size)
> - --newuse (recompiles packages whose USE flags changed, shown by a * next to the
> flag in the output of av)
> 
> Steffen
> 
> Mark wrote:
> > I'm having a problem after I did emerge --update world last night.
> > After it finished, it said 75 files  in /etc needed updating. OK, I've
> > seen this before and have made mistakes with it. So this time, I
> > copied all of /etc to /home/mark/etc.old, and then ran etc-update. I
> > then let it auto merge everything and rebooted.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFC47gwDPBy+6JbS7oRAgmaAJ96/GbAPEH0iEdTFvrUqe21l8WhqACeNZDY
> GSYJzMXyioRenEAv183kxPU=
> =9M7K
> -----END PGP SIGNATURE-----
> --
> gentoo-amd64@gentoo.org mailing list
> 
> 


-- 
Mark
[unwieldy legal disclaimer would go here - feel free to type your own]

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: problem after emerge --update world

[Francesco Talamona]

On Sunday 24 July 2005 17:56, Mark wrote:
> Understood - I'll take that approach next time. Any idea how I can
> get back to normal now though? Thanks

You have now restored the situation when an "etc-update" is needed, so 
you just have to run etc-update (you should see again 75 files to 
consider) and choose per each file what applies: 
-override existing file
-discard updated file
-merge both in a new config file

Keep your /etc/ backup at hand in every case...

Ciao
	Francesco
-- 
Linux Version 2.6.12-gentoo-r6, Compiled #1 Thu Jul 21 07:39:41 CEST 
2005
One 2.2GHz AMD Athlon 64 Processor, 2GB RAM, 4308.99 Bogomips Total
aemaeth
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Maybe a new etc-update is needed? Was: problem after emerge --update world

[Gen Zhang]

[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]

On Sun, 2005-07-24 at 16:48 +0100, Steffen Jobbagy-Felso wrote:
> This may sound harsh, but don't use automerge. Portage/etc-update cannot
> possibly know about every config change you (or the ebuilds) can make. I assume
> etc-update (rightly) doesn't even attempt this and merges based on string
> analysis without thought as to what the settings actually mean, leading to breakage.
> 
> If you never touched a file it's probably save to just overwrite the existing
> one. You always have the backup in case it wasn't save ;)
> That's how I do it anyways.

Ditto for here. However, I was thinking of implementing something more
intelligent, based around a 3-way merge. It's just a quick and dirty
script that scans for updates, ala etc-update, then calls out to
something a little more appropriate, like meld or xxdiff. It would keep
a copy of the 'vanilla' config files in /.etc (or something), and
attempt 3-way merges, assuming that /.etc/config is the common ancestor
of /etc/config and /etc/.config000 (I forget exactly how portage names
them); after a successful merge it would move the new vanilla file
to /.etc.

I hope that makes sense.

Any comments?

Regards,
Gen Zhang


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-amd64] Maybe a new etc-update is needed? Was: problem after emerge --update world

[David Fellows]

> Ditto for here. However, I was thinking of implementing something more
> intelligent, based around a 3-way merge. It's just a quick and dirty
> script that scans for updates, ala etc-update, then calls out to
> something a little more appropriate, like meld or xxdiff. It would keep
> a copy of the 'vanilla' config files in /.etc (or something), and
> attempt 3-way merges, assuming that /.etc/config is the common ancestor
> of /etc/config and /etc/.config000 (I forget exactly how portage names
> them); after a successful merge it would move the new vanilla file
> to /.etc.
> 
> I hope that makes sense.
> 
> Any comments?

Do man dispatch-conf first. :-)

Not that it is perfect by any means.


Dave F

-- 
gentoo-amd64@gentoo.org mailing list