Hi!

The first release candidate for Alpine Linux 3.11 is available for
download.

http://dl-cdn.alpinelinux.org/alpine/v3.11/releases/

Note that the default kernel package name was changed from
linux-vanilla to linux-lts. There are no provides=linux-vanilla yet
which means that you currently don't will get the linux-lts 5.4 kernel
if you upgrade.

Please help test that the various installation variations work.

Hi!

I wonder if anyone is using dahdi-linux kernel module or if we can
remove those for 3.11?

They are for sangoma (previously digium) cards.

-nc

Hi!

I updated ansible-lint package to 4.1.1a1 so it builds with python 3.8.

It looks like upstream has removed the setup.py in favor of `pip
install`.[1]

Do you (or someone else) know how we properly can package
this properly with pip? [2]

Or should we simply remove the package, telling the users to use pip
install and let upstream deal with the user support?

Thanks!

On Tue, 26 Nov 2019 09:59:26 -0500
"Drew DeVault" <sir@cmpwn.com> wrote:

> On Tue Nov 26, 2019 at 2:54 PM, Natanael Copa wrote:
> > CONFIG_PSI=n
> > CONFIG_UNICODE=n
> > CONFIG_KEYS_REQUEST_CACHE=n  
> 
> =y for all kernels
> 
> > CONFIG_TINYDRM_HX8357D=n
> > CONFIG_TINYDRM_ILI9225=n
> > CONFIG_TINYDRM_ILI9341=n
> > CONFIG_TINYDRM_MI0283QT=n

Hi!

I am working on updating the kernel to 5.4 and renaming -vanilla to -lts.

There are a bunch new config options, listed below.

Are there anything specific you think we should enable in:
linux-lts
linux-virt

Are there other config options you think we should enable for the other
architectures?

-nc

On Mon, 25 Nov 2019 10:10:49 -0500
Drew DeVault <sir@cmpwn.com> wrote:

> ---
>  community/doas/APKBUILD | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Merged. Thanks!

I also changed to dynamic build and enabled persist (--with-timestamp).

I am considering moving it to main.

-nc

Hi!

As you may have noticed, the builders for v3.11 is up now.

This means that we need to focus on stabilizing what we have in the
tree and close open issues rather than work on adding new things or do
things that delays the release.

We have a freeze on toolchain and build tools. This means packages that
are used to build other packages (gcc, gnu make, cmake, ninja, flex,
bison, abuild etc). Everything that changes the way packages are built
in significant way.

What we want avoid is having the packages successfully built now, but

On Fri, 25 Oct 2019 12:32:35 +0200
soeren@soeren-tempel.net wrote:

> Hi there,
> 
> Currently Alpine supports (at least) three ways to submit patches:
> 
> 	1. GitLab merge request (MR) on gitlab.alpinelinux.org
> 	2. GitHub pull requests (PR) on github.com/alpinelinux
> 	3. git-format-patches send to the mailing list (ML)
> 
> IMHO this creates an unnecessary maintenance overhead, e.g. you have to
> consult three platforms to figure out if a patch has already been
> submitted somewhere. Additionally, the platforms use different CI

The Alpine Linux project is pleased to announce the immediate
availability of version 3.10.3 of its Alpine Linux operating system.

The full lists of changes can be found in the git log[1] and gitlab[2].

[1]: http://git.alpinelinux.org/cgit/aports/log/?h=v3.10.3
[2]: https://gitlab.alpinelinux.org/alpine/aports/-/milestones/141


Git Shortlog
------------

<pre>
Alex Mirski-Fitton (1):

Hi!

The working group has been working on a proposal for the Alpine Linux
governance. Before we post any suggestions we'd like to try define and
agree on current state and current problem, so we avoid discussions
which are trying to solve different problems due to disagreement what
the problem is.

Richard Mortier has written down the current state, the problems and
what features we want.

Do you think this is a good description of the current state, current
problem and desirable features?