- Aur-requests - lists.archlinux.org

[aur-requests] [PRQ#31774] Deletion Request for libx32-util-linux
by notify＠aur.archlinux.org 30 Jan '22

30 Jan '22

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

1 1

[aur-requests] [PRQ#31773] Deletion Request for libx32-libdbus
by notify＠aur.archlinux.org 30 Jan '22

30 Jan '22

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

1 1

[aur-requests] [PRQ#31772] Deletion Request for libx32-freetype2
by notify＠aur.archlinux.org 30 Jan '22

30 Jan '22

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

1 1

[aur-requests] [PRQ#31771] Deletion Request for libx32-openssl
by notify＠aur.archlinux.org 30 Jan '22

30 Jan '22

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

1 1

[aur-requests] [PRQ#31770] Deletion Request for libx32-glib2
by notify＠aur.archlinux.org 30 Jan '22

30 Jan '22

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/

1 1

[aur-requests] [PRQ#31769] Deletion Request for libx32-fontconfig
by notify＠aur.archlinux.org 30 Jan '22

30 Jan '22

MarsSeed [1] filed a deletion request for libx32-fontconfig [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. [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/libx32-fontconfig/

1 1

[aur-requests] [PRQ#31768] Deletion Request for libx32-harfbuzz
by notify＠aur.archlinux.org 30 Jan '22

30 Jan '22

MarsSeed [1] filed a deletion request for libx32-harfbuzz [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. [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/libx32-harfbuzz/

1 1

[aur-requests] [PRQ#31767] Deletion Request for libx32-icu
by notify＠aur.archlinux.org 30 Jan '22

30 Jan '22

MarsSeed [1] filed a deletion request for libx32-icu [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. [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/libx32-icu/

1 1

[aur-requests] [PRQ#31766] Deletion Request for libx32-bzip2
by notify＠aur.archlinux.org 30 Jan '22

30 Jan '22

MarsSeed [1] filed a deletion request for libx32-bzip2 [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. [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/libx32-bzip2/

1 1

[aur-requests] [PRQ#31765] Deletion Request for libx32-zlib
by notify＠aur.archlinux.org 30 Jan '22

30 Jan '22

MarsSeed [1] filed a deletion request for libx32-zlib [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. [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/libx32-zlib/

1 1