Package: dpkg Version: 1.17.27 When installing packages which *only* have files in /usr, I generally try to leave / read-only. With the recent release of `dpkg` though this has become problematic.
>From the error message, during unpacking `dpkg` is trying to create a file/directory as /usr.dpkg-tmp, which fails if / is read-only. This could actually cause some problems. Notably if `dpkg` is doing this to check whether the filesystem has sufficient free space, this check *WILL* fail since / and /usr could well be different filesystems. This could also cause trouble if /usr.dpkg-tmp is large and / has limited free space. I'm unsure how to rate the severity of this issue. This is distinctly annoying and can trigger warning flags, but I suppose in many cases it won't cause problems for people. Folks who always remount / read-write when upgrading packages may well not notice, but those of use who pay a bit more attention do notice. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
