[Rpm-maint] [rpm-software-management/rpm] Graceful handling of (temporary) read-only mounts during transaction (Issue #3400)
Michal Domonkos
notifications at github.com
Wed Oct 23 16:01:32 UTC 2024
Quoted from #3239:
> Of course, the issue of underlying directory not getting updated goes for _any_ (temporary) mounts we happen to touch during a transaction. This may call for stepping back a bit for an overall strategy (fancy expression for "I don't know" 😆 )
>
> We know what mounts we cross paths with, and we technically even know which ones are readonly mounts. We just don't make a good use of that information: if we try to install something on such a filesystem we fail out with "not enough space" which is a bit confusing. Maybe we could automatically add readonly mounts to %_netsharedpath so they get skipped, but we shouldn't do that for an fs where we're actually trying to install to, only for the mountpoints.
>
> And, that still leaves the question of what to do with _any_ temporary mounts.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3400
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3400 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20241023/de13ce4b/attachment.html>
More information about the Rpm-maint
mailing list