| Age | Commit message (Collapse) | Author |
|---|
|
Update done using:
```
git grep -l sys-libs/zlib dev-* | xargs sed -i -e s@sys-libs/zlib@virtual/zlib@g
git diff --name-only | xargs copybump
git diff --name-only | xargs grep -l PYTHON_COMPAT | xargs gpy-impl -@dead
pkgcheck scan --commits -c SourcingCheck,VisibilityCheck --exit error
```
Followed by manual revert in dev-python/zlib-ng where it accidentally
caught sys-libs/zlib-ng dependencies.
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
|
Result of running the command:
grep --include="*.ebuild" -r . -e 'KEYWORDS=.*[" ]sparc' -l | xargs ekeyword ~sparc
Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>
|
|
Add reminder to ebuild to update the git repo and make a new tag as
required instead of using filesdir: that's how we end up exceeding the
limit; things are very rarely cleaned up here!
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
As noted in 850d5e6b5cd12da2ad9bc37d3b21b87ef210c7f7, this is fine to do
these days. Combined with the LLVM_TARGET fixes from earlier today, this
should lead to a nice build-time improvement too.
Closes: https://bugs.gentoo.org/735154
Signed-off-by: Sam James <sam@gentoo.org>
|
|
We already depend on the right LLVM targets but without =, but we need
that as it's automagic otherwise. I'm not completely convinced we need
it here, but my aim is to avoid breaking things and then improve more
later.
Bug: https://bugs.gentoo.org/735154
Bug: https://bugs.gentoo.org/767700
Bug: https://bugs.gentoo.org/768267
Signed-off-by: Sam James <sam@gentoo.org>
|
|
Signed-off-by: Sam James <sam@gentoo.org>
|
|
When adding / updating `src_unpack` to handle verify-sig and (our) patch
tarballs, it was placed in its correct "position" in most ebuilds, however
these ebuilds were not updated at the time.
Ensure that all rust ebuilds have `src_unpack` immediately before `src_prepare`.
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
My previous fix didn't actually unpack tarballs at all.
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
When the patch tarballs were added the ebuilds were not updated to
ensure that only upstream-signed files are verified.
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
After discussion with upstream, reduce the number of `v`s passed to
of our `x.py` invocations. There is no documentation on why `-vvv` was
added but it's suspected to be development troubleshooting shrapnel.
`-vv` is retained for tests where the extra verbosity may actually be
useful, however for most cases `-v` is suitable as it includes the
invocation along with any warnings or errors; we probably don't need
thousands of backtraces or diagnostic messages.
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
files/ has been too big for a while now. Instead use the rust-patches
repository that was created to manage these patches.
No revbumps required - they were either done beforehand when we dropped
a bad patch _or_ are not required as the only additions are backported
build-time fixes (done in previous commits).
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
|
Rust upstream have identified issues with this patch relating to broken
x87 handling in LLVM.
Drop the patch and revbump all impacted revisions to ensure that this is
cleaned up.
Closes: https://www.github.com/gentoo/gentoo/pulls/40616
Signed-off-by: Matt Jolly <kangie@gentoo.org>
|
