Now that we can, just define __file_lineno as an auxiliary macro that only does
any work in the rare case where an error or warning occurred. This saves an
enormous amount of huffing and puffing defining and undefining macros that are
not used at all in the normal paths, on every rpm startup
A bug is a bug. The database needs to be as robust as anything else in rpm,
security impact or no.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2211#discussioncomment-7495545
You are receiving this because you are subscribed to
I think @rhdesmond is in the situation of needing to process RPM databases that
come from untrusted container images. These databases might be malicious and
might try to exploit a bug in librpm to compromise the vulnerability scanner.
Such a bug would arguably be out of scope for librpm
I opened https://issues.redhat.com/browse/RHEL-15688
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1883#issuecomment-1795068331
You are receiving this because you are subscribed to this thread.
Message ID:
I suppose you care because of RHEL 9. If that's the case, I suggest you open a
RHEL 9 Jira.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1883#issuecomment-1795002390
You are receiving this because you are subscribed to this thread.
4.16 fell out of upstream support with the release of 4.18, about a year ago.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1883#issuecomment-1794994630
You are receiving this because you are subscribed to this thread.
Message ID:
A backport to 4.16 would be good too
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1883#issuecomment-1794989036
You are receiving this because you are subscribed to this thread.
Message ID:
`--macros` is problematic because it requires rewriting the entire path, most
of which is fairly critical to normal operation. Basically rpm must always
initialize itself with the macros from the same version, otherwise there's
weird stuff can happen. Which means, rpm from the host must
To recoup the very useful discussion and ideas from the now withdrawn draft PR:
To make things properly declarative, overriding sections should not be a part
of the plan at all. Instead there should be a way to declare independent build
options one by one. And the "auto" in the name needs to go.
`BuildSystem`, `BuildType`, and `BuildOption(stage)` makes sense to me.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2620#issuecomment-1794452101
You are receiving this because you are subscribed to this thread.
Message ID:
Ok, back to drawing board, now with a much nicer plan.
Thanks for the very valuable feedback + ideas!
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2620#issuecomment-1794447770
You are receiving this because you are subscribed to this
Closed #2620.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2620#event-10870320486
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mailing list
So... the conclusion from all the above rant is that there seems to be an
actual design wanting to come out, that would probably be:
`BuildOption(section):` to add options to the sections in a truly declarative
fashion, and as a shortcut for the most common section, `BuildOption:` without
the
For a real-world examle of the 2-3 benefit, a typical bcond case from Fedora
rpm.spec:
Existing spec:
```
%bcond_without libarchive
[...]
%if %{with libarchive}
BuildRequires: libarchive-devel
%endif
[...]
%prep
cmake \
[...]
%{!?with_libarchive:-DWITH_ARCHIVE=OFF}\
```
Using a section
For a comparison of various alternatives, nothing works better than a
real-world test (using an excerpt from Fedora xterm.spec):
1) Just override the section
```
%conf
%autobuild_conf \
--enable-meta-sends-esc \
--disable-backarrow-key \
--enable-exec-xterm \
15 matches
Mail list logo
