In what has almost started to resemble a predictable annual release
schedule (and we didn't slip nearly as much as last year!), here comes
RPM 4.17.0. It's not quite what we initially planned, but when ever
anything is? There's quite a bit good stuff in there anyhow:
Highlights include:
*
No code changes since rc1 at all, just a version bump.
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/1769
-- Commit Summary --
* Preparing for rpm 4.17.0 final
-- File Changes --
M configure.ac (2)
M po/ar.po
I'm seeing a problem with executing "rpm -qf " (rpm 4.11.3)
When I do strace on that command and watch stat() calls, it shows very
different behavior depending on what I'm querying for.
If I do "rpm -qf /opt/pkg/mylib/1.100" it does exactly one stat() on the
directory I requested.
If I do "rpm
Merged #1769 into rpm-4.17.x.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1769#event-5252482952___
Rpm-maint mailing list
> Are there any known workarounds for rpm 4.11.3 (as it's a system version so
> I'm stuck with it in the office)?
> Maybe there is a patch that could be applied to 4.11.3 without a full upgrade
> (so I could convince our admins to apply it)?
RPM 4.11.3 is horribly insecure, so unless you are
@encukou commented on this pull request.
> @@ -76,47 +76,25 @@
%defined() %{expand:%%{?%{1}:1}%%{!?%{1}:0}}
%undefined() %{expand:%%{?%{1}:0}%%{!?%{1}:1}}
-# Shorthand for %{defined with_...}
+# Handle conditional builds.
+# (see 'conditionalbuilds' in the manual)
+#
+# Internally,
Been stuck on Fedora 32 for too long anyhow, but for debugedit we need
at least 35. Kick out a BDB remnant while at it.
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/1771
-- Commit Summary --
* Drag our CI to this decade
I got back to this; all issues except the nested `%{expand:..}` should be
addressed.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
