First, stop top-posting, and fix your quoting. This is a mess to try to reply to, and your update woes are bad enough to stare at...
On Wed, May 20, 2020 at 4:51 PM n952162 <n952...@web.de> wrote: > > > Well, you're talking about openssl here. I'm trying to go a step at a time > and looking at the first conflict in that first log file: zlib. You'll have to give me the full command line and output of that if you want me to comment. This seems to be a bit of a trend in your emails. You almost always ask a question without including the command line and output. When you do include output you often trim it, which makes it much harder to tell what is going on. > Isn't the source and build instructions to everything on my system here, too? > I mean, if it had to rebuild all the users of zlib, but wasn't being > requested to update them. No. The build instructions are in the repository. When you updated it, you discarded the ebuilds for any no-longer-supported package versions. > > Something that might also help is running: > emerge -auDv --changed-use --keep-going --with-bdeps=y --changed-deps > --backtrack=100 @system > > > Attached ... > 1. You should update all the files in /etc and then run that command again. 2. Did portage not actually let you proceed with the update? As far as I can tell none of those errors are fatal. Assuming that nothing new comes up after you update all your config files in /etc I would proceed with this update. It certainly won't fix all your problems (which is why you have a mountain of messages after the list of packages that will be updated), but it will get a ton of system packages and your toolchain up-to-date, and will probably make it considerably easier to sort through the rest of the updates. The @system set is largely independent of anything else, so getting it updated makes everything else easier. > Actually, I installed this system just a month or two ago, but I used > a CD I burned of the minimal-install-disk that is perhaps a year > old. I wanted to have all my systems have the same basis, until I > proficient enough to do a stage-1 installation ... I guess this is the > way I'm learning how to get there :-( Two things: First, that seems a bit odd, since if you did an emerge --sync before doing the install you should have been installing new packages regardless of what was on the install disk, especially if you downloaded a current stage3. I guess if you used an old stage3 and didn't update anything then you'd be in that state, but you wouldn't have anything not in @system that way. Second, there is no benefit to doing a stage1 install really except in some unusual bootstrapping situations like building install media. You get an identical system if you do a stage1 install, or if you do a stage3 install and at the end do an emerge -e @world. The difference is that you can actually use your system while the latter rebuilds, vs a stage1 where it takes ages before you can just about anything with it. -- Rich
