From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Fix dependencies so show-build-deps won't fail
Date: Tue, 09 Jan 2024 15:30:45 +0100 [thread overview]
Message-ID: <20240109143045.zx-JUVxorn_IqSz0gI3khPRWYFglk85QfSmG7y4-HZ4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47910@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2387 bytes --]
There's a merged pull request on the void-packages repository
Fix dependencies so show-build-deps won't fail
https://github.com/void-linux/void-packages/pull/47910
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
Split up from #47888 to avoid long CI in that PR.
This fixes dependencies in four packages and also fixes handling of `*-32bit` deps.
Before this change:
```
$ for p in bcachefs-tools brother-dcp197c-lpr gcc-multilib nvidia nvidia470 python3-QtPy python3-google-api-python-client qgis ; do ./xbps-src show-build-deps -K $p > /dev/null; done
=> ERROR: bcachefs-tools-1.3.6_1: dependency 'libudev-devel' does not exist!
=> ERROR: brother-dcp197c-lpr-1.1.3_6: dependency 'glibc-32bit' does not exist!
=> ERROR: gcc-multilib-12.2.0_2: dependency 'glibc-32bit' does not exist!
=> ERROR: nvidia-535.146.02_1: dependency 'glibc-32bit' does not exist!
=> ERROR: nvidia470-470.223.02_1: dependency 'glibc-32bit' does not exist!
=> ERROR: python3-QtPy-2.4.1_1: dependency 'font-liberation-ttf' does not exist!
=> ERROR: python3-google-api-python-client-2.80.0_2: dependency 'python3-Django' does not exist!
=> ERROR: qgis-3.34.1_1: dependency 'opencl-clhpp' does not exist!
```
After this change, there is no error. Also running `common/scripts/xbps-cycles.py` will do every package (Those 8 are all the failures I got).
Note that the errors for `python3-QtPy` and `python3-google-api-python-client` show only if #47888 is applied, since they are for checkdepends.
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2024-01-09 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 15:55 [PR PATCH] " tornaria
2024-01-09 14:30 ` ahesford [this message]
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=20240109143045.zx-JUVxorn_IqSz0gI3khPRWYFglk85QfSmG7y4-HZ4@z \
--to=ahesford@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).