A missing epoch is returned as NULL from rpmteE(), but the rpmdb matching code
can't handle NULL in any meaningful way currently. Arguably it should, but
that's a bigger topic...
Specifically convert a missing epoch to a "0" which matches the
behavior in mireSkip() to handle, adjust testcas
Repeating the same message verbatim is not terribly productive.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2178#issuecomment-1274252200
You are receiving this because you are subscribed to this thread.
Message ID: _
@pmatilai pushed 1 commit.
100c80e5b0171470201279244b07f2cdca895edd Add a handler for libselinux log
messages (RhBug:2123719, RhBug:2050774)
--
View it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2201/files/aa1078b1d38cdcfadda8ebf0c2a1a6a907eee12f..100c80e5b0171470201279244b
After sleeping a few nights on it: adding this callback is really the right
thing to do regardless of the audit log issue, any warnings/errors from
libselinux should be forwarded to rpmlog where our own API users have a chance
to discover them. That the pesky audit log gets dealt in the process
On Tue, 2022-04-26 at 05:24 -0700, Aleksandra Fedorova wrote:
> > Forget about Koji, Copr. Or OBS. Solve the task on a local level
> > first. I.e. in plain Mock on the command line.
>
> I agree that Mock is a reference implementation for this. But I'd say
> we need to have build system in mind her
@pmatilai commented on this pull request.
> +|`bzdio` | bzip2 ([flags](#bzip2-flags)) |
+|`xzdio` | xz ([flags](#xz-flags)) |
+|`lzdio` | lzma (legacy) ([flags](#lzma-flags)) |
+|`zstdio` | zstd ([flags](#zstd-flags))
I did not send that, I was asleep 7 hours ago! Anyway the code is already
checking for verbose mode here (and, I assume, elsewhere) so the decision has
already been made as to what qualifies as “verbose.” The real issue is the
forced `true` value of the flag with no way to change it.
--
Rep
Could `mkfifoat()` be emulated with `mknodat()` or `/dev/fd/`?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/#issuecomment-1275499958
You are receiving this because you are subscribed to this thread.
Message ID: __
