Hello Johannes.
johan...@schoepfer.info wrote in <ef3cee10d7c1dd794b6d5339dcade750@schoe\
pfer.info>:
|On 2020-01-01 20:18, Steffen Nurpmeso wrote:
|> russellb...@gmail.com wrote in
|> <202001011657.001gvtjh002...@randytool.net>:
|>| 'v14.9.16 already packaged? May i ask which OS this is?'
|>| Slackware.
|>
|> Thanks. I did not know it was already there, i had a private
|> conversation with the Slackware maintainer who reported test
|> errors; it seems readonly files can be written to on Slackware. :)
|
|The "real" slackware-current Maintainer did a package with the test
|commented out.
|My user-repository(SBo) package for the stable slackware(14.2) isn't
|updated, because
|i wanted to check for the failed tests.
|
|It seems the cause is, that on slackware the packages are typically
|build as root user.
|When i build as unpriviledged "make test" returns:
|600 tests: 600 ok, 0 failure(s). 3 test(s) skipped
|
|Readonly files can be overwritten by the root user, not only on
|slackware.
Hammer. You are so right! Invocations as root i did not take
into account at all.
I fixed it via a general "can we create read-only files" test
case, and pushed it to the entire series ([master],
[stable/{v14.9,stable,latest}]).
Thanks for this report, not a thought on that crossed my mind.
Ciao,
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
