Your message dated Mon, 8 Feb 2010 12:16:32 +0100
with message-id <6a2e33621002080316v37e116bcv87559ce9b5b1a...@mail.gmail.com>
and subject line k3b: FTBFS: cp: cannot stat 
`./debian/tmp/usr/lib/kde3/libk3bmpcdecoder.la':  No such file or directory
has caused the Debian Bug report #552942,
regarding k3b: FTBFS: cp: cannot stat 
`./debian/tmp/usr/lib/kde3/libk3bmpcdecoder.la': No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
552942: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552942
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: k3b
Version: 1.0.5-3
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091028 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[3]: Entering directory 
> `/build/user-k3b_1.0.5-3-amd64-pSAGu8/k3b-1.0.5/obj-x86_64-linux-gnu'
> make[3]: Nothing to be done for `install-exec-am'.
> make[3]: Nothing to be done for `install-data-am'.
> make[3]: Leaving directory 
> `/build/user-k3b_1.0.5-3-amd64-pSAGu8/k3b-1.0.5/obj-x86_64-linux-gnu'
> make[2]: Leaving directory 
> `/build/user-k3b_1.0.5-3-amd64-pSAGu8/k3b-1.0.5/obj-x86_64-linux-gnu'
> make[1]: Leaving directory 
> `/build/user-k3b_1.0.5-3-amd64-pSAGu8/k3b-1.0.5/obj-x86_64-linux-gnu'
> dh_installdirs -pk3b-data 
> dh_installdocs -pk3b-data ./README ./TODO ./AUTHORS  
> dh_installexamples -pk3b-data 
> dh_installman -pk3b-data  
> dh_installinfo -pk3b-data  
> dh_installmenu -pk3b-data 
> dh_installcron -pk3b-data 
> dh_installinit -pk3b-data   
> dh_installdebconf -pk3b-data 
> dh_installemacsen -pk3b-data   
> dh_installcatalogs -pk3b-data 
> dh_installpam -pk3b-data 
> dh_installlogrotate -pk3b-data 
> dh_installlogcheck -pk3b-data 
> dh_installchangelogs -pk3b-data  ./ChangeLog 
> dh_installudev -pk3b-data 
> dh_lintian -pk3b-data 
> dh_install -pk3b-data  
> dh_link -pk3b-data  
> dh_installmime -pk3b-data 
> dh_strip -pk3b-data  
> dh_compress -pk3b-data -X .dcl -X .docbook -X -license -X .tag -X .sty -X .el 
> dh_fixperms -pk3b-data  
> dh_makeshlibs -pk3b-data  
> dh_installdeb -pk3b-data 
> dh_perl -pk3b-data 
> dh_shlibdeps -pk3b-data    
> dh_gencontrol -pk3b-data  
> dh_md5sums -pk3b-data 
> dh_builddeb -pk3b-data 
> dpkg-deb: building package `k3b-data' in `../k3b-data_1.0.5-3_all.deb'.
> dh_installdirs -pk3b 
> dh_installdirs -plibk3b-dev 
> dh_installdirs -plibk3b3 
> dh_installdirs -plibk3b3-extracodecs 
> dh_installdocs -pk3b ./README ./TODO ./AUTHORS  
> dh_installexamples -pk3b 
> dh_installman -pk3b debian/k3b.1 
> dh_installinfo -pk3b  
> dh_installmenu -pk3b 
> dh_installcron -pk3b 
> dh_installinit -pk3b   
> dh_installdebconf -pk3b 
> dh_installemacsen -pk3b   
> dh_installcatalogs -pk3b 
> dh_installpam -pk3b 
> dh_installlogrotate -pk3b 
> dh_installlogcheck -pk3b 
> dh_installchangelogs -pk3b  ./ChangeLog 
> dh_installudev -pk3b 
> dh_lintian -pk3b 
> dh_install -pk3b  
> dh_link -pk3b  
> dh_installmime -pk3b 
> dh_installdocs -plibk3b-dev ./README ./TODO ./AUTHORS  
> dh_installexamples -plibk3b-dev 
> dh_installman -plibk3b-dev  
> dh_installinfo -plibk3b-dev  
> dh_installmenu -plibk3b-dev 
> dh_installcron -plibk3b-dev 
> dh_installinit -plibk3b-dev   
> dh_installdebconf -plibk3b-dev 
> dh_installemacsen -plibk3b-dev   
> dh_installcatalogs -plibk3b-dev 
> dh_installpam -plibk3b-dev 
> dh_installlogrotate -plibk3b-dev 
> dh_installlogcheck -plibk3b-dev 
> dh_installchangelogs -plibk3b-dev  ./ChangeLog 
> dh_installudev -plibk3b-dev 
> dh_lintian -plibk3b-dev 
> dh_install -plibk3b-dev  
> dh_link -plibk3b-dev  
> dh_installmime -plibk3b-dev 
> dh_installdocs -plibk3b3 ./README ./TODO ./AUTHORS  
> dh_installexamples -plibk3b3 
> dh_installman -plibk3b3  
> dh_installinfo -plibk3b3  
> dh_installmenu -plibk3b3 
> dh_installcron -plibk3b3 
> dh_installinit -plibk3b3   
> dh_installdebconf -plibk3b3 
> dh_installemacsen -plibk3b3   
> dh_installcatalogs -plibk3b3 
> dh_installpam -plibk3b3 
> dh_installlogrotate -plibk3b3 
> dh_installlogcheck -plibk3b3 
> dh_installchangelogs -plibk3b3  ./ChangeLog 
> dh_installudev -plibk3b3 
> dh_lintian -plibk3b3 
> dh_install -plibk3b3  
> cp: cannot stat `./debian/tmp/usr/lib/kde3/libk3bmpcdecoder.la': No such file 
> or directory
> dh_install: cp returned exit code 1
> make: *** [binary-install/libk3b3] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2009/10/28/k3b_1.0.5-3_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr             GPG: 1024D/023B3F4F |



--- End Message ---
--- Begin Message ---
Version: 1.70.0~beta1-1


--- End Message ---
_______________________________________________
pkg-kde-extras mailing list
pkg-kde-extras@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-extras

Reply via email to