[build-support] breaks db-import-pkg
the only provider of 'libgl' on i686 ('libglvnd') is not available with the default configuration - this makes a fresh install of 'xorg-server' not possible, as there is no provider of 'libgl'
Updated by bill-auger 3 months ago
- Priority changed from broken to discussion
- Subject changed from [libglvnd]: missing from i686 repo to should i686 [build-support] repo be enabled by default in librechroot
- Project changed from Packages to libretools
- Tracker changed from Packaging request to Porting
yes that seems to be at the heart of the issue - changing title
Updated by oaken-source 26 days ago
- Status changed from open to unconfirmed
- Project changed from libretools to dbscripts
- Tracker changed from Porting to Bug
I tracked down what is causing this. In the db-import log in winston, I see repeated entries like the following:
: | ==> Moving packages from [build-support] to [extra]... : | -> pkgname=libglvnd (i686) : | pkgname=libglvnd (1.1.0-1.2) : | ln: failed to create symbolic link '/srv/repo/main/extra/os//i686/libglvnd-1.1.0-1.2> : | ln: failed to create symbolic link '/srv/repo/main/extra/os//i686/libglvnd-1.1.0-1.2>
this happens because libglvnd has the same pkgname, pkgver and pkgrel in build-support, as it has in extra, so db-import thinks the package must have been moved, instead of realizing they are just identical.
looking here: https://archlinux32.org/packages/?q=libglvnd
we can see that the packages are indeed identical in their identifiers:
i686 i686/extra libglvnd 1.1.0-1.2 2018-10-07 13:50:06 2018-10-14 16:17:04 i686 i686/build-support libglvnd 1.1.0-1.2 2018-10-07 13:50:06 2018-11-13 17:45:34
this means the issue is with our import scripts, not upstream. How exactly our import scripts need to be fixed still needs to be seen.
Updated by oaken-source 25 days ago
I disabled the build-support repo in the db-import conf for arch32 (/etc/dbscripts/config.local.archlinux32) and removed build-support from the repos. This should fix the libglvnd issues going forward.
In the unlikely event, that we need packages from build-support in the future to build i686 packages, one can (temporarily) add the following to pacman.conf (in the chroot):
[build-support] Server = http://mirror.archlinux32.org/$arch/$repo/