viking build error

Bug #996476 reported by Alberto González Palomo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
viking (Debian)
New
Unknown
viking (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

12:41:51 viking-1.2.1$ lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04
12:41:59 viking-1.2.1$ apt-cache policy viking
viking:
  Installed: 1.2.1-3build1
  Candidate: 1.2.1-3build1
  Version table:
 *** 1.2.1-3build1 0
        500 http://mirror.de.leaseweb.net/ubuntu/ precise/universe amd64 Packages
        100 /var/lib/dpkg/status

Steps to reproduce in Ubuntu 12.04:
1. apt-get source viking
2. cd viking-1.2.1/
3. dpkg-buildpackage -rfakeroot

Error message:
-----------------------------------------------------------------
...
src/Makefile.am:18: XP was already defined in condition TRUE, which includes condition HAVE_XSLTPROC ...
configure.ac:321: ... `XP' previously defined here
src/icons/Makefile.am:263: `%'-style pattern rules are a GNU make extension
configure.ac:341: required file `doc/reference/Makefile.in' not found
make[1]: *** [Makefile.in] Error 1
make[1]: Leaving directory `/stor/Software/viking-1.2.1'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-----------------------------------------------------------------

I've tried reaming the XP variable in "configure.ac", but then it fails later with:
configure.ac:341: required file `doc/reference/Makefile.in' not found

After commenting out those lines (the if...then block that tries to load that missing file) it stops at:
-----------------------------------------------------------------
...
Removing patch 0003-Add-missing-lz.patch
Restoring src/Makefile.am

Removing patch 0001-disable-po-check.patch
Restoring po/Makefile.in.in

Patch GPSD-API-v5.patch does not remove cleanly (refresh it or enforce with -f)
dh_quilt_unpatch: quilt --quiltrc /dev/null pop -a || test $? = 2 returned exit code 1
make: *** [clean] Error 25
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
-----------------------------------------------------------------

Revision history for this message
Daniel Letzeisen (dtl131) wrote :
Changed in viking (Ubuntu):
status: New → Confirmed
Revision history for this message
Alberto González Palomo (matmota) wrote :

Using the source package for 1.3.1 from Quetzal does build but only the first time:

1. wget https://launchpad.net/ubuntu/+archive/primary/+files/viking_1.3-1.diff.gz https://launchpad.net/ubuntu/+archive/primary/+files/viking_1.3-1.dsc https://launchpad.net/ubuntu/+archive/primary/+files/viking_1.3.orig.tar.gz
2. dpkg-source -x viking_1.3-1.dsc
3. cd viking-1.3/
4. dpkg-buildpackage -rfakeroot
5. sudo dpkg -i ../viking_1.3-1_amd64.deb

After this, starting Viking as usual shows version 1.3 in Help->About
It seems to run fine.

However, if I try to build it a second time, it fails:
-----------------------------------------------------------------
19:53:56 viking-1.3$ dpkg-buildpackage -rfakeroot
...
make[2]: Entering directory `/stor/Software/viking-1.3'
Making distclean in help
make[3]: Entering directory `/stor/Software/viking-1.3/help'
 cd .. && /bin/bash /home/alberto/stor/Software/viking-1.3/missing --run automake-1.11 --gnu help/Makefile
automake-1.11: cannot open < gnome-doc-utils.make: No such file or directory
make[3]: *** [Makefile.in] Error 1
make[3]: Leaving directory `/stor/Software/viking-1.3/help'
make[2]: *** [distclean-recursive] Error 1
make[2]: Leaving directory `/stor/Software/viking-1.3'
dh_auto_clean: make -j1 distclean returned exit code 2
make[1]: *** [override_dh_auto_clean] Error 29
make[1]: Leaving directory `/stor/Software/viking-1.3'
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
19:54:06 viking-1.3$
-----------------------------------------------------------------

Changed in viking (Debian):
status: Unknown → New
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.