Jenkins build failure: unable to remove jquery

Bug #942903 reported by Allan LeSage
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libdbusmenu-qt
New
Undecided
Unassigned
libdbusmenu-qt (Ubuntu)
New
Undecided
Unassigned

Bug Description

Jenkins builds are failing strangely during teardown, will attach a log. We're setting these failure bugs to high priority so that we can get Coverity and other testing projects going with the successful builds. If you believe this results from a mis-configuration on the Jenkins machine then pls ping alesage or follow-up to this bug.

Revision history for this message
Allan LeSage (allanlesage) wrote :
Revision history for this message
Aurélien Gâteau (agateau) wrote :

That is very strange. What is supposed to happen is this:

- by default upstream libdbusmenu-qt installs documentation in $prefix/share/doc/dbusmenu-qt

- the patch debian/patches/001-dbusmenu-doc-path.diff changes this to $prefix/share/doc/libdbusmenu-qt-doc

- the doc is generated with Doxygen in $prefix/share/doc/libdbusmenu-qt-doc. This steps includes a copy of jquery.js in the doc dir.

- since we don't want to ship multiple copies of jquery.js in all packages which contain documentation generated with Doxygen, the debian/rules removes the jquery.js copy

Looking at the output of the install target, I see this:

"""
-- Installing: /tmp/buildd/libdbusmenu-qt-0.9.0/debian/tmp/usr/share/doc/dbusmenu-qt/jquery.js
"""

This is is the old doc dir, implying 001-dbusmenu-doc-path.diff has not been applied.

Scrolling up the package unpack part I see this:

"""
dpkg-source: info: extracting libdbusmenu-qt in libdbusmenu-qt-0.9.0
dpkg-source: info: unpacking libdbusmenu-qt_0.9.0-2ubuntu1.tar.gz
"""

That is the correct package version. So far so good. A bit further down however there is this:

"""
dpkg-source: info: using source format `3.0 (native)'
"""

That is wrong. It should say "3.0 (quilt)", as specified in debian/source/format. Using "3.0 (native)" means no patches are applied. I am quite confident this is the cause of your problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.