Code-slinging rabbit.


Last active 1 year, 1 month ago


Last active 2 years ago
View more

Recent activity

Re: v3.15 builders bootstrapped 5 days ago

From Ariadne Conill to ~sircmpwn/alpine-devel


On Sun, 17 Oct 2021, Nico Schottelius wrote:

> Yeaaaaaaha! Do we already have the custom of a virtual release party?
> If yes, where & when does it happen?
> If no, is anyone interested in having a virtual (video based?) hangout
> to celebrate? Maybe cheering with a drink of your choice?

As we now have the capacity to do this, I think it might be a reasonable 
idea.  We haven't had the capacity to do this prior to the setup of

Re: v3.15 builders bootstrapped 5 days ago

From Ariadne Conill to ~sircmpwn/alpine-devel


On Sun, 17 Oct 2021, Jakub Jirutka wrote:

> Hi,
> I’m sorry, but there’s one change I have to do (because know one did it so far): upgrade Ruby from 2.7 to 3.
> Next time I would appreciate informing about the freeze period in advance.

We are only in soft freeze.  Feel free to do the Ruby upgrade, but try to 
get it done quickly.

Addressing your other concern, the TSC will outline a release timeline for

Heads up: OpenSSL 3 -> 1.1 migration underway 6 days ago

From Ariadne Conill to ~sircmpwn/alpine-devel


As part of the 3.15 release cycle, we planned to upgrade the system 
OpenSSL to 3.0, because of the improved licensing and isolation of legacy, 
known-broken cryptographic primitives behind a legacy provider module.

Unfortunately, this migration hit a few regressions, notably in apk-tools, 
but also some packages like MariaDB were not anywhere near ready to be 
used in production with OpenSSL 3.  We decided to wait a few weeks to see 
what happened, but we hit a key decision point (preparation for Alpine 
3.15 soft freeze) without any resolution, and so the contingency plan 
automatically came into effect.

The contingency plan, of course, being that we would move back to OpenSSL

Re: The future for Xen in Alpine? a month ago

From Ariadne Conill to ~sircmpwn/alpine-devel


On Thu, 9 Sep 2021, Mogens Jensen wrote:

> Hi,
> As far as I can tell, Xen has always been a first class citizen in
> Alpine: ISO image on download page, available in main, security updates
> quickly available etc.
> Are there any plans for this not to continue in the foreseeable future?
> I have used Xen on Alpine for a long time for various projects, but is
> now in a position where I can influence the decision on software used

Re: [PATCH] libpkgconf: bypass list iteration when pulling variables/dependencies 2 months ago

From Ariadne Conill to ~lattis/muon


On Wed, 18 Aug 2021, Stone Tickle wrote:

> Looks good to me, thanks for this!

Thanks for merging so quickly.  By the way: pkgconf 1.8.1, due to be 
released this weekend, hopefully resolves the memory leak issues when 
working with muon, so you may wish to retry it.


[PATCH] libpkgconf: bypass list iteration when pulling variables/dependencies 2 months ago

From Ariadne Conill to ~lattis/muon

List iteration is only needed for dependency graphs where multiple dependencies
are specified in the queue.  In the case of muon, the dependency resolution queue
only has a single dependency in the resolution queue in any case.

Because of various reasons (people doing crazy things in their autoconf scripts),
pkgconf has to support --modversion et al for multiple dependencies, like its
freedesktop.org counterpart, but this thankfully does not apply to muon.

Signed-off-by: Ariadne Conill <ariadne@dereferenced.org>
 src/external/libpkgconf.c | 33 ++++++++-------------------------
 1 file changed, 8 insertions(+), 25 deletions(-)

diff --git a/src/external/libpkgconf.c b/src/external/libpkgconf.c
[message trimmed]

openssl 3.0 now in testing 2 months ago

From Ariadne Conill to ~sircmpwn/alpine-devel


The time has come for another OpenSSL release migration.  I intend to do a 
system change proposal to switch our default OpenSSL implementation to 
OpenSSL 3.0 in Alpine 3.15 *if* there is not much fall out with testing.

If you want to test your packages, you can do so by building against 
openssl3.0-dev instead of openssl-dev.  Likewise, you can use the OpenSSL 
3.0 CLI by installing openssl3.0 package.  Note you will need to do `apk 
fix openssl` after removing openssl3.0 if you want to go back to the 
OpenSSL 1.1 CLI.

Please test your packages with OpenSSL 3.0, so we can get some idea of 
what the fall out is going to be.  I would like to switch to OpenSSL 3.0

[3.15] System change proposal: Move sudo to community 2 months ago

From Ariadne Conill to ~sircmpwn/alpine-devel

The following system change proposal has been submitted to the Technical 
Steering Committee.  If you are interested, please comment on 
https://gitlab.alpinelinux.org/alpine/tsc/-/issues/1 so that the TSC can 
consider your feedback.


## Summary

At present, `sudo` is in the `main` repository, which requires us to 
provide security support for 2 years.  Upstream `sudo` does not provide an 
"LTS" lifecycle, so this requires either performing security upgrades 
during the maintenance lifecycle, or backporting security fixes by hand.

Re: have next stable (e.g. v3.15) as transitional symlink to edge in the repository? 3 months ago

From Ariadne Conill to ~sircmpwn/alpine-devel


On Fri, 16 Jul 2021, alpine@vodafonemail.de wrote:

> Hi,
> sometimes I'd wish it could be possible to let a system only temporarily follow
> edge development, but stay on the next stable release when it gets out.

To be clear: the contents of the Alpine edge repository *never* become a 
release.  Once in a while, we take the Alpine edge repository, and use 
that as the basis of a distro-wide rebuild to create a new release branch.

Mixing edge and the next release once it is branched is not recommended,

Re: Plan for RISCV64 in Alpine 3.15 3 months ago

From Ariadne Conill to ~sircmpwn/alpine-devel


On Sun, 27 Jun 2021, Roman Shaposhnik wrote:

> Hi!
> so first of all -- thank you all for taking RISCV forward
> while I was traveling -- much appreciated! I see that
> we now have a builder that produces packages and they
> are actually getting deposited at the usual places. E.g.:
>    https://dl-cdn.alpinelinux.org/alpine/edge/main/riscv64/
> Given that, here's my first few infrastructure related questions:
>  1. what does it take for edge packages to show up on: