Bug#696141: kdenetwork: FTBFS: moc: .../kopete/protocols/sms/gsmlibprefs.h: No such file
Control: found -1 4:4.8.4-1 Control: notfound -1 4.8.4-1 On 2012-12-17 08:29:22, Thorsten Glaser wrote: > Source: kdenetwork > Version: 4.8.4-1 It looks like you've forgot the epoch. Fixing the version information. Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Processed: Re: Bug#696141: kdenetwork: FTBFS: moc: .../kopete/protocols/sms/gsmlibprefs.h: No such file
Processing control commands: > found -1 4:4.8.4-1 Bug #696141 [src:kdenetwork] kdenetwork: FTBFS: moc: .../kopete/protocols/sms/gsmlibprefs.h: No such file Marked as found in versions kdenetwork/4:4.8.4-1. > notfound -1 4.8.4-1 Bug #696141 [src:kdenetwork] kdenetwork: FTBFS: moc: .../kopete/protocols/sms/gsmlibprefs.h: No such file The source 'kdenetwork' and version '4.8.4-1' do not appear to match any binary packages No longer marked as found in versions kdenetwork/4.8.4-1. -- 696141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b696141.13563667089979.transcr...@bugs.debian.org
Bug#696638: [kde-workspace] pam file for kscreensaver
Package: kde-workspace Version: 4:4.8.4-5 Severity: wishlist Tags: patch --- Please enter the report below this line. --- by default its not possbile to use an pam file for kscreensaver, it fallsback to "other", this small patch it changing this. kscreensaver calls kcheckpass for the password, and kcheckpass is able to load differen pam files. please integreate, it enables to use an fingerprint reader in combination of encrypted home (kdm login uses a password to decrypt the home, kscreensaver uses a finger to unlock the screen) after the patch, a pam file can be used /etc/pam.d/kcheckpass --- kde-workspace-4.8.4.orig/krunner/lock/lockdlg.cc +++ kde-workspace-4.8.4/krunner/lock/lockdlg.cc @@ -462,7 +462,7 @@ void PasswordDlg::gplugStart() "kcheckpass", "-m", mPlugin->info->method, "-S", fdbuf, + "-c", "kcheckpass", (char *)0); _exit(20); } --- System information. --- Architecture: amd64 Kernel: Linux 3.6.11-iwlwifi-1-g67bf613 Debian Release: wheezy/sid 500 testing ftp.at.debian.org 500 stable dl.google.com 500 stable apt.multi24.com 500 natty ppa.launchpad.net 500 lucid ppa.launchpad.net --- Package information. --- Depends (Version) | Installed =-+-=== kde-workspace-bin (>= 4:4.8.4-5) | 4:4.8.4-5 klipper (>= 4:4.8.4-5) | 4:4.8.4-5 ksysguard (>= 4:4.8.4-5) | 4:4.8.4-5 kde-window-manager (>= 4:4.8.4-5) | 4:4.8.4-5 systemsettings (>= 4:4.8.4-5) | 4:4.8.4-5 freespacenotifier (>= 4:4.8.4-5) | 4:4.8.4-5 Recommends (Version) | Installed ==-+-=== kdm (>= 4:4.8.4-5) | 4:4.8.4-5 kinfocenter (>= 4:4.8.4-5) | 4:4.8.4-5 kmenuedit (>= 4:4.8.4-5) | 4:4.8.4-5 Package's Suggests field is empty. -- Dipl.-Inf. Univ. Florian Reitmeir E-Mail: n...@multi24.com Tel: +43 512 209040 Fax: +43 512 209040 10 HP: http://net.multi24.com Leopoldstrasse 63 6020 Innsbruck / Austria
Processed: Re: Bug#696638: [kde-workspace] pam file for kscreensaver
Processing commands for cont...@bugs.debian.org: > tags 696638 upstream Bug #696638 [kde-workspace] [kde-workspace] pam file for kscreensaver Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 696638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.135637370725943.transcr...@bugs.debian.org
Bug#696141: kdenetwork: FTBFS: moc: .../kopete/protocols/sms/gsmlibprefs.h: No such file
Control: tags -1 unreproducible Control: severity -1 important Hi Thorsten, On Mon, Dec 17, 2012 at 08:29:22AM +, Thorsten Glaser wrote: > kdenetwork fails to build, apparently looking for a file which it > generated a few lines above, according to the attached build log. I tried on amd64 with pbuilder in wheezy and sid, and manually in a clean sid chroot (running debian/rules build-arch ; debian/rules binary-arch). Those 3 runs finished without failures. Can you think of a way to reproduce this on a release arch? I'm downgrading the bug because m68k is not a release arch. Cheers, Ivo -- 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/20121224233411.ga2...@ugent.be
Processed: Re: kdenetwork: FTBFS: moc: .../kopete/protocols/sms/gsmlibprefs.h: No such file
Processing control commands: > tags -1 unreproducible Bug #696141 [src:kdenetwork] kdenetwork: FTBFS: moc: .../kopete/protocols/sms/gsmlibprefs.h: No such file Added tag(s) unreproducible. > severity -1 important Bug #696141 [src:kdenetwork] kdenetwork: FTBFS: moc: .../kopete/protocols/sms/gsmlibprefs.h: No such file Severity set to 'important' from 'serious' -- 696141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b696141.135639206315833.transcr...@bugs.debian.org
Bug#696141: kdenetwork: FTBFS: moc: .../kopete/protocols/sms/gsmlibprefs.h: No such file
Ivo De Decker dixit: >I tried on amd64 with pbuilder in wheezy and sid, and manually in a clean >sid chroot (running debian/rules build-arch ; debian/rules binary-arch). Those >3 runs finished without failures. My guess is that the lines that say /tmp/buildd/kdenetwork-4.8.4/kopete/protocols/sms/services/gsmlib.h:0: Note: No relevant classes found. No output generated. and similar are the cause of this. Maybe the thing that’s generated, like gsmlibprefs.h, is arch-dependent, and if there’s nothing, instead of making an empty one it deletes it or doesn’t create it, thus failing the build. But I’ve not looked in-depth. >Can you think of a way to reproduce this on a release arch? No, since it did not FTBFS there, unless someone figures out why the file’s not there on m68k in the first place… >I'm downgrading the bug because m68k is not a release arch. Agreed, as long as it’s still fixed eventually ;-) bye, //mirabilos -- “It is inappropriate to require that a time represented as seconds since the Epoch precisely represent the number of seconds between the referenced time and the Epoch.” -- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2 -- 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/pine.bsm.4.64l.1212250107330.23...@herc.mirbsd.org
