public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stefan Strogin <steils@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: mgorny@gentoo.org
Subject: Re: [gentoo-dev] [News review] LibreSSL support discontinued
Date: Mon, 4 Jan 2021 11:25:21 +0300	[thread overview]
Message-ID: <X/LQJRr9VklHOX75@gentoo.org> (raw)
In-Reply-To: <78a7442c39dd552b0b13353db491c44d04945d51.camel@gentoo.org>

Hello Michal,

On Sun, Jan 03, 2021 at 09:47:31PM +0100, Michał Górny wrote:
> Hello,
> (...)
> To switch before the aforementioned date, remove 'libressl' from your
> USE flags and CURL_SSL targets.  Afterwards, it is recommended to
> prefetch all the necessary distfiles before proceeding with the system
> upgrade, in case wget(1) becomes broken in the process:
> 
>     emerge --fetchonly dev-libs/openssl net-misc/wget
>     emerge --fetchonly --changed-use @world
> 
> A --changed-use @world upgrade should automatically cause LibreSSL
> to be replaced by OpenSSL, and all affected packages to be rebuilt:
> 
>     emerge --changed-use @world
> 

Doesn't work for me. Emerge prints:

```
[blocks B      ] dev-libs/openssl:0 ("dev-libs/openssl:0" is blocking
dev-libs/libressl-3.3.1)

Total: 37 packages (1 new, 36 reinstalls), Size of downloads: 0 KiB
Conflict: 1 block (1 unsatisfied)
(...)
```

I think you have to remove libressl first, like `emerge -C libressl`,
then install openssl like `emerge -1 openssl`, then rebuild
dependencies. As described here but in opposite way:
https://wiki.gentoo.org/wiki/Project:LibreSSL


  reply	other threads:[~2021-01-04  8:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 20:47 [gentoo-dev] [News review] LibreSSL support discontinued Michał Górny
2021-01-04  8:25 ` Stefan Strogin [this message]
2021-01-04  9:18   ` Marek Szuba
2021-01-04  9:20     ` Michał Górny
2021-01-04  9:21 ` [gentoo-dev] [News review v2] " Michał Górny
2021-01-04 13:39   ` Oliver Smeeton
2021-01-04 13:46     ` Toralf Förster
2021-01-04 14:00       ` Oliver Smeeton
2021-01-04 14:24   ` Aaron Bauman
2021-01-04 14:30     ` Michał Górny
2021-01-04 14:40 ` [gentoo-dev] [News review] " Marc Schiffbauer
2021-01-04 15:08   ` Michał Górny
2021-01-04 15:09 ` [gentoo-dev] [News review v3] " Michał Górny
2021-01-04 19:59   ` Ulrich Mueller
2021-01-04 20:48     ` Michał Górny
2021-01-04 20:51       ` Michał Górny
2021-01-05 11:17 ` [gentoo-dev] [News review] " Michał Górny
2021-03-27  1:47   ` Thomas Mueller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=X/LQJRr9VklHOX75@gentoo.org \
    --to=steils@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox