Daily recipe: failure because of .pc directory

Asked by Boris Dušek

Hello,

I am experiencing the following error when building a source package using daily recipe [1] builds, and the error is not reproducible when testing on my local machine:

...
dpkg-source: info: building gnome-orca in gnome-orca_3.1.0~5180+12~natty1.tar.gz
tar: recipe-3.1.0~5180+12/.pc/01_add_ubiquity-script.patch/src/orca/scripts/apps/ubiquity/__init__.py: Cannot open: Permission denied
tar: recipe-3.1.0~5180+12/.pc/01_add_ubiquity-script.patch/src/orca/scripts/apps/ubiquity/script.py: Cannot open: Permission denied
tar: recipe-3.1.0~5180+12/.pc/01_add_ubiquity-script.patch/src/orca/scripts/apps/ubiquity/Makefile.am: Cannot open: Permission denied
tar: Exiting with failure status due to previous errors
dpkg-source: error: tar -cf - gave error exit status 2
dpkg-buildpackage: error: dpkg-source -i -I -b recipe-3.1.0~5180+12 gave error exit status 29
...

(full log at https://launchpadlibrarian.net/68310640/buildlog.txt.gz)

I workaround the problem by adding "tar-ignore = .pc" to the debian/source/options. But this does not work for Lucid, and is a change w.r.t. original Ubuntu packaging, so I would prefer to know the clean way to handle this, or whether it's a Launchpad bug.

Thanks.

[1]: https://code.launchpad.net/~dusek/+recipe/gnome-orca-daily

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Boris Dušek (dusek) said :
#1

Just adding a note on how I test locally:

bzr dailydeb gnome-orca.recipe build-area
sudo pbuilder build build-area/*.dsc

Btw., is there a way to test locally on my machine in exactly the same way as the daily recipe builder does?

Revision history for this message
Curtis Hovey (sinzui) said :
#2

This sounds like the permission/umask issue that was happening in builds. This affected some builders for several days this week. Take the hack out options and let the builds happen again.

Revision history for this message
Boris Dušek (dusek) said :
#3

Unfortunately I am still not successful. I removed the source/options hack and rebuilt for Lucid, Maverick and Natty. All 3 builds of source package failed again with the same error. See last 3 builds (and their logs [1]) on https://code.launchpad.net/~dusek/+recipe/gnome-orca-daily . Thanks.

[1]: the logs are:
Lucid: https://launchpadlibrarian.net/68714142/buildlog.txt.gz
Maverick: https://launchpadlibrarian.net/68714551/buildlog.txt.gz
Natty: https://launchpadlibrarian.net/68714753/buildlog.txt.gz

Revision history for this message
Boris Dušek (dusek) said :
#4

Still the same build failures (latest an hour ago, i.e. cca. 17:00 UTC).

Revision history for this message
Curtis Hovey (sinzui) said :
#5

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/stamp-autotools-files" that makes the directory or forces the umask.

From the log:
----------------------------------------------
dh_clean
rm -f debian/stamp-autotools-files
test -d . && cd . && \
   rm -f intltool-extract intltool-merge intltool-update po/.intltool-merge-cache; \
   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-3.1.0~5184+14
dpkg-source: info: using source format `3.0 (native)'
dpkg-source: info: building gnome-orca in gnome-orca_3.1.0~5184+14~natty1.tar.gz
tar: recipe-3.1.0~5184+14/.pc/01_add_ubiquity-script.patch/src/orca/scripts/apps/ubiquity/Makefile.am: Cannot open: Permission denied
tar: recipe-3.1.0~5184+14/.pc/01_add_ubiquity-script.patch/src/orca/scripts/apps/ubiquity/script.py: Cannot open: Permission denied
tar: recipe-3.1.0~5184+14/.pc/01_add_ubiquity-script.patch/src/orca/scripts/apps/ubiquity/__init__.py: Cannot open: Permission denied
tar: Exiting with failure status due to previous errors

Revision history for this message
Curtis Hovey (sinzui) said :
#6

I have reported this as a bug since I have not been able to address this issue. I suggest add the tar-ignore = .pc hack back to the recipe until we solve the bug.

Can you help with this problem?

Provide an answer of your own, or ask Boris Dušek for more information if necessary.

To post a message you must log in.