Still Failing: chroot-installation_jessie_install_kde-full_upgrade_to_stretch_aptdpkg_first/134

2017-01-06 Thread jenkins
See 
https://jenkins.debian.net/job/chroot-installation_jessie_install_kde-full_upgrade_to_stretch_aptdpkg_first/134//console
 or just 
https://jenkins.debian.net/job/chroot-installation_jessie_install_kde-full_upgrade_to_stretch_aptdpkg_first/134/
 for more information.

Still Failing: chroot-installation_jessie_install_kde_upgrade_to_stretch_aptdpkg_first/134

2017-01-06 Thread jenkins
See 
https://jenkins.debian.net/job/chroot-installation_jessie_install_kde_upgrade_to_stretch_aptdpkg_first/134//console
 or just 
https://jenkins.debian.net/job/chroot-installation_jessie_install_kde_upgrade_to_stretch_aptdpkg_first/134/
 for more information.

Bug#850462: [src:libkf5ksieve] managing sieve scripts in kmail stops working after some time

2017-01-06 Thread Maximilian Engelhardt
Package: src:libkf5ksieve
Version: 4:16.04.3-1
Severity: normal

--- Please enter the report below this line. ---
Hello,

After a fresh start of kmail managing sieve scripts does work as expected. 
After some time it doesn't work any more. Opening Settings -> Manage Sieve 
Scripts... only shows a never ending spinning wheel and is not loading the 
available scripts. Restarting kmail temporary fixed this.

I've seen upstream has some fixes for sieve connection management and 
backporting the following commits does indeed fix this:

https://cgit.kde.org/libksieve.git/commit/?
id=8fb821950bd8caae0c4a86e1d2ecb4caabab1689
https://cgit.kde.org/libksieve.git/commit/?
id=ee4afdd78597cb9379a39951b9eca94a8e927f98
https://cgit.kde.org/libksieve.git/commit/?
id=6862737561a9ee5fadcd78bd0655d0b45c893534
https://cgit.kde.org/libksieve.git/commit/?
id=9bbf8a1dd9f3683000228773eef5dbeb12e0d008
https://cgit.kde.org/libksieve.git/commit/?
id=3176d1cdf6e36429ac9c6b4ee79b37c22b4273c9

I didn't have a closer look if all of the patches are needed, but applying 
them all solved the problem for me.
All of these are included in 16.08.0 but not in 16.04.3.

It would be nice to get this fixed for streatch. 

Thanks,
Maxi

--- System information. ---
Architecture: 
Kernel:   Linux 4.8.0-2-amd64

Debian Release: stretch/sid
  500 testing httpredir.debian.org 
  500 stable  security.debian.org 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.





signature.asc
Description: This is a digitally signed message part.


Bug#850470: qt3d5-examples: QML examples not running because of a missing dependency

2017-01-06 Thread Federico Brega
Package: qt3d5-examples
Version: 5.7.1+dfsg-1
Severity: normal

Dear Maintainer,

I installed qt3d5-examples but none of the qml examples was running.

For instance, running the simple-qml executable gives:
qrc:/main.qml:55:1: module "Qt3D.Extras" is not installed
qrc:/main.qml:52:1: module "Qt3D.Core" is not installed
qrc:/main.qml:54:1: module "Qt3D.Input" is not installed
qrc:/main.qml:53:1: module "Qt3D.Render" is not installed
qrc:/main.qml:55:1: module "Qt3D.Extras" is not installed
qrc:/main.qml:52:1: module "Qt3D.Core" is not installed
qrc:/main.qml:54:1: module "Qt3D.Input" is not installed
qrc:/main.qml:53:1: module "Qt3D.Render" is not installed
qrc:/main.qml:55:1: module "Qt3D.Extras" is not installed
qrc:/main.qml:52:1: module "Qt3D.Core" is not installed
qrc:/main.qml:54:1: module "Qt3D.Input" is not installed
qrc:/main.qml:53:1: module "Qt3D.Render" is not installed
qrc:/main.qml:55:1: module "Qt3D.Extras" is not installed
qrc:/main.qml:52:1: module "Qt3D.Core" is not installed
qrc:/main.qml:54:1: module "Qt3D.Input" is not installed
qrc:/main.qml:53:1: module "Qt3D.Render" is not installed

Installing "qml-module-qt3d" resolves the problem, please add it to the
dependencies.

Regards

Federico


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qt3d5-examples depends on:
ii  libc6   2.24-8
ii  libqt53dcore5   5.7.1+dfsg-1
ii  libqt53dextras5 5.7.1+dfsg-1
ii  libqt53dinput5  5.7.1+dfsg-1
ii  libqt53dquick5  5.7.1+dfsg-1
ii  libqt53dquickextras55.7.1+dfsg-1
ii  libqt53drender5 5.7.1+dfsg-1
ii  libqt5core5a5.7.1+dfsg-2
ii  libqt5gui5  5.7.1+dfsg-2
ii  libqt5qml5  5.7.1-1
ii  libqt5quick55.7.1-1
ii  libqt5widgets5  5.7.1+dfsg-2
ii  libstdc++6  6.2.1-5
ii  qml-module-qtquick-scene3d  5.7.1+dfsg-1

qt3d5-examples recommends no packages.

qt3d5-examples suggests no packages.

-- no debconf information



Processed: Re: qtwebengine-opensource-src: FTBFS on buildd machines

2017-01-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 849794 serious
Bug #849794 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS 
on buildd machines
Severity set to 'serious' from 'important'
> retitle 849794 qtwebengine-opensource-src: FTBFS in every arch (including 
> "all") but amd64
Bug #849794 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS 
on buildd machines
Changed Bug title to 'qtwebengine-opensource-src: FTBFS in every arch 
(including "all") but amd64' from 'qtwebengine-opensource-src: FTBFS on buildd 
machines'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
849794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#849794: qtwebengine-opensource-src: FTBFS on buildd machines

2017-01-06 Thread Santiago Vila
severity 849794 serious
retitle 849794 qtwebengine-opensource-src: FTBFS in every arch (including 
"all") but amd64
thanks

On Sat, 31 Dec 2016, Boyuan Yang wrote:

> The root of FTBFS seems different on different architectures:
> 
> * i386: OOM
> * mips: "#error Please add support for your architecture in build/
> build_config.h"
> * armhf, armel: "fatal error: gnu/stubs-hard.h: No such file or directory"
> * kfreebsd: "Unknown platform. Qt WebEngine only supports Linux, Windows, and 
> OS X."
> * mipsel: "collect2: fatal error: ld terminated with signal 6 [Aborted]
> compilation terminated.
> terminate called after throwing an instance of 'std::bad_alloc'
>   what():  std::bad_alloc"

Well, you forgot the "all" architecture.

I tried to build this with "dpkg-buildpackage -A" and it failed as well:

https://people.debian.org/~sanvila/build-logs/qtwebengine-opensource-src/

[ Build failures in the "all" architecture are always serious.
  See Bug #830997 for details ].

If you prefer I could file a separate bug for this, but since this
report was already about unbuildability I thought it was simpler to
extend the scope and modify the subject as I did.

> I would suggest making a source-only upload (to experimental, maybe) after 
> applying fixes to test if the fixes are working correctly.
> 
> [0] https://buildd.debian.org/status/package.php?p=qtwebengine-opensource-src

Please make sure you try both "dpkg-buildpackage -A" and
"dpkg-buildpackage -B" before making another upload.

Thanks.



Bug#849794: qtwebengine-opensource-src: FTBFS on buildd machines

2017-01-06 Thread Santiago Vila
On Sat, 31 Dec 2016, Scott Kitterman wrote:

> FTBFS bugs are only RC when there is an existing binary for the architecture.

That's not really accurate, because the binary could have been created
by "cheating" (for example, the package may have missing build-dependencies
but the uploaded packages were made in a chroot that had them installed).

What you mean here, I suppose, is that a FTBFS is not RC when the
failure only happens on architectures that were previously unsupported.

Logically, since this was the initial upload, the list of "supported
architetures" was initially empty.

Thanks.



Bug#850492: lokalize: missing dependancy

2017-01-06 Thread Yuri Kozlov
Package: lokalize
Version: 4:16.08.2-1
Severity: normal

Hello.

If no kinit5 installed in the system, then lokalize do not show PO files 
in the project overview.


-- 
Best Regards,
Yuri Kozlov