Ubuntu
gnome-user-docs package

autopkgtest gutsy gnome-user-docs: erroneous package!

Bug #144498 reported by Ian Jackson autopkgtest
8
Affects Status Importance Assigned to Milestone
gnome-user-docs (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 affects /ubuntu/gnome-user-docs
 importance high

 Test executed for: gutsy source gnome-user-docs
 Outcome: erroneous package!
  blame: arg:tmp/gnome-user-docs/src/gnome-user-docs_2.18.2+svn20070912ubuntu1.dsc dsc:gnome-user-docs
  badpkg: rules binary failed with exit code 2
  quitting: erroneous package: rules binary failed with exit code 2

  erroneous package!

This message is automatically generated by the autopkgtest package
testing system. You are receiving it because:
 The test results appear to indicate a problem with the package
 and reports for package maintainers for gutsy are being directed to
 <email address hidden>

The test log, which is intended to be sufficient to diagnose most
failures, can be found below. However, in case this is not
sufficient, another copy can be found along with output files, saved
temporary files, and so on, at:
 http://autopkgtest.ubuntu.com/autopkgtest-output/

The test environment is an amd64 Xen guest with limited amounts of
memory. The relevant dependencies are installed for each test but
very few other packages. Most autopkgtest reports are FTBFS problems.

If you have any questions about this service please contact me at:
 Ian Jackson <email address hidden>

Regards,
Ian

LOG CUT - please see:

http://autopkgtest.ubuntu.com/autopkgtest-output/gnome-user-docs/log

See original description
Revision history for this message
Matthew East (mdke) wrote :

Reducing the importance of this since the package is building ok on the buildds.

description: updated
Changed in gnome-user-docs:
importance: High → Low
Revision history for this message
Matthew East (mdke) wrote :

Adam has pointed out the cause of this.

22:45:04 < infinity> mdke: A quick look at the build log would lead me to believe that some sort of configure script is
                     running in the "clean" target, rather than the "build" target. Since dpkg-buildpackage runs "clean"
                     before "build", it works, but autopkgtest doesn't do so (so is stuck with the configured variables from
                     the "clean" run right before the source package was built).
22:46:52 < infinity> mdke: A look at a launchpad build log confirms that; configure is being run in "clean", not in "build".

Revision history for this message
Daniel Holbach (dholbach) wrote :

Adam is right, we run @gnome-autogen.sh --prefix=/usr in the clean target to not have to build-depends on all kinds of autotools. I'd say: let's look at this again for Intrepid.

Revision history for this message
Matthew East (mdke) wrote :

Had a report from slagasek that this makes debdiffs difficult to review - he has asked it be fixed for hardy if possible. Increasing importance to Medium.

Changed in gnome-user-docs:
importance: Low → Medium
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-user-docs - 2.22.0+svn20080310ubuntu2

---------------
gnome-user-docs (2.22.0+svn20080310ubuntu2) hardy; urgency=low

  * debian/rules: moved autogen-business into makebuilddir target.
    (LP: #144498)
  * debian/control:
    - added gnome-common, automake1.10 to Build-Depends-Indep,
    - updated bzr branch information,
    - bumped Standards-Version.
  * debian/rules, debian/control: removed gnome-pkg-tools references.

gnome-user-docs (2.22.0+svn20080310ubuntu1) hardy; urgency=low

  * New upstream version, new translations (LP: #201955)

 -- Daniel Holbach <email address hidden> Mon, 17 Mar 2008 08:39:26 +0100

Changed in gnome-user-docs:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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