Bug#316572: apt-build segfaults due to missing authentication (and I couldn't find any help about this)
Package: apt-build Version: 0.12.10 Followup-For: Bug #316572 I have this problem with apt-build: building sources works for almost all packages, but when going to install them it fails with this error: --- Building dependency tree... Done The following NEW packages will be installed: picwiz 0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded. Need to get 0B/34.5kB of archives. After unpacking 106kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! picwiz E: There are problems and -y was used without --force-yes Segmentation fault I can still then install the package by hand with dpkg -i but I would like to have apt-build to do all the job. So I investigated a little in man pages of apt-key and apt-secure, but I couldn't find a working solution*. Any help will be appreciated. Bye. - * In fact I tried the following: 1) I created a gpg key for root: # gpg --gen-key 2) I signed with it the release file in local repository of apt-build: # cd /var/cache/apt-build/repository # gpg -abs -o Release.gpg Release 3) I have add teh key to the accepted ones: # gpg --armor --export rootkeyid | apt-key add - but this seems not to work since, according to what written in apt-secure man page, you need to update the signature every time a new package is uploaded to the repository, and this cannot be done automatically by apt-build after the compilation and before installing the package. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.11092005 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages apt-build depends on: ii apt 0.6.41 Advanced front-end for dpkg ii apt-utils 0.6.41 APT utility programs ii debconf 1.4.58 Debian configuration management sy ii devscripts2.9.7 Scripts to make the life of a Debi ii dpkg-dev 1.13.11package building tools for Debian ii g++ 4:4.0.1-3 The GNU C++ compiler ii gcc 4:4.0.1-3 The GNU C compiler ii libappconfig-perl 1.56-2 Perl module for configuration file ii libapt-pkg-perl 0.1.17 Perl interface to libapt-pkg ii perl 5.8.7-4Larry Wall's Practical Extraction Versions of packages apt-build recommends: ii build-essential 11.1 informational list of build-essent ii fakeroot 1.5.1 Gives a fake root environment -- debconf information: apt-build/arch_alpha: ev4 apt-build/arch_arm: armv2 * apt-build/olevel: Medium * apt-build/build_dir: /var/cache/apt-build/build apt-build/arch_sparc: sparc apt-build/arch_amd: k6 * apt-build/options: apt-build/arch_intel: pentium * apt-build/make_options: * apt-build/repository_dir: /var/cache/apt-build/repository * apt-build/add_to_sourceslist: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328051: libgstreamer-perl: FTBFS: Failed test scripts
Package: libgstreamer-perl Version: 0.04-1 Severity: serious When building 'libgstreamer-perl' in a clean 'unstable' chroot, I get the following error: t/GstRegistry.# Looks like you planned 19 tests but only ran 15. dubious Test returned status 4 (wstat 1024, 0x400) DIED. FAILED tests 16-19 Failed 4/19 tests, 78.95% okay t/GstRegistryPool.ok t/GstSchedulerok t/GstStructureok t/GstTag..ok t/GstTagSetterok 3/3 skipped: tagger tests -- id3tag not found t/GstThread...ok Failed Test Stat Wstat Total Fail Failed List of Failed --- t/GstRegistry.t4 1024198 42.11% 16-19 3 subtests skipped. Failed 1/24 test scripts, 95.83% okay. 4/324 subtests failed, 98.77% okay. make[1]: *** [test_dynamic] Error 255 make[1]: Leaving directory `/libgstreamer-perl-0.04' make: *** [install] Error 2 Regards Andreas Jochens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#190215: Still reviving old bugs: #190215
Tomasz (CC'ed to get attention..:-)), in my work on reviving old bug reports we have in shadow, which actually are about the upstream code, I went to http://bugs.debian.org/190215. Here, in short, the bug submitter suggests that su logs successful root logins with LOG_NOTICE, just like login does. The suggestion seems interesting enough to me. WHat would you think of it ? --
Bug#327355: linux-image-2.6.12-1-k7: amverify w/ ide-tape causes bug, then kernel panic
Horms wrote: > Hi Anthony, > > I am forwarding this to the IDE Tape maintainer for his consideration. > Thank you. Please tell me if anything comes out of it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#259494: Reviving old bugs: #259494
http://bugs.debian.org/259494 Here the bug submitter suggests we should offer a way to restrict lastlog's output to a given range of userID's. CUrrently, the "-u" option is able to show lastlog output for one single user. Maybe extending this to UID "ranges" would be helpful: lastlog -u 1000- lastlog -u 1000-2000 lastlog -u -1000 (the latter is trickier because of the leading minus, maybe) Could you add this somewhere in your TODO list? Or maybe one of my fellow maintainers could write a patch? :-) --
Bug#328049: jack: Wants to delete my flac files instead of renaming them
Subject: jack: Wants to delete my flac files instead of renaming them Package: jack Version: 3.1.1-7 Severity: normal Jack wants to delete my flac files instead of renaming them. To reproduce: 1) Rip a cd using 'jack -E flac -Q' 2) Change into the directory the flac files are in 3) Change the title of a track in jack.freedb using 'vim jack.freedb' 4) Attempt to rename the files to reflect the change using 'jack -R' 5) Panic as jack wants to delete all your flac files [EMAIL PROTECTED]:~/jack/Dave Matthews Band/Stand Up$ jack -R This is jack 3.1.1 (C)2004 Arne Zellentin <[EMAIL PROTECTED]> *warning* disabling VBR because flac doesn't support it. /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ Dave Matthews Band - Stand Up - 01 - Dreamgirl.flac Dave Matthews Band - Stand Up - 02 - Old Dirt Hill (Bring That Beat Back).flac Dave Matthews Band - Stand Up - 03 - Stand Up (For It).flac Dave Matthews Band - Stand Up - 04 - American Baby Intro.flac Dave Matthews Band - Stand Up - 05 - American Baby.flac Dave Matthews Band - Stand Up - 06 - Smooth Rider.flac Dave Matthews Band - Stand Up - 07 - Everybody Wake Up (Our Finest Hour Arrives).flac Dave Matthews Band - Stand Up - 08 - Out of My Hands.flac Dave Matthews Band - Stand Up - 09 - Hello Again.flac Dave Matthews Band - Stand Up - 10 - Louisiana Bayou.flac Dave Matthews Band - Stand Up - 11 - Stolen Away on 55th & 3rd.flac Dave Matthews Band - Stand Up - 12 - You Might Die Trying.flac Dave Matthews Band - Stand Up - 13 - Steady As We Go.flac Dave Matthews Band - Stand Up - 14 - Hunger for the Great Light.flac These files will be deleted, continue? n -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.29 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages jack depends on: ii cdparanoia3a9.8-11 An audio extraction tool for sampl ii flac 1.1.2-3Free Lossless Audio Codec - comman ii python2.3.5-3An interactive high-level object-o ii python-cddb 1.4-3 Python interface to CD-IDs and Fre ii python-eyed3 0.6.6-1Python module for id3-tags manipul ii python-flac 0.0.4-1Free Lossless Audio Codec [Python ii python-pyvorbis 1.3-1 A Python interface to the Ogg Vorb ii vorbis-tools 1.0.1-1.5 Several Ogg Vorbis Tools jack recommends no packages. -- no debconf information signature.asc Description: Digital signature
Bug#328050: Invalid digest algorithm importing .p12 certificate exported from mozilla-firefox
Package: gpgsm Version:1.9.15-6 kernel:2.6.8-2-686 debian: sarge stable libc6: 2.3.2.ds1-22 related link: http://lists.gnupg.org/pipermail/gnupg-users/2005-April/025491.html Can't import .p12 files exported from mozilla-firefox $ gpgsm --import thawte.p12 gpgsm: NOTE: THIS IS A DEVELOPMENT VERSION! gpgsm: It is only intended for test purposes and should NOT be gpgsm: used in a production environment or with production keys! Warning: using insecure memory! gpgsm: gpgsm: GPG_TTY has not been set - using maybe bogus default gpgsm: gpg-protect-tool: gpg-agent is not available in this session gpgsm: gpg-protect-tool: error while asking for the passphrase: Invalid digest algorithm gpgsm: error running `/usr/lib//gpg-protect-tool': exit status 2 gpgsm: total number processed: 0 secmem usage: 0/16384 bytes in 0 blocks -- -- Manuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328048: libapache2-mod-perl2: mod_perl makes apache2 segv
Package: libapache2-mod-perl2
Version: 2.0.1-3
Severity: grave
Justification: renders package unusable
hi,
mod_perl enabled makes apache2 puke with a SIGSEGV; seems to be related
to the perl 5.8 update that happened today. before, it was working fine.
the straces aren't very helpful except for pointing out where it fails.
last few lines of the last strace:
command:
env -i LANG=C PATH=/usr/local/bin:/usr/bin:/bin strace -Ff -o
/tmp/strace_apache2 /usr/sbin/apache2ctl startssl
just like the apache2 init script sets it as, except for the strace
addition.
thanks
=
=
20360 stat64("/etc/perl/AutoLoader.pmc", 0x7fa851b0) = -1 ENOENT (No such file
or directory)
20360 open("/etc/perl/AutoLoader.pm", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No
such file or directory)
20360 stat64("/usr/local/lib/perl/5.8.7/AutoLoader.pmc", 0x7fa851b0) = -1
ENOENT (No such file or directory)
20360 open("/usr/local/lib/perl/5.8.7/AutoLoader.pm", O_RDONLY|O_LARGEFILE) =
-1 ENOENT (No such file or directory)
20360 stat64("/usr/local/share/perl/5.8.7/AutoLoader.pmc", 0x7fa851b0) = -1
ENOENT (No such file or directory)
20360 open("/usr/local/share/perl/5.8.7/AutoLoader.pm", O_RDONLY|O_LARGEFILE) =
-1 ENOENT (No such file or directory)
20360 stat64("/usr/lib/perl5/AutoLoader.pmc", 0x7fa851b0) = -1 ENOENT (No such
file or directory)
20360 open("/usr/lib/perl5/AutoLoader.pm", O_RDONLY|O_LARGEFILE) = -1 ENOENT
(No such file or directory)
20360 stat64("/usr/share/perl5/AutoLoader.pmc", 0x7fa851b0) = -1 ENOENT (No
such file or directory)
20360 open("/usr/share/perl5/AutoLoader.pm", O_RDONLY|O_LARGEFILE) = -1 ENOENT
(No such file or directory)
20360 stat64("/usr/lib/perl/5.8/AutoLoader.pmc", 0x7fa851b0) = -1 ENOENT (No
such file or directory)
20360 open("/usr/lib/perl/5.8/AutoLoader.pm", O_RDONLY|O_LARGEFILE) = -1 ENOENT
(No such file or directory)
20360 stat64("/usr/share/perl/5.8/AutoLoader.pmc", 0x7fa851b0) = -1 ENOENT (No
such file or directory)
20360 open("/usr/share/perl/5.8/AutoLoader.pm", O_RDONLY|O_LARGEFILE) = 58
20360 ioctl(58, TCGETS, 0x7fa84f30) = -1 ENOTTY (Inappropriate ioctl for
device)
20360 _llseek(58, 0, [0], SEEK_CUR) = 0
20360 read(58, "package AutoLoader;\n\nuse strict;"..., 4096) = 4096
20360 read(58, " \'lib\').\n#\n\n(my $calldir"..., 4096) = 841
20360 _llseek(58, 4936, [4936], SEEK_SET) = 0
20360 _llseek(58, 0, [4936], SEEK_CUR) = 0
20360 close(58) = 0
20360 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
20358 <... wait4 resumed> [{WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV}], 0,
NULL) = 20360
20358 --- SIGCHLD (Child exited) @ 0 (0) ---
20358 write(2, "Segmentation fault\n", 19) = 19
20358 exit_group(139) = ?
=
=
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (1000, 'unstable'), (998, 'experimental')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.13-pylon
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages libapache2-mod-perl2 depends on:
ii apache2-common2.0.54-4 next generation, scalable, extenda
ii libapr0 2.0.54-5 the Apache Portable Runtime
ii libc6 2.3.5-6GNU C Library: Shared libraries an
ii libdb4.2 4.2.52-19 Berkeley v4.2 Database Libraries [
ii libdevel-symdump-perl 2.03-3 Perl module for inspecting perl's
ii libexpat1 1.95.8-3 XML parsing C library - runtime li
ii libldap-2.2-7 [libldap2] 2.2.26-4.1 OpenLDAP libraries
ii libldap2 2.2.20-0.1 OpenLDAP libraries
ii libperl5.85.8.7-5Shared Perl library
ii liburi-perl 1.35-1 Manipulates and accesses URI strin
ii libwww-perl 5.803-4WWW client/server library for Perl
ii perl [libmime-base64-perl]5.8.7-5Larry Wall's Practical Extraction
ii perl-base [perlapi-5.8.7] 5.8.7-5The Pathologically Eclectic Rubbis
libapache2-mod-perl2 recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328034: Acknowledgement (twutils: Depends on libtw0 that is waiting in the new pkgs list)
..I set up also a src rep: deb-src http://people.debian.org/~zufus twin/ Regards Marco -- "I videogiochi non influenzano i bambini. Voglio dire, se Pac-Man avesse influenzato la nostra generazione, staremmo tutti saltando in sale scure, masticando pillole magiche e ascoltando musica elettronica ripetitiva." "Videogames do not influence kids. I mean, if Pac-Man influenced our generation, we were all jumping in dark rooms, chomping pills and listening to electronic repeating music." Kristian Wilson, Nintendo Inc. 1989 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327440: O: texi2html -- Convert Texinfo files to HTML
On 12/09/05, Florian Ernst <[EMAIL PROTECTED]> wrote: > retitle 327440 ITA: html2ps -- HTML to PostScript converter > owner 327440 ! > retitle 327441 ITA: texi2html -- Convert Texinfo files to HTML > owner 327441 ! > thanks [EMAIL PROTECTED] BCCed > > On Sat, 10 Sep 2005 16:54:06 +1200, Nigel Jones wrote: > > Sadly, come next week, I will not be able to give it the care it may > > need in future, it'd be better if QA manage this package for now and > > someone else pick it up. > > Sorry to see you go, and I hope whatever might be taking you from > spending time for these packages will resolve soon in a good way. Real Money, Real Work coming up, yeah, just a really busy time. > > In the meantime I'd like to pick up html2ps and texi2html, but I > noticed you already have tackled most serious issues... Sorry to spoil the fun ;) > > Cheers, > Flo > > Good to see someone steping in. > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.1 (GNU/Linux) > > iD8DBQFDJEg6s3U+TVFLPnwRAvz7AJ9InFj5HoFedDqwlXZpFdWx9aAwVACfeAxP > GXwXjqZsRizTKBBUtV+lRMc= > =witc > -END PGP SIGNATURE- > > > -- N Jones
Bug#328046: FTBFS: Conflicting declarations of gz_header
Package: thy
Version: 0.9.4-1
Severity: serious
Tags: patch
thy fails to build because it contains a declaration of gz_header that
conflicts with the declaration in /usr/include/zlib.h:
> cc -c -I. -I../../../src -I.. -DPATCHLEVEL=\"4\" -DEXTRAVERSION=\"" Debian
> (i386)"\" -D_GNU_SOURCE=1 -DSYSCONFDIR=\"/etc\" -DLIBDIR=\"/usr/lib\"
> -Winline -Wshadow -Wpointer-arith -Wmissing-declarations -Wstrict-prototypes
> -Wmissing-prototypes -Wcast-qual -Wbad-function-cast -Wchar-subscripts
> -Wcomment -Wformat -Wformat-nonliteral -Wformat-security -Wimplicit
> -Wmissing-braces -Wparentheses -Wswitch -Wunused -g -O2
> -D_FILE_OFFSET_BITS=64 -I../../../lib ../../../src/gzip.c -o gzip.o
> ../../../src/gzip.c:57: error: 'gz_header' redeclared as different kind of
> symbol
> /usr/include/zlib.h:124: error: previous declaration of 'gz_header' was here
> ../../../src/gzip.c: In function 'thy_zlib_send':
> ../../../src/gzip.c:115: warning: pointer targets in passing argument 1 of
> 'compress2' differ in signedness
--
Matt
only in patch2:
unchanged:
--- thy-0.9.4.orig/src/gzip.c
+++ thy-0.9.4/src/gzip.c
@@ -54,7 +54,7 @@
* We are going the easy way: no filename, no timestamp, no
* nothing. Just a plain dumb gzip header.
*/
-static char gz_header[] = {0x1f, 0x8b, Z_DEFLATED, 0, 0, 0, 0, 0, 0, 0x03};
+static char static_gz_header[] = {0x1f, 0x8b, Z_DEFLATED, 0, 0, 0, 0, 0, 0,
0x03};
/** @internal Opaque type for compressed session data.
*/
@@ -118,9 +118,9 @@
/* Construct gzip header */
free (session->body.header.buff);
session->body.header.buff =
- (char *)bhc_malloc (sizeof (gz_header) + 1);
- memcpy (session->body.header.buff, gz_header, sizeof (gz_header));
- session->body.header.size = sizeof (gz_header);
+ (char *)bhc_malloc (sizeof (static_gz_header) + 1);
+ memcpy (session->body.header.buff, static_gz_header, sizeof
(static_gz_header));
+ session->body.header.size = sizeof (static_gz_header);
session->body.header.offset = 0;
/* Construct gzip footer */
signature.asc
Description: Digital signature
Bug#299831: postfix-mysql causes trouble
Hi, On Tue, Sep 13, 2005, Guillaume Morin wrote: > nss-mysql calls openlog() only to print errors. Thomas, if you fix the > error that is printed before that message, nss-mysql will not interfere > with your application anymore. > > Calling openlog has a purpose here since it would be hard to distinguish > between applications errors and errors from the nss module otherwise. I don't know what error lead to this at Thomas' site, and I certainly agree that during debugging and for system errors, it is ok to use syslog. However connection problems are frequent with databases, and breaking the system logs of random apps because of a temporary connection problem isn't always appreciated. I don't use libnss-mysql myself though, I originally followed because I thought it was a postfix-mysql issue. Bye, -- Loïc Minier <[EMAIL PROTECTED]> Come, your destiny awaits!
Bug#328047: FTBFS: Test case failures
Package: libsql-abstract-limit-perl Version: 0.033-3 Severity: serious libsql-abstract-limit-perl fails to build because some of its test cases fail: > /usr/bin/perl Build test > t/00.load.# Testing SQL::Abstract::Limit 0.033 > ok > t/01.sql.. > # Failed test (t/01.sql.t at line 52) > # died: Can't locate object method "_quote" via package "TheTable" (perhaps > you forgot to load "TheTable"?) at /usr/share/perl5/SQL/Abstract.pm line 190. > > # Failed test (t/01.sql.t at line 53) > # undef > # doesn't match '(?-xism:requestor\,\ worker\,\ colC\,\ colH\ FROM\ > TheTable\ WHERE\ \(\ requestor\ \=\ \?\ AND\ status\ \!\=\ \?\ AND\ \(\ \(\ > worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ > \)\ \))' > > # Failed test (t/01.sql.t at line 54) > # undef > # doesn't match '(?-xism:^SELECT\ requestor\,\ worker\,\ colC\,\ colH\ > FROM\ TheTable\ WHERE\ \(\ requestor\ \=\ \?\ AND\ status\ \!\=\ \?\ AND\ \(\ > \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ > \)\ \)\ \)\ ORDER\ BY\ pay\,\ age\ LIMIT\ 10\ OFFSET\ 70$)' > > # Failed test (t/01.sql.t at line 57) > # died: Can't locate object method "_quote" via package "TheTable" (perhaps > you forgot to load "TheTable"?) at /usr/share/perl5/SQL/Abstract.pm line 190. > > # Failed test (t/01.sql.t at line 58) > # undef > # doesn't match '(?-xism:requestor\,\ worker\,\ colC\,\ colH\ FROM\ > TheTable\ WHERE\ \(\ requestor\ \=\ \?\ AND\ status\ \!\=\ \?\ AND\ \(\ \(\ > worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ > \)\ \))' > > # Failed test (t/01.sql.t at line 59) > # undef > # doesn't match '(?-xism:^SELECT\ requestor\,\ worker\,\ colC\,\ colH\ > FROM\ TheTable\ WHERE\ \(\ requestor\ \=\ \?\ AND\ status\ \!\=\ \?\ AND\ \(\ > \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ > \)\ \)\ \)\ ORDER\ BY\ pay\,\ age\ LIMIT\ 70\,\ 10$)' > > # Failed test (t/01.sql.t at line 62) > # died: Can't locate object method "_quote" via package "TheTable" (perhaps > you forgot to load "TheTable"?) at /usr/share/perl5/SQL/Abstract.pm line 190. > > # Failed test (t/01.sql.t at line 63) > # undef > # doesn't match '(?-xism:requestor\,\ worker\,\ colC\,\ colH\ FROM\ > TheTable\ WHERE\ \(\ requestor\ \=\ \?\ AND\ status\ \!\=\ \?\ AND\ \(\ \(\ > worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ > \)\ \))' > > # Failed test (t/01.sql.t at line 64) > # undef > # doesn't match '(?-xism:^SELECT\ requestor\,\ worker\,\ colC\,\ colH\ > FROM\ TheTable\ WHERE\ \(\ requestor\ \=\ \?\ AND\ status\ \!\=\ \?\ AND\ \(\ > \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ > \)\ \)\ \)\ ORDER\ BY\ pay\,\ age\ ROWS\ 70\ TO\ 80$)' > > # Failed test (t/01.sql.t at line 70) > # died: Can't locate object method "_quote" via package "TheTable" (perhaps > you forgot to load "TheTable"?) at /usr/share/perl5/SQL/Abstract.pm line 190. > > # Failed test (t/01.sql.t at line 71) > # undef > # doesn't match '(?-xism:requestor\,\ worker\,\ colC\,\ colH\ FROM\ > TheTable\ WHERE\ \(\ requestor\ \=\ \?\ AND\ status\ \!\=\ \?\ AND\ \(\ \(\ > worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ > \)\ \))' > > # Failed test (t/01.sql.t at line 79) > # died: Can't locate object method "_quote" via package "TheTable" (perhaps > you forgot to load "TheTable"?) at /usr/share/perl5/SQL/Abstract.pm line 190. > > # Failed test (t/01.sql.t at line 80) > # undef > # doesn't match '(?-xism:requestor\,\ worker\,\ colC\,\ colH\ FROM\ > TheTable\ WHERE\ \(\ requestor\ \=\ \?\ AND\ status\ \!\=\ \?\ AND\ \(\ \(\ > worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ > \)\ \))' > > # Failed test (t/01.sql.t at line 88) > # died: Can't locate object method "_quote" via package "TheTable" (perhaps > you forgot to load "TheTable"?) at /usr/share/perl5/SQL/Abstract.pm line 190. > > # Failed test (t/01.sql.t at line 91) > # undef > # doesn't match '(?-xism:requestor\,\ worker\,\ colC\,\ colH\ FROM\ > TheTable\ X\ WHERE\ \(\ requestor\ \=\ \?\ AND\ status\ \!\=\ \?\ AND\ \(\ > \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ \)\ OR\ \(\ worker\ \=\ \?\ > \)\ \)\ \))' > > # Failed test (t/01.sql.t at line 99) > # died: Can't locate object method "_quote" via package "TheTable" (perhaps > you forgot to load "TheTable"?) at /usr/share/perl5/SQL/Abstract.pm line 190. > > # Failed test (t/01.sql.t at line 100) > # undef > # doesn't match '(?-xism:requestor\,\ worker\,\ colC\,\ colH\ FROM\ > TheTable\ WHERE\ \(\ requestor\ \=\ \?\ AND\ status\ \!\=\ \?\ AND\ \(\ \(\ > worker\ \=\ \?\ \)\ OR\ \(\ worker\
Bug#328044: FTBFS: PIC register ebx clobbered in asm
Package: xmms-goom Version: 1.99.4-4 Severity: serious xmms-goom fails to build because it clobbers the PIC register ebx in an asm statement: > /bin/sh ../libtool --mode=compile gcc -Wall -g -O2 -DPACKAGE_NAME=\"\" > -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"SDL_Goom\" -DVERSION=\"1.99.0\" > -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 > -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 > -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_MMX=1 -c > -funroll-all-loops -fno-schedule-insns -fPIC -DPIC zoom_filter_mmx.c -o > zoom_filter_mmx.lo > gcc -Wall -g -O2 -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" > -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" > -DPACKAGE=\"SDL_Goom\" -DVERSION=\"1.99.0\" -DSTDC_HEADERS=1 > -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 > -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 > -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_MMX=1 -c -funroll-all-loops > -fno-schedule-insns -fPIC -DPIC zoom_filter_mmx.c -fPIC -DPIC -o > .libs/zoom_filter_mmx.o > mmx.h: In function 'zoom_filter_mmx_supported': > mmx.h:72: error: PIC register 'ebx' clobbered in 'asm' -- Matt signature.asc Description: Digital signature
Bug#328045: FTBFS: Unsatisfiable build-dependency on xwwin2.4-headers
Package: xmule Version: 1.10.0b-1 Severity: serious xmule fails to build because it cannot install wxwin2.4-headers, one of its build dependencies: > -> Considering wxwin2.4-headers >-> Trying wxwin2.4-headers >-> Cannot install wxwin2.4-headers; apt errors follow: > Reading package lists... > Building dependency tree... > Package wxwin2.4-headers is not available, but is referred to by another > package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > However the following packages replace it: > wx2.4-headers wx-common -- Matt signature.asc Description: Digital signature
Bug#328043: FTBFS: QWindowsStyle undeclared
Package: attal
Version: 0.9.2-1
Severity: serious
attal fails to build because QWindowsStyle is not declared because
QT_NO_STYLE_WINDOWS is defined and QT_PLUGIN is not defined:
> g++ -c -pipe -Wall -W -O2 -D_REENTRANT -fPIC -DQT_NO_DEBUG
> -DQT_THREAD_SUPPORT -DQT_SHARED -DQT_TABLET_SUPPORT
> -I/usr/share/qt3/mkspecs/default -I. -I.. -I/usr/include/qt3 -o attalStyle.o
> attalStyle.cpp
> attalStyle.h:25: error: expected class-name before '{' token
> attalStyle.cpp: In constructor 'AttalStyle::AttalStyle(QString, int)':
> attalStyle.cpp:37: error: class 'AttalStyle' does not have any field named
> 'QWindowsStyle'
> attalStyle.cpp: In member function 'void AttalStyle::polish(QApplication*)':
> attalStyle.cpp:171: error: 'white' was not declared in this scope
> attalStyle.cpp:172: error: no matching function for call to
> 'QColorGroup::setColor(QColorGroup::ColorRole, )'
> /usr/include/qt3/qpalette.h:77: note: candidates are: void
> QColorGroup::setColor(QColorGroup::ColorRole, const QColor&)
> attalStyle.cpp:174: error: 'black' was not declared in this scope
> attalStyle.cpp:175: error: no matching function for call to
> 'QColorGroup::setColor(QColorGroup::ColorRole, )'
> /usr/include/qt3/qpalette.h:77: note: candidates are: void
> QColorGroup::setColor(QColorGroup::ColorRole, const QColor&)
> attalStyle.cpp: In member function 'void
> AttalStyle::drawBevelButton(QPainter*, int, int, int, int, const
> QColorGroup&, bool, const QBrush*)':
> attalStyle.cpp:335: error: 'red' was not declared in this scope
> attalStyle.cpp: In member function 'void
> AttalStyle::drawPushButton(QPushButton*, QPainter*)':
> attalStyle.cpp:347: error: 'NoBrush' was not declared in this scope
> attalStyle.cpp:358: error: 'SolidLine' was not declared in this scope
> attalStyle.cpp:370: error: 'PE_ArrowDown' was not declared in this scope
> attalStyle.cpp:370: error: 'drawPrimitive' was not declared in this scope
> attalStyle.cpp:379: error: no matching function for call to
> 'QPainter::setBrush()'
> /usr/include/qt3/qpainter.h:111: note: candidates are: void
> QPainter::setBrush(const QBrush&)
> /usr/include/qt3/qpainter.h:112: note: void
> QPainter::setBrush(Qt::BrushStyle)
> /usr/include/qt3/qpainter.h:113: note: void
> QPainter::setBrush(const QColor&)
> attalStyle.cpp: In member function 'void
> AttalStyle::drawPushButtonLabel(QPushButton*, QPainter*)':
> attalStyle.cpp:397: error: 'AlignCenter' was not declared in this scope
> attalStyle.cpp:397: error: 'ShowPrefix' was not declared in this scope
> attalStyle.cpp:400: error: 'drawItem' was not declared in this scope
--
Matt
signature.asc
Description: Digital signature
Bug#328042: FTBFS: Unsatisfiable build-dependency on xlibmesa-dev
Package: chromium Version: 0.9.12-9 Severity: serious Tags: patch chromium fails to build because it has an unsatisfiable build-dependency on xlibmesa-dev: > -> Considering xlibmesa-dev >-> Trying xlibmesa-dev >-> Cannot install xlibmesa-dev; apt errors follow: > Reading package lists... > Building dependency tree... > Package xlibmesa-dev is not available, but is referred to by another package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > However the following packages replace it: > xlibmesa-gl-dev libglu1-xorg-dev Replacing this build-dependency with "xlibmesa-gl-dev | libglu1-xorg-dev" fixes the problem. -- Matt diff -u chromium-0.9.12/debian/control chromium-0.9.12/debian/control --- chromium-0.9.12/debian/control +++ chromium-0.9.12/debian/control @@ -2,7 +2,7 @@ Section: games Priority: optional Maintainer: Mike Furr <[EMAIL PROTECTED]> -Build-Depends: debhelper (>> 3.0.0), libsdl1.2-dev (>= 1.2.2-3.1), libsmpeg-dev, libopenal-dev, libglpng-dev, xlibmesa-dev, dpatch +Build-Depends: debhelper (>> 3.0.0), libsdl1.2-dev (>= 1.2.2-3.1), libsmpeg-dev, libopenal-dev, libglpng-dev, xlibmesa-gl-dev | libglu1-xorg-dev, dpatch Standards-Version: 3.6.2.0 Package: chromium signature.asc Description: Digital signature
Bug#328040: FTBFS: Missing build-dependency on bc
Package: cmucl Version: 19b-release-20050726-4 Severity: serious Tags: patch cmucl fails to build because it cannot run bc: > echo '1 + ' `cat version` | bc > ,version > /bin/sh: bc: command not found Adding bc to the build-dependencies fixes this problem. -- Matt diff -u cmucl-19b-release-20050726/debian/control cmucl-19b-release-20050726/debian/control --- cmucl-19b-release-20050726/debian/control +++ cmucl-19b-release-20050726/debian/control @@ -1,6 +1,6 @@ Source: cmucl Section: devel -Build-Depends: debhelper (>= 4.1.16), lesstif-dev, tetex-extra, cmucl (>= 19b-pre1-20050606-1), hevea, tidy, a2ps, x-dev, gcc-3.4 +Build-Depends: debhelper (>= 4.1.16), lesstif-dev, tetex-extra, cmucl (>= 19b-pre1-20050606-1), hevea, tidy, a2ps, x-dev, gcc-3.4, bc Priority: optional Maintainer: Peter Van Eynde <[EMAIL PROTECTED]> Standards-Version: 3.6.2.1 signature.asc Description: Digital signature
Bug#328041: libsepol1: Priority should be required
Package: libsepol1 Severity: important sysvinit, whose priority is required, pre-depends on libsepol1, whose priority is optional. According to chapter 2 of the Debian Policy Manual: Packages must not depend on packages with lower priority values (excluding build-time dependencies). This also breaks debootstrap, since it doesn't expect this requirement to be violated. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-powerpc Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328039: FTBFS: Uses unsupported -fwritable-strings option
Package: varkon Version: 1.18A-2 Severity: serious varkon fails to build because it uses the obsolete -fwritable-strings option: > gcc -ansi -pedantic -Wall -ffloat-store -fsigned-char -fwritable-strings -O > -DUNIX -DV3_X11 -DWRK_STAT -c -o varkon.o varkon.c > cc1: error: unrecognized command line option "-fwritable-strings" -- Matt signature.asc Description: Digital signature
Bug#328037: FTBFS: No rule to make target linux-gnu-i386
Package: u++ Version: 5.0.1-5 Severity: serious u++ fails to build because there is no rule to build linux-gnu-i386: > /usr/bin/make INSTALLBINDIR=/usr/bin INSTALLLIBDIR=/usr/lib/u++ > INSTALLINCDIR=/usr/include/u++ INSTALLMANDIR=/usr/share/man > INSTALLDOCDIR=/usr/share/doc/u++ CCBUILD=g++ linux-gnu-i386 > make[1]: Entering directory `/tmp/buildd/u++-5.0.1' > make[1]: *** No rule to make target `linux-gnu-i386'. Stop. > make[1]: Leaving directory `/tmp/buildd/u++-5.0.1' -- Matt signature.asc Description: Digital signature
Bug#328038: FTBFS: Automake errors
Package: xemeraldia Version: 0.4.1-1 Severity: serious xemeraldia fails to build because of a number of Automake errors: > automake --foreign > configure.ac: 8: `automake requires `AM_CONFIG_HEADER', not `AC_CONFIG_HEADER' > Makefile.am:18: AM_GNU_GETTEXT in `configure.ac' but `intl' not in SUBDIRS > automake: Makefile.am: AM_GNU_GETTEXT in `configure.ac' but `ALL_LINGUAS' not > defined > automake: Makefile.am: not supported: source file `bitmaps/block1cr.xbm' is > in subdirectory > automake: Makefile.am: not supported: source file `bitmaps/block1.xbm' is in > subdirectory > automake: Makefile.am: not supported: source file `bitmaps/block2cr.xbm' is > in subdirectory > automake: Makefile.am: not supported: source file `bitmaps/block2.xbm' is in > subdirectory > automake: Makefile.am: not supported: source file `bitmaps/block3cr.xbm' is > in subdirectory > automake: Makefile.am: not supported: source file `bitmaps/block3.xbm' is in > subdirectory > automake: Makefile.am: not supported: source file `bitmaps/block4cr.xbm' is > in subdirectory > automake: Makefile.am: not supported: source file `bitmaps/block4.xbm' is in > subdirectory > automake: Makefile.am: not supported: source file `bitmaps/block5cr.xbm' is > in subdirectory > automake: Makefile.am: not supported: source file `bitmaps/block5.xbm' is in > subdirectory > automake: Makefile.am: not supported: source file `bitmaps/block6cr.xbm' is > in subdirectory > automake: Makefile.am: not supported: source file `bitmaps/block6.xbm' is in > subdirectory > automake: Makefile.am: not supported: source file `bitmaps/colorblockcr.xbm' > is in subdirectory > automake: Makefile.am: not supported: source file `bitmaps/colorblock.xbm' is > in subdirectory > automake: Makefile.am: not supported: source file `bitmaps/crush0.xbm' is in > subdirectory > automake: Makefile.am: not supported: source file `bitmaps/crush1.xbm' is in > subdirectory > automake: Makefile.am: not supported: source file `bitmaps/crush2.xbm' is in > subdirectory > automake: Makefile.am: not supported: source file `bitmaps/crush3.xbm' is in > subdirectory > automake: Makefile.am: not supported: source file `bitmaps/crush4.xbm' is in > subdirectory > automake: Makefile.am: not supported: source file `bitmaps/icon.xpm' is in > subdirectory > automake: Makefile.am: not supported: source file `bitmaps/star.xbm' is in > subdirectory > Makefile.am:14: variable `LIBOBJS' not defined -- Matt signature.asc Description: Digital signature
Bug#328036: FTBFS: Missing forward class declarations
Package: tripwire
Version: 2.3.1.2.0-4
Severity: serious
Tags: patch
tripwire fails to build because it is missing some forward class
declarations:
> g++ -DHAVE_CONFIG_H-I. -I. -I../.. -I../../src-g -Wall -O2 -c
> -o fcodatasourceiter.o `test -f 'fcodatasourceiter.cpp' || echo
> './'`fcodatasourceiter.cpp
> ../../src/core/typed.h:57: warning: 'class iTyped' has virtual functions but
> non-virtual destructor
> ../../src/core/serializable.h:79: warning: 'class iSerializable' has virtual
> functions but non-virtual destructor
> ../../src/core/serializable.h:91: warning: 'class iTypedSerializable' has
> virtual functions but non-virtual destructor
> fconameinfo.h:46: warning: 'class iFCONameInfo' has virtual functions but
> non-virtual destructor
> fconame.h:147: error: ISO C++ forbids declaration of 'cFCOName_i' with no type
> fconame.h:147: error: expected ';' before '*' token
--
Matt
only in patch2:
unchanged:
--- tripwire-2.3.1.2.0.orig/src/fco/fconame.h
+++ tripwire-2.3.1.2.0/src/fco/fconame.h
@@ -49,6 +49,7 @@
///
class cFCONameTblNode;
class cFCONameIter;
+class cFCOName_i;
class cFCOName : public iTypedSerializable
{
only in patch2:
unchanged:
--- tripwire-2.3.1.2.0.orig/src/fco/fcosetimpl.h
+++ tripwire-2.3.1.2.0/src/fco/fcosetimpl.h
@@ -46,6 +46,8 @@
#include "fconame.h"
#endif
+class cFCOIterImpl;
+
class cFCOSetImpl : public iFCOSet
{
friend class cFCOIterImpl;
only in patch2:
unchanged:
--- tripwire-2.3.1.2.0.orig/src/tw/fcoreport.h
+++ tripwire-2.3.1.2.0/src/tw/fcoreport.h
@@ -85,6 +85,7 @@
class cFileHeaderID;
class cErrorQueue;
class cFCOReportGenreHeader;
+class cFCOReportSpecIter;
class cFCOReport : public iTypedSerializable
{
signature.asc
Description: Digital signature
Bug#328035: hicolor-icon-theme: FTBFS: Missing Build-Depends on 'cdbs'
Package: hicolor-icon-theme Version: 0.8-2 Severity: serious Tags: patch When building 'hicolor-icon-theme' in a clean 'unstable' chroot, I get the following error: debian/rules clean debian/rules:3: /usr/share/cdbs/1/rules/debhelper.mk: No such file or directory debian/rules:4: /usr/share/cdbs/1/rules/simple-patchsys.mk: No such file or directory debian/rules:5: /usr/share/cdbs/1/rules/utils.mk: No such file or directory debian/rules:6: /usr/share/cdbs/1/class/gnome.mk: No such file or directory make: *** No rule to make target `/usr/share/cdbs/1/class/gnome.mk'. Stop. Please add the missing Build-Depends on 'cdbs' to debian/control. Regards Andreas Jochens diff -urN ../tmp-orig/hicolor-icon-theme-0.8/debian/control ./debian/control --- ../tmp-orig/hicolor-icon-theme-0.8/debian/control 2005-09-13 05:57:45.0 + +++ ./debian/control2005-09-13 05:57:45.0 + @@ -3,7 +3,7 @@ Priority: optional Maintainer: Ross Burton <[EMAIL PROTECTED]> Uploaders: Debian GNOME Maintainers <[EMAIL PROTECTED]>, Akira TAGOH <[EMAIL PROTECTED]>, Andreas Rottmann <[EMAIL PROTECTED]>, Andrew Lau <[EMAIL PROTECTED]>, Carlos Perelló MarÃn <[EMAIL PROTECTED]>, Clément Stenac <[EMAIL PROTECTED]>, Ed Boraas <[EMAIL PROTECTED]>, Edd Dumbill <[EMAIL PROTECTED]>, Emil Soleyman-Zomalan <[EMAIL PROTECTED]>, Guilherme de S. Pastore <[EMAIL PROTECTED]>, Gustavo Noronha Silva <[EMAIL PROTECTED]>, J.H.M. Dassen (Ray) <[EMAIL PROTECTED]>, Joe Drew <[EMAIL PROTECTED]>, Johannes Rohr <[EMAIL PROTECTED]>, Jordi Mallach <[EMAIL PROTECTED]>, Jose Carlos Garcia Sogo <[EMAIL PROTECTED]>, Josselin Mouette <[EMAIL PROTECTED]>, Loic Minier <[EMAIL PROTECTED]>, Marc 'HE' Brockschmidt <[EMAIL PROTECTED]>, OndÅej Surý <[EMAIL PROTECTED]>, Rob Bradford <[EMAIL PROTECTED]>, Robert McQueen <[EMAIL PROTECTED]>, Sebastien Bacher <[EMAIL PROTECTED]>, Sjoerd Simons <[EMAIL PROTECTED]>, Takuo KITAME <[EMAIL PROTECTED]> -Build-Depends-Indep: debhelper (>= 4.0.0), gnome-pkg-tools +Build-Depends-Indep: debhelper, cdbs, gnome-pkg-tools Standards-Version: 3.6.2 Package: hicolor-icon-theme diff -urN ../tmp-orig/hicolor-icon-theme-0.8/debian/control.in ./debian/control.in --- ../tmp-orig/hicolor-icon-theme-0.8/debian/control.in2005-09-13 05:57:45.0 + +++ ./debian/control.in 2005-09-13 05:57:43.0 + @@ -3,7 +3,7 @@ Priority: optional Maintainer: Ross Burton <[EMAIL PROTECTED]> Uploaders: @GNOME_TEAM@ -Build-Depends-Indep: debhelper (>= 4.0.0), gnome-pkg-tools +Build-Depends-Indep: debhelper, cdbs, gnome-pkg-tools Standards-Version: 3.6.2 Package: hicolor-icon-theme -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328034: twutils: Depends on libtw0 that is waiting in the new pkgs list
Package: twutils Version: uninstallable Severity: important twutils is now built against libtw0, that is waiting for approval (being a NEW pkg). In the meantime, to test the new version of twin-0.5.1 and libtw0 (for i386 only, sorry), pkgs are available here: deb http://people.debian.org/~zufus twin/ Regards Marco -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327981: kpsk: uninstallable; needs rebuild for the Qt/KDE transition
Hi Adeodato, i've read and seen it already. Thanks for the report. I will look after ASAP. Regards, Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327901: postgresql-common: Fails after upgrade because of too strict checking of permissions on SSL key file
reassign 327901 postgresql-8.0 8.0.1-1 retitle 327901 postgresql-8.0: SSL cert permission check does not respect ACLs severity important thanks Hi Timo! Timo Weingärtner [2005-09-12 22:46 +0200]: > ---8<---8<--- > FATAL: unsichere Berechtigungen für private Schlüsseldatei > »/var/lib/postgresql/8.0/main/server.key« > DETAIL: Die Datei muss dem Datenbankbenutzer gehören und keine > Berechtigungen für »Gruppe« oder »Andere« haben. > ---8<---8<--- > > I don't want to try it with other locale settings because I don't want > to loose more accounting data. That's ok, I'm German. :-) > It sais "isecure permissions" and wants the file to be owned by the > database user an have maximum permissions of 0700. Right, but that has always been the case with postgresql-8.0. postgresql-common does not do this check, it is done by the postgresql server itself. > My permissions are: > > ---8<---8<--- > # file: etc/ssl/private/server.tiwe.homelinux.org_key.pem > # owner: root > # group: root > user::r-- > user:postgres:r-- > user:Debian-exim:r-- > group::--- > mask::r-- > other::--- > ---8<---8<--- > > (The key file is made immutable to keep cupsys from changing > permissions) Cupsys really shouldn't change the permissions of conffiles. Please file a serious bug against it. > If postgres thinks the file is insecure it could issue a warning, but > refusing to start is NOT OK. It has always been like this, this is not a new feature. However, I agree that the permission check should be more clever and take ACLs into account. I will try to improve the check. > Finally I AM THE ADMIN and I know what I'm doing. I don't need any > program pretending to be more clever than me. I disagree. Even good admins make errors, and a program should not attempt to use an insecure SSL certificate. Once you have a world-readable private key, you should throw it away and generate a new one. Without a failure, you would probably never recognize it. > There was no warning to check permissions before upgrading, so I lost > accounting data (not serious, it costs me no money). As I said, the upgrade did not introduce any new checks. The upgrade merely restarts the server. I suspect that your server had been running for a while, and at that time you introduced the ACLs. This causes no data loss, BTW. As a quick workaround, you can hardllink or copy the certificate and set the permissions to postgres:postgres 0400 (and adapt the path in postgresql.conf, of course). Thanks for the report, Martin -- Martin Pitt http://www.piware.de Ubuntu Developer http://www.ubuntulinux.org Debian Developerhttp://www.debian.org signature.asc Description: Digital signature
Bug#327828: mozilla-firefox: No "program icon" for Firefox
tag 327828 - unreproducible tag 327828 confirmed thanks Okay, I finally got what you meant... and can see the problem... strangely, the file needed for the icon to correctly show up is not provided by a make install anymore... It might be related to all the branding stuff they are putting. I'll check what goes on exactly. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#321808: O: ecb -- Code browser for several languages for Emacs.
> Do you still intend to adopt ecb? (This is just a ping, I'm not > interested in adopting it myself.) > > Thanks, > > Matej > Yes, I am! =) In fact I'm waiting for a sponsor, having posted an RFS at -mentors and at http://sponsors.debian.net . The packages are at http://zakame.spunge.org/pub/debian/ecb/ . My only gripe is that nobody's picking up the RFS. Care to be my sponsor? =P Cheers, Zakame -- ZAK B. ELEP Outside of Home -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#299831: postfix-mysql causes trouble
Loic, Thomas, On 12 Sep 14:29, Loïc Minier wrote: > > |Mar 15 16:28:38 bli nss-mysql[21338]: 9C7E4715DE: > > client=unknown[211.219.107.174] > > I'd rather blame libnss-mysql, which calls openlog. postfix-mysql > has nothing to do with this, and this probably happens because > postfix needs to do some getent() or similar nss queries. > > I'm reassigning to libnss-mysql which should not openlog(). nss-mysql calls openlog() only to print errors. Thomas, if you fix the error that is printed before that message, nss-mysql will not interfere with your application anymore. Calling openlog has a purpose here since it would be hard to distinguish between applications errors and errors from the nss module otherwise. I plan to close this bug unless someone speaks up. Guillaume. -- Guillaume Morin <[EMAIL PROTECTED]> Batailler corps et âmes pour un maudit refus (No one is innocent) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327918: 'man fsck' typos: "contiguos" and "greather"
tag 327918 +pending thanks On Mon, 2005-09-12 at 19:15 -0400, A Costa wrote: > Found a few typos in '/usr/share/man/man1/fsck.cpm.1.gz', see attached > '.diff'. Thank you! In my CVS for next upload. Bdale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327911: dpkg: error processing jde (--configure)
Package: jde
Version: 2.3.5
Tags: patch
The bug seems to be due to void function "jde-require", which seems be fixed
by the changes below to jde-bug.
Even if that problem is fixed, jde still does not work, as it requires cedet
version be between 1.0beta and 1.0 and 1.0pre is considered beyond that
range. The changes to jde.el below should fix that problem.
I also include a patch that fixes the cedet version problem. I came across the
patch after I fixed the bug.
Since /usr/info does not exist in Debian any more, I include a patch to fix
that in emacs-install and emacs-remove, though at present that's not used
since install-info-altdir still does not exist.
--- jde-2.3.5.orig/lisp/jde-bug.el
+++ jde-2.3.5/lisp/jde-bug.el
@@ -36,6 +36,7 @@
;;; Code:
(require 'cl)
+(require 'jde-util)
(require 'jde-parse)
(require 'jde-dbs)
(require 'jde-dbo)
--- jde-2.3.5.orig/lisp/jde.el
+++ jde-2.3.5/lisp/jde.el
@@ -999,13 +999,61 @@
(defun jde-earlier-versionp (ver1 ver2)
"Return non-nil if VER1 is earlier than VER2"
(let ((ver1-betap (string-match "beta" ver1))
-(ver2-betap (string-match "beta" ver2)))
+(ver2-betap (string-match "beta" ver2))
+ (ver1-prep (string-match "pre" ver1))
+ (ver2-prep (string-match "pre" ver2)))
(if (or (and ver1-betap ver2-betap)
(and (not ver1-betap) (not ver2-betap)))
-(string< ver1 ver2)
+(if (and ver2-prep (not ver1-prep))
+ nil
+ (if (and ver1-prep (not ver2-prep))
+ t
+ (string< ver1 ver2)))
(if ver1-betap
(progn
(or (string= ver2 (substring ver1 0 ver1-betap))
--- jde-2.3.5.orig/debian/emacsen-install
+++ jde-2.3.5/debian/emacsen-install
@@ -27,7 +27,7 @@
# Maybe somebody will write it.
if test -x /usr/sbin/install-info-altdir; then
echo install/${PACKAGE}: install Info links for ${FLAVOR}
-install-info-altdir --quiet --section "" ""
--dirname=${FLAVOR} /usr/info/${PACKAGE}.info.gz
+install-info-altdir --quiet --section "" ""
--dirname=${FLAVOR} /usr/share/info/${PACKAGE}.info.gz
fi
install -m 755 -d ${ELCDIR}
--- jde-2.3.5.orig/debian/emacsen-remove
+++ jde-2.3.5/debian/emacsen-remove
@@ -7,7 +7,7 @@
if [ ${FLAVOR} != emacs ]; then
if test -x /usr/sbin/install-info-altdir; then
echo remove/${PACKAGE}: removing Info links for ${FLAVOR}
-install-info-altdir --quiet --remove
--dirname=${FLAVOR} /usr/info/jde.info.gz
+install-info-altdir --quiet --remove
--dirname=${FLAVOR} /usr/share/info/jde.info.gz
fi
echo remove/${PACKAGE}: purging byte-compiled files for ${FLAVOR}
---8<---
Another patch from http://www.02.246.ne.jp/~torutk/jdee/jdee.html that fixes
the cedet 1.0 prerelease version problem
diff -u jde.el.orig jde.el
--- jde.el.orig 2004-12-17 13:29:35.0 +0900
+++ jde.el 2005-05-22 02:23:06.18750 +0900
@@ -987,14 +987,7 @@
(defun jde-check-version (current-version min-version max-version)
"Return non-nil if CURRENT-VERSION >= MIN-VERSION or <= MAX-VERSION."
- (and (or (jde-earlier-versionp current-version
- max-version)
- (string= current-version
-max-version))
- (or (jde-earlier-versionp min-version
- current-version)
- (string= current-version
-min-version
+ (not (inversion-test 'cedet min-version)))
(defun jde-earlier-versionp (ver1 ver2)
"Return non-nil if VER1 is earlier than VER2"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327741: it's more interesting than it looks like.
Hi, apparently there are plenty of files like that one with more desperate notes/copyrights in them. grep "You are not allowed to change this file" * -ril | wc -l shows at least 33 files with such statement. Fabio -- I'm going to make him an offer he can't refuse. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328033: pam_ldap.so no longer loadable with libc6 2.3.5-6
Package: libpam-ldap Version: 178-1sarge1 After upgrading libc6 to 2.3.5-6, pam_ldap is no longer usable. The error reported by dlopen() looks like this: > Sep 13 05:03:30 akk10-int gdm[18038]: PAM unable to > dlopen(/lib/security/pam_ldap.so) > Sep 13 05:03:30 akk10-int gdm[18038]: PAM [dlerror: /lib/tls/libresolv.so.2: > symbol __res_maybe_init, version GLIBC_PRIVATE not defined in file libc.so.6 > with link time reference] > Sep 13 05:03:30 akk10-int gdm[18038]: PAM adding faulty module: > /lib/security/pam_ldap.so Currently, libpam-ldap 178-1sarge1 seems to be the newest package, even for etch and sid. Enrik smime.p7s Description: S/MIME Cryptographic Signature
Bug#323220: darcs patch: Added option to use something else than debuild to build
Tue Sep 13 06:54:47 CEST 2005 Florian Ragwitz <[EMAIL PROTECTED]>
* Added option to use something else than debuild to build
New patches:
[Added option to use something else than debuild to build
Florian Ragwitz <[EMAIL PROTECTED]>**20050913045447] {
hunk ./darcs-buildpackage.hs 23
+import List
+
+split :: Eq a => [a]
+ -> [a]
+ -> [[a]]
+
+split glue xs = split' xs
+where
+split' [] = []
+split' xs = piece : split' (dropGlue rest)
+where (piece, rest) = breakOnGlue glue xs
+dropGlue = drop (length glue)
+
+breakOnGlue :: (Eq a) => [a]
+-> [a]
+-> ([a],[a])
+
+breakOnGlue _ [] = ([],[])
+breakOnGlue glue rest@(x:xs)
+| glue `isPrefixOf` rest = ([], rest)
+| otherwise = (x:piece, rest') where (piece, rest') = breakOnGlue glue xs
hunk ./darcs-buildpackage.hs 46
+ args <- getArgs
+ let (dbp_args, rest) = partition (isPrefixOf "--dbp_builder=") (["--dbp_builder=debuild"] ++ args)
+ let build_cmd = last $ split "=" $ last dbp_args
hunk ./darcs-buildpackage.hs 56
- safeSystem "debuild" (["-i_darcs", "-I_darcs"] ++ args)
+ safeSystem build_cmd (["-i_darcs", "-I_darcs"] ++ rest)
}
Context:
[TAG DEBIAN_darcs-buildpackage_0.5.5
John Goerzen <[EMAIL PROTECTED]>**20050909135152]
Patch bundle hash:
9f54d1166e42704787c829997f7e0ac05b0a9ff6
Bug#327893: fetchmail: Fetchmail 6.2.5-12sarge1 hast broken APOP. Query status=4 (PROTOCOL)
2005-09-12, 23:30 +0200, Nico Golde: > * Claudio André Till Clemens <[EMAIL PROTECTED]> [2005-09-12 23:08]: > > Package: fetchmail > > Version: 6.2.5-12sarge1 > > Severity: important ... > > Yes it seems like the new version made by the security team > lost its support for apop :( > > > I'll try then the version for sid (6.3.5-18). Maybe there is no problem > > with unstable :). > > Yes that would be nice, since I am not using apop. Please > report if it works so if it does we can provide a fixed > package. APOP Works again using 6.3.5-18. Regards Claudio -- +- .''`. ---| Dipl.-Inf. Univ. Claudio Clemens |--| Sarge |---+ | : :' : asturio at gmx (.) net GNU/Linux User #79942 | | `. `' http://asturio.gmxhome.de/begin.html| | `-"YE GODS, I HAVE FEET??!" <- Userfriendly | *** TURN OFF YOUR SYSTEM NOW !!! *** signature.asc Description: Digital signature
Bug#328003: xexec: uninstallable; needs rebuild for the Qt/KDE transition
tags 328003 patch thanks On Mon, Sep 12, 2005 at 08:34:22PM -0500, Zed Pobre wrote: > On Tue, Sep 13, 2005 at 01:47:50AM +0200, Adeodato Simó wrote: > > This is a grave bug filed against your package because it depends on > > libqt3c102-mt, which no longer exists, thus rendering yor package > > uninstallable in unstable. As part of the C++ ABI transition, this > > library has moved to the libqt3-mt package. > Unfortunately, my build box is also my personal workstation, and it > would be hamstrung if I upgraded to libqt3-mt at this moment, as it > would wipe out a good chunk of my graphical applications. If you can > NMU, feel free. Once a few more packages (mostly KDE stuff) make it > across, I'll get an official package built. NMU uploaded, here's the patch. :) diff -u xexec-0.0.3/debian/changelog xexec-0.0.3/debian/changelog --- xexec-0.0.3/debian/changelog +++ xexec-0.0.3/debian/changelog @@ -1,3 +1,11 @@ +xexec (0.0.3-22.1) unstable; urgency=medium + + * Non-maintainer upload. + * Medium-urgency upload for RC bugfix. + * Rebuild xexec for the C++ ABI transition (closes: #328003). + + -- Steve Langasek <[EMAIL PROTECTED]> Mon, 12 Sep 2005 20:15:41 -0700 + Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#319807: libxmlsec 1.2.9
Hi Rene, I appreciate the kick in the rear. I'll get the update submitted within a week. --John Rene Engelhard wrote: > Hi, > > I filed http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319807 49 days > ago and there still was no reaction? Was there a reason? Did you just > oversee it? > > As said, I want OOo to dynamically link against system-xmlsec and not > ship an own (patched, but that patch isn't needed with 1.2.8 anymore) > libxmlsec. > > So I wonder why libxmlsec1 didn't get updated yet? No time? Some other > reason? If you simply don't have time, may I NMU? > > Regards, > > Rene -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323077: initrd-tools: patch for #323077, handle linux-gate.so
On Tue, Sep 13, 2005 at 12:29:43PM +1000, Daniel Quinlan wrote:
> Package: initrd-tools
> Version: 0.1.82
> Followup-For: Bug #323077
>
> e2fsprogs is dying due to the new virtual DSO linux-gate.so
> as described here
> http://www.trilithium.com/johan/2005/08/linux-gate/
>
> see attached patch for a possible fix
>
> -- System Information:
> Debian Release: 3.1
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> Shell: /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.12.2-swsusp-acpi-fbsplash-inotify
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
>
> Versions of packages initrd-tools depends on:
> ii coreutils [fileutils] 5.2.1-2The GNU core utilities
> ii cpio 2.5-1.1GNU cpio -- a program to manage
> ar
> ii cramfsprogs 1.1-6 Tools for CramFs (Compressed ROM
> F
> ii dash 0.5.1-3The Debian Almquist Shell
> ii fileutils 5.2.1-2The GNU file management
> utilities
> ii util-linux2.12-7 Miscellaneous system utilities
>
> initrd-tools recommends no packages.
>
> -- no debconf information
> --- e2fsprogs.distrib 2004-05-05 23:04:43.0 +1000
> +++ e2fsprogs 2005-09-13 12:10:54.0 +1000
> @@ -11,7 +11,7 @@
> ;;
> esac
>
> -for i in `ldd /sbin/tune2fs /usr/bin/awk | sort -u | awk '{print $3}'`
> +for i in `ldd /sbin/tune2fs /usr/bin/awk | grep -v linux-gate.so | sort -u |
> awk '{print $3}' | grep -v ^$`
> do
> mkdir -p `dirname $INITRDDIR/$i`
> cp $i $INITRDDIR/$i
Which version of e2fsprogs and libc6 do you have?
I am wondering iof this is a duplicate of 324550
--
Horms
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328032: darcs: --set-scripts-executable works partially
Package: darcs Version: 1.0.3-2 Severity: important The original file has 0755 but after a "darcs get --set-scripts-executable", the mode is 0754. That is the owner/group flag is set, but not world. IMO, file attribute on *nix is part of the file and failing to restore it is a servere issue. This is information loss. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.31-xbox-chimpanzee-vs-ll Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages darcs depends on: ii libc6 2.3.5-6 GNU C Library: Shared libraries an ii libcurl3 7.13.2-2 Multi-protocol file transfer libra ii libgmp3c2 4.1.4-10 Multiprecision arithmetic library ii libidn11 0.5.18-1 GNU libidn library, implementation ii libncurses55.4-9 Shared libraries for terminal hand ii libreadline5 5.0-10GNU readline and history libraries ii libssl0.9.70.9.7e-3 SSL shared libraries ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328031: erlang: ftbfs [sparc] cp: cannot stat `lib/parsetools/ebin/*.beam'
Package: erlang Version: 1:10.b.7-1 Severity: serious Justification: fails to build from source erlang failed to build on a sparc buildd, duplicated on my sparc pbuilder. === Entering application hipe make[4]: Entering directory `/build/buildd/erlang-10.b.7/lib/hipe/rtl' /build/buildd/erlang-10.b.7/bin/sparc-unknown-linux-gnu/hipe_mkliterals -e > hipe_literals.hrl erlc -W +debug_info +inline -o../ebin hipe_rtl_arch.erl make[4]: *** [../ebin/hipe_rtl_arch.beam] Bus error make[4]: Leaving directory `/build/buildd/erlang-10.b.7/lib/hipe/rtl' make[4]: Entering directory `/build/buildd/erlang-10.b.7/lib/hipe/misc' erlc -W +debug_info -o../ebin hipe_consttab.erl make[4]: *** [../ebin/hipe_consttab.beam] Bus error make[4]: Leaving directory `/build/buildd/erlang-10.b.7/lib/hipe/misc' make[4]: Entering directory `/build/buildd/erlang-10.b.7/lib/hipe/main' sed -e "s;%VSN%;3.5.2;" hipe.hrl.src > hipe.hrl erlc -W +debug_info +nowarn_shadow_vars -o../ebin hipe.erl make[4]: *** [../ebin/hipe.beam] Bus error make[4]: Leaving directory `/build/buildd/erlang-10.b.7/lib/hipe/main' make[4]: Entering directory `/build/buildd/erlang-10.b.7/lib/hipe/cerl' erlc -W +debug_info +nowarn_shadow_vars +inline -o../ebin cerl_lib.erl make[4]: *** [../ebin/cerl_lib.beam] Bus error make[4]: Leaving directory `/build/buildd/erlang-10.b.7/lib/hipe/cerl' make[4]: Entering directory `/build/buildd/erlang-10.b.7/lib/hipe/icode' erlc -W +debug_info +nowarn_shadow_vars -o../ebin hipe_icode.erl make[4]: *** [../ebin/hipe_icode.beam] Bus error make[4]: Leaving directory `/build/buildd/erlang-10.b.7/lib/hipe/icode' make[4]: Entering directory `/build/buildd/erlang-10.b.7/lib/hipe/flow' erlc -W +debug_info -o../ebin hipe_bb.erl make[4]: *** [../ebin/hipe_bb.beam] Bus error make[4]: Leaving directory `/build/buildd/erlang-10.b.7/lib/hipe/flow' make[4]: Entering directory `/build/buildd/erlang-10.b.7/lib/hipe/util' erlc -W +debug_info -o../ebin hipe_timing.erl make[4]: *** [../ebin/hipe_timing.beam] Bus error make[4]: Leaving directory `/build/buildd/erlang-10.b.7/lib/hipe/util' === Leaving application hipe make[3]: Leaving directory `/build/buildd/erlang-10.b.7/lib/hipe' make[2]: Leaving directory `/build/buildd/erlang-10.b.7/lib' if test ! -d /build/buildd/erlang-10.b.7/bootstrap/lib/kernel ; then mkdir /build/buildd/erlang-10.b.7/bootstrap/lib/kernel ; fi if test ! -d /build/buildd/erlang-10.b.7/bootstrap/lib/kernel/ebin ; then mkdir /build/buildd/erlang-10.b.7/bootstrap/lib/kernel/ebin ; fi if test ! -d /build/buildd/erlang-10.b.7/bootstrap/lib/kernel/include ; then mkdir /build/buildd/erlang-10.b.7/bootstrap/lib/kernel/include ; fi cp -f lib/kernel/ebin/*.beam /build/buildd/erlang-10.b.7/bootstrap/lib/kernel/ebin cp -f lib/kernel/include/*.hrl /build/buildd/erlang-10.b.7/bootstrap/lib/kernel/include if test ! -d /build/buildd/erlang-10.b.7/bootstrap/lib/hipe ; then mkdir /build/buildd/erlang-10.b.7/bootstrap/lib/hipe ; fi if test ! -d /build/buildd/erlang-10.b.7/bootstrap/lib/hipe/ebin ; then mkdir /build/buildd/erlang-10.b.7/bootstrap/lib/hipe/ebin ; fi if test -f lib/hipe/ebin/hipe.beam ; then cp lib/hipe/ebin/*.beam /build/buildd/erlang-10.b.7/bootstrap/lib/hipe/ebin; fi if test ! -d /build/buildd/erlang-10.b.7/bootstrap/lib/parsetools ; then mkdir /build/buildd/erlang-10.b.7/bootstrap/lib/parsetools ; fi if test ! -d /build/buildd/erlang-10.b.7/bootstrap/lib/parsetools/ebin ; then mkdir /build/buildd/erlang-10.b.7/bootstrap/lib/parsetools/ebin ; fi if test ! -d /build/buildd/erlang-10.b.7/bootstrap/lib/parsetools/include ; then mkdir /build/buildd/erlang-10.b.7/bootstrap/lib/parsetools/include ; fi cp lib/parsetools/ebin/*.beam /build/buildd/erlang-10.b.7/bootstrap/lib/parsetools/ebin cp: cannot stat `lib/parsetools/ebin/*.beam': No such file or directory make[1]: *** [secondary_bootstrap_copy] Error 1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328030: mapserver: implicitly converted pointers
Package: mapserver Version: 4.6.1-2 Severity: important Tags: patch Our automated buildd log filter[1] detected a problem[2] that will cause your package to segfault on architectures where the size of a pointer is greater than the size of an integer, such as ia64. The _XOPEN_SOURCE definition fixes this warning; the #include fixes another warning about strcasecmp(). [1]http://people.debian.org/~dannf/check-implicit-pointer-functions [2]Function `strptime' implicitly converted to pointer at maptime.c:166 --- mapserver-4.6.1/maptime.c.orig 2005-09-12 20:48:05.0 -0600 +++ mapserver-4.6.1/maptime.c 2005-09-12 20:49:12.0 -0600 @@ -44,9 +44,11 @@ * */ +#define _XOPEN_SOURCE #include #include #include +#include #include "map.h" #include "maptime.h" -- dann frazier <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327563: dx: scripting incompatible with SMP dx...
Hi Daniel,
On Mon, Sep 12, 2005, Daniel Kobras wrote:
> Moi!
>
> On Sat, Sep 10, 2005 at 08:18:27PM -0400, Daniel Freedman wrote:
> > 'dx -script' does not seem to work for me on SMP machines, though
> > forcing dx to use only one processor allows it to succeed:
> > 'dx -processors 1 -script'
>
> Thank you for the report. Unfortunately, I wasn't able to reproduce it
> on a two processor machine. Can you please run "strace -f dx -script"
> and send in the final lines to see where it hangs? Do you use any
> external plugins for dx?
Strace final output appended at end of this email. I'm not using any
external plugins for dx...
> Regards,
>
> Daniel.
Thanks for the help, and best wishes,
Daniel
Tail of strace output:
==
[pid 9757] old_mmap(NULL, 44296, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb725d000
[pid 9757] old_mmap(0xb7267000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x9000) = 0xb7267000
[pid 9757] close(3)= 0
[pid 9757] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb725c000
[pid 9757] old_mmap(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb725b000
[pid 9757] mprotect(0xb7867000, 4096, PROT_READ) = 0
[pid 9757] set_thread_area({entry_number:-1 -> 6, base_addr:0xb725b8e0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}) = 0
[pid 9757] munmap(0xb7fdb000, 58663) = 0
[pid 9757] set_tid_address(0xb725b928) = 9757
[pid 9757] rt_sigaction(SIGRTMIN, {0xb7347370, [], SA_SIGINFO}, NULL, 8) = 0
[pid 9757] rt_sigaction(SIGRT_1, {0xb73473f0, [], SA_RESTART|SA_SIGINFO},
NULL, 8) = 0
[pid 9757] rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
[pid 9757] getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024,
rlim_max=RLIM_INFINITY}) = 0
[pid 9757] _sysctl({{CTL_KERN, KERN_VERSION, 0, 20bb1, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0}, 2, 0xb620, 35,
(nil), 0}) = 0
[pid 9757] rt_sigaction(SIGSEGV, {0x8069230, [SEGV], SA_RESTART}, {SIG_DFL},
8) = 0
[pid 9757] brk(0) = 0x8507000
[pid 9757] brk(0x8528000) = 0x8528000
[pid 9757] open("/etc/mtab", O_RDONLY) = 3
[pid 9757] fstat64(3, {st_mode=S_IFREG|0644, st_size=723, ...}) = 0
[pid 9757] mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0xb7fe9000
[pid 9757] read(3, "/dev/hda1 / ext3 rw,errors=remou"..., 4096) = 723
[pid 9757] close(3)= 0
[pid 9757] munmap(0xb7fe9000, 4096)= 0
[pid 9757] open("/proc/stat", O_RDONLY) = 3
[pid 9757] fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
[pid 9757] mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0xb7fe9000
[pid 9757] read(3, "cpu 94869035 6063 9705171 25736"..., 1024) = 797
[pid 9757] read(3, "", 1024) = 0
[pid 9757] close(3)= 0
[pid 9757] munmap(0xb7fe9000, 4096)= 0
[pid 9757] rt_sigaction(SIGPIPE, {0x8072890, [PIPE], SA_RESTART}, {SIG_DFL},
8) = 0
[pid 9757] rt_sigaction(SIGQUIT, {0x80728f0, [QUIT], SA_RESTART}, {SIG_DFL},
8) = 0
[pid 9757] write(1, "Open Visualization Data Explorer"..., 104Open
Visualization Data Explorer
More Info at www.research.ibm.com/dx
and www.opendx.org
Version - 4.3.2) = 104
[pid 9757] write(1, "\n", 1
) = 1
[pid 9757] stat64("/tmp/P.locks", {st_mode=S_IFREG|S_ISGID|S_ISVTX|0500,
st_size=0, ...}) = 0
[pid 9757] stat64("/tmp/P.locks", {st_mode=S_IFREG|S_ISGID|S_ISVTX|0500,
st_size=0, ...}) = 0
[pid 9757] shmget(1627465825, 770088, IPC_CREAT|0666) = 88113178
[pid 9757] shmat(88113178, 0, 0) = 0xb719e000
[pid 9757] semop(32769, 0xb796, 1
--
Daniel A. Freedman <[EMAIL PROTECTED]>, Graduate Fellow
Electronic Structure Calculations, LASSP, Cornell University
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#323077: initrd-tools: patch for #323077, handle linux-gate.so
Package: initrd-tools
Version: 0.1.82
Followup-For: Bug #323077
e2fsprogs is dying due to the new virtual DSO linux-gate.so
as described here
http://www.trilithium.com/johan/2005/08/linux-gate/
see attached patch for a possible fix
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.2-swsusp-acpi-fbsplash-inotify
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages initrd-tools depends on:
ii coreutils [fileutils] 5.2.1-2The GNU core utilities
ii cpio 2.5-1.1GNU cpio -- a program to manage ar
ii cramfsprogs 1.1-6 Tools for CramFs (Compressed ROM F
ii dash 0.5.1-3The Debian Almquist Shell
ii fileutils 5.2.1-2The GNU file management utilities
ii util-linux2.12-7 Miscellaneous system utilities
initrd-tools recommends no packages.
-- no debconf information
--- e2fsprogs.distrib 2004-05-05 23:04:43.0 +1000
+++ e2fsprogs 2005-09-13 12:10:54.0 +1000
@@ -11,7 +11,7 @@
;;
esac
-for i in `ldd /sbin/tune2fs /usr/bin/awk | sort -u | awk '{print $3}'`
+for i in `ldd /sbin/tune2fs /usr/bin/awk | grep -v linux-gate.so | sort -u |
awk '{print $3}' | grep -v ^$`
do
mkdir -p `dirname $INITRDDIR/$i`
cp $i $INITRDDIR/$i
signature.asc
Description: Digital signature
Bug#327954: droidbattles: uninstallable; needs rebuild for the Qt/KDE transition
On Tue, Sep 13, 2005 at 01:47:45AM +0200, Adeodato Simó wrote: > Simply recompiling and uploading your package should be enough to fix > this; as per this mail [1], you need not bump your Qt, kdelibs or aRts Unfortunately this appears not be the case with droidbattles. Apparently moc doesn't get called anymore or something else to that effect. I'm not quite sure what's going on. All in all, the build system's quite dated and a hack. My plan is to teach myself to use kdevelop and recreate the build system with that. That should be happening... Soon.
Bug#328028: laptop-mode-tools: Invokes hdparm unconditionally
Package: laptop-mode-tools Version: 1.10-1 Hi, This packages recommends hdparm, and on my laptop it's not installed, but then laptop_mode does not check if it's available, and thus I get a hude amount of lines with errors trying to exec it. Please make the invokation of hdparm only if it's available. Or a less desirable solution would be to move it from a Recommends to a Depends. regards, guillem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327898: python2.3-clientcookie: The version in Debian is quite old
Stephane Bortzmeyer wrote: Package: python2.3-clientcookie Version: 0.4.19-1 Severity: wishlist $ apt-cache show python2.3-clientcookie Package: python2.3-clientcookie Priority: optional Section: python Installed-Size: 328 Maintainer: Ganesan Rajagopal <[EMAIL PROTECTED]> Architecture: all Source: clientcookie Version: 1.0.3-1 Depends: python2.3 Filename: pool/main/c/clientcookie/python2.3-clientcookie_1.0.3-1_all.deb Size: 84972 MD5sum: cfe6d3123e7911151d57a953049617af Description: Python 2.3.x module for automating HTTP cookie management ClientCookie is a pure Python module for automatic HTTP cookie management. . This package is built for Python 2.3.x Tag: devel::library, langdevel::python, made-of::lang:python, protocol::http, role::content:data There is, for more than a year, a 1.0.3 on the upstream site (http://wwwsearch.sourceforge.net/ClientCookie/) and interesting programs like mechanize (http://wwwsearch.sourceforge.net/mechanize/) require it. 1.0.3 is already in testing. The package was uploaded to unstable on June 28th. Can you recheck if you've by chance put the package on hold? Please file a bug if mechanize is still breaking with the testing version of python2.3-clientcookie and I'll take look. One more question, since you're a user of this package. I did not package a python2.4 version since python2.4 provides cookielib. If you still see a need for clientcookie for 2.4, I'll consider packaging it. Ganesan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327921: forwarded typos upstream
forwarded 327921 http://bugzilla.remotesensing.org/show_bug.cgi?id=928 forwarded 327922 http://bugzilla.remotesensing.org/show_bug.cgi?id=928 forwarded 327923 http://bugzilla.remotesensing.org/show_bug.cgi?id=928 forwarded 327924 http://bugzilla.remotesensing.org/show_bug.cgi?id=928 thanks I have reported your bug reports upstream in their bug tracking system, bug number 928. They are very prompt, so you can expect this to be fixed in the next version. I will not do a special upload to correct these, but I very much appreciate your bug report. Thanks! -- Jay Berkenbilt <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327515: Critical Regression between 0.8.3 and 0.8.2
On Sat, Sep 10, 2005 at 06:01:55PM +, roucaries bastien wrote: > It is not possible to connect to msn with 0.8-3 and kopete. > Log are not useful and are: > [Sat Sep 10 17:49:52 2005] [CONN_NB] Connection [172.20.3.2:33084 -> > 65.54.239.20:1863 via proxy] created [pending connection] (5 6) > [Sat Sep 10 17:49:52 2005] [CONN_NB] Connection [172.20.3.2:33085 -> > 65.54.239.20:1863 via proxy] created [pending connection] (7 8) > > Theses messages are not in the previous version The only code change between 0.8-2 and 0.8-3 was an OSCAR bugfix and so should really not affect MSN. Please verify that the change is definitely caused by this upgrade of this package, and not related libraries. Thanks. -- Chris Boyle - http://cmb.is-a-geek.org/ GPG: B7D86E0F, MSN: [EMAIL PROTECTED], ICQ: 24151961, AIM: kerneloops, Yahoo: kerneloops, IRC: cmb on irc.uwcs.co.uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#326883: new version of patch for kdevelop 3.2.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Here is the final version of the patch to build KDevelop 3.2.2. I will be NMU'ing KDevelop shortly. Kind regards, Jeremy - -- http://www.jerryweb.org/ : JerryWeb.org http://sailcut.sourceforge.net/ : Sailcut CAD http://opensource.polytechnique.org/ : Polytechnique.org Free Software -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDJify4mJJZqJp2ScRAgeiAKDBc94liUyDxkwFRKcBCVXVErR1OACePZu6 DyxpWCeEi4AUEPfPxuPfnlE= =SRHO -END PGP SIGNATURE- kdevelop3_3.2.2-0.1.diff.gz Description: application/gzip
Bug#328027: RFP: python2.4-matplotlib -- matplotlib is a Python module that implements graphical plotting in a manner similar to the comercial Matlab environment
Package: wnpp Severity: wishlist this is a request for packaging of the Python matplotlib module. it is a Python implementation of plotting and data file loading mainly for scientific purposes. the commands and their usage are very intuitive to users of Matlab and octave. the website is http://matplotlib.sourceforge.net/ the license may be non-free. perhaps it could be included in either non-free or contrib. http://matplotlib.sourceforge.net/license.html thanks for your consideration. Mike Gilbert * Package name: python2.4-matplotlib Version : x.y.z Upstream Author : Name <[EMAIL PROTECTED]> * URL : http://www.example.org/ * License : (GPL, LGPL, BSD, MIT/X, etc.) Description : matplotlib is a Python module that implements graphical plotting in a manner similar to the comercial Matlab environment (Include the long description here.) -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#210125: Please refer to ID 782621
Hi, Did you recieve my email from last week? I'm happy to tell you that you can get a home refinance loan at a rock-bottom rate. Approval process will only take 1 minute. Your tracking number is # B6 623 154 You must visit the link below in 24 hrs to confirm your details. http://www.2mort.com/b.php Best Regards, Alicia Mccullough Dicontinue www.2mort.com/book.php -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#128326: Time sensitive... refer to # L580366
Hi, Did you recieve my email from last week? I'm happy to tell you that you can get a home refinance loan at a rock-bottom rate. Approval process will only take 1 minute. Your tracking number is # E6 369 372 You must visit the link below in 24 hrs to confirm your details. http://www.2mort.com/b.php Best Regards, Henrietta Carver Dicontinue www.2mort.com/book.php -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328026: kino: uninstallable
Package: kino Severity: normal Hi, kino is uninstallable in sid due to a dependency on libquicktime1, which appears to have been replaced with libquicktime0. Thanks, -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (300, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.10-quaternion1 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kino depends on: pn gdk-imlib1 Not found. pn libart2 Not found. ii libaudiofile0 0.2.6-6Open-source version of SGI's audio pn libavc1394-0 Not found. ii libc6 2.3.5-3GNU C Library: Shared libraries an ii libdb33.2.9-22 Berkeley v3 Database Libraries [ru pn libdv2 Not found. ii libesd0 0.2.36-1 Enlightened Sound Daemon - Shared ii libglib1.21.2.10-10 The GLib library of C routines pn libgnome32 Not found. pn libgnomesupport0 Not found. pn libgnomeui32 Not found. ii libgtk1.2 1.2.10-17 The GIMP Toolkit set of widgets fo ii libraw1394-5 0.10.1-1.1 library for direct access to IEEE pn libstdc++2.10-glibc2.2 Not found. ii libxml2 2.6.20-1 GNOME XML library ii xlibs 6.8.2.dfsg.1-5 X Window System client libraries m -- Jason McCarty <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328015: qgis: uninstallable; needs rebuild for the Qt/KDE transition
merge 328015 327597 thanks On Tue, 2005-09-13 at 01:47 +0200, Adeodato Simó wrote: > Package: qgis > Version: 0.6.0-2 > Severity: grave > Tags: sid > > Hello, > > This is a grave bug filed against your package because it depends on > libqt3c102-mt, which no longer exists, thus rendering yor package > uninstallable in unstable. As part of the C++ ABI transition, this > library has moved to the libqt3-mt package. I have been waiting for various dependencies to clear the transition. 8<-snip- > > Finally, if there's a strong reason for which your package should not > be NMUed, please note so in this bug report. Prospective NMUers will > read your reasoning, and will decide if it's strong enough to delay > their upload. > Please do not NMU this package. Some deps have not yet built on all arches. I will upload at the appropriate time. Thanks, Steve > Thanks for your cooperation, and happy hacking! > > > P.S.: There may be an already reported bug against this package for > this very same reason. I've checked for that, and will be merging the > bugs soon. The reason for still filing this bug was to have the > opportunity of including the small bits of information above. I > apologize for the inconvenience. > >
Bug#321808: O: ecb -- Code browser for several languages for Emacs.
On Mon, Aug 08, 2005 at 09:57:57PM +0800, Zak B. Elep wrote: > package ecp > retitle 321808 ITA: ecb -- Code browser for several languages for Emacs. > owner 321808 ! [...] > I'll take this. :) I just happened to fetch this package a couple of > days ago as I was looking on trying out CEDET and ECB. Do you still intend to adopt ecb? (This is just a ping, I'm not interested in adopting it myself.) Thanks, Matej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327959: builds with gcc-4.0
This is just a quick note to let you know that I rebuilt knutclient locally in a clean sid pbuilder chroot, and it built fine. I have not yet upgraded my desktop computer to kde 3.4.2, so I haven't yet tested the new package. If knutclient hasn't been uploaded for the transition yet when I do upgrade, I'll send another e-mail with my testing results. Josh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328025: enigmail: places dialog between two xinerama screens
Package: mozilla-thunderbird-enigmail Version: 2:0.92-3 Severity: minor If two monitors are used with the xinerama-option, the passprase dialog ends up between the screens. It should go to the center of the monitor where the mouse is located. ---<(kaimartin)>--- -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-1-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages mozilla-thunderbird-enigmail depends on: ii gnupg 1.4.1-1GNU privacy guard - a free PGP rep ii libc6 2.3.5-3GNU C Library: Shared libraries an ii libgcc1 1:4.0.1-4 GCC support library ii libstdc++64.0.1-4The GNU Standard C++ Library v3 ii mozilla-thunderbird 1.0.6-3Mozilla Thunderbird standalone mai mozilla-thunderbird-enigmail recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327081: ITP: rpmstrap -- bootstrap a basic RPM-based system
On Mon, Sep 12, 2005 at 02:19:09PM -0500, Sam Hart wrote: > It actually was not my decision to GPLv2 it. I honestly didn't care what > license it was released under. GPLv2 was just what the original base as > written by Branden Robinson was copyrighted under. > > > 1) Identical command-line options: > > > 2) Placing of suite scripts inside of a "scripts/*" directory: > > > 3) Making common functions available to suite scripts: > > that you did seem to copy quite a bit from debootstrap anyway. > No, I did not. Maintaining an identical interface and file layout is not > copying code. There are other things that are copyrightable besides code -- in particular, usage/error messages (depending on their length and number) are likely to be covered by copyright, and it's pretty implausible that those would be the same between debootstrap and rpmstrap *without* direct copying. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#167780: 0.3.4 is in testing
On 12 September 2005 at 23:59, Jeroen van Wolffelaar wrote: | On Sun, Apr 03, 2005 at 08:10:02AM -0500, Dirk Eddelbuettel wrote: | > | > On 31 March 2005 at 02:35, Jeroen van Wolffelaar wrote: | > | tags 167780 moreinfo | > | thanks | > | | > | On Sun, Jan 25, 2004 at 11:25:15AM -0600, Dirk Eddelbuettel wrote: | > | > On Sun, Jan 25, 2004 at 04:16:01PM +, Daniel Silverstone wrote: | > | > > Hi, | > | > > | > | > > Since quantlib is up to date in testing currently, do you still want | > | > > this package to be removed from the arm architecture? | > | > | > | > Yes. | > | > I believe that this has happened recently (but I was gone on vacation for | > the last few days, so something may have changed). | > | > | > If in fact I, as maintainer, have a choice in the matter , then I would like | > | > to request the same for the following packages: | > | > | > | >octave2.1, quantlib, r-base | > | > | > | > for the | > | > | > | >arm, m68k | > | > | > | > architectures. I have spent *way* too much fscking special requests for | > | > these smaller + older architecture which are, quite simply, mismatched for | > | > these numerically-focussed applications and environments. | > | | > | Please convince a porter for those architectures to add the right lines | > | > | > How would I do that? Whenever I discuss this with people from the porting | > teams, their attitude usually is "why -- we may as well build it". Which is | > wrong, IMHO, as these arches _do_ hold up releases of these packages more | > often than I like. | > | > I still need help in this matter. | | I'm sorry, but at this moment I cannot remove those packages. If at some | moment in the future one architectures is lagging behind on this | package, and there is no porter willing to help you fix it, please | request removal then. If this package and the packages (build-)depending | on it don't get added to Packages-arch-specific, it has no use dropping | the builds for those archs. I've no problem removing builds if the | porters are not willing or able to assist in keeping your package | uptodate on their architecture. Please look at http://people.debian.org/~igloo/status.php?email=edd%40debian.org where arm, and in particular m68k, are almost always lagging. Which is why I opened this bug report in Jan (!!) of 2004 (!!) i.e. over 20 months ago. Disappointed, Dirk -- Statistics: The (futile) attempt to offer certainty about uncertainty. -- Roger Koenker, 'Dictionary of Received Ideas of Statistics' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#284805: Buddy icons leftside on the contact list
This request should be fixed by the elipsis code currently in 2.0.0cvs. the particular solution advocated here will only work well with some gtk themes, as the space available to the left side of the icon varies with theme. replacing the protocol icon with the buddy list is not acceptable to us (upstream), as we deam this to be valuable information not so easily conveyed in any other part of the UI. luke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#273460: Show blocked and not in list buddies status
That blog post rather confuses me. Gaim's had msn buddy icon support for some time. but reguardless, gaim'll tell you if the other person has you blocked or does not have you on their list in the tooltip. Do these really need an icon? luke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#223065: Show three dots when buddyname is out of visible list
This functionality is included for gtk 2.6 for gaim 2.0.0, and so this bug will be fixed with that release. luke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328024: xlibmesa-gl fails to install on i386 unstable
Package: xlibmesa-gl Version: 6.8.2.dfsg.1-7 xlibmesa-gl fails to install on Debian/unstable. Here's the transcript: Preparando para reemplazar xlibmesa-gl 6.8.2.dfsg.1-6 (usando .../xlibmesa-gl_6.8.2.dfsg.1-7_i386.deb) ... Desempaquetando el reemplazo de xlibmesa-gl ... dpkg: error al procesar /var/cache/apt/archives/xlibmesa-gl_6.8.2.dfsg.1-7_i386.deb (--unpack): no se puede crear `./usr/X11R6/lib/libGL.so.1.2': No existe el fichero o el directorio dpkg-deb: el subproceso paste fue terminado por la señal (Tubería rota) Se encontraron errores al procesar: /var/cache/apt/archives/xlibmesa-gl_6.8.2.dfsg.1-7_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I'm using Debian GNU/Linux 2.6.13.1 and xserver-xfree86 4.3.0.dfsg.1-14 __ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328023: wine: forgets to remove /usr/bin/wineserver?
Package: wine Severity: normal File: /usr/bin/wineserver I presently have: $ ls -dl /usr/bin/wineserver /usr/lib/wine ls: /usr/lib/wine: No such file or directory lrwxr-xr-x 1 root root 24 May 26 2004 /usr/bin/wineserver -> /usr/lib/wine/wineserver and pn wine pn wine-doc pn wine-utils un winesetup ii winesetuptk 0.7-1.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328022: bittornado-gui: Fails to remove file in bin/
Package: bittornado-gui Version: 0.3.11-4 Severity: normal File: /usr/bin/btcompletedirgui usr/bin/btcompletedirgui is presently an indirectly broken symlink: $ ls -l /usr/bin/btcompletedirgui lrwxr-xr-x 1 root root 34 Sep 21 2004 /usr/bin/btcompletedirgui -> +/etc/alternatives/btcompletedirgui $ ls -l /etc/alternatives/btcompletedirgui lrwxr-xr-x 1 root root 36 Sep 21 2004 /etc/alternatives/btcompletedirgui -> +/usr/bin/btcompletedirgui.bittornado which is nonextant. I have: ii bittornado 0.3.11-4 pn bittornado-gui -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328021: kbiff: uninstallable; needs rebuild for the Qt/KDE transition
Package: kbiff Version: 3.7.1-3.1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328020: synce-kde: uninstallable; needs rebuild for the Qt/KDE transition
Package: synce-kde Version: 0.8.1.1-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328019: stopmotion: uninstallable; needs rebuild for the Qt/KDE transition
Package: stopmotion Version: 0.3.2-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328018: zsafe: uninstallable; needs rebuild for the Qt/KDE transition
Package: zsafe Version: 2.1.3-2 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328017: kxdocker: uninstallable; needs rebuild for the Qt/KDE transition
Package: kxdocker Version: 0.35-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328016: qsynth: uninstallable; needs rebuild for the Qt/KDE transition
Package: qsynth Version: 0.2.3-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328015: qgis: uninstallable; needs rebuild for the Qt/KDE transition
Package: qgis Version: 0.6.0-2 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328014: rosegarden4: uninstallable; needs rebuild for the Qt/KDE transition
Package: rosegarden4 Version: 1.0-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328013: qps: uninstallable; needs rebuild for the Qt/KDE transition
Package: qps Version: 1.9.7.0-3 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328011: mypasswordsafe: uninstallable; needs rebuild for the Qt/KDE transition
Package: mypasswordsafe Version: 0.0.20041004-2 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328012: kdirstat: uninstallable; needs rebuild for the Qt/KDE transition
Package: kdirstat Version: 2.4.4-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328010: qssl: uninstallable; needs rebuild for the Qt/KDE transition
Package: qssl Version: 2.0-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328009: tellico: uninstallable; needs rebuild for the Qt/KDE transition
Package: tellico Version: 0.13.3-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328008: prokyon3: uninstallable; needs rebuild for the Qt/KDE transition
Package: prokyon3 Version: 0.9.2-2 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328007: valknut: uninstallable; needs rebuild for the Qt/KDE transition
Package: valknut Version: 0.3.7-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328006: swscanner: uninstallable; needs rebuild for the Qt/KDE transition
Package: swscanner Version: 0.1.8-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328005: unixodbc: uninstallable; needs rebuild for the Qt/KDE transition
Package: unixodbc Version: 2.2.11-8 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328004: sim: uninstallable; needs rebuild for the Qt/KDE transition
Package: sim Version: 0.9.3-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328003: xexec: uninstallable; needs rebuild for the Qt/KDE transition
Package: xexec Version: 0.0.3-22 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328002: view3ds: uninstallable; needs rebuild for the Qt/KDE transition
Package: view3ds Version: 1.0.0-9 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328001: wvstreams: uninstallable; needs rebuild for the Qt/KDE transition
Package: wvstreams Version: 4.0.2-4 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#328000: wordtrans: uninstallable; needs rebuild for the Qt/KDE transition
Package: wordtrans Version: 1.1pre13-5 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327999: qgo: uninstallable; needs rebuild for the Qt/KDE transition
Package: qgo Version: 1.0.2-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327993: libqt-perl: uninstallable; needs rebuild for the Qt/KDE transition
Package: libqt-perl Version: 3.008-1.3 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327998: qsynaptics: uninstallable; needs rebuild for the Qt/KDE transition
Package: qsynaptics Version: 0.22.0-2 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327997: knoda: uninstallable; needs rebuild for the Qt/KDE transition
Package: knoda Version: 0.7.3-2 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327996: kiosktool: uninstallable; needs rebuild for the Qt/KDE transition
Package: kiosktool Version: 1.0-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327995: ktrack: uninstallable; needs rebuild for the Qt/KDE transition
Package: ktrack Version: 0.3.0-alpha1-6 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327994: ksynaptics: uninstallable; needs rebuild for the Qt/KDE transition
Package: ksynaptics Version: 0.2.0-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327992: kflog: uninstallable; needs rebuild for the Qt/KDE transition
Package: kflog Version: 2.1.1-3 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327991: kwirelessmonitor: uninstallable; needs rebuild for the Qt/KDE transition
Package: kwirelessmonitor Version: 0.5.91-1 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327990: qtstalker: uninstallable; needs rebuild for the Qt/KDE transition
Package: qtstalker Version: 0.26-5 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327989: madman: uninstallable; needs rebuild for the Qt/KDE transition
Package: madman Version: 0.93.0-3 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#327988: lyx: uninstallable; needs rebuild for the Qt/KDE transition
Package: lyx Version: 1.3.4-2 Severity: grave Tags: sid Hello, This is a grave bug filed against your package because it depends on libqt3c102-mt, which no longer exists, thus rendering yor package uninstallable in unstable. As part of the C++ ABI transition, this library has moved to the libqt3-mt package. Simply recompiling and uploading your package should be enough to fix this; as per this mail [1], you need not bump your Qt, kdelibs or aRts build-dependencies. Beware, though, that that may not be the case for all the involved librares. Also, make sure that you build the package in an up to date and clean sid environment, so that final dependencies are correct. Please do this as soon as possible in order to accelerate the Qt/KDE transition to testing. [1] http://lists.debian.org/debian-devel-announce/2005/09/msg0.html Perhaps you find that your package fails to compile with gcc4. If that's the case, there's probably a bug about it in the BTS, and it may include a patch. If not (or if you have doubts about the correctness of the patch), you may be able to find a fix in upstream's CVS, or in the Ubuntu distribution. If your package fails only in arm, m68k, and hppa, see instructions in the above mail. Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your cooperation, and happy hacking! P.S.: There may be an already reported bug against this package for this very same reason. I've checked for that, and will be merging the bugs soon. The reason for still filing this bug was to have the opportunity of including the small bits of information above. I apologize for the inconvenience. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
