Package: pyacidobasic
Version: 0.1-6
Severity: serious
Tags: sid patch
Justification: fails to build from source (but built successfully in the past)

 debian/rules build
dh  build
   dh_testdir
   dh_auto_configure
   dh_auto_build
make[1]: Entering directory `/tmp/buildd/pyacidobasic-0.1'
pyuic4 main.ui | sed -e 's/^from qwt_plot/from PyQt4.Qwt5/' -e 
's%\(icons/[-:a-zA-Z_0-9]*\.svg\)%/usr/share/pyacidobasic/\1%g' > Ui_main.py
/bin/sh: pyuic4: not found
pyuic4 prelevement.ui > Ui_prelevement.py
/bin/sh: pyuic4: not found
make[1]: *** [Ui_prelevement.py] Error 127
make[1]: Leaving directory `/tmp/buildd/pyacidobasic-0.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

Since this is an arch all package, it's never been built on a Debian buildd.

The build system uses pyuic4, which is in pyqt4-dev-tools.  After adding that
to build-depends, one gets the following error:

 debian/rules build
dh  build
   dh_testdir
   dh_auto_configure
   dh_auto_build
make[1]: Entering directory `/tmp/buildd/pyacidobasic-0.1'
pyuic4 main.ui | sed -e 's/^from qwt_plot/from PyQt4.Qwt5/' -e 
's%\(icons/[-:a-zA-Z_0-9]*\.svg\)%/usr/share/pyacidobasic/\1%g' > Ui_main.py
pyuic4 prelevement.ui > Ui_prelevement.py
xsltproc --nonet 
/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl manpage.xml
make[1]: xsltproc: Command not found
make[1]: *** [pyacidobasic.1] Error 127
make[1]: Leaving directory `/tmp/buildd/pyacidobasic-0.1'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2

xsltproc is in the xsltproc package. Which then leads us to:

 debian/rules build
dh  build
   dh_testdir
   dh_auto_configure
   dh_auto_build
make[1]: Entering directory `/tmp/buildd/pyacidobasic-0.1'
pyuic4 main.ui | sed -e 's/^from qwt_plot/from PyQt4.Qwt5/' -e 
's%\(icons/[-:a-zA-Z_0-9]*\.svg\)%/usr/share/pyacidobasic/\1%g' > Ui_main.py
pyuic4 prelevement.ui > Ui_prelevement.py
xsltproc --nonet 
/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl manpage.xml
warning: failed to load external entity 
"/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl"
cannot parse /usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl
make[1]: *** [pyacidobasic.1] Error 4
make[1]: Leaving directory `/tmp/buildd/pyacidobasic-0.1'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2

Which identifies a need for docbook-xsl.  That however moves on to:

 debian/rules build
dh  build
   dh_testdir
   dh_auto_configure
   dh_auto_build
make[1]: Entering directory `/tmp/buildd/pyacidobasic-0.1'
pyuic4 main.ui | sed -e 's/^from qwt_plot/from PyQt4.Qwt5/' -e 
's%\(icons/[-:a-zA-Z_0-9]*\.svg\)%/usr/share/pyacidobasic/\1%g' > Ui_main.py
pyuic4 prelevement.ui > Ui_prelevement.py
xsltproc --nonet 
/usr/share/sgml/docbook/stylesheet/xsl/nwalsh/manpages/docbook.xsl manpage.xml
I/O error : Attempt to load network entity 
http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd
manpage.xml:62: warning: failed to load external entity 
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd";
]>
  ^
Note: Writing pyacidobasic.1
gzip -c9 pyacidobasic.1 > pyacidobasic.1.gz
lrelease-qt4 lang/*.ts 2>/dev/null || lrelease lang/*.ts
/bin/sh: lrelease: not found
make[1]: *** [languages] Error 127
make[1]: Leaving directory `/tmp/buildd/pyacidobasic-0.1'
dh_auto_build: make -j1 returned exit code 2

Which suggests docbook-xml and libqt4-dev.  Then it builds.

The fix for the FTBFS is:

-Build-Depends: debhelper (>= 7), python-central (>= 0.6), python-setuptools 
(>= 0.6b3)
+Build-Depends: debhelper (>= 7), python-central (>= 0.6), python-setuptools 
(>= 0.6b3), pyqt4-dev-tools, libqt4-dev, xsltproc, docbook-xsl, docbook-xml


-- System Information:
Debian Release: squeeze/sid
Architecture: i386 (i686)

Kernel: Linux 2.6.35-22-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to