Bug#671893: pykde4: Fails to build from source

2012-05-08 Thread Scott Kitterman
No, I suspect once we rebuilt pykde4, Eric will be fine. I think I have a handle on this now. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/3570361.nuLUWj0Wt1@sc

Bug#672179: kmail: Kmail can not launch slaves

2012-05-08 Thread Noel David Torres Taño
Package: kmail Version: 4:4.4.11.1+l10n-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropiate *** * What led up to the situation? Upgrading kernel and unrelated software * What exactly did you do (or not do

Processed: Re: Bug#671944: libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable

2012-05-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 671944 minor Bug #671944 [libnepomuk4] libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable Severity set to 'minor' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 67

Bug#671944: libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable

2012-05-08 Thread Pino Toscano
severity 671944 minor thanks Hi, Alle martedì 8 maggio 2012, Ralf Jung ha scritto: > Package: libnepomuk4 > Version: 4:4.7.4-4 > Severity: grave > Justification: renders package unusable > > Virtuoso is missing from testing, and without it, Nepomuk does not > work (also see [1]). As I had to fin

Bug#672065: kdevelop: ftbfs with GCC-4.7

2012-05-08 Thread Matthias Klose
user debian-...@lists.debian.org usertags 672065 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSU

Bug#672044: kdenetwork: ftbfs with GCC-4.7

2012-05-08 Thread Matthias Klose
user debian-...@lists.debian.org usertags 672044 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSU

Bug#672016: kdemultimedia: ftbfs with GCC-4.7

2012-05-08 Thread Matthias Klose
user debian-...@lists.debian.org usertags 672016 + ftbfs-gcc-4.7 thanks The build failure is exposed by building with gcc-4.7/g++-4.7, which is now the default gcc/g++ on x86 architectures. Some hints on fixing these issues can be found at http://gcc.gnu.org/gcc-4.7/porting_to.html -- To UNSU

Bug#672065: kdevelop: FTBFS: ../../../../debuggers/gdb/unittests/debugeeslow.cpp:25:12: error: 'sleep' was not declared in this scope

2012-05-08 Thread Lucas Nussbaum
Source: kdevelop Version: 4:4.2.3-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > /usr/bin/g++ -g

Bug#672044: kdenetwork: FTBFS: ../../../../../../../../kopete/protocols/jabber/googletalk/libjingle/talk/base/socketaddress.cc:284:49: error: 'gethostname' was not declared in this scope

2012-05-08 Thread Lucas Nussbaum
Source: kdenetwork Version: 4:4.7.4-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 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[4]: Enter

Bug#672016: kdemultimedia: FTBFS: ../../juk/stringhash.h:36:9: error: 'contains' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiati

2012-05-08 Thread Lucas Nussbaum
Source: kdemultimedia Version: 4:4.7.4-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > /usr/bi

Bug#671960: kde-runtime: FTBFS: make[4]: *** No rule to make target `/usr/lib/libQtTest.so', needed by `activitymanager/kactivitymanagerd'. Stop.

2012-05-08 Thread Lucas Nussbaum
Source: kde-runtime Version: 4:4.7.4-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120508 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[4]: Enter

Bug#671944: libnepomuk4: Virtuoso entirely missing from testing, making Nepomuk unusable

2012-05-08 Thread Ralf Jung
Package: libnepomuk4 Version: 4:4.7.4-4 Severity: grave Justification: renders package unusable Virtuoso is missing from testing, and without it, Nepomuk does not work (also see [1]). As I had to find out the hard way [2], reporting this against Virtuoso is wrong (sorry for the multiple bug report

Bug#671932: plasma-desktop: segmentation fault after loging, unable to load KDE environment

2012-05-08 Thread Liang Guo
On Tue, May 8, 2012 at 7:42 PM, Darckense wrote: > Package: plasma-desktop > Version: 4:4.7.4-2+b1 > Severity: important > > I have a critical problem with plasma-desktop since I have updated debian sid > two days ago. > > When I tried to log using plasma desktop environment, the environment start

Bug#671872: koffice: FTBFS ("error: ambiguous overload for 'operator<<'")

2012-05-08 Thread Cyril Brulebois
Adam D. Barratt (07/05/2012): > koffice FTBFS having been binNMUed for the exiv2 transition. From the > amd64 build log: […] 12:52:59 [ pinotree] will be hopefully replaced with calligra soon 12:53:52 [ KiBi] meaning it's going to disappear from the exiv2 transition radar? 12:54:13 [ pinotree]

Bug#671932: plasma-desktop: segmentation fault after loging, unable to load KDE environment

2012-05-08 Thread Darckense
Package: plasma-desktop Version: 4:4.7.4-2+b1 Severity: important I have a critical problem with plasma-desktop since I have updated debian sid two days ago. When I tried to log using plasma desktop environment, the environment start to load, and at the end of the splashscreen, I got an error mes