From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: virtualbox-ose: update to 7.1.4.
Date: Wed, 08 Jan 2025 17:33:34 +0100 [thread overview]
Message-ID: <20250108163334.AF9F621641@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-52910@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]
There's a merged pull request on the void-packages repository
virtualbox-ose: update to 7.1.4.
https://github.com/void-linux/void-packages/pull/52910
Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **yes**
- Checks passed locally
<!--
#### 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-glibc
#### Notes
- 015-no-update.patch is updated by myself, just trivial change, deleted patches are no longer needed
- adjusted template as vbox 7.1 is based on Qt6 now. As there is no `qt6-devel` package, I choose a larger `qt6-base-devel` in makedepends. Please let me know if there is a better option. `setuid` change is taken from [Artix](https://gitea.artixlinux.org/packages/virtualbox/commit/a349e60d4475af1623821689696814b294cad618#diff-9b9baac1eb9b72790eef5540a1685306fc43fd6c)
- Works quite well and tested for months.
next prev parent reply other threads:[~2025-01-08 16:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 10:01 [PR PATCH] " Vinfall
2024-11-18 1:51 ` Vinfall
2024-11-23 2:24 ` [PR PATCH] [Updated] " Vinfall
2024-12-23 5:03 ` Vinfall
2024-12-23 5:03 ` Vinfall
2024-12-23 5:33 ` [PR PATCH] [Updated] " Vinfall
2024-12-23 5:35 ` Vinfall
2024-12-26 4:09 ` [PR PATCH] [Updated] " Vinfall
2024-12-26 4:11 ` Vinfall
2025-01-05 11:34 ` [PR REVIEW] " return42
2025-01-05 23:22 ` classabbyamp
2025-01-05 23:23 ` classabbyamp
2025-01-06 6:26 ` Vinfall
2025-01-06 6:27 ` Vinfall
2025-01-06 6:28 ` [PR PATCH] [Updated] " Vinfall
2025-01-06 6:41 ` Vinfall
2025-01-06 6:47 ` [PR REVIEW] " Vinfall
2025-01-06 6:55 ` return42
2025-01-06 17:24 ` classabbyamp
2025-01-07 2:53 ` [PR PATCH] [Updated] " Vinfall
2025-01-07 2:59 ` [PR REVIEW] " Vinfall
2025-01-07 4:05 ` classabbyamp
2025-01-07 4:06 ` classabbyamp
2025-01-07 6:58 ` [PR PATCH] [Updated] " Vinfall
2025-01-07 7:02 ` [PR REVIEW] " Vinfall
2025-01-07 7:07 ` Vinfall
2025-01-07 8:05 ` return42
2025-01-07 11:08 ` return42
2025-01-08 2:56 ` Vinfall
2025-01-08 5:13 ` return42
2025-01-08 16:33 ` classabbyamp [this message]
2025-01-09 2:08 ` Vinfall
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=20250108163334.AF9F621641@inbox.vuxu.org \
--to=classabbyamp@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).