From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [ci skip] revbumps for including Rust dependency metadata using cargo-auditable
Date: Fri, 14 Apr 2023 00:59:01 +0200 [thread overview]
Message-ID: <20230413225901.n3-FV9UszklpSqSFooebBpJP3UCWknSEIZ8Q5Jp_2qs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43255@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2466 bytes --]
There's a closed pull request on the void-packages repository
[ci skip] revbumps for including Rust dependency metadata using cargo-auditable
https://github.com/void-linux/void-packages/pull/43255
Description:
#### Testing the changes
- I tested the changes in this PR: **briefly**
I have built a few of these packages, but not all. @paper42 has though.
This PR has revbumps for (nearly) all packages that haven't been changed since
the change to the build style that includes metadata on all `build_style=cargo`
packages by default.
There are three packages that don't get a revbump here, because they have active
PRs open that will likely be merged soon:
- https://github.com/void-linux/void-packages/pull/43254
- https://github.com/void-linux/void-packages/pull/43143
- https://github.com/void-linux/void-packages/pull/43175 (blocked on https://github.com/void-linux/void-packages/pull/43188)
@Shnatsel, you mentioned in https://github.com/rust-secure-code/cargo-auditable/issues/81#issuecomment-1304257246 that we should let you know when we're rebuilding the remainder of our packages, so that all¹ of our rust packages are shipped with dependency metadata embedded. That is being tackled now with this PR :)
A few more things got split out due to the `--locked` build style change:
- https://github.com/void-linux/void-packages/pull/43233 has now gotten nearly a dozen fixes that previously were in here as revbumps
- https://github.com/void-linux/void-packages/pull/43352
- https://github.com/void-linux/void-packages/pull/43350, although this isn't working yet, and will probably just stay as one of the non-auditable exceptions for the time being.
<!--
#### 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
-->
next prev parent reply other threads:[~2023-04-13 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 9:54 [PR PATCH] " jcgruenhage
2023-04-04 10:41 ` [PR PATCH] [Updated] " jcgruenhage
2023-04-08 18:16 ` jcgruenhage
2023-04-08 18:17 ` jcgruenhage
2023-04-13 5:13 ` classabbyamp
2023-04-13 10:12 ` [PR PATCH] [Updated] " jcgruenhage
2023-04-13 22:58 ` classabbyamp
2023-04-13 22:59 ` classabbyamp [this message]
2023-04-13 22:59 ` classabbyamp
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=20230413225901.n3-FV9UszklpSqSFooebBpJP3UCWknSEIZ8Q5Jp_2qs@z \
--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).