Date: Sun, 8 Nov 2015 14:53:08 -0800
From: Isaac Dunham <ibid.ag@gmail.com>
To: IT Developer <developer@it-offshore.co.uk>
Cc: alpine-aports@lists.alpinelinux.org
Subject: Re: [alpine-aports] Broken packages
Message-ID: <20151108225307.GA13542@newbook>
References: <CAKTwcDMWqZmcLkrkLVQz5Y_MXb4ZkKQ6nY+sqESw+eAR_mCs9w@mail.gmail.com>
 <563F8E76.6070007@it-offshore.co.uk>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <563F8E76.6070007@it-offshore.co.uk>
User-Agent: Mutt/1.5.24 (2015-08-30)

On Sun, Nov 08, 2015 at 06:03:34PM +0000, IT Developer wrote:
> On 08/11/15 17:27, Valery Kartel wrote:
> > Current version libsodium library is so.17
> > There is a list of broken packages, that linked against old version of
> > libsodium.so.13
> > testing/dnscrypt-prosy
> > testing/fastd
> > testing/quicktun
> > testing/tinyssh
> 
> I use tinyssh / dnscrypt-proxy - they still work for me but will be
> broken for new installs.

> > As I see, tinyssh needs 'tcpserver' from testing/ucspi-tcp to start
> > service. But the package testing/ucspi-tcp is not compiled and exists
> > only in git. And tinnyssh's APKBUILD have no ucspi-tcp in depends.
> >
> ucspi-tcp (for tinyssh) is still installable.

apk search only shows ucspi-tcp6.

However, I'd like to comment that anything that can be run via ucspi-tcp
*can* be run via inetd (or with the correct invocation of a suitable
'netcat' version).
 
> Do I need to manually request rebuilds of dependent packages when I
> update libsodium or should rebuilds occur automatically ?


Rebuilds are not automatic; a library that changes ABI should be
followed by a patch series to rebuild each dependency.

HTH,
Isaac Dunham


---
Unsubscribe:  alpine-aports+unsubscribe@lists.alpinelinux.org
Help:         alpine-aports+help@lists.alpinelinux.org
---