Daily recipe: failure because of Permission denied accessing build/patch directories
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
launchpad-buildd |
Triaged
|
Critical
|
Unassigned |
Bug Description
This is a summary of the current state of the issue.
The first patch fails to apply because of permission denied on the ubiquity directory and the three files it contains. This implies a umask issue in the chroot. This is not an issue when building locally
I wonder if a work around for this would be to add a hook in rules for "debian/
From the log:
-------
dh_clean
rm -f debian/
test -d . && cd . && \
rm -f intltool-extract intltool-merge intltool-update po/.intltool-
if test -d doc; then find doc -name '*.omf.out' -exec rm -f \{\} \; ; fi; \
if test -d help; then find help -name '*.omf.out' -exec rm -f \{\} \; ; fi
dpkg-source -i -I -b recipe-
dpkg-source: info: using source format `3.0 (native)'
dpkg-source: info: building gnome-orca in gnome-orca_
tar: recipe-
tar: recipe-
tar: recipe-
tar: Exiting with failure status due to previous errors
affects: | launchpad → launchpad-buildd |
Changed in launchpad-buildd: | |
assignee: | Jelmer Vernooij (jelmer) → nobody |
This may relate to the broken sudo in builds, but since this issue affects natty, maverick, and lucid, another underlying bug may be the cause.