December 2023 - Arch-general - lists.archlinux.org

What is the plan for dhcpd/kea?
by David C. Rankin 20 Dec '23

20 Dec '23

Devs, With ISC dhcpd now mature and frozen (end of life, but ISC will continue to make available on gitlab and if necessary provide bug fixes), the new ISC offering is Kea that is its successor to dhcpd. The wiki notes the successor in the first paragraph https://wiki.archlinux.org/title/Dhcpd but there is no Kea page and no indication if Arch will start packaging Kea. For those of us with long standing ISC bind/dhcpd setups what does the future look like on Arch? Will there be a Kea at some point? -- David C. Rankin, J.D.,P.E.

4 6

Potential conflict with icu package?
by WinFan3672 17 Dec '23

17 Dec '23

Dear all, I was recently performing my system's scheduled maintenance and went to upgrade my packages, as you do. When I attempted to do so, this happened: |$ sudo pacman -Syu [sudo] password for winfan3672: :: Synchronizing package databases... ... :: Starting full system upgrade... resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: unable to satisfy dependency 'libicuuc.so =73-64' required by freerdp :: installing icu (74.2-1) breaks dependency 'libicuuc.so=73-64' required by brltty :: installing icu (74.2-1) breaks dependency 'libicuuc.so=73-64' required by gspell :: installing icu (74.2-1) breaks dependency 'libicuuc.so=73-64' required by harfbuzz-icu :: installing icu (74.2-1) breaks dependency 'libicuuc.so=73-64' required by libphonenumber :: installing icu (74.2-1) breaks dependency 'libicui18n.so=73-64' required by libphonenumber :: installing icu (74.2-1) breaks dependency 'libicuuc.so=73-64' required by raptor :: installing icu (74.2-1) breaks dependency 'libicuuc.so=73-64' required by scribus :: installing icu (74.2-1) breaks dependency 'libicui18n.so=73-64' required by thunderbird :: installing icu (74.2-1) breaks dependency 'libicuuc.so=73-64' required by thunderbird| This piqued my interest as it appears to be a package conflict outside of my control. I performed the upgrade excluding the |icu| package, and (almost) everything is fine now. However, I would like to know: * Is this an issue with the |icu| package? o In this case, this is an issue that needs attention and the relevant maintainer should probably look into it. * Is it an issue with me? o If so, what do I do, aside from ignoring it? I look forward to hearing your response(s). Yours truly, -- WinFan3672.

3 2

re: ddgr broken
by Jude DaShiell 13 Dec '23

13 Dec '23

Correction, both ddgr and ddgr-git throw error 202 when run. What is error code 202? I've never encountered that error code in connection with html yet. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940.

3 4

[Secure Boot] sbctl and MOK
by Giovanni Santini 12 Dec '23

12 Dec '23

Hi everyone, I have my laptop set up using Grub [1] and Shim with hashes [2]. I use sbctl [3] for my key management. I would like to know if any other user is running the same setup and, if so, if they managed to enroll sbctl keys in shim. I am genuinely confused if I should enroll any file from sbctl, since it does not generate a MOK. Bests, Giovanni [1]: https://wiki.archlinux.org/title/GRUB#Shim-lock [2]: https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secu… [3]: https://wiki.archlinux.org/title/Unified_Extensible_Firmware_Interface/Secu…

1 0

extra/surge-xt-common 1.3.0-1 breaks extra/surge-xt-lv2 1.2.3-2
by Ralf Mardorf 12 Dec '23

12 Dec '23

Hi, I don't know where to report this issue, since 2FA for "ralf" at https://gitlab.archlinux.org/ fails with "Invalid authentication code" [1]. extra/surge-xt-common 1.3.0-1 breaks extra/surge-xt-lv2 1.2.3-2, see https://archlinux.org/packages/extra/x86_64/surge-xt-lv2/ https://archlinux.org/packages/extra/x86_64/surge-xt-common/ Regards, Ralf -- [1] yes, already reported to accountsupport(a)archlinux.org ;)

3 3

Proposal about AUR affairs
by Evan Greenup 11 Dec '23

11 Dec '23

Hello, AUR is a unique feature for Arch Linux (include derived distros). It significantly expand the Arch ecosystem. However, for the current infrastructure and workflow for AUR, there are some drawbacks. 1. Difficult to feedback and difficult to contribute (to already existed package). If have any ideas or report, user need to send email to maintainer via email personally. This is not convenient for both maintainers and users. 2. Lack of Peer review, audience supervise. Some packages even if updated frequently by its maintainer, but it doesn't following good practice and not built from source (Not Java, native program), It retrieve from Debian or Ubuntu or Fedora packages, and extract or repackage it in Arch Linux package. And some packages may failed to build, or some of its dependencies are forgotten added by maintainer. 3. The entry with a specific name in AUR is always occupied by the Maintainer who firstly register the package. If there is another maintainer who has better practice than the previous one, This maintainer has to rename his/her package as `xxx-bin` or some sophisticated name else. This is unfair. It lack of refreshing mechanism. 4. upstream software author is difficult to directly contribute to the AUR packaging contribution. For a great number of upstream software author, they are willing to participate in downstream redistribution process. Especially for those young software. But the current AUR workflow block their way to contribute on downstream stuff. 5. Currently,to evaluate whether a AUR package is eligible to move in Arch Linux official packages (extra repo), It only depend on votes and popularity and whether there is a maintainer willing to pick it up. However, those factors is too lack of details. To evaluate the robustness of the eco-position of a package, It should evaulate the discussion, issue report, contribution, and ... And it should be evaluated case by case. I have some ideas to resolve or mitigate the problems above. 1. Create a git repo on gitlab.archlinux.org named aur-meta (Or whatever names which maker users understand easily). This git repo keep a list (table of content) which point to the git repo URI of the AUR packages. 2. For the AUR package, it can be placed on anywhere (github.com, gitlab.com, gitlab.archlinux.org, gitlab.gnome.org ...), the only things needed are these URIs are public accessible (can be git cloned by anyone who know this URI). And it need to keep its PKGBUILD on the top level of git repo. 3. The issue and affairs related to which upstream software is included and which PKGBUILD git repo is selected, goes to issues section of aur-meta. For packaging specific problems, it goes to the AUR package git repo. 4. If a package is orphaned or too broken/bad practice, the contributor who has access to aur-meta can simply change the pointer to a alternative PKGBUILD git repo which is better in practice and liveliness. 5. If user find there is package which need to be improved, it can firstly report it to PKGBUILD maintainer via the issue section of git repo. If the maintainer long time not response or insist to keep bad practice. The user can write a proposal in aur-meta to change the pointer to another alternative. This is what a community driven packaging method should be. 6. The name of entry in aur-meta is the package name, not the name of PKGBUILD git repo. (git repo can have different name). Many upstream software author would create a separate git repo along with their software repo which is dedicated for PKGBUILD. The design above, is just for demonstrate ideas, improvements can be made further. Evan

15 27

Re: Arch Linux release 2023.12.01 comes with Linux Kernel 6.6.3
by Turritopsis Dohrnii Teo En Ming 11 Dec '23

11 Dec '23

On Saturday, December 9th, 2023 at 10:58 PM, Doug Newgard <dnewgard(a)outlook.com> wrote: > On Sat, 09 Dec 2023 14:51:37 +0000 > Turritopsis Dohrnii Teo En Ming teo.en.ming(a)protonmail.com wrote: > > > I am confused. > > > > On the Arch Linux download page https://archlinux.org/download/ , it clearly > > says Current Release 2023.12.01 with Linux Kernel 6.6.3. > > > Yes, that is the release of the ISO, not of Arch Linux. And it doesn't actually > matter what ISO you use. You could use the ISO from 2-3 months ago and the > installed system will be the same, because as I said, it always downloads the > latest packages to install. There are no packages on the ISO. Noted with thanks. I think I understand already. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore

2 1

Arch Linux release 2023.12.01 comes with Linux Kernel 6.6.3
by Turritopsis Dohrnii Teo En Ming 09 Dec '23

09 Dec '23

Subject: Arch Linux release 2023.12.01 comes with Linux Kernel 6.6.3 Good day from Singapore, After I have downloaded and installed Arch Linux release 2023.12.01, can I upgrade the Linux Kernel from 6.6.3 to 6.6.5 easily? Is the Linux Kernel 6.6.5 package available in the repository? Thank you. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore Blogs: https://tdtemcerts.blogspot.com https://tdtemcerts.wordpress.com GIMP also stands for Government-Induced Medical Problems. Sent with Proton Mail secure email.

4 7

Re: Arch Linux release 2023.12.01 comes with Linux Kernel 6.6.3
by Turritopsis Dohrnii Teo En Ming 09 Dec '23

09 Dec '23

On Saturday, December 9th, 2023 at 3:46 AM, Rafael Fontenelle <rffontenelle(a)gmail.com> wrote: > It is available in core-testing: > https://archlinux.org/packages/core-testing/x86_64/linux/ Thanks for the link! I saw linux 6.6.5.arch1-1 already. The latest Linux Kernel. I am going to install Arch Linux on my refurbished/2nd hand Aftershock gaming laptop these few days. Thank you! Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore

1 0

ddgr package broken
by Jude DaShiell 08 Dec '23

08 Dec '23

Originally this package worked. Now it's throwing error 202 on all searches. I suspect duckduckgo changed something or google changed something to break this package. Remote possibility some package on archlinux set the breakage off but I figure that to be highly unlikely. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940.

1 0