Re: [arch-dev-public] Windows Subsystem Linux - Arch Linux as official container?

2018-01-29 Thread Christian Rebischke via arch-dev-public
On Mon, Jan 29, 2018 at 03:09:16PM -0600, Public mailing list for Arch Linux development wrote: > On Mon, 29 Jan 2018 22:00:28 +0100 > Christian Rebischke via arch-dev-public wrote: > > > Hello everybody, > > I would like to start a discussion about Windows

Re: [arch-dev-public] Arch Linux Docker / Vagrant: Current situation

2018-01-29 Thread Santiago Torres-Arias via arch-dev-public
> > The official images projects info is on [1] and [2] if you want to read > > more in-depth/updated information. I'll summarize here though: > > > > 1) A TU/Arch Linux "affiliate" submits a PR to the official images > > repository, which basically contains the following: > > 1.

[arch-dev-public] Windows Subsystem Linux - Arch Linux as official container?

2018-01-29 Thread Christian Rebischke via arch-dev-public
Hello everybody, I would like to start a discussion about Windows Subsystem Linux and Arch linux. You all might know that Microsoft has increased their participation in open source software a lot since Satya Nadella is CEO of Microsoft. They even implemented a subsystem on Windows 10 for

[arch-dev-public] New devops member - Phillip Smith (fukawi2)

2018-01-29 Thread Florian Pritz via arch-dev-public
Hi, We have a new member joining the sysadmin/devops team by recommendation of Allan. I've already rolled out root and git access. Welcome Phillip, let's break stuff! (slightly) ;) Florian signature.asc Description: OpenPGP digital signature

Re: [arch-dev-public] Windows Subsystem Linux - Arch Linux as official container?

2018-01-29 Thread Doug Newgard via arch-dev-public
On Mon, 29 Jan 2018 22:00:28 +0100 Christian Rebischke via arch-dev-public wrote: > Hello everybody, > I would like to start a discussion about Windows Subsystem Linux and > Arch linux. You all might know that Microsoft has increased their > participation in open

Re: [arch-dev-public] Windows Subsystem Linux - Arch Linux as official container?

2018-01-29 Thread Bartłomiej Piotrowski via arch-dev-public
Whoa, this is so good to bash that I can't decide where to begin. Microsoft started noticing Linux (or rather stopped to fight it so valiantly) when they realized where the money is. On this ground alone I don't see a reason to help some corporation in putting our logo on their website so they

Re: [arch-dev-public] Windows Subsystem Linux - Arch Linux as official container?

2018-01-29 Thread Doug Newgard via arch-dev-public
On Mon, 29 Jan 2018 22:14:55 +0100 Christian Rebischke via arch-dev-public wrote: > On Mon, Jan 29, 2018 at 03:09:16PM -0600, Public mailing list for Arch Linux > development wrote: > > On Mon, 29 Jan 2018 22:00:28 +0100 > > Christian Rebischke via arch-dev-public

Re: [arch-dev-public] Windows Subsystem Linux - Arch Linux as official container?

2018-01-29 Thread Gaetan Bisson via arch-dev-public
[2018-01-29 22:00:28 +0100] Christian Rebischke via arch-dev-public: > They even implemented a subsystem on Windows 10 for executing natively > ELF binaries on Windows. This system is based on docker images and some > nice guys from Microsoft have asked Allan and me if Arch Linux would be >

Re: [arch-dev-public] New dbscripts maintainer (aka: Making dbscripts great again!)

2018-01-29 Thread Pierre Schmitz
Sure, I am not suggesting a rewrite; but when we do it a slightly different approach could be taken. Also to explain it further: Whether I or someone else is reviewing PRs I suggest a way how we could manage such major refactorings. ATM the diff between gbfs and our origin branch reads as: 80

Re: [arch-dev-public] New dbscripts maintainer (aka: Making dbscripts great again!)

2018-01-29 Thread Gaetan Bisson via arch-dev-public
[2018-01-29 16:51:54 +0100] Florian Pritz via arch-dev-public: > Eli offered to take the lead on getting that done and also later > migrating us to git instead of svn. If there are no objections I'll help > where necessary and give him access to the dbscripts and devtools repos > in two weeks.

[arch-dev-public] Abandoning nvidia 340xx packages - does anyone want them?

2018-01-29 Thread Sven-Hendrik Haase
I do not have any devices which require me to run nvidia 340xx packages and I haven't tested them for quite some time now. The most recent nvidia devices which require 340xx because the regular nvidia package dropped support for them are now 8-9 years old. I'm not really sure there is merit in

Re: [arch-dev-public] New dbscripts maintainer (aka: Making dbscripts great again!)

2018-01-29 Thread Eli Schwartz via arch-dev-public
On 01/29/2018 02:19 PM, Pierre Schmitz wrote: > Hi all. I feel bad about this. I was not transparent at all about my > plans and got lost in a pile of projects which are only slowly > progressing. I started improving dbscripts to make it easier to work > with; which led to creating a Docker base

Re: [arch-dev-public] Arch Linux Docker / Vagrant: Current situation

2018-01-29 Thread Pierre Schmitz
About the ISO bus factor: * I just recently put the whole process into a simple script to make it easier for anybody else to build ISOs. Unfortunately at least the signing process requires some manual work. See https://github.com/pierres/archiso-manager About the official Docker Image: * The

Re: [arch-dev-public] Arch Linux Docker / Vagrant: Current situation

2018-01-29 Thread Jelle van der Waa
On 01/29/18 at 12:31pm, Santiago Torres-Arias via arch-dev-public wrote: > Hi, > > Sorry I've been quite sick (to the point of barely having energy to look > at the computer). I'm back on my feet now though :) > > > > Sangy/Santiago[3] was so nice to speak with the docker guys. They said > > >

Re: [arch-dev-public] New dbscripts maintainer (aka: Making dbscripts great again!)

2018-01-29 Thread Eli Schwartz via arch-dev-public
On 01/29/2018 03:27 PM, Pierre Schmitz wrote: > Two possible strategies: > a) Gradual migration: It might not work out for some aspects, but > maybe there is way to prepare the current code to replace svn by git > and postpoing the actual switch to the very end. It's also a good > strategy to

Re: [arch-dev-public] Arch Linux Docker / Vagrant: Current situation

2018-01-29 Thread Santiago Torres-Arias via arch-dev-public
Hi, Sorry I've been quite sick (to the point of barely having energy to look at the computer). I'm back on my feet now though :) > > Sangy/Santiago[3] was so nice to speak with the docker guys. They said > > they would approve our docker image and we could move it to the other > > official

Re: [arch-dev-public] PSA: third-party gems have been split from 'ruby' package

2018-01-29 Thread Christian Rebischke via arch-dev-public
On Fri, Jan 26, 2018 at 04:36:32PM -0800, Public mailing list for Arch Linux development wrote: > Hello folks > > There been a packaging issue with 'ruby' package that annoyed me for a > while. The problem comes from the fact that ruby-lang.org source > tarballs contain ruby sources itself *and*

[arch-dev-public] New dbscripts maintainer (aka: Making dbscripts great again!)

2018-01-29 Thread Florian Pritz via arch-dev-public
Hi, Once again, debug repos came up in IRC. AFAIK progress on this is blocked by Pierre not responding/merging patches. gbs has implemented quite a lot in dbscripts itself, but we still need someone to come up with a migration plan, testing and deploying the whole thing. Eli offered to take the

Re: [arch-dev-public] PSA: third-party gems have been split from 'ruby' package

2018-01-29 Thread Anatol Pomozov via arch-dev-public
Hi Christian On Mon, Jan 29, 2018 at 9:36 AM, Christian Rebischke wrote: > On Fri, Jan 26, 2018 at 04:36:32PM -0800, Public mailing list for Arch Linux > development wrote: >> Hello folks >> >> There been a packaging issue with 'ruby' package that annoyed me for a

Re: [arch-dev-public] New dbscripts maintainer (aka: Making dbscripts great again!)

2018-01-29 Thread Pierre Schmitz
Hi all. I feel bad about this. I was not transparent at all about my plans and got lost in a pile of projects which are only slowly progressing. I started improving dbscripts to make it easier to work with; which led to creating a Docker base image to be able to test the latter. Most of my free