Caution when moving packages built against glibc 2.27

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Caution when moving packages built against glibc 2.27

arch dev mailing list
Care should be taken when building against glibc 2.27 (which is currently
in [staging]).

In particular:

   - While glibc 2.27 is in [staging], new rebuilds should not be started.
   - After glibc 2.27 migrates to [testing], packages built against it
   should remain in [testing] until glibc 2.27 lands in [core].

The above considerations must be taken into account because packages built
against glibc 2.27 might depend on versioned symbols that are not found in
glibc 2.26 and thus will not work. [1]

[1] https://bugs.archlinux.org/task/58216
Reply | Threaded
Open this post in threaded view
|

Re: Caution when moving packages built against glibc 2.27

arch dev mailing list
On 13 April 2018 at 18:17, Evangelos Foutras <[hidden email]>
wrote:

> Care should be taken when building against glibc 2.27 (which is currently
> in [staging]).
>
> In particular:
>
>    - While glibc 2.27 is in [staging], new rebuilds should not be started.
>    - After glibc 2.27 migrates to [testing], packages built against it
>    should remain in [testing] until glibc 2.27 lands in [core].
>
> The above considerations must be taken into account because packages built
> against glibc 2.27 might depend on versioned symbols that are not found in
> glibc 2.26 and thus will not work. [1]
>
> [1] https://bugs.archlinux.org/task/58216
>

It's been a few days since glibc 2.27 was moved to [testing]. This is a
reminder not to move packages built against it to the stable repos.