building packages from source and installing doesn't work

Bug #942831 reported by Cian Wilson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Spud
Fix Released
Undecided
Unassigned

Bug Description

I'm in the process of trying to debug some things in spud so was trying to build the packages and install them from source. Sadly this doesn't seem to be working for me. (This may not be a bug so if someone could point out if I'm doing something wrong it would be much appreciated.)

I'm running:
(1) bzr co lp:spud trunk
(2) cd trunk/
(3) debuild -uc -us
(this produces a lot of output but appears to finish successfully with the line: "Finished running lintian", and generates .deb files in the directory above)
(4) cd ../
(5) sudo dpkg -i *.deb
(this produces output that again seems successful:
dpkg: warning: downgrading diamond from 1.1.3+504~natty1 to 1.1.3.
(Reading database ... 356449 files and directories currently installed.)
Preparing to replace diamond 1.1.3+504~natty1 (using diamond_1.1.3_all.deb) ...
Unpacking replacement diamond ...
dpkg: warning: downgrading libspud-dev from 1.1.3+504~natty1 to 1.1.3.
Preparing to replace libspud-dev 1.1.3+504~natty1 (using libspud-dev_1.1.3_amd64.deb) ...
Unpacking replacement libspud-dev ...
dpkg: warning: downgrading python-dxdiff from 1.1.3+504~natty1 to 1.1.3.
Preparing to replace python-dxdiff 1.1.3+504~natty1 (using python-dxdiff_1.1.3_all.deb) ...
Unpacking replacement python-dxdiff ...
dpkg: warning: downgrading python-spud from 1.1.3+504~natty1 to 1.1.3.
Preparing to replace python-spud 1.1.3+504~natty1 (using python-spud_1.1.3_amd64.deb) ...
Unpacking replacement python-spud ...
dpkg: warning: downgrading spudtools from 1.1.3+504~natty1 to 1.1.3.
Preparing to replace spudtools 1.1.3+504~natty1 (using spudtools_1.1.3_all.deb) ...
Unpacking replacement spudtools ...
Setting up python-dxdiff (1.1.3) ...
Setting up spudtools (1.1.3) ...
Setting up diamond (1.1.3) ...
Setting up libspud-dev (1.1.3) ...
Setting up python-spud (1.1.3) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place)
(6) diamond
(this fails:
Cannot locate GUI!)

Tips/hints/reports on reproducibility appreciated.

Related branches

Revision history for this message
Patrick Farrell (pefarrell) wrote :

dpkg -L on the diamond package yields:

/tmp
/tmp/diamond
/tmp/diamond/trunk
/tmp/diamond/trunk/debian
/tmp/diamond/trunk/debian/diamond
/tmp/diamond/trunk/debian/diamond/usr
/tmp/diamond/trunk/debian/diamond/usr/share
/tmp/diamond/trunk/debian/diamond/usr/share/diamond
/tmp/diamond/trunk/debian/diamond/usr/share/diamond/plugins
/tmp/diamond/trunk/debian/diamond/usr/share/diamond/plugins/flml
/tmp/diamond/trunk/debian/diamond/usr/share/diamond/gui
/tmp/diamond/trunk/debian/diamond/usr/share/diamond/gui/gui.glade
/tmp/diamond/trunk/debian/diamond/usr/share/diamond/gui/diamond.svg

i.e., the Debian package has installed stuff (GUI included) into /tmp/diamond. I assume this is related to the recent fiddling with the setup.py.in ...

Changed in spud:
status: New → Confirmed
Revision history for this message
Patrick Farrell (pefarrell) wrote :

As described in another bug, it appeared that precise wasn't honouring the --root option, and so the diamond package wasn't building on precise. Tim added code to go through the argument list and manually honour the --root option. But it looks like --root is honoured by maverick/natty, and so the --root now takes effect twice ...

Revision history for this message
Patrick Farrell (pefarrell) wrote :

I think it's fixed in my branch; feel free to review.

Revision history for this message
Cian Wilson (cwilson) wrote :

Confirmed fixed in that branch.

Changed in spud:
status: Confirmed → Fix Committed
Changed in spud:
status: Fix Committed → 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.