- Aur-requests - lists.archlinux.org

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

05 Feb '22

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

1 1

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

05 Feb '22

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

1 1

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

05 Feb '22

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

1 1

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

05 Feb '22

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

1 1

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

05 Feb '22

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

1 1

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

05 Feb '22

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

1 1

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

05 Feb '22

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

1 1

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

05 Feb '22

MarsSeed [1] filed a deletion request for libx32-freetype2 [2]: My deletion request for this package has been accepted on 2022-01-29 23:26, yet it still exists. Why? [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/libx32-freetype2/

1 1

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

05 Feb '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#32238] Orphan Request for sailfishos-sdk-bin
by notify＠aur.archlinux.org 05 Feb '22

05 Feb '22

Louis [1] filed an orphan request for sailfishos-sdk-bin [2]: This package has been flagged out og date for more than 2 years [1] https://aur.archlinux.org/account/Louis/ [2] https://aur.archlinux.org/pkgbase/sailfishos-sdk-bin/

1 1