Search results for "Deletion request for pkgbase" - Aur-requests

[aur-requests] [PRQ#32189] Deletion Request for libx32-tk

by notify＠aur.archlinux.org

MarsSeed [1] filed a deletion request for libx32-tk [2]: Please delete libx32- AUR packages: • Package have not been updated in 6 years or more. • Owner replied in email to me, agreeing to the deletion. • In case of libx32- packages, naming violates Arch guidelines*. Name should end with '-x32', not start with 'libx32-'. • Most such packages cannot be built because of already dropped dependencies from AUR. • Even if built, X32 executables won't work with any mainstream kernels from any distros. Only on kernels custom-built with niche x32 ABI support. • Whoever wants to use such a special architecture would not be able to use it from unbuildable, unmaintained 6-year old build scripts from the AUR. But they could use Debian x32 or build Gentoo from scratch for the x32 ABI, or find some IoT-specific distro (X32 ABI might be relevant for some low-end IoT devices). [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/libx32-tk/

3 years, 10 months

[aur-requests] [PRQ#31770] Deletion Request for libx32-glib2

by notify＠aur.archlinux.org

MarsSeed [1] filed a deletion request for libx32-glib2 [2]: Please delete libx32- and -x32 AUR packages: • Packages have not been updated in 6 years or more. • Owner replied in email to me, agreeing to the deletion. • In case of libx32- packages, naming violates Arch guidelines*. Name should end with '-x32', not start with 'libx32-'. • Most such packages cannot be built because of already dropped dependencies from AUR. • Even if built, X32 executables won't work with any mainstream kernels from any distros. Only on kernels custom-built with niche x32 ABI support. • Whoever wants to use such a special architecture would not be able to use it from unbuildable, unmaintained 6-year old build scripts from the AUR. But they could use Debian x32 or build Gentoo from scratch for the x32 ABI, or find some IoT-specific distro where X32 ABI *might* be relevant. [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/libx32-glib2/

3 years, 10 months

[PRQ#49195] Deletion Request for ros2-foxy

by notify＠aur.archlinux.org

MarsSeed [1] filed a deletion request for ros2-foxy [2]: Unneeded, defunct package. ROS 2 Foxy distribution was based on Ubuntu 20.04, and is EOL since March 2023. On AUR it depends on broken packages, and it is also incompatible with many of Arch core's new library versions. Actually it doesn't make sense to maintain old foreign distro packages on Arch which are targeted for legacy Ubuntu LTS versions, because Arch is a leading-edge rolling distro, whose aim and offering is freshness, not very long backwards compatibility with ancient toolchains and system libraries. Arch users should migrate to the newest maintained ROS 2 distribution (Iron Irwini), or better yet, ROS 2 Rolling. (Packages for both are available on AUR.) Or they could just use the main upstream ROS distribution images. [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/ros2-foxy/

2 years, 2 months

[PRQ#49196] Deletion Request for ros2-galactic

by notify＠aur.archlinux.org

MarsSeed [1] filed a deletion request for ros2-galactic [2]: Unneeded, defunct package. ROS 2 Galaxy distribution was based on Ubuntu 20.04, and is EOL since Dec 2022. On AUR it depends on broken packages, and it is also incompatible with many of Arch core's new library versions. Actually it doesn't make sense to maintain old foreign distro packages on Arch which are targeted for legacy Ubuntu LTS versions, because Arch is a leading-edge rolling distro, whose aim and offering is freshness, not very long backwards compatibility with ancient toolchains and system libraries. Arch users should migrate to the newest maintained ROS 2 distribution (Iron Irwini), or better yet, ROS 2 Rolling. (Packages for both are available on AUR.) Or they could just use the main upstream ROS distribution images. [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/ros2-galactic/

2 years, 2 months

Re: [PRQ#43764] Deletion Request for petsc-git-release

by Marcell Meszaros

It seems AUR/petsc-git also builds the release branch, just like this package. So deleting this package won't cause a loss: AUR users still can get the same 'rolling stable' version from the same branch via the latter package. (N.b. AUR/petsc-git has a misleading name, as typically a git package is for the latest development branch, not for a stable release maintenance branch. But I guess following the latter makes the built software more reliable for end-users; that is actually what upstream recommends for them.) On 6 July 2023 16:21:43 GMT+02:00, notify(a)aur.archlinux.org wrote: >entshuld [1] filed a deletion request for petsc-git-release [2]: > >I have to rename this package, but I realistically have no time to >maintain it, anyway. > >[1] https://aur.archlinux.org/account/entshuld/ >[2] https://aur.archlinux.org/pkgbase/petsc-git-release/

2 years, 5 months

Re: [PRQ#46871] Deletion Request for python2-pandas

by Marcell Meszaros

The package that optdepends on this, python2-py6s is also broken, because one of its dependencies is broken. But no one pushes for a solution, because no one actually uses those libraries anymore, and that includes the package owners themselves. On 30 August 2023 21:09:24 GMT+02:00, notify(a)aur.archlinux.org wrote: >MarsSeed [1] filed a deletion request for python2-pandas [2]: > >I recommend to delete this now-unused legacy Python2 scientific >library. > >There is only an optional consumer on AUR that refers to this, >python2-py6s. >And that is also a legacy library and it is not used by anything else >anymore (its last dependent was python2-arcsi, which has been long >broken due to H5Py/GDAL incompatibility, so it got deleted.) > >[1] https://aur.archlinux.org/account/MarsSeed/ >[2] https://aur.archlinux.org/pkgbase/python2-pandas/

2 years, 3 months

Re: [PRQ#46480] Deletion Request for yajl-edenhill-git

by Marcell Meszaros

This fork from 2019 actually only contains one commit on top of the original yajl. And that one commit just creates another function that copies the input string verbatim to the output, without verification. This is wholly superfluous, useless, and even defeats the intention written in its source comment that says "input must be a valid JSON". Duh. On 20 August 2023 02:39:38 GMT+02:00, notify(a)aur.archlinux.org wrote: >MarsSeed [1] filed a deletion request for yajl-edenhill-git [2]: > >The source fork used here has not been developed for 4 years. [a] > >The package is an orphan. > >Repo carries the stable yajl, and there's a yajl-git package on AUR. > >[a]: >https://github.com/edenhill/yajl/tree/edenhill > >[1] https://aur.archlinux.org/account/MarsSeed/ >[2] https://aur.archlinux.org/pkgbase/yajl-edenhill-git/

2 years

[PRQ#52605] Deletion Request for elogind

by notify＠aur.archlinux.org

MarsSeed [1] filed a deletion request for elogind [2]: Unmaintained for 2 years. But it does not belong here: AUR packages have to be compatible with Arch Linux. This isn't: not installable due to having declared conflicts with systemd-sysvcompat (dependency of 'base'), as well as undeclared conflicts with core/filesystem and core/systemd. Current version of this package is carried by systemd-less Arch Linux derivatives like Artix. Please delete the following reverse dependencies that are also not installable on Arch Linux: - dbus-xdg (PRQ#49445) (dbus exists in Artix Linux repo) - libratbag-nosystemd-git (PRQ#52601) - miraclecast-nosystemd-git (PRQ#52602) - plymouth-nosystemd (PRQ#52408) (plymouth exists in Artix Linux repo) Artix Linux does host even VCS packages, so the '-git' builds in the list above can be submitted there. [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/elogind/

1 year, 11 months

[PRQ#69340] Deletion Request for vkcube-git

by notify＠aur.archlinux.org

MarsSeed [1] filed a deletion request for vkcube-git [2]: Broken, abandoned package from 2023. Upstream was only actively maintained until 2022, then received one PR merge done in 2024 (carrying a commit from 2023). [a] It seems to be a fork of Khronos Group's cube (vkcube) from vulkan- tools [b], carried by Arch/extra repo. The fork has unresolved issues [c], e.g. with dual Intel iGPU + discrete NVIDIA GPU on Wayland (Issue #62), among others. Arch/extra/vulkan-tools offers both a 'vkcube' and a 'vkcube-wayland' executable. The latter's upstream is under active and continual maintenance by Khronos Group and contributors. [b] [a]: http://github.com/krh/vkcube/commits/master [b]: http://github.com/KhronosGroup/Vulkan-Tools/tree/main/cube [c]: https://github.com/krh/vkcube/issues [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/vkcube-git/

10 months, 2 weeks

[PRQ#44683] Deletion Request for rocblas-polaris-bin

by notify＠aur.archlinux.org

MarsSeed [1] filed a deletion request for rocblas-polaris-bin [2]: Abandoned patched binary from 2022-04 for rocblas, available in repo. One-time effort, flagged OOD since 2022-07, but never updated. Doesn't declare sources, uses wget to download them. Doesn't declare the needed conflicts. Gfx8 (gfx803) Radeon devices from 2017 like Radeon RX 550, 570, 580 have been having crashes as far back as ROCm 3.7, then ROCm 4.0 in 2020 has officially declared that these platforms as unsupported. [a] Just because a patched build enables the use of these legacy GPU's, it won't make this rocblas build run without errors, if it works at all. Not useful to keep this unofficial hackjob of a package for legacy GPU's from 2017. [a]: https://github.com/RadeonOpenCompute/ROCm/issues/1353 [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/rocblas-polaris-bin/

2 years, 5 months

Aur-requests search results for query "Deletion request for pkgbase"