- Aur-requests - lists.archlinux.org

[aur-requests] [PRQ#32165] Deletion Request for libdnf
by notify＠aur.archlinux.org 05 Feb '22

05 Feb '22

larchunix [1] filed a deletion request for libdnf [2]: Adopted in community repo. [1] https://aur.archlinux.org/account/larchunix/ [2] https://aur.archlinux.org/pkgbase/libdnf/

1 1

[aur-requests] [PRQ#32164] Deletion Request for libcomps
by notify＠aur.archlinux.org 05 Feb '22

05 Feb '22

larchunix [1] filed a deletion request for libcomps [2]: Adopted in community repo. [1] https://aur.archlinux.org/account/larchunix/ [2] https://aur.archlinux.org/pkgbase/libcomps/

1 1

[aur-requests] [PRQ#32163] Deletion Request for dnf
by notify＠aur.archlinux.org 05 Feb '22

05 Feb '22

larchunix [1] filed a deletion request for dnf [2]: Adopted in community repo. [1] https://aur.archlinux.org/account/larchunix/ [2] https://aur.archlinux.org/pkgbase/dnf/

1 1

[aur-requests] [PRQ#32162] Deletion Request for libmodulemd
by notify＠aur.archlinux.org 05 Feb '22

05 Feb '22

larchunix [1] filed a deletion request for libmodulemd [2]: Adopted in community repo. [1] https://aur.archlinux.org/account/larchunix/ [2] https://aur.archlinux.org/pkgbase/libmodulemd/

1 1

[aur-requests] [PRQ#32191] Deletion Request for libx32-systemd
by notify＠aur.archlinux.org 05 Feb '22

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-systemd [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-'. • This package 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-systemd/

1 1

[aur-requests] [PRQ#32190] Deletion Request for libx32-tcl
by notify＠aur.archlinux.org 05 Feb '22

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-tcl [2]: Please delete libx32- 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-'. • This package 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-tcl/

1 1

[aur-requests] [PRQ#32189] Deletion Request for libx32-tk
by notify＠aur.archlinux.org 05 Feb '22

05 Feb '22

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/

1 1

[aur-requests] [PRQ#32188] Deletion Request for libx32-xz
by notify＠aur.archlinux.org 05 Feb '22

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-xz [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-'. • This package 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-xz/

1 1

[aur-requests] [PRQ#32187] Deletion Request for libx32-yajl
by notify＠aur.archlinux.org 05 Feb '22

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-yajl [2]: Please delete libx32- 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 (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-yajl/

1 1

[aur-requests] [PRQ#32186] Deletion Request for libx32-libldap
by notify＠aur.archlinux.org 05 Feb '22

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-libldap [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 (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-libldap/

1 1