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

[arch-dev-public] Archweb update
by Jelle van der Waa 13 Feb '20

13 Feb '20

Hi, A new archweb has been deployed with the following notable changes: * Implement planet functionality for archweb, to replace planet.archlinux.org which is Python 2 and not going to be ported. Every user on archweb can configure the website and website_rss urls in their profile which will be shown on planet after a systemd service pulls the RSS feeds in. [1] [2] Note that the implementation is a bit different from a normal planet, since only a limited amount of text is saved in archweb and the HTML is "purified" using python-bleach. It is mostly aimed at aggregating our feeds. * Add new RSS feeds for stable / non stable repos [3] Note that soon planet.archlinux.org will point to archweb and the old planet will die. [1] https://www.archlinux.org/devel/profile/ [2] https://www.archlinux.org/planet/ [3] https://www.archlinux.org/feeds/

1 0

[arch-dev-public] Making package signing keys available in our WKD
by Jonas Witschel 04 Feb '20

04 Feb '20

Hi everybody, since version 5.2 pacman supports downloading the package signing keys from our newly implemented Web Key Directory (WKD) [1]. Since the key server network that we are currently relying on for this purpose is not in a very healthy state any more [2], it seems like a good time to store all PGP keys in our WKD to be independent of the key servers. This will require an update of some the existing keys: keys in the WKD are looked up by email address, so you need to have an user ID with an @archlinux.org email address on your PGP key to make use of our existing WKD (or set up a WKD on your own server in case you are using a custom domain for your email address). I you don't have an @archlinux.org email address yet, you can talk to the Devops team e.g. using the #archlinux-devops IRC channel to get on set up. To see if your key is already in our WKD, please visit [3]. If all three columns are green, you are all set, otherwise you need to take one of the following actions: - If the "Has @archlinux.org UID" column is "No", you need to add an additional UID to your PGP key: $ gpg --edit-key YOURKEY adduid save $ gpg --send-keys YOURKEY - If the "Uses @archlinux.org email for packaging" column is "No", you need to set the PACKAGER variable in your makepkg.conf to use your (newly created) @archlinux.org UID. Please double-check the configuration of all the machines you use to build packages since the packager email address is used for the key lookup in pacman. - If the "@archlinux.org UID is fully trusted" column is "No", your key already has the required format, but the UID needs to be signed by at least three master key holders. You do not need to do anything right now (apart from maybe changing the PACKAGER variable as described in the previous bullet point). In order to make it easier for the master key holders to sign all the new UIDs, it would be great if everybody could add the new UID to their key within the next two months. I will then collect all the new and currently untrusted UIDs and submit them to the key holders for batch signing. If there are any questions on adding the new UID or adjusting the packager variable, please do not hesitate to contact me. Cheers, Jonas [1] https://bugs.archlinux.org/task/63171 [2] https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f [3] https://wiki.archlinux.org/index.php/User:Diabonas/WKD_support_by_developer…

1 0

[arch-dev-public] Replacing bzr with breezy
by Maxime Gauduin 04 Feb '20

04 Feb '20

Hi folks, As you may know bzr is python2 only, and most distros [0] [1] are switching over to a drop-in replacement fork named breezy [2]. The latest version just added python 3.8 support, so I pushed a package to [extra] [3]. I propose we add a symlink from bzr to brz in the breezy package, and conflict with/replace the bzr package so we can drop bzr, bzr- fastimport and python2-fastimport (fastimport is built in breezy) and leave in a world with three less python2 packages. Any objection? [0] https://fedoraproject.org/wiki/Changes/ReplaceBazaarWithBreezy [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883146 [2] https://www.breezy-vcs.org/ [3] https://www.archlinux.org/packages/extra/x86_64/breezy/ Cheers, -- Maxime

2 2

[arch-dev-public] mailman3/hyperkitty/postorius in the repos now
by David Runge 03 Feb '20

03 Feb '20

Hey all! I'm just on my way home from FOSDEM - train time, mail time ;-) I've spent the last weeks bringing the mailman3 ecosystem(!) to [community] and [community-testing] (~56 packages). Today I've added wiki pages for mailman3 [1] (it will replace the current mailman page once it's done by moving that to be 'mailman2' and eventually deleting it), hyperkitty [2] and postorius [3]. I've done initial integration tests with mailman3, hyperkitty and postorius and they "should just work"(TM). Before moving all the stuff to [community] and replacing the wiki page, it would be great to get some further integration testing with actual mail servers (note the expansion macro [4] in the mailman article) and importing of mailman2 data [5] [6] going. Any help is very much appreciated, as the switch requires quite the data migration and configuration changes for e.g. our own lists (the archives of some of them are pretty large). Additionally, the hosting aspects of both Hyperkitty and Postorius need some expansion as well (e.g. for Apache setups and for proper subdomain setups). Everyone, feel invited to install and test the applications and propose fixes and expansions to the documentation (or packages) as needed. Best, David [1] https://wiki.archlinux.org/index.php/User:Davezerave/Mailman [2] https://wiki.archlinux.org/index.php/Hyperkitty [3] https://wiki.archlinux.org/index.php/Postorius [4] https://wiki.archlinux.org/index.php/User:Davezerave/Mailman#Integrate_with… [5] https://wiki.archlinux.org/index.php/User:Davezerave/Mailman#Migrate_from_m… [6] https://wiki.archlinux.org/index.php/Hyperkitty#Importing_mailman2_archives -- https://sleepmap.de

3 3

[arch-dev-public] Absent until next week
by Eli Schwartz 27 Jan '20

27 Jan '20

Due to a family wedding, I will be gone for a week, until late Monday Feb. 3 or Tuesday Feb. 4. I won't have internet other than limited mobile data, but can still be contacted via email/IRC, which I shall check semi-regularly. Sorry for the late notice. :) Feel free to update anything that needs updating while I'm gone. -- Eli Schwartz Bug Wrangler and Trusted User

1 0

[arch-dev-public] Package openvpn in [core]?
by Christian Hesse 27 Jan '20

27 Jan '20

Hello everybody, currently the package openvpn is located in our [core] repository and it's like that since the beginning of time. [0] Following a discussion on IRC and our definition for official repositories [1] we think there is no reason to have it there. Thus I would like to move it (and its dependency pkcs11-helper) to [extra]. If you have any concern please raise your hand now! [0] https://git.archlinux.org/svntogit/packages.git/commit/?h=packages/openvpn&… [1] https://wiki.archlinux.org/index.php/Official_repositories#core -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}

3 3

[arch-dev-public] FOSDEM Dinner 2020
by Morten Linderud 21 Jan '20

21 Jan '20

Yo! Last year at FOSDEM we held a dinner with 15 people, some members from the Arch team and some users that wanted to join. It was a great event and people had a nice dinner with some nice chats afterwards on various pubs. For this year I plan to do the same with some changes. First of all, we are going to be holding it on saturday around 18:00 - 19:00 as opposed to friday. This is to ensure people are able to arrive friday evening, AND keep their phones after their dinner. I'm still looking for mine :/ To make it managable I'll cap the attendees to around 15 people. Priority for members of the Arch team (developers, trusted users and support staff). Any free spots after this can be taken by anyone interested :). Send an email *offlist* so I have some ability to keep track and inform you about further booking details. The users requesting spots will get a headsup the week before FOSDEM to give all staff a chance to reply. Please ask me if you have any questions :) --- I have again CC'ed arch-dev-public since I don't actually know how many people watch arch-events (hinthint subscribe!). Sorry for the noise, and please do tell me if we are better off not cross-posting emails like these :) -- Morten Linderud PGP: 9C02FF419FECBE16

2 3

[arch-dev-public] rsync & bundled zlib
by Christian Hesse 16 Jan '20

16 Jan '20

Hello everybody, to date we ship rsync with bundled zlib to keep compatibility with rsync up to version 3.1.0 and it's old-style --compress option. This is no longer required with rsync 3.1.1, which was released on 2014-06-22 - nearly six years ago! The bundled zlib carries some security issues, so time to act - one way or another. Even old-stable Debian Jessie [0] has rsync version 3.1.1. So any concern to finally drop bundled zlib and use system zlib? I would suggest to post a news item, feel free to give thoughts and feedback. --- >8 --- rsync compatibility Our `rsync` package was shipped with bundled `zlib` to provide compatibility with old-style `--compress` option up to version 3.1.0. Version 3.1.1 was released on 2014-06-22 and is shipped by all major distributions now. So we decided to finally drop the bundled library and ship a package with system `zlib`. Go and blame those running old versions if you encounter errors with `rsync 3.1.3-3`. --- >8 --- [0] https://packages.debian.org/de/jessie/rsync -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}

4 5

[arch-dev-public] Guidelines for news posting
by Sven-Hendrik Haase 16 Jan '20

16 Jan '20

Hi all, in light of recent events, we had a little get-together in #archlinux-staff to hack on an initial suggestion on guidelines for news posting. If we can agree on these, they should be added on the news posting page on archweb (and perhaps somewhere on the wiki). The draft we came up with is this: Every news post needs to have a corresponding draft submitted to arch-dev-public and wait for feedback for at least 24 hours unless: 1. it is urgent (and would be too late after 24 hours) 2. it is a simple --overwrite rule, or 3. there are strong reasons for the team member posting the draft to believe that it should not be visible to the public before it is announced. In this third case, the draft should be submitted to the staff(a)lists.archlinux.org ML instead. Happy to hear about feedback. Cheers, Sven

2 3

[arch-dev-public] Todos for language specific rebuilds
by Christian Rebischke 13 Jan '20

13 Jan '20

Hi everybody, I would like to propose that we create todos for rebuilds of language specific packages. We had two major rebuilds in the last months: python3.8 and ruby2.7. Can we agree that we create a todo before such rebuilds? The advantages outweigh the disadvantages. We would gain: * More people help rebuilding the packages. * Every maintainer gets informed about the rebuild. * Maintainers have the possibility to test the packages. If tools exist for creating todos, I would like to ask the persons with such tools to make them available for everybody (if not already happened). Greetings, shibumi

6 7