From: Duncaen <over...@googlemail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: update error MISSING: libssl35-2.2.4_1
Date: Thu, 29 Oct 2015 05:05:26 -0700 (PDT) [thread overview]
Message-ID: <22dd2312-3fbf-4df1-abfd-cd83793b62f9@googlegroups.com> (raw)
In-Reply-To: <d22477a5-78d0-4530-8cca-48cd1f7a5667@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1284 bytes --]
xbps-install -Su ca-certificates
Am Donnerstag, 29. Oktober 2015 10:31:54 UTC+1 schrieb johnny goodbye:
>
> After succesfully updating xbps-install
> # xbps-install -Syu
> [*] Updating `http://repo.voidlinux.eu/current/x86_64-repodata' ...
> x86_64-repodata: 934KB [avg rate: 3058KB/s]
> [*] Updating `
> http://repo.voidlinux.eu/current/multilib/nonfree/x86_64-repodata' ...
> [*] Updating `http://repo.voidlinux.eu/current/multilib/x86_64-repodata'
> ...
> x86_64-repodata: 357KB [avg rate: 450MB/s]
> [*] Updating `http://repo.voidlinux.eu/current/nonfree/x86_64-repodata'
> ...
> MISSING: libssl35-2.2.4_1
> Transaction aborted due to unresolved dependencies.
>
> Then trying:
> # xbps-install libssl35
> libressl-2.2.3_1 broken, needs `libcrypto35-2.2.4_3'
> libressl-openssl-2.2.3_1 broken, needs `libcrypto35-2.2.4_3'
> libtls6-2.2.3_1 broken, needs `libcrypto35-2.2.4_3'
> libressl-2.2.3_1 broken, needs `libssl35-2.2.4_3'
> libressl-openssl-2.2.3_1 broken, needs `libssl35-2.2.4_3'
> libtls6-2.2.3_1 broken, needs `libssl35-2.2.4_3'
> Transaction aborted due to unresolved dependencies.
>
> then
> # xbps-install libssl35 libcrypto35 libressl libressl-openssl libtls6
> MISSING: libssl35-2.2.4_1
> Transaction aborted due to unresolved dependencies.
>
>
> How to solve?
>
[-- Attachment #1.2: Type: text/html, Size: 3632 bytes --]
next prev parent reply other threads:[~2015-10-29 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 9:31 johnny goodbye
2015-10-29 12:05 ` Duncaen [this message]
2015-10-29 12:44 ` johnny goodbye
2015-10-29 12:58 ` johnny goodbye
2015-10-29 13:02 ` Duncaen
2015-10-29 13:10 ` Duncaen
2015-10-29 14:45 ` Chris Brannon
2015-10-29 23:08 ` johnny goodbye
2015-10-30 15:26 ` johnny goodbye
2015-11-09 8:17 ` Juan RP
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=22dd2312-3fbf-4df1-abfd-cd83793b62f9@googlegroups.com \
--to="over..."@googlemail.com \
--cc="void..."@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).