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

Away until 2024-08-12
by David Runge 30 Jul '24

30 Jul '24

Hi all, I'll be on holidays from tomorrow until 2024-08-12 and only sporadically read mails etc. Please feel free to bump/move packages I maintain. Have a good summer! :) Best, David -- https://sleepmap.de

1 0

Resignation
by Florian Pritz 28 Jul '24

28 Jul '24

Hi, Sadly I have no longer had the time necessary to properly handle master key holder and packager duties for a while now. I don't feel like it's fair to you guys and our users to keep this up any longer so I'm officially resigning now. Most pressing topics that come to mind for someone wanting to take over: * I hold a master key, so you'll need to find a new holder for that * perl 5.40 update * various bug reports on Gitlab for my packages * a few flagged packages Thanks for all the nice memories since "[2008-10-19 14:38] installed filesystem (2008.03-2)". While I will no longer be involved in Arch development, I'll still continue to use it and this nice, old install will also continue to live on. Hope to see you guys around :) Florian

5 4

libassuan 3.0.1-1 pulled from testing after crashing pacman
by David Runge 22 Jul '24

22 Jul '24

Hi all, please note that I have just pulled libassuan 3.0.1-1 from core-testing. In this patch-level release some major issues emerged, that break pacman: ``` pacman -Ss test pacman: /usr/lib/libassuan.so.9: version `LIBASSUAN_1.0' not found (required by /usr/lib/libgpgme.so.11) ``` Please note that if you have libassuan 3.0.1-1 installed, you may have to use an installation media or static pacman to get back to 3.0.0-1. I'm very sorry to have caused any inconvenience over this. I will contact upstream about this momentarily. Best, David -- https://sleepmap.de

1 0

Fwd: [PATCH v6] kbuild: add script and target to generate pacman package
by Jan Alexander Steffens (heftig) 16 Jul '24

16 Jul '24

Hi, recently there's been an effort to add a `pacman-pkg` target to the Linux kernel build system, which uses a PKGBUILD to build `linux-upstream` packages for Arch Linux. Since this is of interest to us, I'm forwarding the latest patch email to our list here to give you a chance to provide feedback to the author. I can see this making bisection of kernel issues (or just testing patches) much easier, especially for users. It's also quite an unusual way of calling makepkg. The email is also available at [lore.kernel.org](https://lore.kernel.org/linux-kbuild/20240716-kbuild-pacma…. Greetings, Jan PS: My apologies for sending this twice; the first email was sent with "Markdown" formatting in Evolution, which didn't quite do what I think it would. This one uses "Markdown as HTML", which should have both `text/plain` and `text/html` variants.

1 0

Fwd: [PATCH v6] kbuild: add script and target to generate pacman package
by Jan Alexander Steffens (heftig) 16 Jul '24

16 Jul '24

1 0

AUR Maintenance Saturday 13 July 12:00 UTC
by Jelle van der Waa 13 Jul '24

13 Jul '24

Hi all, We are having some performance issues with the AUR's git repository which requires some maintenance. [1] This means that the AUR will be unavailable for some time starting 12:00 UTC till it is done (hopefully 2 hours, could be more). [1] https://gitlab.archlinux.org/archlinux/infrastructure/-/issues/599

2 1

Urgent news draft: The sshd service needs to be restarted after upgrading to openssh-9.8p1
by Robin Candau 01 Jul '24

01 Jul '24

Hi everyone, As you might have heard by now (or experienced it already), the latest openssh-9.8p1 release requires the sshd daemon to be restarted otherwise new connections cannot establish (the one used to upgrade the package remains intact though). To prevent people from eventually blocking themselves out any further, we would like to introduce a `post_upgrade` transaction for the openssh-9.8p1 package which will restart the sshd service (a MR for that is being worked on [1]), accompanied by an urgent news entry (similarly to what was done for the openssh-8.2p1 release) [2]. Given the urgent aspect of the news, it would be nice to have some quick feedback if possible. I intend to post the news as soon as openssh-9.8p1-2 is released with the `post_upgrade` transaction. --------------- News draft: # The sshd service needs to be restarted after upgrading to openssh-9.8p1 After upgrading to openssh-9.8p1, the existing SSH daemon will be unable to accept new connections. (See https://gitlab.archlinux.org/archlinux/packaging/packages/openssh/-/issues/5) When upgrading remote hosts, please make sure to restart the SSH daemon using `systemctl restart sshd` right after upgrading. If you are upgrading to openssh-9.8p1-2 or higher, this restart will happen automatically. --------------- [1] https://gitlab.archlinux.org/archlinux/packaging/packages/openssh/-/issues/… [2] https://archlinux.org/news/sshd-needs-restarting-after-upgrading-to-openssh… -- Regards, Robin Candau / Antiz

2 2

Taking a break soon
by Orhun Parmaksiz 26 Jun '24

26 Jun '24

Hey! I will be taking a break from computers between the dates 29-06-2024 and 26-07-2024. During this period I won't have access to the internet so I will be pretty much unreachable. But if there is something hella urgent drop me a call on my cell - I might or might not call back. Let me know if there is anything (in the following days) and feel free to bump my packages. P.S. everything is fine, just need some time to reset :) Have a nice summer everyone!

2 1

glib2-devel split from glib2
by Jan Alexander Steffens (heftig) 11 Jun '24

11 Jun '24

Hi, Thanks to Fabian, as of 2.80.3-1, the development utilities requiring additional dependencies (*python*, *python-packaging*, *libelf*) have been split from *glib2* into *glib2-devel* with proper depends. You may need to add *glib2-devel* to the makedepends of your packages to get them to build again. At the same time, consider removing *python* or *python-packaging* from the makedepends if they were only added to run gdbus-codegen, glib-genmarshal or glib-mkenums. Greetings, Jan

1 0

pre-releases (for systemd & co) in core-testing
by Christian Hesse 08 Jun '24

08 Jun '24

Hello everybody, I used to push later pre-releases for essential core packages (for example systemd and util-linux) to core-testing. The idea was to have some extra testing even before building the final packages. For some time this worked quite well... Lately this broke, though. Our current tooling (pkgctl from devtools) builds packages (at least core ones) in core-testing. We then moved a package that was built with util-linux 2.40rc2. It's dynamic linking was ok, but it required the symbol MOUNT_2_40 from libmount.so, still breaking. We had to move the util-linux pre-release packages to core to solve this. Of course this had not been detected before, because packages in testing were ok in that combination. So wondering how to solve this, and have some extra testing anyway. The more people testing pre-release packages the better... Having said that - I have set up a custom repository for now with systemd 256rc2. To test that add these lines to your pacman.conf: [testing] Server = https://pkgbuild.com/~eworm/$repo/$arch/ Feedback welcome! -- 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 7