> > imposes its own signal handling on users when the db is open
>
> Can turn that off since
> [56f49d7](https://github.com/rpm-software-management/rpm/commit/56f49d7f5af7c1c8a3eb478431356195adbfdd25)
> right?
API users turning off signal handling is not a solution, it's a problem in its
own r
Closed #1290 via #1291.
--
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/issues/1290#event-3485664720___
Rpm-maint mailing list
Rpm-mai
Merged #1291 into master.
--
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/1291#event-3485664711___
Rpm-maint mailing list
Rpm-mai
The other thing is that leaving regressions sitting in the tree with the notion
that somebody will fix it at some point is just not okay at all: that s***
*will* accumulate and cause hell to pay when the time to make the next release
comes. *Ideally* rpm should be release ready at any given comm
Is there a matching dnf options, like `--setopt=tsflags=noartifacts,nodocs`?
--
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/1274#issuecomment-650109484_
We need to come up with a plan how to deal with obsoleted crypto in rpm. MD5 is
practically gone long since and SHA1 is on its way out too, to the point that
it's not necessarily even possible to calculate these algorithms anymore (eg
MD5 on FIPS mode). Yet we still carry them in various more-or
Should've been in commit 07ed169da37db05773b608043db859fe2c362a8f
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/1293
-- Commit Summary --
* Add RPMTRANS_FLAG_NOARTIFACTS symbol to Python bindings
-- File Changes --
M
Merged #1293 into master.
--
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/1293#event-3486446227___
Rpm-maint mailing list
Rpm-mai
Bump. We sure would like to make progress on this so that rpm-ostree can start
supporting lua appropriately and not asking packagers to rewrite their
scriptlets.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://gith
