* Helmut Grohne <hel...@subdivi.de> [250711 23:09]:
He was reusing a tarball from pbuilder and that tarball lacks an entry for /. I suspect that sbuild creates the root directory for the container with the default umask and never chmods it to 0755. When he created a new tarball with / included, it just worked. Would it be reasonable for sbuild's container runtime to also cover this case?
The advantage being here would be an easier transition path for pbuilder users.
I'm wondering if this is really worth doing. Did you have to tell sbuild about the pbuilder tarball?
If so, then the easier option would be to let sbuild create the tarball, and not point it to the pbuilder tarball.
By default it will also recreate the tarball after one week. Chris
