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 | Kind | Status |
|---|---|---|---|---|---|---|---|
| Packages with invalid .BUILDINFO | 2022-05-18 | David Runge | While working on package validation for repod, the following packages were found to have invalid .BUILDINFO files. The invalid values most often consist of long obsoleted option keywords (see options subsection in https://man.archlinux.org/man/makepkg.conf.5#OPTIONS). In case there are questions, please reach out via mail or IRC. As we would like to be able to have a consistent and reproducible set of packages in the official repositories, the below packages need to be rebuilt to have stricter validation that can even be run on a daily basis. Rebuilds go straight to the stable repositories | 58 | 57 | Rebuild | Incomplete |
| Packages with invalid buildtoolver in .BUILDINFO | 2022-05-17 | David Runge | While working on validation for repod, the below packages have been found to have an invalid buildtoolver in their .BUILDINFO file (see https://man.archlinux.org/man/BUILDINFO.5), while having devtools as their buildtool (which is likely caused by not using the canonical devtools). To be able to provide strict validation for ingoing packages in the future, we would like to be able to ensure, that packages built with devtools are valid and that they can be rebuilt using the same tooling. To circumvent issues such as these, please only use devtools for building packages for the official repositories. This is likely going to become a fixed input requirement in the future. Rebuilds go straight to the stable repositories. | 255 | 254 | Rebuild | Incomplete |
| cuda 11.7 rebuild | 2022-05-12 | Sven-Hendrik Haase | Rebuilds to staging | 10 | 1 | Rebuild | Incomplete |
| libuhd 4.2.0 rebuild | 2022-05-05 | Antonio Rojas | Packages go to [staging] | 8 | 2 | Rebuild | Incomplete |
| go 1.18 | 2022-04-27 | Jelle van der Waa | Rebuild all golang packages to build with golang 1.18 to make our packages use the runtime improvements of the last X golang releases \o/ Packages go to the stable repositories directly. | 237 | 34 | Rebuild | Incomplete |
| Rebuild packages signed by 9437DD3815A7A9169E3D3946AFF5D95098BC6FF5 | 2022-03-06 | Evangelos Foutras | Access to the key was lost and a new key is in the process of being added to the keyring: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/147 | 33 | 12 | Rebuild | Incomplete |
| ffmpeg4.4 removal | 2022-02-18 | Maxime Gauduin | New todo to progressively phase out ffmpeg4.4, no rush, just something to keep in mind. Packages can go to extra/community directly. | 30 | 23 | Task | Incomplete |
| DRAFT: OpenSSL 3.0 | 2022-01-09 | Pierre Schmitz | **NOTE**: This is a draft and lists all packages linking to an openssl library. Check the mailing list about information when and how this massive rebuild starts. (openssl-3.0 was not yet pushed into [staging]) List was created like this: https://gist.github.com/pierres/6ed603a7934baec58d7742f1bc6362b6 Most packages should compile fine with OpenSSL 3. There might be deprecation warnings though. If packages still need openssl version 1.1: * Add a dependency to the new "openssl-1.1" package * Compile with e.g. CPPFLAGS+=" -I/usr/include/openssl-1.1" LDFLAGS+=" -L/usr/lib/openssl-1.1" Living documentation about packages that work and fail with OpenSSL 3: https://md.archlinux.org/s/t8HOyhNOi | 494 | 494 | Rebuild | Incomplete |
| OpenSSL 1.0 retirement | 2022-01-08 | Pierre Schmitz | OpenSSL 1.0 is not supported by the upstream project and does not receive any security fixes (at least not without a support contract). For obvious reasons is not advisable to use a security related library that has reach end if life. We should remove support for version 1.0 and any packages that depend on it. If possible these packages can be compiled against openssl-1.1 instead. | 5 | 4 | Task | Incomplete |
| PHP 7 retiredment | 2022-01-08 | Pierre Schmitz | php7 packages were introduced to ease the transition from 7 to 8 as PHP5-Code would throw warnings did not work with version 8 anymore: https://archlinux.org/news/php-80-and-php-7-legacy-packages-are-available/ php7 packages will be removed soon. This list contains packages that still depend on php7. Most actively maintained projects do support PHP 8 by now and we simply need to adjust dependencies. Packages that are no longer in active development should be removed from the repos; we might want to write a combined announcement for these. I did look into most of these packages; see https://lists.archlinux.org/pipermail/arch-dev-public/2022-January/030610.html for details. | 8 | 8 | Task | Incomplete |
| Remove python2 optdepends from package | 2021-12-20 | Morten Linderud | We are trying to remove python2, several packages has optional dependencies on python2 and they should be removed. If the script isn't ported to python yet, it might be an idea to drop the script completely. | 11 | 3 | Task | Incomplete |
| 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. | 250 | 49 | Task | 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 can support GTK3 or 4 just by tweaking the build configuration. Please check if it is possible to upgrade packages to GTK3 or GTK4 (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. A build-time gtk2 replacement that is a compatibility layer for using gtk3 is available as the "gtk2-compat" package. It may only work for some projects. Upgraded packages can be pushed directly to extra/community. Thank you! A list of notes about GTK2 packages can be found here https://md.archlinux.org/QfM91GeYSxeT6Y5VoJ5Hrw Feel free to expand. | 105 | 77 | Task | 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= | 265 | 42 | Task | 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/ | 203 | 5 | Task | Incomplete |
| hdf5 1.12.2 | 2022-05-15 | Bruno Pagani | As always, hdf5 requires everything linking to it to be rebuild even for patch updates (https://bugs.archlinux.org/task/60567). So here we go, packages go to [staging]. | 24 | 0 | Rebuild | Complete |
| jasper 3.0.3 rebuild | 2022-05-11 | Levente Polyak | packages go to staging. | 13 | 0 | Rebuild | Complete |
| Rebuild Todo List Poppler 22.05.0 update | 2022-05-05 | Andreas Radke | libpoppler.so.119 -> libpoppler.so.121 Please push packages to the staging repos. https://lists.freedesktop.org/archives/poppler/2022-April/015171.html https://lists.freedesktop.org/archives/poppler/2022-May/015227.html | 9 | 0 | Rebuild | Complete |
| podofo rebuild | 2022-05-04 | Jelle van der Waa | podofo rebuild | 5 | 0 | Rebuild | Complete |
| onednn 2.6 rebuild | 2022-04-29 | Sven-Hendrik Haase | Goes to staging, move directly to stable after last package built | 3 | 0 | Rebuild | Complete |
| Transmission DHT 0.27 rebuild | 2022-04-29 | Brett Cornwall | dht 0.27 has been released recently and addresses a minor bug [1]. Transmission upstream is en route to updating its included dep to 0.27 as well [2]. DHT 0.27 has been updated in [community], the transmission packages can be built from that. [1] https://github.com/jech/dht/commit/2b3a6364d0925b4e1eb14baa4f8f76a464fa331d [2] https://github.com/transmission/transmission/pull/3015/files | 1 | 0 | Rebuild | Complete |
| libglog 0.6.0 rebuild | 2022-04-27 | Antonio Rojas | Packages go to [staging] | 6 | 0 | Rebuild | Complete |
| dav1d 1.0.0 rebuild | 2022-04-25 | Levente Polyak | all packages go to [staging] | 11 | 0 | Rebuild | Complete |
| Rebuild packages signed by subkeys of 3DCE51D60930EBA47858BA4146F633CBB0EB4BF2 | 2022-04-22 | David Runge | The packages signed by (some) subkeys of 3DCE51D60930EBA47858BA4146F633CBB0EB4BF2 need to be rebuilt as they are expired. For reference see the related tickets [1][2]. Rebuilds go straight to the stable repositories. [1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/161 [2] https://bugs.archlinux.org/task/74538 | 0 | 0 | Rebuild | Complete |
| QEMU 7.0.0 packaging changes | 2022-04-21 | David Runge | With QEMU 7.0.0 the package has been turned into a split package. Previous functionality has been largely superseded by meta packages: * qemu -> qemu-desktop * qemu-headless -> qemu-base * qemu-headless-arch-extra/ qemu-arch-extra -> qemu-emulators-full The qemu package itself is now a virtual package, while qemu-common provides some shared functionality. The qemu-{base,desktop,full} meta packages provide qemu (in different feature richness) and also each provide all optdepends. The user mode and system emulators, as well as all hardware emulation and drivers, etc. can now be addressed granularly. Please adjust your packages according to the new setup (e.g. either by depending on specific system emulators or on one of the meta packages). Rebuilds go to [staging]/ [community-staging]. | 11 | 0 | Rebuild | Complete |
| quazip 1.3 | 2022-04-16 | Antonio Rojas | Pakages go to [staging] | 7 | 0 | Rebuild | Complete |
| Rebuild packages signed by 4B1DE545A801D4549BFD3FEF90CB3D62C13D4796 | 2022-04-08 | David Runge | As described in https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/148 we are about to retire the main signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7. For this to happen we need to rebuild all packages currently signed by packager keys which will be invalidated by that action. All package rebuilds go straight to the stable repositories. WARNING: No packager key addressed in this or any of the other rebuilds can be used for the rebuild! Affected packagers are hereby asked to refrain from using their packager key and create a new one instead: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/add-a-new-packager-key | 18 | 0 | Rebuild | Complete |
| Rebuild packages signed by 48C3B1F30DDD0FE67E516D16396E3E25BAB142C1 | 2022-04-08 | David Runge | As described in https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/148 we are about to retire the main signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7. For this to happen we need to rebuild all packages currently signed by packager keys which will be invalidated by that action. All package rebuilds go straight to the stable repositories. WARNING: No packager key addressed in this or any of the other rebuilds can be used for the rebuild! Affected packagers are hereby asked to refrain from using their packager key and create a new one instead: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/add-a-new-packager-key | 47 | 0 | Rebuild | Complete |
| Rebuild packages signed by CE0BDE71A759A87F23F0F7D8B61DBCE10901C163 | 2022-04-08 | David Runge | As described in https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/148 we are about to retire the main signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7. For this to happen we need to rebuild all packages currently signed by packager keys which will be invalidated by that action. All package rebuilds go straight to the stable repositories. WARNING: No packager key addressed in this or any of the other rebuilds can be used for the rebuild! Affected packagers are hereby asked to refrain from using their packager key and create a new one instead: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/add-a-new-packager-key | 92 | 0 | Rebuild | Complete |
| Rebuild packages signed by 69DA34D78FE0EFD596AC6D049D893EC4DAAF9129 | 2022-04-08 | David Runge | As described in https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/148 we are about to retire the main signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7. For this to happen we need to rebuild all packages currently signed by packager keys which will be invalidated by that action. All package rebuilds go straight to the stable repositories. WARNING: No packager key addressed in this or any of the other rebuilds can be used for the rebuild! Affected packagers are hereby asked to refrain from using their packager key and create a new one instead: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/add-a-new-packager-key EDIT: Withdrawed, see corresponding ticket. | 0 | 0 | Rebuild | Complete |
| Rebuild packages signed by 962855F072C7A01846405864FCF3C8CB5CF9C8D4 | 2022-04-08 | David Runge | As described in https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/148 we are about to retire the main signing key AB19265E5D7D20687D303246BA1DFB64FFF979E7. For this to happen we need to rebuild all packages currently signed by packager keys which will be invalidated by that action. All package rebuilds go straight to the stable repositories. WARNING: No packager key addressed in this or any of the other rebuilds can be used for the rebuild! Affected packagers are hereby asked to refrain from using their packager key and create a new one instead: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/add-a-new-packager-key | 123 | 0 | Rebuild | Complete |
| pdal 2.4 rebuild | 2022-04-02 | Sven-Hendrik Haase | Rebuild goes to staging | 7 | 0 | Rebuild | Complete |
| Electron 18 | 2022-04-02 | Nicola Squartini | Update packages to depend on explicit electron version, e.g. electron17. | 4 | 0 | Rebuild | Complete |
| CuDNN 8.3.3.40 rebuild | 2022-03-23 | Konstantin Gizdov | Rebuild CuDNN dependent packages. | 5 | 0 | Rebuild | Complete |
| Rebuild packages signed by C521846436D75A3294795B27B4360204B250F0D3 | 2022-02-24 | David Runge | The new packager key with the ID CAA1D2323A05219AA2F01AA4E642299183ED727E has been added to archlinux-keyring [1]. All packages still signed by the previous key (C521846436D75A3294795B27B4360204B250F0D3) need to be rebuilt, so that signatures on it can be revoked. Rebuilds go straight to the stable repositories. [1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/114 | 39 | 0 | Rebuild | Complete |
| Rebuild packages signed by 3E518BF2526FD1979E8AAE4965C110C1EA433FC7 | 2022-02-24 | David Runge | The new packager key with the ID 89E7B9331C4AE7D7FAF7D305C132293954BBE4AD has been added to archlinux-keyring [1]. All packages still signed by the previous key (3E518BF2526FD1979E8AAE4965C110C1EA433FC7) need to be rebuilt, so that signatures on it can be revoked. Rebuilds go straight to the stable repositories. [1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/119 | 111 | 0 | Rebuild | Complete |
| Rebuild packages signed by 2C118C620F02DB9AC1D0F9FA94DD2393DA2EE423 | 2022-02-24 | David Runge | The new packager key with the ID 0CADAACF70F64C654E131B3111675C743429DDEF has been added to archlinux-keyring [1]. All packages still signed by the previous key (2C118C620F02DB9AC1D0F9FA94DD2393DA2EE423) need to be rebuilt, so that signatures on it can be revoked. Rebuilds go straight to the stable repositories. [1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/120 | 28 | 0 | Rebuild | Complete |
| Rebuild packages signed by EB4F9E5A60D32232BB52150C12C87A28FEAC6B20 | 2022-02-24 | David Runge | The new packager key with the ID 56C3E775E72B0C8B1C0C1BD0B5DB77409B11B601 has been added to archlinux-keyring [1]. All packages still signed by the previous key (EB4F9E5A60D32232BB52150C12C87A28FEAC6B20) need to be rebuilt, so that signatures on it can be revoked. Rebuilds go straight to the stable repositories. [1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/122 | 18 | 0 | Rebuild | Complete |
| Rebuild packages signed by 355BDB97ED4724E6B3A450E7A3D9562A589874AB | 2022-02-24 | David Runge | The new packager key with the ID 209A36D43CE2E87DA861FC58539DFD48135182EF has been added to archlinux-keyring [1]. All packages still signed by the previous key (355BDB97ED4724E6B3A450E7A3D9562A589874AB) need to be rebuilt, so that signatures on it can be revoked. Rebuilds go straight to the stable repositories. [1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/125 | 27 | 0 | Rebuild | Complete |
| Rebuild packages signed by 3FFA6AB7B69AAE6CCA263DDE019A7474297D8577 | 2022-02-24 | David Runge | The new packager key with the ID 80247D99EABD3A4D1E3A1836E85B8683EB48BC95 has been added to archlinux-keyring [1]. All packages still signed by the previous key (3FFA6AB7B69AAE6CCA263DDE019A7474297D8577) need to be rebuilt, so that signatures on it can be revoked. Rebuilds go straight to the stable repositories. [1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/126 | 2 | 0 | Rebuild | Complete |
| Rebuild packages signed by DB2277BCD500AA3825610BDDDB323392796CA067 | 2022-02-24 | David Runge | The new packager key with the ID 531ECF3644A44FEA0B47DBCDE1E3CF0539448BFF has been added to archlinux-keyring [1]. All packages still signed by the previous key (DB2277BCD500AA3825610BDDDB323392796CA067) need to be rebuilt, so that signatures on it can be revoked. Rebuilds go straight to the stable repositories. [1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/128 | 52 | 0 | Rebuild | Complete |
| Rebuild packages signed by A9B6710D760F6617C530746EC847B6AEB0544167 | 2022-02-24 | David Runge | The new packager key with the ID A667E8A1B61D07A50FC430DF69DF1F2EB44B05BE has been added to archlinux-keyring [1]. All packages still signed by the previous key (A9B6710D760F6617C530746EC847B6AEB0544167) need to be rebuilt, so that signatures on it can be revoked. Rebuilds go straight to the stable repositories. [1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/129 | 8 | 0 | Rebuild | Complete |
| Rebuild packages signed by CB33B736591A9CA06098A9A5FCAC9CF5A6EE1209 | 2022-02-24 | David Runge | The new packager key with the ID DB5B4A9546601F945389C66940AC6F48D55AB11D has been added to archlinux-keyring [1]. All packages still signed by the previous key (CB33B736591A9CA06098A9A5FCAC9CF5A6EE1209) need to be rebuilt, so that signatures on it can be revoked. Rebuilds go straight to the stable repositories. [1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/131 | 6 | 0 | Rebuild | Complete |
| Rebuild packages signed by EC3CBE7F607D11E663149E811D1F0DC78F173680 | 2022-02-24 | David Runge | The new packager key with the ID D89FAAEB4CECAFD199A2F5E612C6F735F7A9A519 has been added to archlinux-keyring [1]. All packages still signed by the previous key (EC3CBE7F607D11E663149E811D1F0DC78F173680) need to be rebuilt, so that signatures on it can be revoked. Rebuilds go straight to the stable repositories. [1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/132 | 4 | 0 | Rebuild | Complete |
| Rebuild packages signed by 6EA3F3F3B9082632A9CBE931D53A0445B47A0DAB | 2022-02-24 | David Runge | The new packager key with the ID 25ACE777F62C5E5ACBF2C0474E532176DBAD6F47 has been added to archlinux-keyring [1]. All packages still signed by the previous key (6EA3F3F3B9082632A9CBE931D53A0445B47A0DAB) need to be rebuilt, so that signatures on it can be revoked. Rebuilds go straight to the stable repositories. [1] https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/134 | 11 | 0 | Rebuild | Complete |
| libgit2 1.4.1 | 2022-02-18 | David Runge | The upgrade to libgit2 >= 1.4.0 introduces a soname change: libgit2.so=1.3-64 -> libgit2.so=1.4-64 Rebuilds go to [staging]/ [community-staging] | 28 | 0 | Rebuild | Complete |
| libnfs 5.x rebuild | 2022-02-17 | Ike Devolder | rebuild packages linking with libnfs 5.x libnfs-5.0.1 can be found in community-staging When all are completed could someone with enough powers move the packages, since only kodi is in community and thus the only one I can move from this list | 5 | 0 | Rebuild | Complete |
| Split out python-pylibiio | 2022-02-17 | David Runge | With libiio 0.23.0-4 the Python bindings are split out to python-pylibiio. Any packages making use of the python bindings need to rely on python-pylibiio instead now. Changes go to [community-staging]. | 3 | 0 | Rebuild | Complete |
| Switch to python-installer from python-install | 2022-02-16 | Daniel M. Capella | The new installer 0.5.0 release provides the CLI interface, so now it's time to switch. https://installer.readthedocs.io/en/latest/cli/installer/ | 32 | 0 | Task | Complete |
| Adding explicit depends on libcanberra | 2022-02-10 | Jan Alexander Steffens | I want to remove the libcanberra dep from gtk3. In order to not break packages due to the missing transitive depend, we should add a direct dep on libcanberra for the packages that link to it. Packages can go straight to extra/community. For details, see https://bugs.archlinux.org/task/73517 This list was generated via: comm -23 <(sogrep all libcanberra) <(pactree -srud1 libcanberra | sort) | 17 | 0 | Task | Complete |