From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] prepare-32bit hook fails for meta (sub)packages
Date: Thu, 12 Oct 2023 14:49:44 +0200 [thread overview]
Message-ID: <20231012124944.Hwo2keXSJUTDe3OJqi4Jgs9uDKJiJ3Qyhfquowu0mF0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46612@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]
Closed issue by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/46612
Description:
### Discussed in https://github.com/void-linux/void-packages/discussions/45987
<div type='discussions-op-text'>
<sup>Originally posted by **SpidFightFR** September 9, 2023</sup>
Hey, i got a question.
I made a pull request to update mesa to version 23.1.6 (https://github.com/void-linux/void-packages/pull/45635), when i was in vacation. Everything went well.
Though yesterday i made a PR for mesa 23.1.7 (https://github.com/void-linux/void-packages/pull/45974), and closed the previous PR, to not flood the Pull requests, but i saw that mesa 23.1.7 i686 build in the workflow failed so i guessed it wasn't ready yet.
So i reactivated the PR for 23.1.6 which we knew went correctly before i close it. But the same bug for the `Build packages (i686, i686, glibc, linux/386, 1)` workflows happens for no reason:
```
cp: cannot stat '/destdir//mesa-ati-dri-23.1.7/*': No such file or directory
=> ERROR: mesa-ati-dri-23.1.7_1: post-install_80-prepare-32bit: 'cp -a ${PKGDESTDIR}/* ${destdir32}/' exited with 1
=> ERROR: in hook() at common/hooks/post-install/80-prepare-32bit.sh:64
=> ERROR: in run_func() at common/xbps-src/shutils/common.sh:21
=> ERROR: in run_pkg_hooks() at common/xbps-src/shutils/common.sh:262
=> ERROR: in main() at common/xbps-src/libexec/xbps-src-doinstall.sh:66
```
(this is the error i got for 23.1.7, but 23.1.6 gets the same error)
I'm unsure why it happens, especially for 23.1.6 because, again, it worked before i closed it.
If someone can help, it would be much appreciated.</div>
prev parent reply other threads:[~2023-10-12 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 17:38 [ISSUE] " classabbyamp
2023-10-11 18:21 ` SpidFightFR
2023-10-12 12:49 ` sgn [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=20231012124944.Hwo2keXSJUTDe3OJqi4Jgs9uDKJiJ3Qyhfquowu0mF0@z \
--to=sgn@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).