DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=qUnCMSRb/EuHqmzcuPOokbJEuRg9SUmlNHy5BaFO69o8Rsoqj2nxqglyMJ2ijG9PjD
         sJWtSHxV5rJ/BQ3/q2VzTSvAEI4Pcr00nKFootj/6xVKORBOFujvLqh7cQKntJpuiAxo
         2/fEPHlgRRJtquYvmsOLN7jvvEYvKRhweBrNg=
Precedence: list
MIME-Version: 1.0
Date: Fri, 14 May 2010 10:53:19 +0200
Message-ID: <AANLkTimm48rCUdTnvHb1bw0TaqkHcMZ7_WhN9IxJwVtb@mail.gmail.com>
Subject: [alpine-devel] openssl-1.0.0 upgrade
From: Natanael Copa <natanael.copa@gmail.com>
To: Alpine Developers <alpine-devel@lists.alpinelinux.org>
Content-Type: text/plain; charset=ISO-8859-1

Seems like uclibc nptl is more or less working so I take the
opportunity to break the edge build again and upgrade openssl.

since many apps depends on openssl and critical packages (abuild,
apk-tools, git) we need be somewhat careful on the upgrade.

We have 2 options:
1. create new package names for new package (libcrypto1.0 + libssl1.0)
and allow them to be installed side-by-side.
2. temporarily build static apk-tools and abuild, (possibly git too),
push to build-edge, upgrade openssl, and rebuild all packages linked
to libcrypto or openssl.

I think we will try option #1.

We will try avoid break edge but this is a high-risk operation so be
prepared for edge breakages during the day.

Thanks for your patience.

-- 
Natanael Copa


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---