Bug #3485
Housekeeping #3501: Drop [community{,-staging,-testing}], [staging], [testing] - import [core{-staging,-testing}], [extra{-staging,-testing}]
community.db is empty and packages are missing
0%
Description
Today I tried to install a new system from scratch, using pacstrap and arch-chroot. The base packages installed fine, but when I tried to install "networkmanager", I was not able to due to missing dependencie, such as "pcsclite".
The pcsclite package is in the community repo, but it seems like there's nothing there now. When I checked /var/lib/pacman/sync/community.db the file was just a few bytes long (practically empty).
My guess this problem comes because Arch has merged the community repo into the extra repo, as it is announced here:
https://archlinux.org/news/git-migration-completed/
History
Updated by bill-auger 12 months ago
- Assignee set to bill-auger
- Status changed from unconfirmed to in progress
yes, that is because arch has merged [community] into [extra]; but the repo server has not enough disk space to handle the migration automatically - until the packages are flowing again, some packages will be unavailable, and building/publishing new packages will be tricky - i have been prioritizing the essential rebuilds of gstreamer, python, and qt5 dependents, which are blocking most users from upgrading this week; but this problem is definitely known and will be corrected ASAP
Updated by dllud 12 months ago
Those whishing to upgrade python to 3.11 should be aware of this issue. Many python packages were in [community] and are now impossible to upgrade to the versions built upon python 3.11.
Better refrain from upgrading python until bill-auger finds a way to land all [community] packages into [extra].
Updated by bill-auger 12 months ago
i think all of the repos are working now - the sync with arch took almost 18 hours; but it appears to have completed successfully
just to note, ideally, if some package depends so strongly on a specific python
version, we should collect those on #3487 and add the version constraint like
pyqt5 has - that version constraint for pyqt5 is protecting most users now,
from any harm of upgrading python