From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Some 32bit packages don't have the deps correctly rewritten to -32bit packages
Date: Wed, 13 Oct 2021 21:43:57 +0200 [thread overview]
Message-ID: <20211013194357.jH_5UeLxW6RShVufUQmRUWzJEVJcVRtkuus-ASe305M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23368@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/issues/23368#issuecomment-942659892
Comment:
qt5-concurrent-32bit bug occurs because `pre-pkg/05-prepare-32bit.sh` reads `shlib-provides` file generated by `pre-pkg/06-shlib-provides.sh`, thus subpackages processed earlier will never be rewritten to depend on `-32bit` versions of subpackages processed later.
Splitting pre-pkg phase to two phases, first with `06-shlib-provides.sh collect_sonames ${PKGDESTDIR}`, and second with `05-prepare-32bit.sh`, `06-shlib-provides.sh collect_sonames ${_destdir32}` would be needed. Replacing 32bit packages with multilib prefixes might be better alternative.
On pango: when rebuild, depends looks fine, despite of no relevant changes done recently. The thing I did was about whether -devel-32bit packages are generated, but didn't changed rewriting of deps.
pkgver: pango-devel-32bit-1.48.9_1
run_depends:
fribidi-devel-32bit>=0
harfbuzz-devel-32bit>=0
libXft-devel-32bit>=0
libthai-devel-32bit>=0
pango-xft>=1.48.9_1
pango-32bit>=1.48.9_1
pkgver: eudev-libudev-devel-32bit-3.2.10_1
run_depends:
eudev-libudev>=3.2.10_1
next prev parent reply other threads:[~2021-10-13 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23368@inbox.vuxu.org>
2020-09-29 22:26 ` ericonr
2021-09-30 4:16 ` dmarto
2021-09-30 4:17 ` dmarto
2021-09-30 4:19 ` dmarto
2021-09-30 4:24 ` dmarto
2021-10-07 8:02 ` dmarto
2021-10-13 5:27 ` ericonr
2021-10-13 5:28 ` ericonr
2021-10-13 19:43 ` Chocimier [this message]
2022-04-17 2:06 ` github-actions
2022-07-19 2:14 ` github-actions
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=20211013194357.jH_5UeLxW6RShVufUQmRUWzJEVJcVRtkuus-ASe305M@z \
--to=chocimier@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).