Candidate revision debhelper_7.4.20ubuntu1

Bug #583352 reported by أحمد المحمودي (Ahmed El-Mahmoudy)
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debhelper (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: debhelper

  * Merge with Debian; remaining changes:
    - dh_installinit: Add --upstart-only and --onlyscripts-upstart modes.
    - Add various autoscripts for above: postinst-upstart,
      postinst-upstart-replace, postinst-upstart-restart,
      prerm-upstart, prerm-upstart-norestart, preinst-removeconffile.
    - dh_installudev: Change default init.d symlink priority to 40.

Related branches

Revision history for this message
أحمد المحمودي (Ahmed El-Mahmoudy) (aelmahmoudy) wrote :
Changed in debhelper (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel Holbach (dholbach) wrote :

You might want to drop the gconf change. Also does it FBTFS for me on amd64 maverick:

t/buildsystems/buildsystem_tests .. 289/300
# Failed test 'DEB_BUILD_OPTIONS=parallel=5 with --parallel'
# at t/buildsystems/buildsystem_tests line 569.
# Structures begin differing at:
# $got->[0] = 'make[2]: *** [FIRST] Error 10'
# $expected->[0] = Does not exist

# Failed test '(exit status=0) DEB_BUILD_OPTIONS=parallel=5 with --parallel'
# at t/buildsystems/buildsystem_tests line 570.
# got: '2'
# expected: '0'
t/buildsystems/buildsystem_tests .. 298/300 # Looks like you failed 2 tests of 300.
t/buildsystems/buildsystem_tests .. Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/300 subtests

Test Summary Report
-------------------
t/buildsystems/buildsystem_tests (Wstat: 512 Tests: 300 Failed: 2)
  Failed tests: 289-290
  Non-zero exit status: 2
Files=7, Tests=521, 19 wallclock secs ( 0.26 usr 0.10 sys + 5.41 cusr 2.63 csys = 8.40 CPU)
Result: FAIL
Failed 1/7 test programs. 2/521 subtests failed.
make[1]: *** [test] Error 2
make[1]: Leaving directory `/tmp/buildd/debhelper-7.4.20ubuntu1'
dh_auto_test: make -j1 test returned exit code 2
make: *** [build] Error 29
dpkg-buildpackage: error: debian/rules build gave error exit status 2
E: Failed autobuilding of package
I: unmounting dev/pts filesystem
I: unmounting proc filesystem
I: cleaning the build env

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

Please ignore my comment about the gconf change, it was done in Debian.

Revision history for this message
أحمد المحمودي (Ahmed El-Mahmoudy) (aelmahmoudy) wrote : Re: [Bug 583352] Re: Candidate revision debhelper_7.4.20ubuntu1

It build on i386 maverick in Launchpad:
https://launchpad.net/~aelmahmoudy/+archive/ppa/+build/1757116/+files/buildlog_ubuntu-maverick-i386.debhelper_7.4.20ubuntu1_FULLYBUILT.txt.gz

--
 ‎أحمد المحمودي (Ahmed El-Mahmoudy)
  Digital design engineer
 GPG KeyID: 0xEDDDA1B7
 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package debhelper - 7.4.20ubuntu1

---------------
debhelper (7.4.20ubuntu1) maverick; urgency=low

  * Merge with Debian (LP: #583352); remaining changes:
    - dh_installinit: Add --upstart-only and --onlyscripts-upstart modes.
    - Add various autoscripts for above: postinst-upstart,
      postinst-upstart-replace, postinst-upstart-restart,
      prerm-upstart, prerm-upstart-norestart, preinst-removeconffile.
    - dh_installudev: Change default init.d symlink priority to 40.

debhelper (7.4.20) unstable; urgency=low

  * Drop one more call to dpkg-architecture. Closes: #580837
    (Raphael Geissert)
  * Further reduce the number of calls to dpkg-architecture to zero,
    in a typical package with no explicit architecture mentions
    in control file or debhelper config files.
  * dh_perl: use debian_abi for XS modules. Closes: #581233
 -- ALEFHAHMEEMDAL ALEFLAMMEEMHAHMEEMWAWDALYEH (Ahmed El-Mahmoudy) <email address hidden> Thu, 20 May 2010 14:37:56 +0300

Changed in debhelper (Ubuntu):
status: Confirmed → Fix Released
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.