Package Todo Lists
Todo lists are used by the developers when a rebuild of a set of packages is needed. This is common when a library has a version bump, during a toolchain rebuild, or a general cleanup of packages in the repositories. The progress can be tracked here, and completed todo lists can be browsed as well.
| Name | Creation Date | Creator | Description | Package Count | Incomplete Count | Status |
|---|---|---|---|---|---|---|
| Cleanup of python-setuptools dependency for console scripts | 2021-01-13 | Felix Yan | In recent versions of setuptools and Python, console-script entry points are using stdlib importlib by default, thus python-setuptools (provider of the pkg_resource module) is no longer a runtime dependency. Please check your package. If python-setuptools is only listed as dependency or optional dependency because of its console scripts (not in install_requires for other reasons, for example), please consider moving it to makedepends or removed, respectively. Packages go to stable repos directly. | 251 | 152 | Incomplete |
| GTK 2 EOL | 2020-12-20 | Alexander Rødseth | GTK 2 has reached its end of life: https://blog.gtk.org/2020/12/16/gtk-4-0/ Many of the listed packages, like GIMP and Xfce4, support versions later than GTK 2 in their development releases. Please check if it is possible to upgrade packages to GTK 3 or GTK 4 (which are pretty similar to each other, in terms of API), or drop the dependency on the gtk2 package, if it's an optional dependency. Just mark packages as complete if it's not feasible to patch, drop or upgrade them. Upgraded packages can be pushed directly to extra/community. Thank you! Update: Please don't push development releases or remove optional GTK 2 dependencies that are still needed. Use good judgement. Applying patches to support GTK 3 or 4 is also a possibility. The intention behind this TODO is to just look at the packages, and see if they can be upgraded. For instance, several of the packages I maintain could be upgraded just by enabling GTK3 when building. Packages that depend on wxgtk2 were also added to the list. | 195 | 160 | Incomplete |
| libxcrypt rebuild | 2020-08-20 | Bartłomiej Piotrowski | The new glibc in [testing] repository drops libcrypt.h header and corresponding static library. The upstream plans to eventually remove libcrypt from glibc tree in favor of a separate project libxcrypt; it's now available in [testing]. There's no breakage (famous last words) as glibc still ships libcrypt.so.1 for backwards compatibility, while libxcrypt package provides development headers and library with bumped soname version due to removal of the functions providing insecure hashes. You may need to add '#include <crypt.h>' if it was missing before as uninstd.h no longer provides a declaration of the crypt function. Packages go to [testing] until the toolchain is moved to [core]. | 111 | 33 | Incomplete |
| gst-plugins-good split | 2020-03-27 | Jan Alexander Steffens | Two plugins were split out from gst-plugins-good: gst-plugin-gtk gst-plugin-qmlgl Please check whether your packages need either and fix their deps. | 61 | 8 | Incomplete |
| Remove usage of makepkg subroutines from PKGBUILDs | 2020-01-17 | David Runge | The use of makepkg subroutines has been discussed in an old ticket [1]. In 2017 a warning about this was added to namcap and recently the wiki has been been updated to reflect this [2]. A list of packages (with false positives) can be found here [3]. Time for a cleanup! As a sidenote: If you find, that you are shadowing a test run in check() (e.g. `test || warning "Test is broken"`) please consider *why* you are doing this and whether only a subset of the tests can be run instead (e.g. because parts of the tests are integration tests anyways, that can not be run in makechrootpkg). [1] https://bugs.archlinux.org/task/43502 [2] https://wiki.archlinux.org/index.php/Arch_package_guidelines#Package_etiquette [3] https://pkgbuild.vdwaa.nl/?q=(msg%20%7Cmsg2%20%7Cwarning%20%7Cerror%20%7Cplain%20)&i=nope&files=.*%2Ftrunk%2FPKGBUILD&repos= | 244 | 33 | Incomplete |
| Conversion of programs that use Python 2 to Python 3 | 2019-12-23 | Chih-Hsuan Yen | Python 2.7 branch is going to be EOL'ed on 2020-01-01 [1]. A previous Todo [2] suggests to remove unused Python 2 libraries. In this Todo, I suggest to investigate programs that still use Python 2, either as runtime dependency or build/check dependencies, and see if it's possible to use Python 3 instead. Notes for some packages are available at https://wiki.archlinux.org/index.php/User:Yan12125/python3-conversion. Whenever you have changed a package to use Python 3, feel free to either move the corresponding row to the Done section or simply remove the row. Also, feel free to update notes if there are something new (e.g., a new Python 3-compatible version released, patches merged, new patches proposed, ...). Package can go directly into the repo; [staging] is not necessary. [1] https://devguide.python.org/ [2] https://www.archlinux.org/todo/die-python2-die/ | 202 | 46 | Incomplete |
| Fix unquoted variables which break building the package in certain scenarios | 2019-09-20 | Robin Broda | These packages have unquoted variables to paths which can contain spaces, this will lead to word-splitting during variable expansion and break the building of these packages. This is a packaging bug, fixes do not require a rebuild and can simply go to trunk. | 542 | 67 | Incomplete |
| Phasing out gconf and libglade | 2019-03-27 | Balló György | GConf was used in GNOME 2 as the settings storage daemon. It's deprecated since 2010 in favor of GSettings, and does not receive any fixes since 2013. Libglade is deprecated in favor of GtkBuilder since 2009, and does not receive any fixes since then. After a half year of the proposals[1][2], we try to get rid from these packages. This list contains all applications that depend on these libraries. If the package can be built without these libraries, do so. Otherwise, contact with upstream for a solution, or remove the package. Updated packages can go straight to extra/community. [1] https://lists.archlinux.org/pipermail/arch-dev-public/2018-September/029373.html [2] https://lists.archlinux.org/pipermail/arch-dev-public/2018-September/029378.html | 30 | 3 | Incomplete |
| Remove pepper-flash from optional dependencies | 2021-01-19 | Evangelos Foutras | Flash Player reached end-of-life on December 31, 2020. Before dropping it from [extra], we have to remove it from a few browsers' optional dependencies. | 3 | 0 | Complete |
| PHP 8 compatibility | 2021-01-18 | Pierre Schmitz | The PHP modules for PHP 8 are now rebuilt and a php7 package is available for software that is not compatible yet. Please check compatibility with your packages * If your package works fine with PHP 8 (e.g. documented by upstream or tested by yourself) just mark it as complete; a rebuild is not needed. * If you know your package will not work with PHP 8 update its dependency to the php7 packages. Make sure to update config or scripts as the php7 biaries have the "7" postfix. E.g. /usr/bin/php7 or /usr/bin/php-fpm7 Updates to these packages should be moved to [testing] or [community-testing] | 27 | 0 | Complete |
| libplacebo 3.104.0 soname bump | 2021-01-13 | Levente Polyak | libplacebo 3.104.0 has soname 104 which should be built in staging | 3 | 0 | Complete |
| libdav1d.so.5 soname bump | 2021-01-13 | Levente Polyak | libdav1d has a new soname version .5 which requires rebuilds put into staging and built against dav1d 0.8.1-1 | 6 | 0 | Complete |
| podofo rebuild | 2021-01-10 | Jelle van der Waa | New podofo release bumps the soname and requires a rebuild, rebuilds go into [staging]. | 5 | 0 | Complete |
| PHP-8 and PHP7 module rebuild | 2021-01-08 | Pierre Schmitz | The php package has been updated to version 8. For the meantime we keep version 7 packaged as php7. Both packages are available in [staging]. php7 will dropped once all the scripts we provide (and the ecosystem in general) is compatible with version 8. Module should be recompiled for version 8 and if desired provided for php7 as well. Let me know if you have to drop the module for one version due to incompatibility. If you like to provide both versions a split package might be the easiest approach. For an example see APCu: https://github.com/archlinux/svntogit-packages/blob/packages/php-apcu/trunk/PKGBUILD Once all rebuilds are done the packages are moved to [testing] to check those that depend on php. | 28 | 0 | Complete |
| libopenraw 0.3.0 release | 2020-12-19 | Frederik Schwan | Rebuild for libopenraw 0.3.0. libopenraw-0.3.0 is in [community-staging]. | 2 | 0 | Complete |
| Electron 11 | 2020-11-21 | Nicola Squartini | Push to [community-staging]. | 7 | 0 | Complete |
| Remaining rebuilds for Python 3.9 | 2020-11-13 | Evangelos Foutras | These are the last remaining packages that need a rebuild for Python 3.9. They either fail to build or have test failures in check(). If a package in this list also exists in staging, it does not mean it's done; if it's marked as failed on [1] then it likely has test failures. (In this case, the staging package was built with --nocheck to satisfy other packages' checkdeps and avoid dependency cycles, and therefore needs a proper rebuild.) Please commit a fix to /trunk and click on the failed task on [1] to retry it. You don't need to bump pkgrel as the automatic rebuilder does that before building and pushing a new package. Build logs of the failed rebuilds are available on either [1] or [2]. loqs has also shared some notes about failed builds [3], which might be useful for some of these failures. Some packages might require fixes to one or more of their dependencies that have already been rebuilt. (For example, python-libcst's backtrace indicates that the actual issue lies in python-typing_inspect.) [1] https://rebuilds.foutrelis.com/ [2] https://pkgbuild.com/~foutrelis/failed-py39-builds/ [3] https://gist.github.com/loqs/8bdcf882d63155cc353197c171862ba5 | 105 | 0 | Complete |
| gdk-pixbuf-xlib split | 2020-11-09 | Jan Alexander Steffens | gdk-pixbuf2 2.42.0 moved the deprecated libgdk_pixbuf_xlib-2.0.so to a separate project. A new package gdk-pixbuf-xlib is available in [staging] that contains libgdk_pixbuf_xlib-2.0.so. Please update your depends and push to staging. | 7 | 0 | Complete |
| wlroots 0.12.0 | 2020-11-08 | Maxim Baz | New wlroots release is in community-staging Please check your packages and push a rebuild or a new version when available. Thanks :) | 4 | 0 | Complete |
| imagemagick 7.0.10.37 rebuild | 2020-11-07 | Antonio Rojas | libMagickCore-7.Q16HDRI.so.7 -> 8 libMagickWand-7.Q16HDRI.so.7 -> 8 | 15 | 0 | Complete |
| glslang 11 rebuild | 2020-11-04 | Sven-Hendrik Haase | Rebuilds go to staging. | 6 | 0 | Complete |
| hidapi now optdepends on libusb and libudev | 2020-11-01 | Filipe Laíns | Hey! hidapi used to have an hard dependency on libusb, but as it is only required when using the libusb backend (libhidapi-libusb.so) I've made it optional. hidapi 0.10.0 also gained a dependency for the hidraw backend. It now needs libudev. Please check which backend your package uses. If it uses the libusb one (libhidapi-libusb.so), please add a hard dependency on libusb. If it uses the hidraw one (libhidapi-hidraw.so), please add a hard dependency on libudev.so. If you have any questions feel free to reach out to me on IRC or email. Cheers! Filipe | 14 | 0 | Complete |
| fmt ABI breakage | 2020-10-28 | Maxime Gauduin | fmt 7.1.0 changed its ABI without bumping the soname, so let's rebuild, packages go directly to extra/community https://github.com/fmtlib/fmt/issues/1961 | 10 | 0 | Complete |
| net-snmp 5.9 rebuild | 2020-10-27 | Felix Yan | The upgrade to net-snmp 5.9 introduces soname bumps: usr/lib/libnetsnmp.so.35 -> libnetsnmp.so.40 usr/lib/libnetsnmpagent.so.35 -> libnetsnmpagent.so.40 usr/lib/libnetsnmphelpers.so.35 -> libnetsnmphelpers.so.40 usr/lib/libnetsnmpmibs.so.35 -> libnetsnmpmibs.so.40 usr/lib/libnetsnmptrapd.so.35 -> libnetsnmptrapd.so.40 usr/lib/libsnmp.so.35 -> libsnmp.so.40 Rebuilds go to [staging]/[community-staging] respectively. | 15 | 0 | Complete |
| Python modules including site-packages/tests/ | 2020-10-22 | Morten Linderud | Some packages doesn't exclude their test directory from packaging. As these directories contains similar or sometimes the same files they are bound to cause package conflicts. Either rm the directory from the package, or patch `setup.py` as shown in the example patch, and push to stable repositories. https://github.com/clueboard/milc/commit/e115b711253500b51a4b4478ba9d30c317f19856 https://bugs.archlinux.org/task/68380 | 7 | 0 | Complete |
| Remove libjpeg from depends/makedepends/optdepends and use shared object dependency | 2020-10-18 | David Runge | The libjpeg-turbo package provides libjpeg.so. In the past this has been reflected by a "libjpeg=major.minor.patch" entry in the provides array. This approach requires manual intervention in the libjpeg-turbo PKGBUILD and is less useful than a shared object provides as that automatically exposes the shared object version [1]. The libjpeg-turbo package now has "libjpeg.so" and "libturbojpeg.so" in the provides array, which makes the entry for "libjpeg=major.minor.patch" obsolete. Please replace a "libjpeg-turbo" or "libjpeg" in depends with a shared object depends [2] (if your package in fact links against it), and a "libjpeg" in makedepends or optdepends with "libjpeg-turbo". Afterwards push a rebuilt package to the respective stable repository. Note in regards to depends array: * If you would like to only have the respective shared object in the eventual depends array, add "libjpeg-turbo" to makedepends and add "libjpeg.so" (or "libturbojpeg.so" depending on your requirement) in the package() function (e.g. by `depends+=('libjpeg.so')`). * If you would like to have both the package and the shared object in the depends array, add "libjpeg-turbo" first and then the shared object. Note in regards to the package list in the TODO: All packages that directly link against libjpeg.so or libturbojpeg.so are considered. If your package does not yet have a direct dependency on libjpeg-turbo's shared objects but is in the list, please add it, as transitive dependencies are discouraged [2]. If you are unsure of what this all means, please get in touch via mail or IRC! :) [1] https://wiki.archlinux.org/index.php/Arch_package_guidelines#Package_relations [2] https://wiki.archlinux.org/index.php/Arch_package_guidelines#Package_dependencies | 0 | 0 | Complete |
| Remove legacy libusbx dependency | 2020-10-17 | David Runge | The current libusb in [testing] dropped the legacy provides for libusbx. Please rebuild and push your packages to the respective stable repositories while depending on libusb or even better libusb-1.0.so [1] instead. [1] https://wiki.archlinux.org/index.php/Arch_package_guidelines#Package_dependencies | 5 | 0 | Complete |
| libgit2 1.1.0 | 2020-10-15 | David Runge | The upgrade to libgit2 1.1.0 introduces a soname bump: libgit2.so=1.0-64 -> libgit2.so=1.1-64 Rebuilds go to [staging]/[community-staging] respectively. | 11 | 0 | Complete |
| LLVM 11 | 2020-10-12 | Evangelos Foutras | libLLVM-10.so -> libLLVM-11.so libclang.so.10 -> libclang.so.11 libclang-cpp.so.10 -> libclang-cpp.so.11 I added llvm10 for bootstrapping the rust/ldc rebuilds, by rebuilding them in staging to use llvm10{,-libs} and then reverting back to regular llvm. llvm10 can also be used for packages not ported to LLVM 11, as long as they don't also use other LLVM components like clang. | 51 | 0 | Complete |
| cuda 11.1 rebuild | 2020-09-28 | Konstantin Gizdov | CUDA 11.1 is officially considered the first production release of CUDA 11 after the General Availability version of 11.0.3. CUDA 11.1 seems to introduce some significant changes compared to CUDA 11.0, e.g. it now supports GCC 10 as host compiler. Also, notably, it is build upon driver 455.23.05 version, which is not available for public consumption yet, but official release notes say it should work fine with any version above 455.23. There is also a new PTX compiler static library and support for Ampere based cards (compute capability 8.6). IMPORTANT: we should try to retire gcc9 and ensure everything still works. | 12 | 0 | Complete |
| GNOME 3.38 | 2020-09-27 | Jan Alexander Steffens | GNOME 3.38 has entered [staging]. The following changes require rebuilds: libhandy: libhandy-0.0.so.0 -> libhandy-1.so.0 libhandy0 now contains the old library. Upgrade your packages to libhandy 1 or move the dep to libhandy0. evolution-data-server: libedataserver-1.2.so.24 -> libedataserver-1.2.so.25 tepl: libtepl-4.so.0 -> libtepl-5.so.0 vala: libvala-0.48.so.0 -> libvala-0.50.so.0 (et valadoc) tracker3: libtracker-sparql-3.0.so.0 tracker still contains the old library, but its miners are no longer automatically started. Check if your package can be upgraded to tracker3 or if tracker support can reasonably be removed, otherwise leave as-is. mutter: libmutter-6.so.0 -> libmutter-7.so.0 sysprof: libsysprof-capture-3.a -> libsysprof-capture-4.a | 27 | 0 | Complete |
| libupnp 1.14.0 | 2020-09-25 | David Runge | The upgrade to libupnp 1.14.0 introduces a (or rather several) soname bump(s). While mpd and vlc seem to build fine with it, amule and jami-daemon are (out-of-the-box) only compatible with libupnp <= 1.12.1. For the latter case libupnp1.12 has been added to [community-staging]. However, note that the libraries and directories have been renamed to prevent name conflicts! If you can make amule and/or jami-daemon compatible with the latest libupnp, all the better! Rebuilds go to [staging]/[community-staging]. | 9 | 0 | Complete |
| bullet 3.05 rebuild | 2020-09-24 | Sven-Hendrik Haase | To staging | 4 | 0 | Complete |
| pdal 2.2.0 | 2020-09-11 | Sven-Hendrik Haase | Rebuilds go to [staging]. | 4 | 0 | Complete |
| libwebsockets 4.1.0 rebuild | 2020-09-07 | David Runge | The upgrade to libwebsockets 4.1.0 introduced a soname bump. Rebuilds go to community-staging. | 4 | 0 | Complete |
| Electron 10 | 2020-08-27 | Nicola Squartini | Push to [community-staging]. I've added the electron9 in [community-staging] package for those who need it. | 10 | 0 | Complete |
| opusfile 0.12 rebuild | 2020-08-16 | Alexander Rødseth | Rebuilds go to staging. Thanks! | 9 | 0 | Complete |
| openvdb 7.1 rebuild | 2020-08-14 | Sven-Hendrik Haase | Rebuilds go to staging. | 3 | 0 | Complete |
| Electron 9.2 | 2020-08-07 | Nicola Squartini | There should be no breaking changes. If rebuild is needed push to [community-staging]. | 7 | 0 | Complete |
| fmt, libebml, libmatroska and x264 rebuild | 2020-08-04 | Maxime Gauduin | All libs had a soname bump and some packages are overlapping so let's do it all at once. | 25 | 0 | Complete |
| Lua 5.4 rebuild | 2020-06-30 | Anatol Pomozov | Lua 5.4 is released a and we need to rebuild lua specific packages. lua 5.4 is in [staging]. There is also lua53 package in [testing] one can use if the package is not compatible with 5.4. | 64 | 0 | Complete |
| removal of "xorg-font-utils" transitional package | 2020-06-26 | Andreas Radke | We are going to drop the transitional package "xorg-font-utils" together with the ToDo list to remove unneeded fontconfig and xorg-mkfontscale dependencies from font packages. Please remove "xorg-font-utils" from all PKGBUILDs and replace with the packages that were covered by its dependencies where needed: xorg-bdftopcf / xorg-mkfontdir / xorg-mkfontscale / xorg-font-util These should only be used in "makedepends" where possible. Packages can go to extra/community. | 37 | 0 | Complete |
| remove unneeded fontconfig and xorg-mkfontscale dependencies from font packages | 2020-06-26 | Eli Schwartz | These packages only provide font data files, but depend on programs that make use of the fonts. This is a legacy of the pre-hook days, when each package included a post_upgrade scriptlet that ensured the fontconfig/xorg cache was rebuilt. The dependencies should be removed, and if/when the fontconfig or xorg-mkfontscale packages are installed, they will build the entire font cache from scratch. Be sure to also remove the xorg-font-utils dummy package if it is still a dependency. See https://bugs.archlinux.org/task/66012 | 48 | 0 | Complete |
| Remove .doctrees from installed files for reproducible builds | 2020-06-22 | Jelle van der Waa | The .doctrees file is generated by sphinx are cached files used when developing documentation so that sphinx does not have to reparse all markdown files. They shouldn't be packaged as they are not required and they lead to the package being unreproducible as the pickled files contain unreproducible data. | 8 | 0 | Complete |
| Perl 5.32.0 rebuild | 2020-06-21 | Florian Pritz | packages go to staging. upstream release notes: https://metacpan.org/pod/release/XSAWYERX/perl-5.32.0/pod/perldelta.pod EDIT: we will rebuild this list automatically with Evangelos' rebuilder. | 532 | 0 | Complete |
| python-pillow 7 | 2020-06-15 | Kyle Keen | Pillow 7 dropped python2 support (yay!), and tweaked the API in a reverse incompatible fashion: https://pillow.readthedocs.io/en/stable/releasenotes/ Please test if your package works (or builds for makedeps, or passes for checkdeps) with python-pillow-7, which is in [staging]. If it does work, check it off and do nothing. If it doesn't work, either patch for pillow 7 (and push to [staging]), or tweak the imports from `PIL` to `PIL6` and change the dependency to python-pillow6 (and push to [community]). Python2 packages require no changes. | 46 | 0 | Complete |
| jsoncpp 1.9.3 soname change | 2020-06-13 | Levente Polyak | packages to to staging | 10 | 0 | Complete |
| cuda 11 rebuild | 2020-06-08 | Sven-Hendrik Haase | cuda 11 is out. It's technically an rc but nvidia is kinda so-so about rc hygiene. Important things to note: - compute_80 and sm_80 have been added so add those targets if applicable. - sm_30 and sm_32 have been dropped so remove those from your targets. - sm_52 is now the default target. - Now officially uses gcc 9 as its main compiler. Rebuilds go to testing and will stay there for a good long while. https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html | 11 | 0 | Complete |
| Move from `go-pie` dependency to `go` | 2020-06-02 | Morten Linderud | Yo. This is the followup after the go-pie removal. All of the listed packages should still have some dependency on go-pie. Please move these packages to the go, and utilize the new guidelines to achieve PIE and RELRO binary hardening where applicable. https://wiki.archlinux.org/index.php/Go_package_guidelines | 94 | 0 | Complete |
| x265 3.4 rebuild | 2020-06-02 | Maxime Gauduin | Same as usual, I'll probably have time to do everything. | 9 | 0 | Complete |