- Arch-general - lists.archlinux.org

Building in a clean chroot
by Pocket 05 May '25

05 May '25

I am getting this error when running is there a way to fix this? Using makechrootpkg -c -r "$CHROOT" -- --ignorearch --skippgpcheck works fine $ arch-nspawn $CHROOT/root pacman -Syy :: Synchronizing package databases... custom 11.5 KiB 261 KiB/s 00:00 [#############################################] 100% core.db failed to download extra 9.5 MiB 15.9 MiB/s 00:01 [#############################################] 100% alarm.db failed to download aur.db failed to download error: failed retrieving file 'aur.db' from mirror.archlinuxarm.org : The requested URL returned error: 404 error: failed retrieving file 'alarm.db' from mirror.archlinuxarm.org : The requested URL returned error: 404 error: failed retrieving file 'core.db' from mirror.archlinuxarm.org : The requested URL returned error: 404 warning: too many errors from mirror.archlinuxarm.org, skipping for the remainder of this transaction error: failed to synchronize all databases (failed to retrieve some files) -- Hindi madali ang maging ako

3 6

Refreshing pacman database
by Pocket 04 May '25

04 May '25

pacman -Syy refreshes all db for all repositories Is there a way to have pacman only refresh a single repository db? Ie pacman -Syy custom only refreshes custom withou refreshing core extra etc -- Hindi madali ang maging ako

2 1

Arrogant reply on forums
by Qtra Gabriex 03 May '25

03 May '25

Guy with 63,000+ forum posts replies arrogantly over me asking for actual deletion to be implemented. Brings up multiple tragedies. This upsets me because I once donated $20 to the Software in the Public Interest and wish for positivity and inclusion. https://bbs.archlinux.org/viewtopic.php?id=305290

12 13

Does redis returning to AGPL license effect the redis/valkey package replacement decision?
by David C Rankin 02 May '25

02 May '25

Devs, I was a bit surprised to see the following as the lead article on The Register daily stories for today: Redis 'returns' to open source with AGPL license https://www.theregister.com/2025/05/01/redis_returns_to_open_source/ After Arch's recent transition from redis to valkey due redis switching to the SSPLv1 license last year, does the decision by redis to relicense ver. 8 going forward under AGPL mean that redis will come back as a package or is Arch sticking with valkey? -- David C. Rankin, J.D.,P.E.

2 2

Re: Arch-general Digest, Vol 29, Issue 3
by Alessandra 02 May '25

02 May '25

Hi, I am weighing in as a user. Sure community spirit is important but someone already said it, please don't use historical events that affected millions of people as a comparison for an issue you are having that's not really impeding on your ability to staying alive. Milk was spilled, share the link to the post, we can all weigh in collectively whether it is a matter the community should investigate further or leave it. Thank you to anyone that spend time, modding, contributing to packages and thats answered my questions in post or on Reddit ! Cheerio! 2025-05-02T08:06:06Z arch-general-request(a)lists.archlinux.org: > Send Arch-general mailing list submissions to > arch-general(a)lists.archlinux.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > arch-general-request(a)lists.archlinux.org > > You can reach the person managing the list at > arch-general-owner(a)lists.archlinux.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Arch-general digest..." > > Today's Topics: > > 1. Re: Arrogant reply on forums (LuKaRo) > 2. Re: Arrogant reply on forums (Óscar García Amor) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 2 May 2025 09:46:21 +0200 > From: LuKaRo <lists(a)lrose.de> > Subject: Re: Arrogant reply on forums > To: arch-general(a)lists.archlinux.org > Message-ID: <a18f92b5-4050-4f7f-b953-9f37dc907549(a)lrose.de> > Content-Type: multipart/alternative; > boundary="------------0zPYycE2iWyI60ADO9wAssk9" > > Out of curiosity: Is it? I couldn't find a source, where the purpose of > arch-general is defined, but I thought it is for "general Arch Linux > stuff", which includes community topics for me. > > lukaro > > On 5/2/25 6:00 AM, Martin Zecher wrote: >> Please stop spamming our emails, this is for technical stuff. You can >> freely discuss about human rights and whatever you want somewhere else. >> >> >> ==== >> Martin Zecher >> >> El jue, 1 may 2025, 22:55, Ralf Mardorf <ralf-mardorf(a)riseup.net> >> escribió: >> >> On Fri, 2025-05-02 at 00:51 +0200, Camelia Lavender wrote: >> > I think that the direct reference and comparison to hitler and >> nazism >> > (in the reply) was completely inappropriate and quite frankly >> > unacceptable, because it is antisemitic, and it makes it look like >> > those things weren't extremely serious. >> >> The accusation of anti-Semitism does not make sense. A comparison with >> Hitler and the NAZIS is inappropriate in most cases, but not >> automatically anti-Semitic. There is currently a world situation in >> which diplomacy should be practiced and insinuations of anti-Semitism >> should be treated with great caution. Labeling unpopular >> worldviews and >> questionable opinions as anti-Semitic per se does not help in any way. >> You don't necessarily have to go one better. Please stop! >>

1 0

Would it be possible to include sdl3-freerdp3 in the freerdp package?
by Mathieu Lemoine 28 Apr '25

28 Apr '25

Hello, I have been using the sdl-freerdp3 for a few months now (with the wayland driver), as it works better than the wlfreerdp3 client. Lately I've started to see messages saying sdl-freerdp3 (the SDL2 client) is now deprecated and we should switch over to the SDL3 client (sdl3-freerdp, or I guess sdl3-freerdp3). But it's not currently included in the package. What would be the best way to reach out to the package maintainer so this gets included? https://archlinux.org/packages/extra/x86_64/freerdp/flag/ seems like the wrong place, registrations on the GitLab are closed because of SPAM, and I couldn't find an email for the package Maintainers. So I'm basically left with the general ML. Apologies if this is not the right place to ask about this.

2 1

Replaced redis with valkey and nextcloud broke?
by David C Rankin 27 Apr '25

27 Apr '25

All, I replaced redis with valkey tonight on a long-running nextcloud install. I followed the wiki pages exactly: https://wiki.archlinux.org/title/Valkey (I set all options as shown to suppress warnings) and https://wiki.archlinux.org/title/Nextcloud#Valkey_(Redis) (valkey is running on unixsockets per the wiki) However, upon starting/enabling valkey and restarting apache, attempting to reach nextcloud results in: <quote> Internal Server Error The server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the server log. </quote> git, http and nextcloud were added to the valkey group: $ grep valkey /etc/group valkey:x:971:git,http,nextcloud valkey is up and happily running and the socket has 0770 permissions per the wiki: $ scs valkey ● valkey.service - Advanced key-value store Loaded: loaded (/usr/lib/systemd/system/valkey.service; enabled; preset: 5:185mdisabled) Active: active (running) since Sat 2025-04-26 21:09:31 CDT; 17min ago Invocation: 5dc6c28081374c00837d5f7f94c38a95 Main PID: 1913 (valkey-server) Status: "Ready to accept connections" Tasks: 6 (limit: 4575) Memory: 3.4M (peak: 3.9M) CPU: 1.100s CGroup: /system.slice/valkey.service └─1913 "/usr/bin/valkey-server 127.0.0.1:6379" Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * Running mode=standalone, port=6379. Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * Server initialized Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * Loading RDB produced by Valkey version 8.1.1 Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * RDB age 784 seconds Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * RDB memory usage when created 0.85 Mb Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * Done loading RDB, keys loaded: 0, keys expired: 0. Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * DB loaded from disk: 0.000 seconds Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * Ready to accept connections tcp Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * Ready to accept connections unix Apr 26 21:09:31 2pi systemd[1]: Started Advanced key-value store. $ l /run/valkey/ total 0 drwxr-xr-x 2 valkey valkey 60 Apr 26 21:09 . drwxr-xr-x 46 root root 1100 Apr 26 21:09 .. srwxrwx--- 1 valkey valkey 0 Apr 26 21:09 valkey.sock The config.php was updated per the wiki to use valkey: $ sudo tail /etc/webapps/nextcloud/config/config.php 'filelocking.enabled' => true, 'memcache.distributed' => '\\OC\\Memcache\\Redis', 'memcache.locking' => '\\OC\\Memcache\\Redis', 'redis' => array ( 'host' => '/run/valkey/valkey.sock', 'port' => 0, 'timeout' => 0.0, ), ); Attempting to access the nextcloud instance results in 6 messages in nextcloud.log (they repeat each time nextcloud does its cron update). I've summarized each in pretty-print so they are readable: 1. { "reqId": "Ga2ygrBvnNRsfUk5PSik", "level": 4, "time": "2025-04-27T01:34:11+00:00", "remoteAddr": "192.168.6.196", "user": false, "app": "app_api", "method": "GET", "url": "/nextcloud/login", "message": "Error during app service registration: Permission denied", ... "File": "/usr/share/webapps/nextcloud/lib/private/RedisFactory.php", "Line": 104, "message": "Error during app service registration: Permission denied", "exception": {}, "CustomMessage": "Error during app service registration: Permission denied" } } 2. { "reqId": "Ga2ygrBvnNRsfUk5PSik", "level": 4, "time": "2025-04-27T01:34:11+00:00", "remoteAddr": "192.168.6.196", "user": false, "app": "no app in context", "method": "GET", "url": "/nextcloud/login", "message": "Could not boot webhook_listeners: Redis server went away", ... "File": "/usr/share/webapps/nextcloud/lib/private/Memcache/Redis.php", "Line": 59, "message": "Could not boot webhook_listeners: Redis server went away", "exception": {}, "CustomMessage": "Could not boot webhook_listeners: Redis server went away" } } 3. { "reqId": "Ga2ygrBvnNRsfUk5PSik", "level": 4, "time": "2025-04-27T01:34:11+00:00", "remoteAddr": "192.168.6.196", "user": false, "app": "no app in context", "method": "GET", "url": "/nextcloud/login", "message": "Could not boot workflowengine: Redis server went away", ... "File": "/usr/share/webapps/nextcloud/lib/private/Memcache/Redis.php", "Line": 59, "message": "Could not boot workflowengine: Redis server went away", "exception": {}, "CustomMessage": "Could not boot workflowengine: Redis server went away" } } 4. { "reqId": "Ga2ygrBvnNRsfUk5PSik", "level": 3, "time": "2025-04-27T01:34:11+00:00", "remoteAddr": "192.168.6.196", "user": false, "app": "index", "method": "GET", "url": "/nextcloud/login", "message": "Redis server went away", ... "File": "/usr/share/webapps/nextcloud/lib/private/Memcache/Redis.php", "Line": 59, "message": "Redis server went away", "exception": {}, "CustomMessage": "Redis server went away" } } 5. { "reqId": "Ga2ygrBvnNRsfUk5PSik", "level": 3, "time": "2025-04-27T01:34:11+00:00", "remoteAddr": "192.168.6.196", "user": false, "app": "core", "method": "GET", "url": "/nextcloud/login", "message": "Redis server went away", ... "File": "/usr/share/webapps/nextcloud/lib/private/Memcache/Redis.php", "Line": 59, "message": "Redis server went away", "exception": {}, "CustomMessage": "Redis server went away" } } 6. { "reqId": "Ga2ygrBvnNRsfUk5PSik", "level": 3, "time": "2025-04-27T01:34:11+00:00", "remoteAddr": "192.168.6.196", "user": false, "app": "core", "method": "GET", "url": "/nextcloud/login", "message": "Redis server went away", ... "File": "/usr/share/webapps/nextcloud/lib/private/Memcache/Redis.php", "Line": 59, "message": "Redis server went away", "exception": {}, "CustomMessage": "Redis server went away" } } This has me baffled. Both the valkey(redis) and nextcloud wiki changes make logical sense and seem like that should result in a painless upgrade. I was not so lucky. Is there something else needed to switch nextcloud from redis to valkey? 1. I stopped/disabled redis. 2. Installed valkey removing redis 3. Updated all configs per both wikis 4. started/enabled valkey (all good) 5. restarted httpd (all good) 6. attempted to access nextcloud (failed with the error above) Anybody have any ideas how I can get nextcloud back up and running with valkey? Worst case I'll try disableing redis/valkey altogether in the nextcloud config and run without caching -- not optimal. It was running perfectly with redis before the upgrade, so I'm stuck. -- David C. Rankin, J.D.,P.E.

1 1

Notice that flashed on wiki access today - too fast to read - was it important?
by David C Rankin 27 Apr '25

27 Apr '25

Arch Devs, On access of https://wiki.archlinux.org today, a dialog flashed to the screen immediately before the wiki main page was rendered, but the dialog flashed too quickly to read. Was it important or require any action? May have just been a wiki update note, dark mode looks a bit different? -- David C. Rankin, J.D.,P.E.

8 12

Journal log entries while installing an ISO image
by Friedrich Romstedt 23 Apr '25

23 Apr '25

Hi, Yesterday I prepared an USB stick with the recent version of the Arch Linux installation medium (Release 2025-04-01). This is about some error entries in the system journal, which I encountered during copying this ISO image over. The respective transcripts are provided inline, as well as attached in the form of plain text files. I used initially $ sudo cp <ISO> /dev/sda. After having finished that process, I spotted some error log entries in the system journal: Apr 20 15:30:25 T470p sudo[21475]: friedrich : TTY=pts/2 ; PWD=/home/friedrich/(...) ; USER=root ; COMMAND=/usr/bin/cp archlinux-2025.04.01-x86_64.iso /dev/sda Apr 20 15:30:25 T470p sudo[21475]: pam_unix(sudo:session): session opened for user root(uid=0) by friedrich(uid=1000) Apr 20 15:33:10 T470p systemd[1]: systemd-udevd.service: Watchdog timeout (limit 3min)! Apr 20 15:33:10 T470p systemd[1]: systemd-udevd.service: Killing process 359 (systemd-udevd) with signal SIGABRT. Apr 20 15:34:40 T470p systemd[1]: systemd-udevd.service: State 'stop-watchdog' timed out. Killing. Apr 20 15:34:40 T470p systemd[1]: systemd-udevd.service: Killing process 359 (systemd-udevd) with signal SIGKILL. Apr 20 15:36:10 T470p systemd[1]: systemd-udevd.service: Processes still around after SIGKILL. Ignoring. Apr 20 15:37:38 T470p kernel: sda: sda1 sda2 Apr 20 15:37:38 T470p sudo[21475]: pam_unix(sudo:session): session closed for user root Apr 20 15:37:38 T470p systemd[1]: systemd-udevd.service: Main process exited, code=killed, status=9/KILL Apr 20 15:37:38 T470p systemd[1]: systemd-udevd.service: Failed with result 'watchdog'. Apr 20 15:37:38 T470p systemd[1]: systemd-udevd.service: Consumed 4.845s CPU time, 51.6M memory peak. Apr 20 15:37:38 T470p systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 1. Apr 20 15:37:38 T470p systemd[1]: Starting Rule-based Manager for Device Events and Files... Apr 20 15:37:39 T470p systemd-udevd[21582]: Using default interface naming scheme 'v257'. Apr 20 15:37:39 T470p systemd[1]: Started Rule-based Manager for Device Events and Files. Apr 20 15:38:19 T470p kernel: usb 1-1: USB disconnect, device number 7 Because I had doubts about the integrity of the thus prepared USB stick, I repeated the process, this time using $ su - and # dd if=<ISO> of=/dev/sda bs=8M. Here, I encountered similar logs: Apr 20 15:38:53 T470p kernel: sda: sda1 sda2 Apr 20 15:38:53 T470p kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Apr 20 15:39:07 T470p su[21650]: (to root) friedrich on pts/2 Apr 20 15:39:07 T470p su[21650]: pam_unix(su:session): session opened for user root(uid=0) by friedrich(uid=1000) Apr 20 15:44:05 T470p systemd[1]: systemd-udevd.service: Watchdog timeout (limit 3min)! Apr 20 15:44:05 T470p systemd[1]: systemd-udevd.service: Killing process 21582 (systemd-udevd) with signal SIGABRT. Apr 20 15:45:35 T470p systemd[1]: systemd-udevd.service: State 'stop-watchdog' timed out. Killing. Apr 20 15:45:35 T470p systemd[1]: systemd-udevd.service: Killing process 21582 (systemd-udevd) with signal SIGKILL. Apr 20 15:47:05 T470p systemd[1]: systemd-udevd.service: Processes still around after SIGKILL. Ignoring. Apr 20 15:48:35 T470p systemd[1]: systemd-udevd.service: State 'final-sigterm' timed out. Killing. Apr 20 15:48:35 T470p systemd[1]: systemd-udevd.service: Killing process 21582 (systemd-udevd) with signal SIGKILL. Apr 20 15:48:56 T470p kernel: sda: sda1 sda2 Apr 20 15:48:56 T470p systemd[1]: systemd-udevd.service: Main process exited, code=killed, status=9/KILL Apr 20 15:48:56 T470p systemd[1]: systemd-udevd.service: Failed with result 'watchdog'. Apr 20 15:48:56 T470p systemd[1]: systemd-udevd.service: Consumed 1.101s CPU time, 7.4M memory peak. Apr 20 15:48:56 T470p systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 2. Apr 20 15:48:56 T470p systemd[1]: Starting Rule-based Manager for Device Events and Files... Apr 20 15:48:56 T470p systemd-udevd[21808]: Using default interface naming scheme 'v257'. Apr 20 15:48:56 T470p systemd[1]: Started Rule-based Manager for Device Events and Files. Apr 20 15:49:13 T470p kernel: usb 1-1: USB disconnect, device number 8 In the second run, where I kept an eye on the journal, I noticed that the error entries were logged a few minutes *before* the copying process completed. There were no errors reported by both of these directly. The pen drive is booting and working just fine. However, I felt this behaviour being worth it to be reported. Maybe someone else can make sense of it. Best, Friedrich

4 7

Building with cmake
by Pocket 21 Apr '25

21 Apr '25

I am building packages following DeveloperWiki:Building in a clean chroot When building packages that are associated with gnome I get the following error: CMake Error at wsrep-lib/CMakeLists.txt:5 (cmake_minimum_required): Compatibility with CMake < 3.5 has been removed from CMake. Update the VERSION argument <min> value. Or, use the <min>...<max> syntax to tell CMake that the project requires at least <min> but has been updated to work with policies introduced by <max> or earlier. Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway. Adding export CMAKE_POLICY_VERSION_MINIMUM=3.5 doesn't correct my problem. Is there another way to get past this without adding -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to the PKGBUILD? -- Hindi madali ang maging ako

2 2