Thanks for your response. So can I just revert the related patches introduced
in 4.6.0 for now? I'm worry that you might change some behaviors in 6.0 and it
will be somewhat different from 4.6.0.
--
Reply to this email directly or view it on GitHub:
**Is your feature request related to a problem? Please describe.**
When upgrading kernel, we will make initrd in `posttrans` script. But the
process of making initrd may fail in some unusual situations, and we only get a
warning message, the rpm command returns 0.
If the rpm command is
Now I don't have other idea, thanks!
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2380#issuecomment-1418691309
You are receiving this because you are subscribed to this thread.
Message ID:
>
Yes, add a recursive chmod is not a good choice. I prefer to not remove build
directory when users don't use `--clean` option.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2380#issuecomment-141867
You are receiving this
> No, that commit is not the problem, it's just the messenger.
>
> See #1382
https://github.com/rpm-software-management/rpm/commit/b34333fa021c0ee7215714eeef96d1a2843ea08e
changed the default behavior. Now users running `rpmbuild -ba *spec` will
automatically remove the build directory, so
