January 2018 - Arch-dev-public - lists.archlinux.org

[arch-dev-public] Improving overall experience for contributors
by Bartłomiej Piotrowski 06 Feb '19

06 Feb '19

Hi all, Spending some time outside the regular Arch circles, I realized that the way we "outreach" potential contributors is at least imperfect. One of the problems I keep hearing about is that there is no clear place where potential contributors could start. Sure, some things seem obvious to us: take care of some wiki article or adopt orphan AUR packages. It isn't actually that easy. Not everyone is interested in editing or maintaining random packages, and while there is plenty to do, how someone new could know it? We could use help not only with existing projects like archweb, pyalpm or namcap, but also with development of new code (for example a maintainable rebuild automation) and infrastructure side (which is in fact too generic term that could be better described). I am totally in love with What can I do for Mozilla?[1] which is open source, so why not steal this wonderful idea? But it also means we need a way to communicate with people interested in helping us: at least an IRC channel and new mailing list. Another thing that I heard in last few months isthat it is actually hard for potential TU candidates to find a sponsor. While I believe it is perfectly fine to e-mail few potential sponsors to ask for opinion, throwing random messages at people doesn't sound really appealing. In my humble opinion, we should rethink the way we recruit people and probably introduce fine-grained permissions to dbscripts that would allow to limit new maintainers to limited set of packages. We should also lower our expectations towards candidates. At least once we rejected one for some stupid reason (no fingerpointing here, I'm not saint either), leaving packages they wanted to adopt virtually orphan. It's better to help amn inexperienced packager gain experience than voting no, really; to be brutally honest, quite a lot of packaging work we are handling doesn't have much in common with rocket science. I also wanted to touch mailing lists vs GitHub vs Gitlab topic but we will tackle it another time. Your thoughts? Bartłomiej [1] https://whatcanidoformozilla.org/

8 11

[arch-dev-public] New build server in Singapore
by Bartłomiej Piotrowski 04 Apr '18

04 Apr '18

Hi all, for those of you that are living closer to Asia than Europe, there is new build server available, located in Singapore. It is considerably less beefy than soyuz, but should be okay for regular builds. All packagers should be able to ssh into it with username and the key used on other servers. The address is sgp.pkgbuild.com. You can compare fingerprints below: SHA256:f9VrDpIpOHvgWk+OXXRG+VMvJlbs577YFZfyxPtXKqU (ED25519) SHA256:fDdeGInsD764tfnGCbNIPH69L4k7mNs98ttFpTOv01U (RSA) SHA256:MsoXUmTXowWcPb4gma3U60Po0/5sTT5Fg+oM8bWIIUE (ECDSA) It also hosts a mirror available at https://sgp.mirror.pkgbuild.com Enjoy, Bartłomiej

3 4

[arch-dev-public] Arch Linux Docker / Vagrant: Current situation
by Christian Rebischke 12 Mar '18

12 Mar '18

Hello Everybody, It's now over a half year ago that I've started working together with sangy and pierre on our vagrant and docker images. I would like to give you a short update on this topic. The Arch Linux Vagrant images are currently be build for libvirt and virtualbox. We have over 3800 downloads at the moment and slowly catching up to the community based arch linux vagrant images.[1] My first goal has been to add some hypervisors, but due to the fact that we have only libvirt and virtualbox in our repositories I have dismissed this plan. The automated build process works fine so far (except some issues with qemu[2] and the dependency on punctual iso releases on soyuz. The latter should we definitly fix. Currently the iso images are build manually. Can we automate this somehow? I really rely on punctual releases otherwise the automated build will fail and somebody needs to trigger the build again manually. Happened about 1-2 times..) The other topic is the docker image. Has anybody of you contact to pierre? He doesn't answer my mails and he is the only one with access to the repository on github. 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 images[4]. But for this we need to do some changes on our docker repository on github. (As long I understood sangy correct it would be just some new branches). best regards, chris / shibumi [1] https://app.vagrantup.com/archlinux/boxes/archlinux [2] https://github.com/hashicorp/packer/issues/5769 [3] https://www.archlinux.org/people/support-staff/#sangy [4] https://hub.docker.com/explore/

7 19

[arch-dev-public] Windows Subsystem Linux - Arch Linux as official container?
by Christian Rebischke 07 Mar '18

07 Mar '18

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 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 interested to participate in this project. The steps for getting into the project are: * Signup in the Microsoft Appstore (we would get a free voucher if we want to participate) as Organization (we need the ok from one of our trademark holders for this step) * modifying our docker container a little bit * pushing it into the microsoft appstore So what do you think? Should we participate in that project? Here are some pros and contras: pro: - CentOS and Ubuntu are there too - Would be a nice chance to increase the awareness about Arch Linux - might get people to change from Windows to Arch Linux (or linux in general) - Nice way to test our docker image in production - People who are forced to work on windows at work can use Arch Linux at work as well - More bugreports / feedback / forum activity? contras: - Microsoft is Microsoft (I think I don't need to explain) - More Newbies? - Somebody would need to maintain it (I would do it) - If Arch Linux partnerships with Microsoft could lead into bad image? I would like to hear as much feedback as possible. So don't be shy :) I want to give feedback to the microsoft guys in round about 1 week. I guess that should be enough to dicuss this topic. So deadline is 2018-02-7 -- Chris

8 11

[arch-dev-public] PSA: third-party gems have been split from 'ruby' package
by Anatol Pomozov 02 Mar '18

02 Mar '18

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* some third party packages from rubygems.org. The third-party gems shipped by 'ruby' tarball are: minitest, net-telnet, did_you_mean, power_assert, rake, test-unit, xmlrpc, rdoc. Currently we repack these gems and ship it as a part of ruby Arch package. Because gems are bundled with ruby package we have no way to update gems separately. All we can do is to wait until ruby developers update their bundle and release it. The plan is to split these gems from 'ruby' package and install it independently from what ruby developers bundle. Upcoming ruby changes do that - ruby-2.5.0-4 will not include any of the third-party gems mentioned above. Two popular packages - rake and rdoc will get Arch packages (ruby-rake and ruby-rdoc respectively). Other gems need to be installed either from AUR or from gem.

2 3

[arch-dev-public] New dbscripts maintainer (aka: Making dbscripts great again!)
by Florian Pritz 12 Feb '18

12 Feb '18

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 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. I'm also CC'ing Pierre and gbs so they can jump in if necessary. Florian

4 6

[arch-dev-public] Abandoning nvidia 340xx packages - does anyone want them?
by Sven-Hendrik Haase 31 Jan '18

31 Jan '18

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 maintaining these so unless anyone wants them I'll drop them to AUR in two weeks.

3 4

[arch-dev-public] New devops member - Phillip Smith (fukawi2)
by Florian Pritz 29 Jan '18

29 Jan '18

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

1 0

Re: [arch-dev-public] New dbscripts maintainer (aka: Making dbscripts great again!)
by Florian Pritz 29 Jan '18

29 Jan '18

On 29.01.2018 16:57, Bruno Pagani wrote: > Le 29/01/2018 à 16:51, Florian Pritz via arch-dev-public a écrit : >> I'm also CC'ing Pierre and gbs so they can jump in if necessary. > > Did you forgot to add them or they were in CC/I/? ;) They were, but it seems mailman removed it. Probably because they are both subscribed to the list. Thanks for checking. Florian

1 0

[arch-dev-public] Introducing python-imdby while dropping imdbpy
by David Runge 17 Jan '18

17 Jan '18

Hey all, I am deleting imdbpy (legacy python) and introduce python-imdbpy (python 3.x) instead. Upstream switched to the current python some time last year and dropped support for python 2.x. Best, David -- https://sleepmap.de

1 0