After thinking about this once again, we *do* catch other kinds of attempts to
write to a read-only fs through disk space checking, but this mountpoint case
falls through the other read-only checking because an existing directory does
not take any more space on the fs.
I think there's one clear thing we should do: stop the transaction in
pre-flight checks if it tries to touch a read-only filesystem.
Forget about any fancy automatic stuff, we just don't know what the right thing
to do would be.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3400#issuecomment-2636742148
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3400/2636742...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
https://lists.rpm.org/mailman/listinfo/rpm-maint
