https://labs.parabola.nu/https://labs.parabola.nu/favicon.ico?15367742552019-01-17T19:57:37ZParabola Issue Trackerdbscripts - Bug #2140: [build-support] breaks db-import-pkghttps://labs.parabola.nu/issues/2140?journal_id=110472019-01-17T19:57:37Zbill-auger
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/11047/diff?detail_id=5217">diff</a>)</li></ul> dbscripts - Bug #2140: [build-support] breaks db-import-pkghttps://labs.parabola.nu/issues/2140?journal_id=110482019-01-18T14:31:14ZGNUtooGNUtoo@cyberdimension.org
<ul></ul><p>Maybe it's available in arch32's build-support repository</p> dbscripts - Bug #2140: [build-support] breaks db-import-pkghttps://labs.parabola.nu/issues/2140?journal_id=110652019-01-19T03:40:07Zbill-auger
<ul><li><strong>Priority</strong> changed from <i>broken</i> to <i>discussion</i></li><li><strong>Subject</strong> changed from <i>[libglvnd]: missing from i686 repo</i> to <i>should i686 [build-support] repo be enabled by default in librechroot</i></li><li><strong>Project</strong> changed from <i>Packages</i> to <i>libretools</i></li><li><strong>Tracker</strong> changed from <i>Packaging Request</i> to <i>Porting</i></li></ul><p>yes that seems to be at the heart of the issue - changing title</p> dbscripts - Bug #2140: [build-support] breaks db-import-pkghttps://labs.parabola.nu/issues/2140?journal_id=110662019-01-19T03:42:40Zbill-auger
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/11066/diff?detail_id=5234">diff</a>)</li></ul> dbscripts - Bug #2140: [build-support] breaks db-import-pkghttps://labs.parabola.nu/issues/2140?journal_id=112842019-02-09T01:06:34Zbill-auger
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-3 priority-default closed" href="/issues/2100">Bug #2100</a>: repo [build-support] needs to be added to the pacman.conf in i686 LibreChroots</i> added</li></ul> dbscripts - Bug #2140: [build-support] breaks db-import-pkghttps://labs.parabola.nu/issues/2140?journal_id=112852019-02-09T01:09:37Zbill-auger
<ul></ul><p>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</p> dbscripts - Bug #2140: [build-support] breaks db-import-pkghttps://labs.parabola.nu/issues/2140?journal_id=117942019-03-28T13:20:22Zoaken-source
<ul><li><strong>Status</strong> changed from <i>open</i> to <i>unconfirmed</i></li><li><strong>Project</strong> changed from <i>libretools</i> to <i>dbscripts</i></li><li><strong>Tracker</strong> changed from <i>Porting</i> to <i>Bug</i></li></ul><p>I tracked down what is causing this. In the db-import log in winston, I see repeated entries like the following:</p>
<pre>
[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>
</pre>
<p>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.</p>
<p>looking here: <a class="external" href="https://archlinux32.org/packages/?q=libglvnd">https://archlinux32.org/packages/?q=libglvnd</a></p>
<p>we can see that the packages are indeed identical in their identifiers:</p>
<pre>
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
</pre>
<p>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.</p> dbscripts - Bug #2140: [build-support] breaks db-import-pkghttps://labs.parabola.nu/issues/2140?journal_id=117982019-03-29T07:48:35Zoaken-source
<ul><li><strong>Priority</strong> changed from <i>discussion</i> to <i>broken</i></li><li><strong>Assignee</strong> set to <i>oaken-source</i></li><li><strong>Status</strong> changed from <i>unconfirmed</i> to <i>in progress</i></li></ul> dbscripts - Bug #2140: [build-support] breaks db-import-pkghttps://labs.parabola.nu/issues/2140?journal_id=117992019-03-29T07:48:57Zoaken-source
<ul><li><strong>Subject</strong> changed from <i>should i686 [build-support] repo be enabled by default in librechroot</i> to <i>[build-support] breaks db-import-pkg</i></li></ul> dbscripts - Bug #2140: [build-support] breaks db-import-pkghttps://labs.parabola.nu/issues/2140?journal_id=118002019-03-29T08:36:08Zoaken-source
<ul></ul><p>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.</p>
<p>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):</p>
<pre>
[build-support]
Server = http://mirror.archlinux32.org/$arch/$repo/
</pre> dbscripts - Bug #2140: [build-support] breaks db-import-pkghttps://labs.parabola.nu/issues/2140?journal_id=118012019-03-29T08:36:24Zoaken-source
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li><li><strong>Status</strong> changed from <i>in progress</i> to <i>fixed</i></li></ul>