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

[arch-dev-public] Urgent news item: sshd needs restarting after upgrading to openssh-8.2p1
by Gaetan Bisson 17 Feb '20

17 Feb '20

Dear all, I'd like to post the following news item within the hour. ======== Title: sshd needs restarting after upgrading to openssh-8.2p1 Conent: After upgrading to openssh-8.2p1, the existing SSH daemon will be unable to accept new connections. When upgrading remote hosts, please make sure to restart the SSH daemon using `systemctl restart sshd` right after `pacman -Syu`. ======== I deeply regret not spotting this while the package was in [testing]. And I also regret not being able to diagnose what the exact problem is just now. Given time is of the essence, I propose posting the above news quickly even I don't consider it a very satisfying solution... Cheers. -- Gaetan

3 8

[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