> Ehm, never mind that, this is widely used in Fedora specs. Sigh.
Yeah, I came to post this. It's just 180 packages outside of `%changelog`
though, so it's not impossible to fix.
--
Reply to this email directly or view it on GitHub:
@Vogtinator SSE is part of the baseline spec for x86-64. For 32-bit i386, this
was never properly enabled—there isn't a way to check that the SSE context
switching support has been wired up properly. Obviously, it doesn't matter at
this point because SSE software support is pervasive.
--
OSXSAVE only indicates that it's safe to use XGETBV, I think. In glibc, we mask
AVX etc. if XCR0 indicates it's not available:
https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/x86/cpu-features.c;h=978eb29f72550deeb237cc76c5cf78c153f0ffb6;hb=7b3d8558d92a123743699c577704aab4a2f3d949#l115
The current logic is based solely on CPUID. This is not correct because it does
not verify that the software stack (firmware/hypervisor/kernel) supports YMM
and ZMM registers. For that, it is necessary to read the XCR0 register using
the XGETBV instruction.
--
Reply to this email directly or
* Neal H. Walfield:
> Hi Florian,
>
> On Tue, 10 May 2022 12:04:52 +0200,
> Florian Weimer wrote:
>> * Neal H. Walfield:
>>
>> > There are two major constraints. Because rpm's OpenPGP API is public,
>> > it must be preserved until the next soname b
* Neal H. Walfield:
> There are two major constraints. Because rpm's OpenPGP API is public,
> it must be preserved until the next soname bump. And, the OpenPGP
> backend should be pluggable.
How is this plug-in mechanism supposed to work? Via RPM configuration
files?
Thanks,
Florian
* Colin Walters:
> On Wed, Dec 15, 2021, at 5:34 PM, Florian Weimer wrote:
>> * Chris Murphy:
>>
>>> Fedora 36 seems like a good time to do this. What do you think?
>>
>> It's a bit odd to locate a database under /usr that isn't pre-built and
>> inst
* Chris Murphy:
> Fedora 36 seems like a good time to do this. What do you think?
It's a bit odd to locate a database under /usr that isn't pre-built and
installed. I guess in theory there could be systems with a read-only
/usr out there that still allow installation of packages into /opt.
As far as I can see, `rpmfcApply` in `build/rpmfc.c` overwrites `%name` with
the subpackage name. It would be nice to be able to pass the current source
package name to a dependency generator as an argument. This will allow the
dependency generator not to run for certain source packages (e.g.,
@fweimer-rh commented on this pull request.
> @@ -105,6 +104,7 @@ function check_rpath() {
allow_ORIGIN=1
for j; do
+ lower=$(echo $j | grep -o "$2" | awk '{print tolower($0)}')
I think you can use the `,,` expansion operator here:
```
$ bash -c 'echo ${0,,*}' FOO
foo
```
Yes, `ET_REL` files can be skipped. If you are changing the file anyway, please
also add `-W` to the `readelf` invocations, so that the output does not get
truncated.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
It might also be nice to use `posix_spawn`, which can be implemented more
efficiently that the usual `fork`/`execve` sequence.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
This needs to be gated by an option, in case the command being run doesn't
expect any data on standard input and exits before completely reading all input.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@Conan-Kudo:
> Wouldn't that happen during the package build, rather than at runtime? It
> seems like that's a package build-time action.
I quoted the wrong part (Github doesn't seem to support automated quoting). I
was actually referring to this:
> I was thinking that it would be better to do
@bmwiedemann wrote:
> The alternative approach would be to change the macro generating them and
> first touch source .py files to set their date to $SOURCE_DATE_EPOCH so that
> this gets embedded in .pyc headers
I doubt that RPM can do this without delayed script execution because the
On 10/06/2016 09:10 AM, Pavlina Varekova wrote:
Extend %changelog to support full timestamps
The newly accepted date format is
Mon Jan 6 09:02:22 CEST 2016
(like output of "date" command). Original format "Mon Jun 6 2016" is still
supported.
I think it would be better to use ISO 8601 format
This protection is in the way if the --short-circuit -bb is used to
build packages for testing the effects of complex dependency changes
in a spec file.
diff --git a/build/build.c b/build/build.c
index 04b039c..1bcc436 100644
--- a/build/build.c
+++ b/build/build.c
@@ -265,7 +265,7 @@ static rpmRC
to decompression is spent
in SHA-256 hashing. The win for compression is obviously smaller
because compression itself takes more time.
--
Florian Weimer / Red Hat Product Security
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org
explicitly.
--
Florian Weimer / Red Hat Product Security
___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
19 matches
Mail list logo
