Re: [Rpm-maint] [rpm-software-management/rpm] Revert "Allow packagers to specify individual scriptlets as critical" (#700)

2019-05-14 Thread Panu Matilainen
Actually it's not this patch that should be discussed but the behavior overall, but that belongs to a ticket or a PR implementing something new. -- 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

Re: [Rpm-maint] [rpm-software-management/rpm] Revert "Allow packagers to specify individual scriptlets as critical" (#700)

2019-05-14 Thread Panu Matilainen
Merged #700 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/700#event-2339406668___ Rpm-maint mailing list Rpm-maint

Re: [Rpm-maint] [rpm-software-management/rpm] Revert "Allow packagers to specify individual scriptlets as critical" (#700)

2019-05-10 Thread Panu Matilainen
The patch aside (which I believe is necessary at any rate), discussion on what to do about this would be welcome. RHEL carries a patch to enable a "strict mode" for scriptlet failures (ie bring back the duplicates on scriptlet-failures), and Suse seems to have something similar. -- You are rec

[Rpm-maint] [rpm-software-management/rpm] Revert "Allow packagers to specify individual scriptlets as critical" (#700)

2019-05-10 Thread Panu Matilainen
This alleged solution to the problem of not all scriptlet errors being reflected in our exit code is not a solution at all, it just pushes the problem to somebody elses lap and introduces inconsistency and an untracked incompatibility as well. This reverts commit 5455f02523a9b8583d5a942a6d97f1084f