Bug#847527: FTBFS on mips*

2016-12-09 Thread Sandro Knauß
Control: block -1 by 844227

Hey,

the issue is already known but outside the scope of the package itself.

Best Regards,

sandro

--

Am Freitag, 9. Dezember 2016, 02:27:32 CET schrieb Michael Biebl:
> Source: kwallet-kf5
> Version: 5.28.0-2
> Severity: serious
> 
> The package FTBFS on mips* with with the following error message
> 
> /usr/bin/c++   -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -Wall
> -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long
> -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual
> -Werror=return-type -pedantic -fexceptions  -Wl,--enable-new-dtags
> -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined
> CMakeFiles/kwalletd5.dir/main.cpp.o
> CMakeFiles/kwalletd5.dir/kbetterthankdialog.cpp.o
> CMakeFiles/kwalletd5.dir/kwalletd.cpp.o
> CMakeFiles/kwalletd5.dir/kwalletwizard.cpp.o
> CMakeFiles/kwalletd5.dir/ktimeout.cpp.o
> CMakeFiles/kwalletd5.dir/kwalletsessionstore.cpp.o
> CMakeFiles/kwalletd5.dir/migrationagent.cpp.o
> CMakeFiles/kwalletd5.dir/migrationwizard.cpp.o
> CMakeFiles/kwalletd5.dir/knewwalletdialog.cpp.o
> CMakeFiles/kwalletd5.dir/kwalletadaptor.cpp.o
> CMakeFiles/kwalletd5.dir/kwallet4_interface.cpp.o
> CMakeFiles/kwalletd5.dir/kwalletd5_automoc.cpp.o  -o kwalletd5
> -Wl,-rpath,/«PKGBUILDDIR»/obj-mips-linux-gnu/src/runtime/kwalletd/backend:/«
> PKGBUILDDIR»/obj-mips-linux-gnu/src/api/KWallet: -rdynamic
> backend/libkwalletbackend5.so.5.28.0
> ../../api/KWallet/libKF5Wallet.so.5.28.0
> /usr/lib/mips-linux-gnu/libKF5IconThemes.so.5.28.0
> /usr/lib/mips-linux-gnu/libKF5Service.so.5.28.0
> /usr/lib/mips-linux-gnu/libKF5DBusAddons.so.5.28.0
> /usr/lib/mips-linux-gnu/libKF5Notifications.so.5.28.0
> /usr/lib/mips-linux-gnu/libgpgmepp.so -lpthread -lgpgme -lassuan
> -L/usr/lib/mips-linux-gnu -lgpg-error -lgcrypt
> /usr/lib/mips-linux-gnu/libKF5WindowSystem.so.5.28.0
> /usr/lib/mips-linux-gnu/libKF5ConfigWidgets.so.5.28.0
> /usr/lib/mips-linux-gnu/libKF5Codecs.so.5.28.0
> /usr/lib/mips-linux-gnu/libKF5ConfigGui.so.5.28.0
> /usr/lib/mips-linux-gnu/libKF5Auth.so.5.28.0
> /usr/lib/mips-linux-gnu/libKF5WidgetsAddons.so.5.28.0
> /usr/lib/mips-linux-gnu/libQt5Widgets.so.5.7.1
> /usr/lib/mips-linux-gnu/libQt5Gui.so.5.7.1
> /usr/lib/mips-linux-gnu/libKF5I18n.so.5.28.0
> /usr/lib/mips-linux-gnu/libKF5CoreAddons.so.5.28.0
> /usr/lib/mips-linux-gnu/libKF5ConfigCore.so.5.28.0
> /usr/lib/mips-linux-gnu/libQt5DBus.so.5.7.1
> /usr/lib/mips-linux-gnu/libQt5Xml.so.5.7.1
> /usr/lib/mips-linux-gnu/libQt5Core.so.5.7.1
> CMakeFiles/kwalletd5.dir/kwalletd.cpp.o: In function
> `KWalletD::keyDoesNotExist(QString const&, QString const&, QString
> const&)':
> ./obj-mips-linux-gnu/src/runtime/kwalletd/./src/runtime/kwalletd/kwalletd.cp
> p:1805: undefined reference to `KWallet::Backend::entryDoesNotExist(QString
> const&, QString const&) const'
> ./obj-mips-linux-gnu/src/runtime/kwalletd/./src/runtime/kwalletd/kwalletd.cp
> p:1805: undefined reference to `KWallet::Backend::entryDoesNotExist(QString
> const&, QString const&) const'
> ./obj-mips-linux-gnu/src/runtime/kwalletd/./src/runtime/kwalletd/kwalletd.cp
> p:1810: undefined reference to `KWallet::Backend::entryDoesNotExist(QString
> const&, QString const&) const'
> ./obj-mips-linux-gnu/src/runtime/kwalletd/./src/runtime/kwalletd/kwalletd.cp
> p:1810: undefined reference to `KWallet::Backend::entryDoesNotExist(QString
> const&, QString const&) const'
> collect2: error: ld returned 1 exit status
> 
> 
> The full build logs are available at
> https://buildd.debian.org/status/package.php?p=kwallet-kf5&suite=unstable
> 
> 
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (200, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)



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


Processed: block 847527 by 844227

2016-12-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 847527 by 844227
Bug #847527 [src:kwallet-kf5] FTBFS on mips*
847527 was blocked by: 844227 844558 844464 844357
847527 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #847527 to the same blocks 
previously set
> thanks
Stopping processing here.

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



Still Failing: chroot-installation_jessie_install_kde_upgrade_to_stretch_aptdpkg_first/130

2016-12-09 Thread jenkins
See 
https://jenkins.debian.net/job/chroot-installation_jessie_install_kde_upgrade_to_stretch_aptdpkg_first/130//console
 or just 
https://jenkins.debian.net/job/chroot-installation_jessie_install_kde_upgrade_to_stretch_aptdpkg_first/130/
 for more information.

Bug#847527: FTBFS on mips*

2016-12-09 Thread Michael Biebl
Am 09.12.2016 um 13:16 schrieb Sandro Knauß:
> Control: block -1 by 844227

Oh right, I remember the guy filing that bug report.

> Hey,
> 
> the issue is already known but outside the scope of the package itself.
> 

Too bad reportbug doesn't show Affects: bug reports. Maybe it should.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Still Failing: chroot-installation_jessie_install_kde-full_upgrade_to_stretch_aptdpkg_first/130

2016-12-09 Thread jenkins
See 
https://jenkins.debian.net/job/chroot-installation_jessie_install_kde-full_upgrade_to_stretch_aptdpkg_first/130//console
 or just 
https://jenkins.debian.net/job/chroot-installation_jessie_install_kde-full_upgrade_to_stretch_aptdpkg_first/130/
 for more information.

Bug#758206: marked as done (kopete: Crash when connecting Jabber Account)

2016-12-09 Thread Debian Bug Tracking System
Your message dated Fri, 09 Dec 2016 22:35:26 +0100
with message-id <1481319326.11141.7.ca...@gmx.net>
and subject line New upstream version
has caused the Debian Bug report #758206,
regarding kopete: Crash when connecting Jabber Account
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.)


-- 
758206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: kopete: Crash when connecting Jabber Account
Package: kopete
Version: 4:4.13.3-1
Severity: important

Dear Maintainer,

kopete reproducibly crashes when connecting to our internal XMPP Server.

I have tried to delete all configuration of kopete
(from .kde/share/{apps,config} and recreate the account. As soon as I
try to connect, kopete crashes again.

The crash occurs since the last update. 

My configuration is:
[Account_JabberProtocol_xxx@xxx]
AccountId=xxx@
AllowPlainTextPassword=true
Color=8,0,255
CustomServer=false
ExcludeConnect=false
GoogleTalk=false
HideSystemInfo=false
Identity=x
MergeMessages=true
OldEncrypted=false
PasswordIsWrong=false
Port=5222
Priority=1
Protocol=JabberProtocol
ProxyJID=
RememberPassword=true
Resource=Kopete
SendComposingEvent=true
SendDeliveredEvent=true
SendDisplayedEvent=true
SendEvents=true
SendGoneEvent=true
Server=
UseSSL=false



The backtrace is:

Application: Kopete (kopete), signal: Segmentation fault
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6db38c7900 (LWP 23216))]

Thread 4 (Thread 0x7f6d95d92700 (LWP 23219)):
#0  0x7f6daa9a662d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f6daa9a6989 in g_mutex_lock () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6daa964699 in g_main_context_prepare () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6daa964f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f6daa9650ec in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f6db12bf017 in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f6db12904f1 in 
QEventLoop::processEvents(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7f6db1290805 in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7f6db118ec39 in QThread::exec() () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f6db1272033 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x7f6db119139f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x7f6dab4530a4 in start_thread (arg=0x7f6d95d92700) at 
pthread_create.c:309
#12 0x7f6dafc1504d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f6d8700 (LWP 23231)):
#0  0x7f6dafc21c7e in __GI___clock_gettime (clock_id=1, tp=0x7f6d8fffea90) 
at ../sysdeps/unix/clock_gettime.c:115
#1  0x7f6db11e5865 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#2  0x7f6db12bfdb5 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#3  0x7f6db12be79c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x7f6db12be845 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7f6daa96468d in g_main_context_prepare () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f6daa964f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f6daa9650ec in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f6db12bf017 in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f6db12904f1 in 
QEventLoop::processEvents(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x7f6db1290805 in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x7f6d97abc63b in QCA::SyncThread::run() () from 
/usr/lib/x86_64-linux-gnu/libqca.so.2
#12 0x7f6db119139f in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x7f6dab4530a4 in start_thread (arg=0x7f6d8700) at 
pthread_create.c:309
#14 0x7f6dafc1504d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f6d8f7fe700 (LWP 23232)):
#0  0x7f6daa964604 in g_main_context_prepare () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f6daa964f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6daa9650ec in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6db12bf017 in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /u

Bug#799384: marked as done (kde-workspace: Screen goes black on startup)

2016-12-09 Thread Debian Bug Tracking System
Your message dated Fri, 09 Dec 2016 22:40:06 +0100
with message-id <1481319606.11141.10.ca...@gmx.net>
and subject line No longer reproducible
has caused the Debian Bug report #799384,
regarding kde-workspace: Screen goes black on startup
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.)


-- 
799384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kde-workspace
Version: 4:4.11.22-3
Severity: important


Hi,


I dist-upgraded my system to unstable.
Now, when I start into KDE from KDM the "normal" KDE-startup dialog is
shown.
At one point the screen turns black and only the curser is visible.

I have kwin_x11 installed.

What I have tried:
* Turning of the compositor (Shift + Alt + F12) -> the standard
background becomes visible again
* Pressing Ctrl + Alt + Enf brings up the Logout/shutdown dialog
* starting from the console (startx startkde) -> kde starts and
restores my previous windows; However taskbar, pager etc. are missing


Best regards



Ben





-- System Information:

Debian Release: stretch/sid

  APT prefers unstable

  APT policy: (500, 'unstable')

Architecture: amd64 (x86_64)

Foreign Architectures: i386



Kernel: Linux 4.1.0-2-amd64 (SMP w/2 CPU cores)

Locale: LANG=en_GB.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
(ignored: LC_ALL set to en_GB.UTF-8)

Shell: /bin/sh linked to /bin/dash

Init: systemd (via /run/systemd/system)



Versions of packages kde-workspace depends on:

ii  freespacenotifier  4:4.11.22-3

ii  kde-workspace-bin  4:4.11.22-3

ii  klipper4:4.11.22-3



Versions of packages kde-workspace recommends:

ii  kdm  4:4.11.22-3



kde-workspace suggests no packages.



-- no debconf information
--- End Message ---
--- Begin Message ---
KDE works fine for me, I therefore close this bug. --- End Message ---


Bug#846410: kdevelop crahses when starting (5.0.1)

2016-12-09 Thread Lisandro Damián Nicanor Pérez Meyer
tag 846410 unreproducible moreinfo
severity 846410 important
thanks

Hi! I've tried to reproduce this bug in an up-to-date sid environment without 
luck.

Please try again with an up to date system. If it still crashed please try 
with a clean environment (a new user). In case you can not reproduce it with a 
new user please keep your user's config so we can track the issue if 
necessary.

Thanks, Lisandro.

-- 
Los errores ortográficos y de redacción fueron insertados con la única
intención de testear sus conocimientos de la lengua castellana.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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


Processed: Re: Bug#846410: kdevelop crahses when starting (5.0.1)

2016-12-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 846410 unreproducible moreinfo
Bug #846410 [kdevelop] kdevelop crahses when starting (5.0.1)
Added tag(s) moreinfo and unreproducible.
> severity 846410 important
Bug #846410 [kdevelop] kdevelop crahses when starting (5.0.1)
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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



Bug#847195: Kdevelop: please package newer version

2016-12-09 Thread Lisandro Damián Nicanor Pérez Meyer
On martes, 6 de diciembre de 2016 15:16:13 ART Roman Lebedev wrote:
> Package: kdevelop
> Version: 4:5.0.1-2
> Severity: normal
> 
> Dear maintainer, kdevelop 5.0.3 is avaliable.
> It would be nice to upgrade

There is currently no direct maintainer looking at it, we are keeping it under 
the team's umbrella as muuch as we can.

In my case my time is limited and I won't be able to do it in time for Strech, 
so if anyone is willing to help here help would be apreciated.


-- 
Sea estricto cuando envíe y tolerante cuando reciba. En otras palabras, solo
envíe paquetes que cumplan rigurosamente con lo estándares, pero espere
paquetes que tal vez no cumplan del todo y trate de lidiar con ellos.
  Andrew S. Tanenbaum, de su libro "Computer Networks"

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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


Still Failing: chroot-installation_jessie_install_kde-full_upgrade_to_stretch/132

2016-12-09 Thread jenkins
See 
https://jenkins.debian.net/job/chroot-installation_jessie_install_kde-full_upgrade_to_stretch/132//console
 or just 
https://jenkins.debian.net/job/chroot-installation_jessie_install_kde-full_upgrade_to_stretch/132/
 for more information.

Processing of qt3d-opensource-src_5.7.1~20161122+dfsg-1_amd64.changes

2016-12-09 Thread Debian FTP Masters
qt3d-opensource-src_5.7.1~20161122+dfsg-1_amd64.changes uploaded successfully 
to localhost
along with the files:
  qt3d-opensource-src_5.7.1~20161122+dfsg-1.dsc
  qt3d-opensource-src_5.7.1~20161122+dfsg.orig.tar.xz
  qt3d-opensource-src_5.7.1~20161122+dfsg-1.debian.tar.xz
  libqt53dcore5_5.7.1~20161122+dfsg-1_amd64.deb
  libqt53dextras5_5.7.1~20161122+dfsg-1_amd64.deb
  libqt53dinput5_5.7.1~20161122+dfsg-1_amd64.deb
  libqt53dlogic5_5.7.1~20161122+dfsg-1_amd64.deb
  libqt53dquick5_5.7.1~20161122+dfsg-1_amd64.deb
  libqt53dquickextras5_5.7.1~20161122+dfsg-1_amd64.deb
  libqt53dquickinput5_5.7.1~20161122+dfsg-1_amd64.deb
  libqt53dquickrender5_5.7.1~20161122+dfsg-1_amd64.deb
  libqt53drender5_5.7.1~20161122+dfsg-1_amd64.deb
  qml-module-qt3d_5.7.1~20161122+dfsg-1_amd64.deb
  qml-module-qtquick-scene3d_5.7.1~20161122+dfsg-1_amd64.deb
  qt3d-assimpsceneio-plugin_5.7.1~20161122+dfsg-1_amd64.deb
  qt3d-gltfsceneio-plugin_5.7.1~20161122+dfsg-1_amd64.deb
  qt3d-opensource-src_5.7.1~20161122+dfsg-1_amd64.buildinfo
  qt3d5-dbg_5.7.1~20161122+dfsg-1_amd64.deb
  qt3d5-dev_5.7.1~20161122+dfsg-1_amd64.deb
  qt3d5-doc-html_5.7.1~20161122+dfsg-1_all.deb
  qt3d5-doc_5.7.1~20161122+dfsg-1_all.deb
  qt3d5-examples_5.7.1~20161122+dfsg-1_amd64.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



qt3d-opensource-src_5.7.1~20161122+dfsg-1_amd64.changes is NEW

2016-12-09 Thread Debian FTP Masters
binary:libqt53dextras5 is NEW.
binary:libqt53dquickextras5 is NEW.
binary:qt3d-assimpsceneio-plugin is NEW.
binary:qt3d-gltfsceneio-plugin is NEW.
binary:qt3d-gltfsceneio-plugin is NEW.
binary:libqt53dquickextras5 is NEW.
binary:libqt53dextras5 is NEW.
binary:qt3d-assimpsceneio-plugin is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports