Subject: [alpine-aports] Broken packages

From: Valery Kartel <[email-masked]>
Date: Sun, 8 Nov 2015 19:27:19 +0200

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

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.

Somebody needs this packages?

Think it's a reason to move them to unmaintained.

---

From: IT Developer <[email-masked]>
Date: Sun, 8 Nov 2015 18:03:34 +0000

I use tinyssh / dnscrypt-proxy - they still work for me but will be
broken for new installs.

ucspi-tcp (for tinyssh) is still installable.

Do I need to manually request rebuilds of dependent packages when I
update libsodium or should rebuilds occur automatically ?

Stuart.

On 08/11/15 17:27, Valery Kartel wrote:
> 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.
>

---

From: Isaac Dunham <[email-masked]>
Date: Sun, 8 Nov 2015 14:53:08 -0800

> 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).
 
> 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:  [email-masked]
Help:         [email-masked]
---

---

From: IT Developer <[email-masked]>
Date: Mon, 9 Nov 2015 00:44:14 +0000

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.

---

From: Valery Kartel <[email-masked]>
Date: Mon, 9 Nov 2015 01:14:24 +0200

It need to be agreed some kind of fair play, I think.

When upgrading a library it should be informed about the list of packages
that depend on it, and can be broken.

the easiest way is to grep a dependent list, increase their $pkgrel
variable and commit it.

In case of libsodium is:
$ cd aports
$ grep -lr libsodium-dev */*/APKBUILD | xargs -n1 dirname
main/zeromq
testing/dnscrypt-proxy
testing/fastd
testing/quicktun
testing/tinyssh

from this list the only main/zeromq commited to rebuild