From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Obsolete package removal on x86_64 builder can race with multilib generation on i686 builder
Date: Thu, 22 Apr 2021 19:29:43 +0200 [thread overview]
Message-ID: <20210422172943.EQ9cwHMot0hFG2OQ_0CbgO0OnNy4EPZtsRIOShoX3z0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30420@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/30420#issuecomment-824728696
Comment:
> Given that the multilib repo is exclusively x86_64 packages, and your suggestion is to clean it by an unrelated architecture, this feels like an XBPS bug.
The problem is that i686 writes the repo. This comes down to the same issue with running the cleanup in a cronjob instead of part of the build pipeline, there is a inherent race condition between `xbps-create` creating the package and then `xbps-rindex` adding the packages to the repository index: While the `.xbps` packages for the specific architecture are not in the `-repodata`, they are considered obsolete.
1. The multilib repo is exclusively i686 packages with a x86_64 label.
2. The repository is not unrelated, its created and maintained by the i686 builder.
next prev parent reply other threads:[~2021-04-22 17:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 5:30 [ISSUE] Unresolved dependencies, missing libglapi-32bit linkert
2021-04-22 5:39 ` ericonr
2021-04-22 5:58 ` ericonr
2021-04-22 6:01 ` ericonr
2021-04-22 6:05 ` Obsolete package removal on x86_64 builder can race with multilib generation on i686 builder ericonr
2021-04-22 6:05 ` ericonr
2021-04-22 6:15 ` the-maldridge
2021-04-22 6:31 ` Oreo639
2021-04-22 9:53 ` linkert
2021-04-22 9:53 ` [ISSUE] [CLOSED] " linkert
2021-04-22 9:54 ` linkert
2021-04-22 10:35 ` Duncaen
2021-04-22 10:35 ` Duncaen
2021-04-22 10:52 ` Duncaen
2021-04-22 10:55 ` Duncaen
2021-04-22 17:29 ` Duncaen [this message]
2021-04-22 21:55 ` Oreo639
2021-04-22 21:58 ` Oreo639
2021-04-22 21:59 ` Oreo639
2021-04-22 22:02 ` Oreo639
2021-04-22 22:03 ` Oreo639
2021-04-22 22:03 ` Duncaen
2021-04-22 22:04 ` Oreo639
2021-04-25 16:52 ` ericonr
2021-04-25 16:52 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210422172943.EQ9cwHMot0hFG2OQ_0CbgO0OnNy4EPZtsRIOShoX3z0@z \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).