- Aur-requests - lists.archlinux.org

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

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-libxml2 [2]: Please delete libx32- AUR packages: • Package has 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-libxml2/

1 1

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

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-libxft [2]: Please delete libx32- AUR packages: • Package has 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-libxft/

1 1

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

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-libxdmcp [2]: Please delete libx32- AUR packages: • Package has 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-libxdmcp/

1 1

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

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-libxcb [2]: Please delete libx32- AUR packages: • Package has 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-libxcb/

1 1

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

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-libxau [2]: Please delete libx32- AUR packages: • Package has 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-libxau/

1 1

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

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-libtirpc [2]: Please delete libx32- AUR packages: • Package has 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-libtirpc/

1 1

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

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-libssh2 [2]: Please delete libx32- AUR packages: • Package has 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-libssh2/

1 1

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

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-libidn [2]: Please delete libx32- AUR packages: • Package has 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-libidn/

1 1

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

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-mpdecimal [2]: Please delete libx32- AUR packages: • Package has 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-mpdecimal/

1 1

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

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-ncurses [2]: Please delete libx32- AUR packages: • Package has 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-ncurses/

1 1