DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=SoUO1jTaCteEX9cC9+UlEz8SfWt6FKMR3I+4C64ZvQ4aX+vTLEj9ejPruqSIDaeY+B
         tRXEajAvkH8ave+/iqSkrkrG7KEbBrKkKHsBTxv41Z77oaHS1jwUVWsB9nqOGJKfS7y8
         cj4DUmEUzNAZhbiOiYmL4+Lra+4CSliiEI70w=
Precedence: list
MIME-Version: 1.0
In-Reply-To: <20110406153619.50914a56@ncopa-desktop.nor.wtbts.net>
References: <20110406153619.50914a56@ncopa-desktop.nor.wtbts.net>
Date: Wed, 6 Apr 2011 16:33:03 +0200
Message-ID: <BANLkTi=SiNoNywDVKoGe4yw9sJ_D=BNePQ@mail.gmail.com>
Subject: Re: [alpine-devel] apk-tools-2.1 and abuild-2.9 in edge
From: Carlo Landmeter <clandmeter@gmail.com>
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: alpine-devel@lists.alpinelinux.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 6, 2011 at 3:36 PM, Natanael Copa <ncopa@alpinelinux.org> wrote=
:
> Hi,
>
> We have upgraded apk-tools-2.1 and abuild-2.9 in edge. In addidtion
> so some exciting new features (as install_if and a nicer
> progrerssbar) there are some changes that you should be aware of.
>
> 1) Pure multiarch support. If you previously had arch as last element
> for your repo in /etc/apk/repositories, then you need to remove it.
>
> 2) The $HOME/.cache/apks temporary abuild repo (for its own built
> dependencies) has moved to $HOME/.cache/abuild/$repo, where repo is
> either 'main' or 'testing'. This means that if you dont have 'testing'
> in your repositories, you will not be able to build packages in 'main'
> which has dependencies in 'testing'. This is a feature. This also means
> that in order to build things in 'testing' (or other repo) you need
> have 'main' in you system apk repos.
>
> 3) you can no longer upgrade directly from alpine v1.x or v2.0 to edge.
> You will need a newer apk-tools. Either upgrade to alpine v2.1 first and
> from there to edge, or download apk-tools-static manually. This also
> affect upgrading to the upcoming v2.2. I am thinking of making an
> upgrade script that can be downloaded to perform the upgrade.
>
> In short:
> * remove x86 or x86_64 as last element from url
> =A0in /etc/apk/repositories if its there.
>
> * replace $HOME/.cache/apks with $HOME/.cache/abuild/main if you have
> =A0it in your /etc/apk/repositories.
>
> * watch out if you upgrade from earlier than v2.1
>
> -nc

WARNING: Make sure you first try to update apk-tools instead of full system=
.
If this fails and you get apk: missing apk (wrong arch apk tools) you
can still download static apk and:
apk fix --reinstall apk-tools


-carlo


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---