Hi,

On Mon, 18 Jul 2022, Wolf wrote:

> Hello,
>
> I would like to inquire about the `community/rust' package. After
> reading this [0] fun debate bug thread over at debian bug tracker, I've
> started to wonder what is the state of this in alpine.
>
> It looks like at least some of the patches in community/rust do not fall
> under any of these categories (from [1]):
>
> - porting the software to a different architecture

Hi,

On Wed, 22 Jun 2022, Markus Kolb wrote:

> Am 22.06.2022 14:14, schrieb Paul Zillmann:
>> Hello Markus,
>> 
>> I've read thru the entire conversation - the problem you are drawing isn't 
>> one.
>> 
>> 1. The passwd calls have an adduser call right above them, creating a
>> system user with that name.
>> That fails if the user already exists and would return a non-zero
>> return code. Thereby the package installation fails.

Hi,

On Tue, 21 Jun 2022, Tomas Kolda wrote:

>> void linux already does, unless you specifically mean multilib'd at the
>> same time.
>>
>> and gentoo, of course :)
>>
> Nice I did not know that. From what I see there they are also not
> combining. Both are having it as separate flavor builds (one or the
> other).
>

Hi,

On Tue, 21 Jun 2022, Natanael Copa wrote:

> On Tue, 21 Jun 2022 10:49:07 +0200
> Tomas Kolda <koldat@gmail.com> wrote:
>
>
>>> I would rather spend the resources on fixing the issues with musl.
>>>
>> I completely agree and understand your view. Unfortunately I am not in
>> a position to offer or fund the resources.
>
> This is what I was afraid of.

Hi,

On Sat, 18 Jun 2022, Markus Kolb wrote:

> Hello,
>
> I'm trying to maintain 2 packages I'm using with Alpine and would not like to 
> see being removed from the repositories from future releases.
> But I could see that there is some basic problem.
> Currently you are unlocking users in pre-install of packages without any 
> further checks of the existing system environment.
> There is assumed the user is not existing, there is no username clash, the 
> user has not set a password, the user is used only for this package and so 
> on.

Hi,

On Tue, 21 Jun 2022, Laurent Bercot wrote:

>
> I find it interesting that when thinking about such things (making
> a distro supporting two libcs, or supporting two init systems, or
> patching some software to work with the better-known alternative, or...)
> the frame of reference is always "adding the support of $biggerthing
> to a project that has $smallthing as a characteristic", and never the
> opposite.
>
> It always ends up meaning more burden for the project that typically
> has fewer resources, less manpower, and that is only kept afloat by

Hi,

On Tue, 21 Jun 2022, Tomas Kolda wrote:

> Trying to send email again from my personal email as my previous post
> was marked as invalid.
>
> Hi,
>
> I know that this topic is very sensitive in Alpine, but please let me
> describe first what and why we would like to achieve.
>
> 1. We love to use Alpine for our containers. Alpine has very fresh
> versions packages, it is very easy to use, versatile, customizable and

Hello,

I am pleased to announce that pursuant to Technical Steering Committee 
ticket 47 that we have decided to remove the main-vs-community ACL 
restrictions on the aports repository, meaning anyone who is presently an 
Alpine developer (e.g. with commit privileges) may now commit to the main 
repository in aports.

We will also be scheduling some additional TSC work items to improve the 
onboarding process for developers as well as formally specifying the 
requirements for vetting new developers.

As a general reminder: Alpine developers as a consequence of their work 
have effective root access to every Alpine install, so please be mindful

Hi,

On Thu, 20 Jan 2022, Nico Schottelius wrote:

>
> Ariadne Conill <ariadne@dereferenced.org> writes:
>> Gitlab allows opening "private" bugs.
>
> Is there a day one does not learn something new?
>
> Thanks a lot for the pointer, much appreciated.

Gitlab refers to them as "sensitive issues."  In this case, because the 
complaint was originally posted on alpine-devel list, it is a public

Hi,

On Thu, 20 Jan 2022, Nico Schottelius wrote:

> Ariadne Conill <ariadne@dereferenced.org> writes:
>> [ ... ]
>> For future reference, issues can be raised with the Council on the
>> Council's issue tracker:
>>
>> https://gitlab.alpinelinux.org/alpine/council/-/issues/new
>
> Everyone who knows me knows I'm all for transparency, but if it was me
> trying to reach out to the CoC for reporting misconduct / misbehaviour,
> I would not feel properly protected.