[gentoo-dev] Packages up for grabs
Due to retiring of the proxy maintainer, the following patches are up for grabs: acct-group/automx2 acct-group/milter-regex acct-group/ossec acct-user/automx2 acct-user/milter-regex acct-user/ossec acct-user/ossecm acct-user/ossecr app-antivirus/fangfrisch dev-python/pymilter mail-filter/amavisd-new mail-filter/milter-regex net-mail/automx2 net-mail/muchsync signature.asc Description: This is a digitally signed message part
[gentoo-portage-dev] Fixing EAPI 8 --enable-static once and for all
Attached a patch to finally fix https://bugs.gentoo.org/814380. When I opened the bug, it was clear that I intended to only disable static libtool archive building. Unfortunately, I hadn't done the necessary due diligence, and it turns out how we detect the "--enable-static" flag is overly broad and leads to a sizable number of false positives in EAPI 8. I have 937 EAPI 8 packages on my machine, and in 0 cases does my patch now produce static libraries where none were produced before, while it successfully reduces the annoying QA warnings on packages that don't use libtool or use the flag for different purposes: 1. packages that have an "off-target"/false-positive flag triggering the current logic: dev-libs/nspr-4.35 --enable-static-rtl Use the MSVC static runtime library sys-fs/lvm2-2.03.16 --enable-static_linkuse this to link the tools to their libraries 2. packages with a real --{dis,en}able-static flag, but with semantics that don't actually disable building of static-libs: dev-util/strace-5.19 --enable-static link strace statically sys-process/htop-3.2.1 --enable-static build a static htop binary [default=no] media-video/mkvtoolnix-71.1.0 --enable-static make a static build of the applications (no) --enable-static-qt link to static versions of the Qt library (no) dev-util/strace has a $(use_enable static) option, and the other two are default disabled. Hence in all of these cases, the patch does not change the build output. 3. packages with a --{dis,en}able-static flag that controls building of static libraries, but with a slightly different --help output that doesn't trigger the updated glob anymore: dev-libs/icu-72.1 --enable-static build static libraries default=no dev-libs/nettle-3.8.1 --disable-staticDo not build any static library net-print/cups-2.4.2 --enable-static install static libraries All of these packages pass a $(use_enable static-libs static) option, hence none of them would be affected by the missing --disable-static. With this extensive analysis, I believe this patch to be safe.
[gentoo-portage-dev] [PATCH] Make EAPI 8 `--disable-static` logic libtool-specific
* The intention has always been to only target `configure` scripts that use libtool, not just any script with a `--disable-static*` option. * libtool has been using the same `configure` format for at least the past 15 years (going back to libtool 1.5.22): 1. shared and static libraries enabled (the main use case): --enable-shared[=PKGS] build shared libraries [default=yes] --enable-static[=PKGS] build static libraries [default=yes] 2. shared libraries enabled and static libraries disabled: --enable-static[=PKGS] build static libraries [default=no] --enable-shared[=PKGS] build shared libraries [default=yes] 3. shared libraries disabled and static libraries enabled: --enable-shared[=PKGS] build shared libraries [default=no] --enable-static[=PKGS] build static libraries [default=yes] Bug: https://bugs.gentoo.org/814380 --- bin/phase-helpers.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bin/phase-helpers.sh b/bin/phase-helpers.sh index 2217e5a0b..6f691f6ff 100644 --- a/bin/phase-helpers.sh +++ b/bin/phase-helpers.sh @@ -655,8 +655,8 @@ econf() { fi if ___eapi_econf_passes_--disable-static; then - if [[ ${conf_help} == *--disable-static* || \ - ${conf_help} == *--enable-static* ]]; then + if [[ ${conf_help} == *--enable-shared\[=PKGS\]* && + ${conf_help} == *--enable-static\[=PKGS\]* ]]; then conf_args+=( --disable-static ) fi fi -- 2.38.1
[gentoo-dev] Last rites: multiple packages lacking Python 3.10 support
# Michał Górny (2022-11-18) # These packages still lack support for Python 3.10. In general, they # did not see any activity recently and either have no maintainer # or their respective maintainers did not reply to the bug. Many # of them do not have tests enabled or have unresolved test failures. # Removal on 2022-12-18. Tracker bug #823185. app-admin/ansible-cmdb app-arch/bloscpack app-backup/borgweb app-i18n/fcitx-sunpinyin app-i18n/ibus-kkc app-i18n/ibus-sunpinyin app-i18n/libkkc app-i18n/libkkc-data app-i18n/sunpinyin app-i18n/sunpinyin-data app-i18n/xsunpinyin app-portage/distpatch app-text/q-text-as-data app-vim/pydiction app-vim/vimoutliner dev-libs/aws-sdk-cpp dev-python/Rx dev-python/bert dev-python/flask-assets dev-python/libpy_simdjson dev-python/parallax dev-python/pytest-salt dev-python/requests_pkcs12 dev-python/slackclient dev-python/tvdb_api dev-python/webassets dev-python/ws4py dev-util/comparator dev-util/kdevelop-python dev-util/rosinstall_generator games-util/pyfa mate-extra/caja-hide media-gfx/netpaint media-plugins/mythplugins media-sound/marrie media-tv/tvnamer net-analyzer/carl net-im/skype-dbus-mock sci-libs/bmrblib sci-mathematics/relational sys-cluster/crmsh -- Best regards, Michał Górny