From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 7978E1382C5 for ; Wed, 20 May 2020 21:24:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3258BE0A5C; Wed, 20 May 2020 21:24:54 +0000 (UTC) Received: from mail-ej1-f42.google.com (mail-ej1-f42.google.com [209.85.218.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C77BBE0A4A for ; Wed, 20 May 2020 21:24:53 +0000 (UTC) Received: by mail-ej1-f42.google.com with SMTP id x20so6024467ejb.11 for ; Wed, 20 May 2020 14:24:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=1xBxQ2qBPFrRQ5ZZeg4i95/NSya6MV5/UI8jM5anFpM=; b=YdCL8gdSnRcY7XArQ9Xlh4GXPfO6MN5jSjTCQ5z2XgIYAg/1TTWRwkGeFU6N7TSvVC ADMYq/LYezhAx1G9cNB/vsr2LaDgh+YX6lhYJV1LGadgUlWhyZdm0cERvgE2ASopJNRh 17llJd/Zhw87eHjafxSlg0Xr/CmvdZpAGvB/drkfqAWMESdoIqO66U8nBUCAr6BOGgPO b5V0asXC1fJamAEB1RlVgZ9WwAsPutvpe1+4ERdMHw4xGZDBwvjxjfFE7VhDwjhIktz+ MzrGXwxUyARdyCN1Rh0TMPxYTB9P7jX6YbIohncZyoCsczhD0JwAu1RFwLZj107QAXok WGpg== X-Gm-Message-State: AOAM530BTta3rHipsyduOApzJsFoOw9eyZUIeogEXwcZOpTiYPoVs4VA 5uUUqz9BlE9TcxwepOfYDXB6pJB9ms9LEKfZhgY4ciNeAmJ0xA== X-Google-Smtp-Source: ABdhPJxHumPJkzSdJe9q5Ttyzxeg/QfeP7BR62qvGh1aeKUbyWXUORr4OW0cdzhhvC3HzoK8csOM8eQnIaRYijQCAMk= X-Received: by 2002:a17:906:34c7:: with SMTP id h7mr941425ejb.300.1590009891993; Wed, 20 May 2020 14:24:51 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <58627e0c-0ff6-7280-7506-63a43abfd988@web.de> <20200520165928.cziltdysjc3pbzg3@ad-gentoo-main> <9b443081-d522-31f0-2d7c-061a37f5ea35@gmail.com> <4d06e249-4ae7-048d-7478-17ad62e942ec@web.de> In-Reply-To: <4d06e249-4ae7-048d-7478-17ad62e942ec@web.de> From: Rich Freeman Date: Wed, 20 May 2020 17:24:40 -0400 Message-ID: Subject: Re: [gentoo-user] slot conflict for the same package: how to add a USE flag? To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 9bdc04aa-0b6b-4487-bd92-71940db61309 X-Archives-Hash: a212f72b46ba84ed194bc7136bc659f3 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 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