X-Original-To: alpine-aports@mail.alpinelinux.org Delivered-To: alpine-aports@mail.alpinelinux.org Received: from mail.alpinelinux.org (dallas-a1.alpinelinux.org [127.0.0.1]) by mail.alpinelinux.org (Postfix) with ESMTP id 77953DC6A2E for ; Mon, 9 Nov 2015 00:44:08 +0000 (UTC) Received: from apollo.thewebhostserver.com (apollomail.thewebhostserver.com [46.23.65.248]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 38E80DC1CF8 for ; Mon, 9 Nov 2015 00:44:07 +0000 (UTC) Received: from [81.4.121.188] (port=54399 helo=[10.8.0.10]) by apollo.thewebhostserver.com with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.86) (envelope-from ) id 1ZvaZ2-0028ar-71; Mon, 09 Nov 2015 00:44:04 +0000 Reply-To: developer@it-offshore.co.uk Subject: Re: [alpine-aports] Broken packages References: <563F8E76.6070007@it-offshore.co.uk> <20151108225307.GA13542@newbook> To: Isaac Dunham Cc: alpine-aports@lists.alpinelinux.org From: IT Developer X-Enigmail-Draft-Status: N1110 Organization: IT Offshore Message-ID: <563FEC5E.8090104@it-offshore.co.uk> Date: Mon, 9 Nov 2015 00:44:14 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 X-Mailinglist: alpine-aports Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 In-Reply-To: <20151108225307.GA13542@newbook> Content-Type: multipart/alternative; boundary="------------060708010606010703030001" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - apollo.thewebhostserver.com X-AntiAbuse: Original Domain - lists.alpinelinux.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - it-offshore.co.uk X-Get-Message-Sender-Via: apollo.thewebhostserver.com: authenticated_id: developer@it-offshore.co.uk X-Source: X-Source-Args: X-Source-Dir: X-Virus-Scanned: ClamAV using ClamSMTP This is a multi-part message in MIME format. --------------060708010606010703030001 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit In the tinyssh "README.alpine" there are also instructions for running tinyssh via inetd. apk search does not show 'ucspi-tcp' but it is still installable: ------------------------------------------------------------------------ musl64 [~/aports/testing/tinyssh]$ sudo apk del ucspi-tcp (1/1) Purging ucspi-tcp (0.88-r1) Executing busybox-1.24.1-r4.trigger OK: 275 MiB in 100 packages musl64 [~/aports/testing/tinyssh]$ sudo apk add ucspi-tcp (1/1) Installing ucspi-tcp (0.88-r1) Executing busybox-1.24.1-r4.trigger OK: 275 MiB in 101 packages musl64 [~/aports/testing/tinyssh]$ which tcpserver /usr/bin/tcpserver ------------------------------------------------------------------------ Stuart. On 08/11/15 22:53, Isaac Dunham wrote: > 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 --------------060708010606010703030001 Content-Type: text/html; charset="windows-1252" Content-Transfer-Encoding: quoted-printable In the tinyssh "README.alpine" there are also instructions for running tinyssh via inetd.

apk search does not show 'ucspi-tcp' but it is still installable:

musl64 [~/aports/testing/tinyssh]$ sudo apk del ucspi-tcp
(1/1) Purging ucspi-tcp (0.88-r1)
Executing busybox-1.24.1-r4.trigger
OK: 275 MiB in 100 packages
musl64 [~/aports/testing/tinyssh]$ sudo apk add ucspi-tcp
(1/1) Installing ucspi-tcp (0.88-r1)
Executing busybox-1.24.1-r4.trigger
OK: 275 MiB in 101 packages
musl64 [~/aports/testing/tinyssh]$ which tcpserver
/usr/bin/tcpserver


Stuart.

=A0


On 08/11/15 22:53, Isaac Dunham wrote:
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/u=
cspi-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).
=20
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

--------------060708010606010703030001-- --- Unsubscribe: alpine-aports+unsubscribe@lists.alpinelinux.org Help: alpine-aports+help@lists.alpinelinux.org ---