Project

General

Profile

Bug #2140

[build-support] breaks db-import-pkg

bill-auger - over 5 years ago - . Updated about 5 years ago.

Status:
fixed
Priority:
broken
Assignee:
oaken-source
% Done:

100%

Description

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'

Related issues

Related to libretools - Bug #2100: repo [build-support] needs to be added to the pacman.conf in i686 LibreChrootsnot-a-bug

Actions

History

#1

Updated by bill-auger over 5 years ago

  • Description updated (diff)
#2

Updated by GNUtoo over 5 years ago

Maybe it's available in arch32's build-support repository

#3

Updated by bill-auger about 5 years 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

#4

Updated by bill-auger about 5 years ago

  • Description updated (diff)
#5

Updated by bill-auger about 5 years ago

  • Related to Bug #2100: repo [build-support] needs to be added to the pacman.conf in i686 LibreChroots added
#6

Updated by bill-auger about 5 years ago

yep - this same bug hit a few months ago also - ive changed the topic of this BR to discuss whether the [build-support] repo should be enabled by default in i686 librechroots

#7

Updated by oaken-source about 5 years 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:

[9182]:     | ==> Moving packages from [build-support] to [extra]...
[9182]:     |   -> pkgname=libglvnd (i686)
[9182]:     |     pkgname=libglvnd (1.1.0-1.2)
[9182]:     | ln: failed to create symbolic link '/srv/repo/main/extra/os//i686/libglvnd-1.1.0-1.2>
[9182]:     | 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.

#8

Updated by oaken-source about 5 years ago

  • Priority changed from discussion to broken
  • Assignee set to oaken-source
  • Status changed from unconfirmed to in progress
#9

Updated by oaken-source about 5 years ago

  • Subject changed from should i686 [build-support] repo be enabled by default in librechroot to [build-support] breaks db-import-pkg
#10

Updated by oaken-source about 5 years 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/
#11

Updated by oaken-source about 5 years ago

  • % Done changed from 0 to 100
  • Status changed from in progress to fixed

Also available in: Atom PDF