From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [ci skip] freecad: update to 0.20.1, update pyside to 5.15.5 and others related
Date: Sun, 28 Aug 2022 22:04:00 +0200 [thread overview]
Message-ID: <20220828200400.HJmuChQh0GP6wHuA3yaC1zeU9Vd0R25VuuxlcOKJ7Kk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38856@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
There's a closed pull request on the void-packages repository
[ci skip] freecad: update to 0.20.1, update pyside to 5.15.5 and others related
https://github.com/void-linux/void-packages/pull/38856
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### 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 (x86_64-musl) : **YES**
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64 (glibc): partial, since some packages can't be crossbuilded
#### Additional comments
* runtime test are OK, apart these related to pivy, see below
* superseeds PR #36356 regarding FreeCAD update
* about pivy: ~~some SIGSEGV on running FreeCAD when it's using Coin/pivy.
See https://github.com/coin3d/pivy/issues/98
However, this is affecting current FreeCAD binary packaging too.~~
~~Update: added patch on coin/pivy that fixed it~~
2nd update: bump pivy to 0.6.8 (just released) that includes this fix
ping @luzpaz @karl-nilsson @Piraty
prev parent reply other threads:[~2022-08-28 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 13:26 [PR PATCH] " yopito
2022-08-23 13:39 ` [PR PATCH] [Updated] " yopito
2022-08-24 13:41 ` yopito
2022-08-25 11:56 ` yopito
2022-08-26 7:01 ` [PR REVIEW] " Piraty
2022-08-26 8:39 ` [PR PATCH] [Updated] " yopito
2022-08-26 8:39 ` [PR REVIEW] " yopito
2022-08-28 20:04 ` Piraty [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=20220828200400.HJmuChQh0GP6wHuA3yaC1zeU9Vd0R25VuuxlcOKJ7Kk@z \
--to=piraty@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).