Re: [gentoo-user] Re: emerge world looking grim
On Wed, Aug 26, 2015 at 12:10 AM, Harry Putnam rea...@newsguy.com wrote: The only thing I can say on my own behalf is that there was once a time when it wasn't so far fetched to start emerge -vC 'ing stuff. Many thing's can be removed with `emerge -C` and recovered from, but I doubt unmerging packages in @system was ever a well supported operation...
Re: [gentoo-user] Re: emerge world looking grim
On 24/08/2015 15:35, Harry Putnam wrote: Alan Mackenzie a...@muc.de writes: I'd recommend you then just to reinstall. Remembering my fights with stupid error messages from emerge, and so on, I wish I'd just reinstalled months earlier than I did. Thanks for the frank suggestions and noted lack unix hero talk... hehe. The other Alan Mac chipping in :-) I know how you feel, I get it too when confronted with Python Web frameworks. Very confusing stuff to this old brain. I understand portage's magic, it makes sense to me and I can see through the spell. I don't understand web framework magic and can't see through the spell. sigh -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Re: emerge world looking grim
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 24/08/15 23:59, Rich Freeman wrote: On Mon, Aug 24, 2015 at 9:39 AM, Alec Ten Harmsel a...@alectenharmsel.com wrote: On Mon, Aug 24, 2015 at 09:35:36AM -0400, Harry Putnam wrote: Alan Mackenzie a...@muc.de writes: I'd recommend you then just to reinstall. Remembering my fights with stupid error messages from emerge, and so on, I wish I'd just reinstalled months earlier than I did. Thanks for the frank suggestions and noted lack unix hero talk... hehe. I personally think that updating glibc and gcc, then continuing with the rest of the system update is the easiest path forward. You won't lose your portage config, it will probably be a little bit faster, and it requires a lot less manual intervention (running a handful of commands vs. following the handbook).. Agree. I probably get update issues of this complexity at least annually. I couldn't tell you when I installed my stage3 on this box, but it was a LONG time ago and I'm constantly cleaning up /etc cruft from things being moved around. I would not rush to just reinstall a gentoo box unless you get really stuck, or this is part of a configuration management workflow (which I fully encourage - there is something to be said for blowing away your install and reinstalling every time you do a package update, just to demonstrate that you're able to do it from a disaster-recovery standpoint). +1 There's also the fact that working through conflicts like this is also an educational experience in itself, making it easier for the next time. - -- wraeth wra...@wraeth.id.au GnuPG Key: B2D9F759 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iF4EAREIAAYFAlXbJLQACgkQXcRKerLZ91keqgD+JX2qXS8/Db/Y5oR8DDA2TsUQ VmNTY7qyU1iWBzzwZm8A/A9f2dIIhj7e5McD2cmeLnyf0TszISU85vyOQTsJ7bWI =gjmo -END PGP SIGNATURE-
Re: [gentoo-user] Re: emerge world looking grim
On Mon, Aug 24, 2015 at 09:35:36AM -0400, Harry Putnam wrote: Alan Mackenzie a...@muc.de writes: I'd recommend you then just to reinstall. Remembering my fights with stupid error messages from emerge, and so on, I wish I'd just reinstalled months earlier than I did. Thanks for the frank suggestions and noted lack unix hero talk... hehe. I personally think that updating glibc and gcc, then continuing with the rest of the system update is the easiest path forward. You won't lose your portage config, it will probably be a little bit faster, and it requires a lot less manual intervention (running a handful of commands vs. following the handbook).. Alec
Re: [gentoo-user] Re: emerge world looking grim
On Mon, Aug 24, 2015 at 9:39 AM, Alec Ten Harmsel a...@alectenharmsel.com wrote: On Mon, Aug 24, 2015 at 09:35:36AM -0400, Harry Putnam wrote: Alan Mackenzie a...@muc.de writes: I'd recommend you then just to reinstall. Remembering my fights with stupid error messages from emerge, and so on, I wish I'd just reinstalled months earlier than I did. Thanks for the frank suggestions and noted lack unix hero talk... hehe. I personally think that updating glibc and gcc, then continuing with the rest of the system update is the easiest path forward. You won't lose your portage config, it will probably be a little bit faster, and it requires a lot less manual intervention (running a handful of commands vs. following the handbook).. Agree. I probably get update issues of this complexity at least annually. I couldn't tell you when I installed my stage3 on this box, but it was a LONG time ago and I'm constantly cleaning up /etc cruft from things being moved around. I would not rush to just reinstall a gentoo box unless you get really stuck, or this is part of a configuration management workflow (which I fully encourage - there is something to be said for blowing away your install and reinstalling every time you do a package update, just to demonstrate that you're able to do it from a disaster-recovery standpoint). -- Rich
Re: [gentoo-user] Re: emerge world looking grim
On Mon, Aug 24, 2015 at 9:46 AM, James wirel...@tampabay.rr.com wrote: Hello Harry. Gentoo has the handbook for it's main install. A bit of a drag but good for for a refresher or leaning. Rich put up an excellent set of VM gentoo install instructins [1]: My main goals with those notes (I wouldn't call them instructions at this point) were to cover: 1. Btrfs raid1, which many seemed to be struggling with. 2. dracut, which many also seemed to be struggling with. 3. Integrated systemd+openrc instructions. I found that the differences were actually very minor in my guide, while the distinction seems much bigger in the handbook. My next steps are to clean this all up into a blog article (less notes, more actual instructions), and then probably merge these into the handbook. The latter will take a bit more effort as I don't want to be disruptive, but I think that some of our defaults are outdated. In particular I really think the handbook should present dracut as the mainstream initramfs solution and genkernel's initramfs as an alternative. I have no issues with using genkernel to build a kernel, though you'd need to use the option to run menuconfig and pick your init. I'm not proposing making systemd the default. If you follow the guide in the order I've written it using systemd vs openrc really doesn't change much at all besides what profile you use, your kernel settings, and one line in your grub config. And that was a big part of why I wrote this guide. My hunch from numerous container installs is that a streamlined systemd install looks almost the same as an openrc install and by merging the instructions you can make either path easy to follow while leaving all the choice in the hands of the user. The main challenge I see with integrating systemd as the numerous places where the instructions have you run rc-update and instead you'd need systemctl enable. It is a trivial change, but my main concern is doing it in a way that doesn't add confusion or bloat. Many distros actually use a wrapper of some kind so that they can have one procedure for either, but I don't care for that. One of the things I really like about Gentoo is that we stick to upstream and don't do what Debian does like wrap systemd wrappers around bash init scripts. In any case, the notes as they currently stand are not something I'd recommend to a new user. They're fine for experienced users looking for the short version. When I get them integrated into the handbook I think it will be an overall improvement and usable for new users. -- Rich
Re: [gentoo-user] Re: emerge world looking grim
On 24/08/2015 16:46, Harry Putnam wrote: Alan McKinnon alan.mckin...@gmail.com writes: Working thru all the guff with all you posters patient help would probably have been the best but between posting and seeing answers (suring the morning in the wee hours). I jumped stupid and starting uninstalling some of the blockers. So, I've made the mess considerably worse... maybe unsolvable since I have no gcc now and so no way to grind out the builds plus other truly boneheaded uninstalls that appear to have rendered my system unusable just like the little warning says when you gentoo -vC pkg ... whee. Ah yes. That was a supremely thick move on your part :-) [1] I'm pretty sure at this point... I best to get a re-install going. It can be fixed. If you want the learning experience, here's how you would do it: It isn't the dead-end it first appears. Yes, you do need a compiler to compile anything (including any version of the compiler itself), and now you don't have one. Solution: figure out a way to get one! Maybe your make.conf is set up to create binary packages, the variable is PKGDIR. Look in that directory for gcc, and emerge it (yes, you can emerge a tarball directly). Repeat for all important packages you unmerged. Now you have a compiler, because you don't need a compiler to untar a tarball. Or you can get a binary package from anywhere else you trust. Now, if you were to have unmerged python, or tar, bzip2 - then that is a bigger problem. Boot off a rescue CD, mount your regular system somewhere and untar into that location. Assuming of course that your rescue CD has the tools you need like tar and bzip2 (most of what is in @system) Also it may help some of you posters to know that this install was not fully developed and an in common use OS anywayA reinstall will loose nothing of any importance. Whatever is there of importance would be in /home /etc/ and maybe /var so I've rsynced them to my current Solaris desktop and will have any needed files to use later after the reinstall has progressed to a higher level. Thank you all for the suggestions they are most instructive and my notes from them should prove useful down the road. PS - Its coming back to me how gentoo is installed with the stage3 and portage downloads. Again, thanks for your patience Either way, you should be back up and running come Thursday latest :-) Hey, this is Gentoo, here we like watching gcc outpt scroll by for hours/days at a time. [1] Reminds me of an old joke: Q: What's the second worst sound you can hear a sysadmin make? A: Uh-oh Q: And the worst sound? A: Oops Looks like you had an oops moment there -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Re: emerge world looking grim
On Mon, 24 Aug 2015, Alan McKinnon wrote: Or you can get a binary package from anywhere else you trust. My personal favourite: chroot into a stage3 and quickpkg gcc. Then copy to your install and voila.
Re: [gentoo-user] Re: emerge world looking grim
On Mon, Aug 24, 2015 at 10:46 AM, Harry Putnam rea...@newsguy.com wrote: So, I've made the mess considerably worse... maybe unsolvable since I have no gcc now and so no way to grind out the builds plus other truly boneheaded uninstalls that appear to have rendered my system unusable just like the little warning says when you gentoo -vC pkg ... whee. Uh, not to drag you through the mud, but what gave you the idea to try that? I'm mainly interested so that we can go fix it if there is some document that is leading people astray. The suggestion was to check gcc-config -l, and then set a recent version of gcc if it isn't already selected. That should be the correct fix, though you might need to install a newer gcc version. You don't need to use emerge -C to do any of that. That command is one of those I know what I'm doing commands which will happily mess up your system. At this point your simplest solution is to create a binary package of whatever it is you got rid of and re-install it, but that is going to be a lot more complex than the minor issue you were having before. Your email is pretty light on details, so I don't even know what it was that you uninstalled. I'd suggest not doing stuff like this in the future. I can pretty much guarantee that emerge output like the one you posted will happen to you a few times a year and is fairly routine if you have a system with many packages on it. Granted, you won't have quite as much to deal with if you update daily/weekly, but still, you probably shouldn't go into panic mode everytime portage wants help with something because it happens fairly often. -- Rich
Re: [gentoo-user] Re: emerge world looking grim
On Mon, Aug 24, 2015 at 11:36 AM, James wirel...@tampabay.rr.com wrote: Are you going to roll out some notes on putting raid-1::btrfs onto HD? Or just the VM install? The notes should work just fine for installing that on an HD. Is there something you found missing in them? The only thing they aren't targeted at is EFI. I'd need to mess with that a bit in a VM as I do not have any EFI hardware other than my chromebook, which seems fussier than most as far as what it boots. -- Rich
Re: [gentoo-user] Re: emerge world looking grim
On 24/08/2015 18:49, Jeremi Piotrowski wrote: On Mon, 24 Aug 2015, Alan McKinnon wrote: Or you can get a binary package from anywhere else you trust. My personal favourite: chroot into a stage3 and quickpkg gcc. Then copy to your install and voila. I knew there was a way to do it, just couldn't remember how. So I decided to not run the open_mouth insert_foot scripts hardwired in my brain :-) Thanks! -- Alan McKinnon alan.mckin...@gmail.com
Re: [gentoo-user] Re: emerge world looking grim
Alan McKinnon wrote: [1] Reminds me of an old joke: Q: What's the second worst sound you can hear a sysadmin make? A: Uh-oh Q: And the worst sound? A: Oops Looks like you had an oops moment there I have quite a few of those Uh oh moments. I think top on my list tho is oh crap. :-( Dale :-) :-)
