[buildd-tools-devel] Bug#842232: Package build cannot chmod files such that they are unreadable or unwriteable

Luca Falavigna dktrkranz at debian.org
Thu Oct 27 07:39:34 UTC 2016


Package: sbuild
Version: 0.71.0-2


I was notified of an issue on my Deb-o-Matic instances, which I think
boils down to sbuild.

Trying building f-el package from unstable using this command:
   sbuild -A -s -d unstable --arch=amd64 -c unstable-i386-sbuild
f-el_0.19.0-1.dsc
package fails in the test suite, as per attached build log.

This is the comment of OP:
------------------------------------------------------------
My package's test suite, run using an override_dh_auto_test stanza in
debian/rules, fails because it cannot render a file unreadable nor
unwriteable.

The package is an Emacs Lisp library providing functions including
predicates to test if a file is unreadable or unwriteable. The test
suite runs chmod 000 foo.txt, and then invokes the library's functions
to see whether foo.txt is unreadable. Similarly, the test runs chmod
400 foo.txt and then invokes the library's function to see whether
foo.txt is unwriteable. In both cases the function returns false
instead of true.

The test suite entries for predicates that return whether a file is
executable or not pass successfully.
------------------------------------------------------------

Detailed sbuild/schroot configuration files can be found in the
original bug report at
https://github.com/debomatic/debomatic/issues/31

-- 
Cheers,
Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: f-el_0.19.0-1.buildlog
Type: application/octet-stream
Size: 122918 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20161027/4bf6e79f/attachment-0001.obj>


More information about the Buildd-tools-devel mailing list