Void Linux discussion
 help / color / mirror / Atom feed
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 06:10:06 -0700 (PDT)	[thread overview]
Message-ID: <e4a3238a-7723-4fba-bc95-180580061eb6@googlegroups.com> (raw)
In-Reply-To: <80856c35-ed4e-4af9-b57f-97bbf8ef2d5c@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 988 bytes --]

or try xbps-query -x libressl-openssl this one is obsolete and an older 
version of ca-certificates depends on it this is why i suggestet to update 
ca-ceriticates first, that worked for others, maybe there is more that 
depends on libressl-openssl and hast to be updated first.

Am Donnerstag, 29. Oktober 2015 14:02:41 UTC+1 schrieb Duncaen:
>
> The newest version is libssl35-2.2.4_3 (
> https://github.com/voidlinux/void-packages/blob/master/srcpkgs/libressl/template
> )
> Maybe you can find out what depends on libssl35-2.2.4_1 with xbps-query -X 
> libssl35-2.2.4_1 and update them first.
>
> Am Donnerstag, 29. Oktober 2015 13:58:33 UTC+1 schrieb johnny goodbye:
>>
>>
>>
>> Maybe a packaging error?
>> When searching 
>> https://github.com/voidlinux/void-packages/search?utf8=%E2%9C%93&q=libssl35-2.2.4_1&type=Code
>> I only find
>> libssl.so.35 *libssl35-2*.2.2_1
>>
>> In http://repo.voidlinux.eu/current/multilib/ you can find
>>  *libssl35*-*32bit*-*2.2.4_1*.x86_64.xbps
>>
>

[-- Attachment #1.2: Type: text/html, Size: 3120 bytes --]

  reply	other threads:[~2015-10-29 13:10 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
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 [this message]
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=e4a3238a-7723-4fba-bc95-180580061eb6@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).