This is needed to allow changing autoinstalled header tag without actually
reinstalling package from file.
This may be useful in case you need to modify autoinstalled flag of package
which is updated in repository or removed from it
without actually updating or otherwise changing package.
Signed-off-by: Aleksei Nikiforov
---
lib/rpmte.c | 8
1 file changed, 8 insertions(+)
diff --git a/lib/rpmte.c b/lib/rpmte.c
index 40aa5e9..238c8b6 100644
--- a/lib/rpmte.c
+++ b/lib/rpmte.c
@@ -39,6 +39,7 @@ struct rpmte_s {
char * arch;
This is a bug fix and enhancement update to the stable 4.13.x branch. In
particular, several file trigger related bugs (previously addressed in
4.14.x) are fixed in this release. Additionally, support for
with/without/unless rich dependencies has been backported in this release.
The reason
Adding AUTOINSTALLED through a transaction like this is far more complex than
necessary, particularly since rpm itself does not need nor use that tag for any
purpose whatsoever.
There are already existing rpm interfaces to retrieve a header, add a tag, and
re-register the header.
What is the
> On Mar 28, 2018, at 11:52 AM, Aleksei Nikiforov
> wrote:
>
> Hi
>
> 28.03.2018 15:21, Jeff Johnson пишет:
>> Adding AUTOINSTALLED through a transaction like this is far more complex
>> than necessary, particularly since rpm itself does not need nor use that tag
Closed #422.
--
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/422#event-1546438120___
Rpm-maint mailing list
OK. thanks. Not a bug then. I can fix it in the spec
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
My understanding is that this was done as way to allow the package maintainer
to PREVENT debug processing. There are numerous cases, where the debugedit
split/strip behavior can trigger problems. So by using the executable flag, it
was easy to disable special processing for those items.
--
> On Mar 28, 2018, at 8:00 PM, Burhan Wani (burwani) wrote:
>
> Hello,
> I wanted to know why dual signing feature was removed from rpm 4.2 onwards.
> Is there a security risk to using rpm dual signing ? What would be the best
> way to implement dual signing in rpm.
>
Hello,
I wanted to know why dual signing feature was removed from rpm 4.2 onwards. Is
there a security risk to using rpm dual signing ? What would be the best way to
implement dual signing in rpm.
Regards,
Burhan Wani
___
Rpm-maint mailing list
Hi
28.03.2018 15:21, Jeff Johnson пишет:
Adding AUTOINSTALLED through a transaction like this is far more complex than
necessary, particularly since rpm itself does not need nor use that tag for any
purpose whatsoever.
There are already existing rpm interfaces to retrieve a header, add a
11 matches
Mail list logo