Your message dated Mon, 9 Jun 2014 23:56:45 +0200
with message-id <20140609215645.GB31565@spin>
and subject line fixed by 4.13.1-1 upload
has caused the Debian Bug report #750285,
regarding korundum: FTBFS: dh_install: ruby-kde4 missing files 
(usr/lib/*/ruby/vendor_ruby/*/nepomuk.so), aborting
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.)


-- 
750285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: korundum
Version: 4:4.11.3-4
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140601 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> make[2]: Nothing to be done for 'preinstall'.
> make[2]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "None"
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/korundum4.so
> -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/lib/kde4/krubypluginfactory.so
> -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/bin/krubyapplication
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/ruby/vendor_ruby/2.1.0/KDE/korundum4.rb
> -- Installing: /«PKGBUILDDIR»/debian/tmp/usr/bin/rbkconfig_compiler4
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/soprano.so
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/ruby/vendor_ruby/2.1.0/soprano/soprano.rb
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/akonadi.so
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/ruby/vendor_ruby/2.1.0/akonadi/akonadi.rb
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/kio.so
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/ruby/vendor_ruby/2.1.0/kio/kio.rb
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/khtml.so
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/ruby/vendor_ruby/2.1.0/khtml/khtml.rb
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/ktexteditor.so
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/ruby/vendor_ruby/2.1.0/ktexteditor/ktexteditor.rb
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/solid.so
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/ruby/vendor_ruby/2.1.0/solid/solid.rb
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/plasma_applet.so
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/ruby/vendor_ruby/2.1.0/KDE/plasma.rb
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0/okular.so
> -- Installing: 
> /«PKGBUILDDIR»/debian/tmp/usr/lib/ruby/vendor_ruby/2.1.0/okular/okular.rb
> make[1]: Leaving directory '/«PKGBUILDDIR»/obj-x86_64-linux-gnu'
>    debian/rules override_dh_install
> make[1]: Entering directory '/«PKGBUILDDIR»'
> dh_install --list-missing
> dh_install: ruby-kde4 missing files 
> (usr/lib/*/ruby/vendor_ruby/*/nepomuk.so), aborting
> make[1]: *** [override_dh_install] Error 2

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/06/01/korundum_4.11.3-4_unstable.log

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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Hi,

the list of installed files has been updated in 4.13.1-1 upload. The
package now builds fine in a clean environment. I am thus closing this
bug report.

Cheers,

Cédric

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to