Package: qbrew
Version: 0.3.9-2
Severity: serious

This package no longer builds in unstable:

> Automatic build of qbrew_0.3.9-2 on coconut0 by sbuild/ia64 0.49
...
> dh_testroot
> rm -f build-stamp
> rm -f configure-stamp
> /usr/bin/make distclean
> make[1]: Entering directory `/build/tbm/qbrew-0.3.9'
> make[1]: *** No rule to make target `distclean'.  Stop.
> make[1]: Leaving directory `/build/tbm/qbrew-0.3.9'
> make: [clean] Error 2 (ignored)
> # Revert patches with quilt
> QUILT_PATCHES=debian/patches quilt pop -a -R || test $? = 2
> No patch removed
> # Clean up after quilt
> rm -rf .pc/
> dh_clean
>  debian/rules build
> dh_testdir
> # Apply patches with quilt
> QUILT_PATCHES=debian/patches quilt push -a  || test $? = 2
> Applying patch docs_installation.diff
> patching file qbrew.pro
> patching file src/resource.h
> 
> Applying patch force_release_version.diff
> patching file configure
> 
> Applying patch copyright_typo.diff
> patching file src/resource.h
> 
> Applying patch remove_beerxml_filter.diff
> patching file src/resource.h
> 
> Now at patch remove_beerxml_filter.diff
> CFLAGS="-Wall -g -O2" ./configure --prefix=/usr
> Configuring qbrew package...
> Checking for qmake...yes
> Checking Qt version...4.2.0
> Checking if a simple Qt program builds...no!
> ERROR: could not build a simple Qt program. See config.log
> Be sure you have a properly configured Qt build environment. This application
> requires a Qt library version of 4.1.0 or greater. Some systems separate Qt
> into separate runtime and development packages. If this is your case, Make 
> sure
> you have both. The 'qmake' command should be in your path, and you may need to
> use either the QTDIR environment variable or the --qtdir configure option. It
> may be necessary to use the --spec option if qmake cannot determine your build
> system.
> make: *** [configure-stamp] Error 1

-- 
Martin Michlmayr
http://www.cyrius.com/


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

Reply via email to