From nobody at parabola.nu Wed Oct 4 13:32:16 2023 From: nobody at parabola.nu (Parabola Website Notification) Date: Wed, 04 Oct 2023 13:32:16 -0000 Subject: [Dev] Orphan nonsystemd package [util-linux] marked out-of-date Message-ID: <20231004133216.2851826.56514@winston.parabola.nu> kwopleq at proton.me wants to notify you that the following packages may be out-of-date: The user provided the following additional text: The version 2.39.2 is available From nobody at parabola.nu Wed Oct 11 00:32:35 2023 From: nobody at parabola.nu (Parabola Website Notification) Date: Wed, 11 Oct 2023 00:32:35 -0000 Subject: [Dev] Orphan Libre package [iceweasel] marked out-of-date Message-ID: <20231011003235.2851828.87997@winston.parabola.nu> eliotreyna at disroot.org wants to notify you that the following packages may be out-of-date: * iceweasel 1:118.0-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/iceweasel/ The user provided the following additional text: Firefox source code has been updated to the version 118.0.2. The following fixes are: -Printing issues on SVG images. -CORS XHR with authentication not working. -h264 WebRTC video not working in some contexts. -Stability issues. For more information, please go to the links below: https://www.mozilla.org/en-US/firefox/118.0.2/releasenotes/ https://bugzilla.mozilla.org/buglist.cgi?order=bug_list&bug_id=1851991,1799326,1856637 Thanks. From wael at waelk.tech Fri Oct 13 08:24:05 2023 From: wael at waelk.tech (Wael Karram) Date: Fri, 13 Oct 2023 09:24:05 +0100 Subject: [Dev] [PKGBUILD] GNUBoot Utils Message-ID: <9eaa05e0362cb10eb8232601445361026a118f88.camel@waelk.tech> Hello, Seeing as Libreboot is no longer considered fit for building packages from under the FSDG, I have packaged gnuboot-utils as a replacement. Note though that this package might be changed soon as upstream stabilizes, though from my understanding the utils are stable anyway as they haven't been changed much if at all compared to older libreboot versions (when it was still FSDG compliant). -- Kind Regards, Wael Karram. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Packaged-gnuboot-utils-as-a-replacement-for-the-libr.patch Type: text/x-patch Size: 5880 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From nobody at parabola.nu Sat Oct 14 09:39:38 2023 From: nobody at parabola.nu (Parabola Website Notification) Date: Sat, 14 Oct 2023 09:39:38 -0000 Subject: [Dev] Orphan Libre package [ktorrent] marked out-of-date Message-ID: <20231014093938.2851826.83800@winston.parabola.nu> kwopleq at proton.me wants to notify you that the following packages may be out-of-date: * ktorrent 23.04.3-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/ktorrent/ * ktorrent 23.04.3-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/ktorrent/ * ktorrent 23.04.3-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/ktorrent/ The user provided the following additional text: The version 23.08.2 is available in arch repo. From nobody at parabola.nu Wed Oct 18 04:11:45 2023 From: nobody at parabola.nu (Parabola Website Notification) Date: Wed, 18 Oct 2023 04:11:45 -0000 Subject: [Dev] Orphan Libre package [python-pyqt5] marked out-of-date Message-ID: <20231018041145.2851826.19317@winston.parabola.nu> eliotreyna at disroot.org wants to notify you that the following packages may be out-of-date: * pyqt5-debug 5.15.9-2.parabola5.1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/pyqt5-debug/ * pyqt5-debug 5.15.9-2.parabola4 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/pyqt5-debug/ * pyqt5-debug 5.15.9-2.parabola6 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/pyqt5-debug/ * python-pyqt5 5.15.9-2.parabola5.1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/python-pyqt5/ * python-pyqt5 5.15.9-2.parabola4 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/python-pyqt5/ * python-pyqt5 5.15.9-2.parabola6 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/python-pyqt5/ The user provided the following additional text: PyQT5 is actually avariable in the version 5.15.10, which is needed to the PyQT5-based programs as Shotcut and Openshot. From nobody at parabola.nu Mon Oct 23 16:16:13 2023 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 23 Oct 2023 16:16:13 -0000 Subject: [Dev] Orphan Nonprism package [kio5] marked out-of-date Message-ID: <20231023161613.2851826.58597@winston.parabola.nu> kwopleq at proton.me wants to notify you that the following packages may be out-of-date: The user provided the following additional text: The version 5.111.0 is available From nobody at parabola.nu Tue Oct 24 07:41:33 2023 From: nobody at parabola.nu (Parabola Website Notification) Date: Tue, 24 Oct 2023 07:41:33 -0000 Subject: [Dev] Orphan Libre package [iceweasel] marked out-of-date Message-ID: <20231024074133.2851826.12045@winston.parabola.nu> dario86 at tutamail.com wants to notify you that the following packages may be out-of-date: * iceweasel 1:118.0.2-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/iceweasel/ The user provided the following additional text: Firefox 119 is out. From nobody at parabola.nu Thu Oct 26 05:44:49 2023 From: nobody at parabola.nu (Parabola Website Notification) Date: Thu, 26 Oct 2023 05:44:49 -0000 Subject: [Dev] Orphan Libre package [kinfocenter] marked out-of-date Message-ID: <20231026054449.2851828.36173@winston.parabola.nu> kwopleq at proton.me wants to notify you that the following packages may be out-of-date: * kinfocenter 5.27.8-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/kinfocenter/ * kinfocenter 5.27.8-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/kinfocenter/ * kinfocenter 5.27.8-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kinfocenter/ * kinfocenter-debug 5.27.8-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/kinfocenter-debug/ * kinfocenter-debug 5.27.8-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/kinfocenter-debug/ * kinfocenter-debug 5.27.8-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/kinfocenter-debug/ The user provided the following additional text: The version 5.27.9 is the latest From pagure at pagure.io Thu Oct 26 11:24:23 2023 From: pagure at pagure.io (=?utf-8?q?Grizzly_User?=) Date: Thu, 26 Oct 2023 11:24:23 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2390=3A_libre/iceweasel=3A_11?= =?utf-8?q?9=2E0-1=2Eparabola1?= Message-ID: grizzlyuser opened a new pull-request against the project: `abslibre` that you are following: `` libre/iceweasel: 119.0-1.parabola1 `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/90 From daniil at kovalev.website Thu Oct 26 12:10:55 2023 From: daniil at kovalev.website (Daniil Kovalev) Date: Thu, 26 Oct 2023 15:10:55 +0300 Subject: [Dev] Issues with manual Iceweasel build Message-ID: <20231026151055.796a2fb2@arch-pc.localdomain> Hello. I want to create an AUR (and probably a PCR) package iceweasel-xdg similar to firefox-xdg https://aur.archlinux.org/packages/firefox-xdg. It's intended to get rid of .mozilla directory in home catalogue and move it to $XDG_CONFIG_HOME. I use abslibre/libre/iceweasel package build scripts as a starting point https://git.parabola.nu/abslibre.git/tree/libre/iceweasel. Unfortunately, I can't even build the vanilla iceweasel from these sources! The first error I face looks as follows: psutil<=5.9.4,>=5.4.2: Installed with unexpected version "5.9.6" When downgraded to system python-psutil 5.9.5, many other errors like ones listed below occur: cwhy 0.0.4 requires openai-async, which is not installed. ratarmount 0.13.0 requires rarfile, which is not installed. rich-cli 1.8.0 requires rich-rst, which is not installed. trash-cli 0.23.2.13.2 requires typing, which is not installed. ledgerwallet 0.3.1.dev2 has requirement click>=8.0, but you have click 7.1.2. ledgerwallet 0.3.1.dev2 has requirement protobuf<4,>=3.20, but you have protobuf 4.24.3. cwhy 0.0.4 has requirement click>=8.1.3, but you have click 7.1.2. ratarmount 0.13.0 has requirement python-xz~=0.4.0, but you have python-xz 0.5.0. parse-type 0.6.1 has requirement six>=1.15, but you have six 1.13.0. rich-cli 1.8.0 has requirement click<9.0.0,>=8.0.0, but you have click 7.1.2. rich-cli 1.8.0 has requirement rich<13.0.0,>=12.4.0, but you have rich 13.6.0. rich-cli 1.8.0 has requirement textual<0.2.0,>=0.1.18, but you have textual 0.34.0. python-pptx 0.6.22 has requirement Pillow<=9.5.0,>=3.3.2, but you have pillow 10.1.0. poetry 1.6.1 has requirement jsonschema<4.18.0,>=4.10.0, but you have jsonschema 4.19.1. poetry 1.6.1 has requirement poetry-plugin-export<2.0.0,>=1.5.0, but you have poetry-plugin-export 1.3.0. poetry 1.6.1 has requirement requests<3.0,>=2.26, but you have requests 2.25.1. black 23.7.0 has requirement click>=8.0.0, but you have click 7.1.2. black 23.7.0 has requirement packaging>=22.0, but you have packaging 21.3. sphinx 7.2.6 has requirement Jinja2>=3.0, but you have jinja2 2.11.3. They are mostly related to version mismatch between bundled python packages an system ones. For example, sphinx 7.2.6 is a system package, but we try to use a bundled Jinja2=2.11.3 which is too old for system sphinx (while an up-to-date system Jinja=3.1.2 is actually installed!) I suppose that I can try to build a package in a clean chroot and it should help with at least some errors. But I don't think that having a package which is so reliant on correct environment for proper build is a nice idea. I'm going to put that to AUR, and people rarely build AUR packages in a clean chroot - they mostly run makepkg -si or use a helper which does the same. So, I would be glad if someone could answer at least some of the following questions. 1. Does everyone face the same issues with python packages when building iceweasel without using clean chroot? 2. How is iceweasel binary package shipped in libre repository compiled? Is it done in a clean chroot? 3. Are there any plans to make build possible without chroot to empty environment? 4. If I do this part of work, could it be merged to Parabola's iceweasel pkgbuild or is that a non-feature/out-of-scope/etc? 5. As far as I understood, Parabola's build of iceweasel tries to use system libraries instead of bundled ones as much as possible. Do the errors I get indicate that this work is not finished yet? Thanks! -- Daniil Kovalev From bill-auger at peers.community Thu Oct 26 18:39:46 2023 From: bill-auger at peers.community (bill-auger) Date: Thu, 26 Oct 2023 14:39:46 -0400 Subject: [Dev] Issues with manual Iceweasel build In-Reply-To: <20231026151055.796a2fb2@arch-pc.localdomain> References: <20231026151055.796a2fb2@arch-pc.localdomain> Message-ID: <20231026143946.14d145f5@parabola.localdomain> On Thu, 26 Oct 2023 15:10:55 +0300 Daniil wrote: > I suppose that I can try to build a package in a clean chroot and it should > help with at least some errors. But I don't think that having a package which > is so reliant on correct environment for proper build is a nice idea. I'm going > to put that to AUR, and people rarely build AUR packages in a clean chroot you really can not do much about that - there is no general way to guarantee that the same PKGBUILD will build in every possible environment - that is the very reason why to prefer building in a clean chroot - that eliminates the variables which are out of the control of the maintainer and guarantees that everyone is building it in a suitable environment, without resorting to heavy foreign approaches like docker On Thu, 26 Oct 2023 15:10:55 +0300 Daniil wrote: > 1. Does everyone face the same issues with python packages when building > iceweasel without using clean chroot? i doubt if anyone does that; and no one would recommend doing so - compiling in a clean or custom build environment is always the preferred way for any program - that is why most python programs for example, build and often expect to run in a "virtual-env", which is effectively a python chroot - that is because it is not possible to trust that every environment is sufficient and configured sanely parabola users can avoid many such headaches by building with libremakepkg - it is a very simple way to setup a clean and reproducible build environment if people have incompatibilities with their python environment, is is most likely that they have python packages installed from a third-party (such as pip), rather than using distro packages exclusively - if third-party software is in the environment, especially if it is installed at the system level with sudo etc, the system is tainted and is not supportable by anyone other than oneself - AUR users should understand that - the wise option is to keep an entire OS, chroot, or VM dedicated only for development and compiling, or even to spin up a fresh one for every program and delete it afterward On Thu, 26 Oct 2023 15:10:55 +0300 Daniil wrote: > 2. How is iceweasel binary package shipped in libre repository compiled? Is it > done in a clean chroot? as a matter of policy, all packages published by parabola are built in a clean chroot with libremakepkg, with networking disabled - that is another good reason to prefer an isolated build environment - to have an active internet connection during the build is another potential source of conflicts, and the possibility for sources and binaries, which would not be accounted for or audited, to influence the build, all out of the control of the PKGBUILD maintainer - mozilla and anything else which uses the rust compiler will do exactly that - anyone who would prefer to use iceweasel or icecat instead of firefox or chromium, should also not want it compiled with networking enabled, for all of the same reasons On Thu, 26 Oct 2023 15:10:55 +0300 Daniil wrote: > 3. Are there any plans to make build possible without chroot to empty > environment? no - as i explained, it is not possible for any upstream or distro or package maintainer to support that use-case generally, without expecting everyone to use the same environment, such as a custom docker container - parabola supports that use-case generally with libremakepkg On Thu, 26 Oct 2023 15:10:55 +0300 Daniil wrote: > 4. If I do this part of work, could it be merged to Parabola's iceweasel > pkgbuild or is that a non-feature/out-of-scope/etc? sure, if parabola users want that - i do not understand the motivation though - what is the value of moving the user config directory? - why would anyone care which directory is used? - that directory is extremely brittle, and should never be touched by the user On Thu, 26 Oct 2023 15:10:55 +0300 Daniil wrote: > 5. As far as I understood, Parabola's build of iceweasel tries to use system > libraries instead of bundled ones as much as possible. Do the errors I get > indicate that this work is not finished yet? that work is ever finished - mozilla is the most difficult software to maintain of any parabola package, and has the most complicated PKGBUILD of any parabola package - it is perhaps the most complicated PKGBUILD of any PKGBUILD anywhere every major release requires dependency tweaks - that is why upstreams such as mozilla tend to vendor everything but the kitchen sink; but even that is not sufficient for most releases; because the mozilla devs target LTS distros such as ubuntu and fedora - maintaining mozilla software on a rolling distro is a never-ending challenge From daniil at kovalev.website Thu Oct 26 21:38:55 2023 From: daniil at kovalev.website (Daniil Kovalev) Date: Fri, 27 Oct 2023 00:38:55 +0300 Subject: [Dev] Issues with manual Iceweasel build In-Reply-To: <20231026143946.14d145f5@parabola.localdomain> References: <20231026151055.796a2fb2@arch-pc.localdomain> <20231026143946.14d145f5@parabola.localdomain> Message-ID: <20231027003855.28158846@arch-pc.localdomain> Thanks for such a detailed answer! OK, the miracle did not happen, and I'll have to use a clean chroot :) Thanks for providing references to right tools for that! > sure, if parabola users want that - i do not understand the motivation though - > what is the value of moving the user config directory? - why would anyone care > which directory is used? - that directory is extremely brittle, and should > never be touched by the user This is just about aesthetics of not having many dotfiles in home directory :) Although mozilla configs are not intended to be changed manually (maybe except stuff like userChrome.css), a one might not want to have such a "useless" directory in home. Many people ignore that, but some (definitely not only me) become frustrated. > that work is ever finished - mozilla is the most difficult software to maintain > of any parabola package, and has the most complicated PKGBUILD of any parabola > package - it is perhaps the most complicated PKGBUILD of any PKGBUILD anywhere > > every major release requires dependency tweaks - that is why upstreams such as > mozilla tend to vendor everything but the kitchen sink; but even that is not > sufficient for most releases; because the mozilla devs target LTS distros such > as ubuntu and fedora - maintaining mozilla software on a rolling distro is a > never-ending challenge Ah, I get it now. I'll try to play with this PKBUILD a bit, but not sure if such attempts of enhancements succeed. If there are some results worth mentioning, I'll let you know. -- Daniil Kovalev From bill-auger at peers.community Fri Oct 27 00:18:14 2023 From: bill-auger at peers.community (bill-auger) Date: Thu, 26 Oct 2023 20:18:14 -0400 Subject: [Dev] Issues with manual Iceweasel build In-Reply-To: <20231027003855.28158846@arch-pc.localdomain> References: <20231026151055.796a2fb2@arch-pc.localdomain> <20231026143946.14d145f5@parabola.localdomain> <20231027003855.28158846@arch-pc.localdomain> Message-ID: <20231026201814.76a8909c@parabola.localdomain> thats just how the cookie crumbles - programs have been sourcing and creating dotfiles since long before mozilla, the FHS, $XDG_CONFIG_HOME, or the ~/.config directory - most people are not so annoyed by it - that is why programs like `ls`, GUI file managers, and other programs hide dotfiles by default - they are expected to be there and expected to be messy; and they are probably never going away if you do this, bear in mind that you can not assume that every system will have $XDG_CONFIG_HOME set or have the XDG tools at all - you would want to test for it and fallback to the default mozilla_dir=${XDG_CONFIG_HOME:-$HOME/.mozilla} also, if the FHS means anything, $XDG_CONFIG_HOME is not the proper place for the .mozilla directory - $XDG_CONFIG_HOME is the per-user analog for /etc - that is for user-maintained configuration files - if the .mozilla directory were installed system-wide, it would be under /usr/share/ or /usr/local/share/, according to the FSH semantics - given what the .mozilla directory is used for, the appropriate directory is ~/.local/share/mozilla (aka: $XDG_DATA_HOME/mozilla), which is the per-user analog for /usr/share/ one last but of advice - you probably do not need to do this yourself - its not like you are are the only person who has had that idea there - there is an open ticket for that feature request - if i had this motivation, i would get on that thread and encourage mozilla to implement it for everyone https://bugzilla.mozilla.org/show_bug.cgi?id=259356 From bill-auger at peers.community Fri Oct 27 00:25:42 2023 From: bill-auger at peers.community (bill-auger) Date: Thu, 26 Oct 2023 20:25:42 -0400 Subject: [Dev] Issues with manual Iceweasel build In-Reply-To: <20231026201814.76a8909c@parabola.localdomain> References: <20231026151055.796a2fb2@arch-pc.localdomain> <20231026143946.14d145f5@parabola.localdomain> <20231027003855.28158846@arch-pc.localdomain> <20231026201814.76a8909c@parabola.localdomain> Message-ID: <20231026202542.2621014f@parabola.localdomain> On Thu, 26 Oct 2023 20:18:14 -0400 bill-auger wrote: > if i had this motivation, i would get on that > thread and encourage mozilla to implement it for everyone mozilla ... and any of the thousands of other legacy programs which do not respect the FHS of XDG From pagure at pagure.io Fri Oct 27 04:11:09 2023 From: pagure at pagure.io (=?utf-8?q?bill-auger?=) Date: Fri, 27 Oct 2023 04:11:09 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2390=3A_libre/iceweasel=3A_11?= =?utf-8?q?9=2E0-1=2Eparabola1?= In-Reply-To: Message-ID: billauger commented on the pull-request: `libre/iceweasel: 119.0-1.parabola1` that you are following: `` merged `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/90 From pagure at pagure.io Fri Oct 27 04:11:17 2023 From: pagure at pagure.io (=?utf-8?q?bill-auger?=) Date: Fri, 27 Oct 2023 04:11:17 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2390=3A_libre/iceweasel=3A_11?= =?utf-8?q?9=2E0-1=2Eparabola1?= In-Reply-To: Message-ID: billauger closed without merging a pull-request against the project: `abslibre` that you are following. Closed pull-request: `` libre/iceweasel: 119.0-1.parabola1 `` https://pagure.io/abslibre/pull-request/90 From daniil at kovalev.website Fri Oct 27 09:55:22 2023 From: daniil at kovalev.website (Daniil Kovalev) Date: Fri, 27 Oct 2023 12:55:22 +0300 Subject: [Dev] Issues with manual Iceweasel build In-Reply-To: <20231026202542.2621014f@parabola.localdomain> References: <20231026151055.796a2fb2@arch-pc.localdomain> <20231026143946.14d145f5@parabola.localdomain> <20231027003855.28158846@arch-pc.localdomain> <20231026201814.76a8909c@parabola.localdomain> <20231026202542.2621014f@parabola.localdomain> Message-ID: <20231027125522.14d95e58@arch-pc.localdomain> > one last but of advice - you probably do not need to do this yourself - its not > like you are are the only person who has had that idea there - there is an open > ticket for that feature request - if i had this motivation, i would get on that > thread and encourage mozilla to implement it for everyone > > https://bugzilla.mozilla.org/show_bug.cgi?id=259356 Sure, I'm not going to implement that by myself - fortunately, a patch https://phabricator.services.mozilla.com/D6995 is available (although not merged to mainline yet). It's linked to the ticket 259356 you mentioned. It's already used by firefox-xdg AUR package https://aur.archlinux.org/packages/firefox-xdg. I'll check if it properly handles cases you mentioned like not having $XDG_CONFIG_HOME, thanks for giving attention to that! > thats just how the cookie crumbles - programs have been sourcing and creating > dotfiles since long before mozilla, the FHS, $XDG_CONFIG_HOME, or the ~/.config > directory - most people are not so annoyed by it - that is why programs like > `ls`, GUI file managers, and other programs hide dotfiles by default - they are > expected to be there and expected to be messy; and they are probably never > going away Sure, trying to get rid of them is a non-ending holy war. However, if we can't drink all the vodka, it doesn't mean that we cannot at least try :) As for me, there are now many cases when dotfiles are not meant to be hidden files but are treated as "special" files - ones that a person want to always see, but a dot-prefix gives them a special meaning which may vary depending on context. In such cases, it's convenient to have an alias like alias l='ls -Alv --color=always --group-directories-first' And it would be cool not to see tons of dotfiles in home when running that (the home is actually the only directory which is so massively cluttered with dotfiles; having dotfiles always displayed in any other directory is almost always OK IMHO). P.S. On my machine, the list of dotfiles in home (except .config, .cache and .local) looks as follows: .dbus, .hplip, .mozilla, .ssh, .profile. So, at the end of 2023, we a finally close to a *relatively* clean home at least for some sets of software installed. Thanks xdg-ninja and Arch wiki XDG base directory page. -- Daniil Kovalev From wael at waelk.tech Sat Oct 28 13:52:19 2023 From: wael at waelk.tech (Wael Karram) Date: Sat, 28 Oct 2023 16:52:19 +0300 Subject: [Dev] [PKGBUILD][PATCH] LaGrange Update Message-ID: Hello, I've attached a patch to update lagrange gemini browser to the latest version v1.17.2. -- Kind Regards, Wael Karram. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Updated-lagrange-to-1.17.2.patch Type: text/x-patch Size: 960 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From nobody at parabola.nu Sun Oct 29 19:12:42 2023 From: nobody at parabola.nu (Parabola Website Notification) Date: Sun, 29 Oct 2023 19:12:42 -0000 Subject: [Dev] Orphan nonsystemd package [xdg-user-dirs] marked out-of-date Message-ID: <20231029191242.2851826.93118@winston.parabola.nu> kwopleq at proton.me wants to notify you that the following packages may be out-of-date: The user provided the following additional text: The version 0.18 is the latest version in available Artix