Bug#1006445: openssh-server: Killed by seccomp after accepting connection (i386)
Package: openssh-server Version: 1:8.9p1-2.1 Severity: important Tags: patch Dear Maintainer, After accepting an ssh connection, the sshd process is killed and I see the following in dmesg: audit: type=1326 audit(1645794361.669:40): auid=0 uid=100 gid=65534 ses=1 subj==unconfined pid=8338 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=4003 syscall=414 compat=0 ip=0xb7ee3559 code=0x0 Sysycall 414 is ppoll_time64, so I'm guessing this is fallout from ongoing 2038 fixes. The attached patch fixes this by adding ppoll_time64 the seccomp sanbox filters, which seems reasonable as ppoll is already allowed. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 5.16.0-2-686-pae (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openssh-server depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.79 ii dpkg 1.21.1 ii init-system-helpers1.62 ii libaudit1 1:3.0.7-1 ii libc6 2.33-7 ii libcom-err21.46.5-2 ii libcrypt1 1:4.4.27-1.1 ii libgssapi-krb5-2 1.19.2-2 ii libkrb5-3 1.19.2-2 ii libpam-modules 1.4.0-11 ii libpam-runtime 1.4.0-11 ii libpam0g 1.4.0-11 ii libselinux13.3-1+b1 ii libssl1.1 1.1.1m-1 ii libsystemd0250.3-2 ii libwrap0 7.6.q-31 ii lsb-base 11.1.0 ii openssh-client 1:8.9p1-2.1 ii openssh-sftp-server1:8.9p1-2 ii procps 2:3.3.17-6 ii runit-helper 2.10.3 ii ucf3.0043 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages openssh-server recommends: ii libpam-systemd [logind] 250.3-2 pn ncurses-term ii xauth1:1.1-1 Versions of packages openssh-server suggests: ii molly-guard 0.7.2 pn monkeysphere pn ssh-askpass pn ufw -- debconf information: ssh/insecure_telnetd: ssh/vulnerable_host_keys: * ssh/use_old_init_script: true ssh/new_config: true ssh/insecure_rshd: * openssh-server/permit-root-login: true ssh/disable_cr_auth: false openssh-server/password-authentication: false ssh/encrypted_host_key_but_no_keygen: diff -ur clean/sandbox-seccomp-filter.c openssh-8.9p1/sandbox-seccomp-filter.c --- clean/sandbox-seccomp-filter.c 2022-02-23 11:31:11.0 + +++ openssh-8.9p1/sandbox-seccomp-filter.c 2022-02-25 13:16:17.319892443 + @@ -273,6 +273,9 @@ #ifdef __NR__newselect SC_ALLOW(__NR__newselect), #endif +#ifdef __NR_ppoll_time64 + SC_ALLOW(__NR_ppoll_time64), +#endif #ifdef __NR_ppoll SC_ALLOW(__NR_ppoll), #endif
Bug#976718: fastboot is completely broken
Package: fastboot Version: 1:10.0.0+r36-1~stage1.3 Severity: grave Justification: renders package unusable Dear Maintainer, $ fastboot devices fake placeholder until fastboot builds Closer inventigation shows that the fastboot binary has indeed been replaced by a small shell script with zero functionality -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-4-amd64 (SMP w/6 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled fastboot depends on no packages. Versions of packages fastboot recommends: ii android-sdk-platform-tools 27.0.0+12 fastboot suggests no packages. -- no debconf information
Bug#856487: libsbc1: compiling with gcc > 4.9 causes stack corruption
Package: libsbc1
Version: 1.3-1+b2
Followup-For: Bug #856487
Not a stack corruption.
This is miscompilation of sbc_analyze_4b_8s_armv6. gcc appears to look
into the asm function and decides that it does not clobber r3 (which the
normal ARM ABI says is call clobbered). The last out += out_stride ends
up incrementing the pointer by an arbitrary amount.
The attached patch works around the bug.
I'm not entirely sure whether this is a gcc bug or not, but at best it's
surprising behavior from gcc. I've attached a reduced testcase for the
toolchain
folks to argue over (compile with gcc -O2, tested with gcc 6.3.0-2 from
sid).
Paul
diff -ur clean/sbc/sbc_primitives_armv6.c sbc-1.3/sbc/sbc_primitives_armv6.c
--- clean/sbc/sbc_primitives_armv6.c2013-04-30 17:19:23.0 +0100
+++ sbc-1.3/sbc/sbc_primitives_armv6.c 2017-04-17 16:43:49.918809345 +0100
@@ -102,6 +102,7 @@
"pop{r8-r11}\n"
"stmia r1, {r4, r5, r6, r7}\n"
"pop{r1, r4-r7, pc}\n"
+:::"r0", "r2", "r3", "ip"
);
}
@@ -258,6 +259,7 @@
"pop{r8-r11}\n"
"stmia r1!, {r4, r5, r6, r7}\n"
"pop{r1, r4-r7, pc}\n"
+:::"r0", "r2", "r3", "ip"
);
}
/* Compile with -O2 on arm */
#include
#include
static void __attribute__((naked)) frob(int16_t *a, int32_t *b, const int16_t
*c)
{
/* The explicit clobber of r3 should not be necessary because that it
is implied by the function call?
gcc6 seems to look into the naked function and assume r3 is
preserved accross the call. */
__asm__ volatile ("mov r3, #0x8000\n\t"
"str r3, [r1]\n\t"
"bx lr"
#if 0
:::"r3"
#endif
);
}
int16_t c[4];
struct sbc_encoder_state;
void test(struct sbc_encoder_state *state,
int16_t *x, int32_t *out, int out_stride)
{
frob(x + 24, out, c);
out += out_stride;
frob(x + 16, out, c);
out += out_stride;
frob(x + 8, out, c);
out += out_stride;
frob(x + 0, out, c);
}
int main()
{
static int16_t a[32];
static int32_t b[32];
test(NULL, a, b, 8);
return 0;
}
Bug#855920: fail2ban: FTBFS: test_rewrite_file: AssertionError: False is not true
Package: fail2ban Followup-For: Bug #855920 Dear Maintainer, Test failures occur if the build environment does not have the tzdata package installed. The test harness hardcodes TZ="Europe/Zurich". Patch below fixes this by encoding the equyivalent explicit timezone rather than using the geographic lookup. Paul diff -ur clean/fail2ban/tests/utils.py fail2ban-0.9.6/fail2ban/tests/utils.py --- clean/fail2ban/tests/utils.py 2016-12-09 14:48:45.0 + +++ fail2ban-0.9.6/fail2ban/tests/utils.py 2017-04-16 13:41:19.933359352 +0100 @@ -95,7 +95,7 @@ # Set the time to a fixed, known value # Sun Aug 14 12:00:00 CEST 2005 # yoh: we need to adjust TZ to match the one used by Cyril so all the timestamps match - os.environ['TZ'] = 'Europe/Zurich' + os.environ['TZ'] = 'CET-01CEST-02,M3.5.0,M10.5.0' time.tzset() MyTime.setTime(1124013600)
Bug#797531: molly-guard: Fails to install if kexec-tools also installed
Package: molly-guard Version: 0.6.1 Severity: important Tags: patch Dear Maintainer, Installation fails with: trying to overwrite '/sbin/coldreboot', which is also in package kexec-tools 1:2.0.9-1 Looks we're missingthe preinst/postrm hooks to setup the diversion. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages molly-guard depends on: ii procps 2:3.3.10-2 molly-guard recommends no packages. molly-guard suggests no packages. -- no debconf information diff -ur molly-guard-0.6.1/debian/molly-guard.postrm clean/debian/molly-guard.postrm --- molly-guard-0.6.1/debian/molly-guard.postrm 2015-08-31 12:05:30.170992359 +0100 +++ clean/debian/molly-guard.postrm 2015-08-29 18:37:14.0 +0100 @@ -19,7 +19,7 @@ case "$1" in remove) -for cmd in halt poweroff reboot shutdown cldreboot ; do +for cmd in halt poweroff reboot shutdown ; do dpkg-divert --package molly-guard --rename --remove /sbin/$cmd done rmdir --ignore-fail-on-non-empty /lib/molly-guard diff -ur molly-guard-0.6.1/debian/molly-guard.preinst clean/debian/molly-guard.preinst --- molly-guard-0.6.1/debian/molly-guard.preinst 2015-08-31 12:05:44.623418607 +0100 +++ clean/debian/molly-guard.preinst 2015-08-29 18:37:14.0 +0100 @@ -15,7 +15,7 @@ case "$1" in install|upgrade) mkdir -p /lib/molly-guard -for cmd in halt poweroff reboot shutdown coldreboot ; do +for cmd in halt poweroff reboot shutdown ; do dpkg-divert --package molly-guard --divert /lib/molly-guard/$cmd --rename /sbin/$cmd done ;;
Bug#797531: molly-guard: Fails to install if kexec-tools also installed
Oops, wrong patch (earlier, broken version). Correct one attached.diff -ur molly-guard-0.6.1/debian/molly-guard.postrm clean/debian/molly-guard.postrm --- clean/debian/molly-guard.postrm 2015-08-29 18:37:14.0 +0100 +++ molly-guard-0.6.1/debian/molly-guard.postrm 2015-08-31 12:05:30.170992359 +0100 @@ -19,7 +19,7 @@ case "$1" in remove) -for cmd in halt poweroff reboot shutdown ; do +for cmd in halt poweroff reboot shutdown coldreboot ; do dpkg-divert --package molly-guard --rename --remove /sbin/$cmd done rmdir --ignore-fail-on-non-empty /lib/molly-guard diff -ur molly-guard-0.6.1/debian/molly-guard.preinst clean/debian/molly-guard.preinst +++ molly-guard-0.6.1/debian/molly-guard.preinst 2015-08-31 12:05:44.623418607 +0100 --- clean/debian/molly-guard.preinst 2015-08-29 18:37:14.0 +0100 @@ -15,7 +15,7 @@ case "$1" in install|upgrade) mkdir -p /lib/molly-guard -for cmd in halt poweroff reboot shutdown ; do +for cmd in halt poweroff reboot shutdown coldreboot ; do dpkg-divert --package molly-guard --divert /lib/molly-guard/$cmd --rename /sbin/$cmd done ;;
Bug#782703: dstat: crashes if TIOCGWINSZ and curses both unavailable
Package: dstat Version: 0.7.2-4 Severity: normal Tags: patch Dear Maintainer, I recently encountered a crash on a machine with a slightly wonky terminal config. If both termios.TIOCGWINSZ and curses.tigetnum fail in initterm(), then we die in gettermsize() with NameError: global name 'termsize' is not defined. There are already fallbacks to handle this case, we just need to make sure termsize is initialized to a suitable value when no terminal info is available. Patch below does this. Paul diff -u clean/dstat dstat-0.7.2/dstat --- clean/dstat 2010-06-11 06:08:01.0 + +++ dstat-0.7.2/dstat 2015-03-23 11:44:39.510401178 + @@ -1998,6 +1998,7 @@ ### Unbuffered sys.stdout #sys.stdout = os.fdopen(1, 'w', 0) +termsize = None, 0 try: global fcntl, struct, termios import fcntl, struct, termios -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dstat depends on: pn python:any none dstat recommends no packages. dstat suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702761: cinnamon: taskbar menus are very slow
I had the same issue, it was caused by the bump-mapped transparecy, which I guess my graphics hardwre (Intel Atom/i915) can't handle. Commenting out the background-bumpmap: line in /usr/share/cinnamon/theme/cinnamon.css worked around the problem. Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607642: More info for #607642
On 01/07/2011 01:26 PM, Paul Brook wrote: Further investigation shows that it's actually the use of GUID partition tables that cause confusion. grub-probe correctly identifies filesystem and LVM device, but fails to map partitions for the constituent devices. The lack of GUID partition table support is not directly relevant to this bug. I'm sure there are other partitioning schemes that grub does not understand. GPT is supported by GRUB. As long as it correctly has 0xee partition in its protective MBR. GPT support (or lack of) is a tangential issue. The issue is that grub should gracefully cope with cases where it is unable to access some partitions. The probe function (is_path_readable_by_grub) fails to check for appropriate partmap support, causing higher level code to make incorrect decisions. Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607642: More info for #607642
Further investigation shows that it's actually the use of GUID partition tables that cause confusion. grub-probe correctly identifies filesystem and LVM device, but fails to map partitions for the constituent devices. The lack of GUID partition table support is not directly relevant to this bug. I'm sure there are other partitioning schemes that grub does not understand. Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607642: grub-pc: gurb-mkconfig failure due to incorrect probe
Package: grub-pc
Version: 1.98+20100804-11
Severity: important
Tags: patch
grub-mkconfig fails on a system where / can not be accessed by grub.
The is_path_readable_by_grub function only checks that the filesystem is
known to grub. In my case (lvm+raid) grub understands the filesystem, but
not device partition mappings. grub-mkconfig incorreclty tries to use files
(specifically unicode.pf2) under /usr, causing 00_header to fail when it calls
prepare_grub_to_access_device for this file.
Patch below fixes this by making is_path_readable_by_grub also probe the
partmap. grub-mkconfig then correctly falls back to the files in
/boot/grub.
diff -ur clean/util/grub-mkconfig_lib.in grub2/util/grub-mkconfig_lib.in
--- clean/util/grub-mkconfig_lib.in
+++ grub2/util/grub-mkconfig_lib.in
@@ -61,6 +61,11 @@ is_path_readable_by_grub ()
return 1
fi
+ # abort if file is in a partition we don't know about
+ if ${grub_probe} -t partmap $path /dev/null 21 ; then : ; else
+return 1
+ fi
+
return 0
}
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/volumes-root64 / ext4 rw,noatime,barrier=1,data=ordered 0 0
/dev/mapper/volumes-scratch /scratch ext4 rw,noatime,barrier=1,data=ordered 0 0
/dev/mapper/volumes-home /home ext4 rw,noatime,barrier=1,data=ordered 0 0
/dev/md1 /boot ext3 rw,noatime,errors=continue,barrier=0,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-WDC_WD3200SD-01KNB0_WD-WMAMR1540877
(hd1) /dev/disk/by-id/ata-WDC_WD3200SD-01KNB0_WD-WMAMR1541006
(hd2) /dev/disk/by-id/ata-WDC_WD5000AAKS-00YGA0_WD-WCAS81161381
(hd3) /dev/disk/by-id/ata-WDC_WD5000AAKS-22YGA0_WD-WCAS82395254
*** END /boot/grub/device.map
-- System Information:
Debian Release: 6.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.36-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages grub-pc depends on:
ii debconf [debconf-2.0] 1.5.37 Debian configuration management sy
ii grub-common 1.98+20100804-11 GRand Unified Bootloader, version
ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib
ii libdevmapper1.02.1 2:1.02.48-4 The Linux Kernel Device Mapper use
ii ucf 3.0025+nmu1 Update Configuration File: preserv
grub-pc recommends no packages.
Versions of packages grub-pc suggests:
ii desktop-base 6.0.4 common files for the Debian Deskto
-- debconf information excluded
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588788: perl: ftbfs with gcc4.5
Package: perl
Version: 5.10.1-13
Severity: normal
Tags: patch
By default patchlevel.h includes git_version.h. The latter is generated by
configure.
However the debian/config.debian uses patchlevel.h before running configure.
This has always been fairly borken, but old GCC processed the rest of the file
anyway, and none noticed the compiler errors. Recent GCC consider this a fatal
error and produce no output.
Defining PERL_PATCHLEVEL_H_IMPLICIT avoids requiring git_version.h while still
providing the necessary symbols.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.33-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages perl depends on:
ii libbz2-1.0 1.0.5-4 high-quality block-sorting file co
ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib
ii libdb4.74.7.25-9 Berkeley v4.7 Database Libraries [
ii libgdbm31.8.3-9 GNU dbm database routines (runtime
ii perl-base 5.10.1-13minimal Perl system
ii perl-modules5.10.1-13Core Perl modules
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
Versions of packages perl recommends:
ii make 3.81-8 An utility for Directing compilati
ii netbase 4.42 Basic TCP/IP networking system
Versions of packages perl suggests:
pn libterm-readline-gnu-perl | l none (no description available)
ii perl-doc 5.10.1-13 Perl documentation
-- no debconf information
=== modified file 'debian/config.debian'
--- debian/config.debian2010-05-04 16:32:38 +
+++ debian/config.debian2010-07-12 09:46:37 +
@@ -2,7 +2,8 @@
eval $(echo '#include ./patchlevel.h
SETver=PERL_REVISION.PERL_VERSION;
-SETsubver= PERL_SUBVERSION' | gcc -E - | sed -n '/^SET/{s///;s/ //gp;}')
+SETsubver= PERL_SUBVERSION' | gcc -E -DPERL_PATCHLEVEL_H_IMPLICIT - \
+| sed -n '/^SET/{s///;s/ //gp;}')
fullver=$ver.$subver
nextver=$ver.$(($subver+1))
Bug#533642: dpkg-dev: dpkg-shlibdeps fails on symbols exported by libgcc_s
Now it seems that the irrlicht library depends on those symbols provided by libgcc_s.so.1 (and does not define them locally contrary to what was seen by Aurélien in libvorbis in #462318) and of course dpkg-shlibdeps complains because they can't be found in the symbols file. ... So should I revert the blacklist entirely? Or should I revert the blacklist partially? In that case, which symbols must be blacklisted? Under normal curcumstances, I'd expect every shared library and application to require __aeabi_* from libgcc. Under normal circumstances these will come from libgcc_s.so, but if you link with --static-libgcc then you'll get your own copy. These symbols are defined by the EABI and the runtime must supply in some form. The EABI is deliberately vague about exactly where/how, but on Linux it is normal for these for come from libgcc. However use of these functions is entirely optional, hence building them into your library instead of using libgcc_s.so is ok (though obviously has the same undesirable consequences as any sort of static library). I'm afraid I have no clue how dpkg-shlibdeps works, so can't really guess what the right answer to your blacklist question is. Paul -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523603: kformula: Broken dependency on kcontrol
Package: kformula Version: 1:1.6.3-7+b1 Severity: important kformula depends on kcontrol. kcontrol no longer exists in kde4, rendering the package uninstallable. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.28-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kformula depends on: ii kcontrol 4:3.5.10.dfsg.1-2 control center for KDE ii koffice-libs 1:1.6.3-7+b1 common libraries and binaries for ii libc6 2.9-6 GNU C Library: Shared libraries ii libgcc11:4.3.3-5 GCC support library ii libstdc++6 4.3.3-5 The GNU Standard C++ Library v3 Versions of packages kformula recommends: ii khelpcent 4:4.0.0.really.3.5.10.dfsg.1-2 help center for KDE kformula suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#465947: muscleframework: FTBFS on armel
Package: muscleframework
Version: 1.1.6-4
Severity: important
Tags: patch
Justification: fails to build from source
Build fails on armel because configure script does not recognize the
triplet arm-linux-gnueabi. Attached patch fixes this by relaxing the target
matching (accept linux-gnu* rather than exactly linux-gnu).
Paul
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: armel (armv5tel)
Kernel: Linux 2.6.24-1-iop32x
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
diff -ur clean/MCardPlugin/configure muscleframework-1.1.6/MCardPlugin/configure
--- clean/MCardPlugin/configure 2006-11-25 20:50:21.0 +
+++ muscleframework-1.1.6/MCardPlugin/configure 2008-02-15 02:52:54.0 +
@@ -2522,7 +2522,7 @@
case ${build_os} in
- linux-gnu) arch=linux ;;
+ linux-gnu*) arch=linux ;;
*bsd*) arch=bsd ;;
*darwin*) arch=darwin ;;
*solaris*) arch=solaris ;;
diff -ur clean/MCardPlugin/configure.in muscleframework-1.1.6/MCardPlugin/configure.in
--- clean/MCardPlugin/configure.in 2006-11-25 20:50:20.0 +
+++ muscleframework-1.1.6/MCardPlugin/configure.in 2008-02-15 02:52:27.0 +
@@ -15,7 +15,7 @@
dnl Select OS specific versions of source files.
case ${build_os} in
- linux-gnu) arch=linux ;;
+ linux-gnu*) arch=linux ;;
*bsd*) arch=bsd ;;
*darwin*) arch=darwin ;;
*solaris*) arch=solaris ;;
Bug#464797: tightvnc: FTBFS on Arm
Thanks a lot! Do the package work well when it has been built? Yes. Both client and server seem to work as expected. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#464797: tightvnc: FTBFS on Arm
Package: tightvnc Version: 1.2.9-21 Severity: important Tags: patch Justification: fails to build from source Package fails to build on ARM. Looks like confusion between Arm32Architecture and ArmArchitecture in the configure scripts. Patch below fixes the system detection file to generate the defines that the rest of the config is expecting. Paul diff -ur clean/Xvnc/config/cf/Imake.cf tightvnc-fixed/Xvnc/config/cf/Imake.cf --- clean/Xvnc/config/cf/Imake.cf +++ tightvnc-fixed/Xvnc/config/cf/Imake.cf @@ -711,7 +711,7 @@ # undef __alpha__ # endif /* __alpha__ */ # ifdef __arm__ -# define Arm32Architecture +# define ArmArchitecture # undef arm # undef __arm # undef __arm__ -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: arm (armv5tejl) Kernel: Linux 2.6.22.2 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#460133: hal: hlad-addon-input does not release device nodes.
Package: hal
Version: 0.5.10-5
Severity: important
Tags: patch
hald-addon-input does not release evdev device nodes when a device is
removed. Because hald still has the device open the kernel cannot free
the device node. After a number of plug/unplug cycles (typically 32)
runs out of device nodes, effectively preventing hotplug of USB HID.
This is a major issue on systems with USB keyboards/mice that are
unplugged on a regular basis, e.g. a laptop or USB hub that is powered
off ovenight.
When a physical device is removed the destroy_data callback is invoked.
This cears the GIOChannel hash table without releasing the channel
object. Because the FD is never released the kernel never removes the
device, and remove_device is never called. Even if remove_device were
called the hash entry has been cleared, so the channel would still not
be released. At best this leaks file descriptors, at worst if results
in the DoS described above.
The attached patch fixes this be releasing the channel object in
remove_device.
Paul
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages hal depends on:
ii adduser 3.105 add and remove users and groups
ii dbus 1.1.2-1 simple interprocess messaging syst
ii hal-info 20071212-2 Hardware Abstraction Layer - fdi f
ii libc62.7-5 GNU C Library: Shared libraries
ii libdbus-1-3 1.1.2-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.74-1 simple interprocess messaging syst
ii libexpat11.95.8-4XML parsing C library - runtime li
ii libgcc1 1:4.2.2-4 GCC support library
ii libglib2.0-0 2.14.4-2The GLib library of C routines
ii libhal-storage1 0.5.10-5Hardware Abstraction Layer - share
ii libhal1 0.5.10-5Hardware Abstraction Layer - share
ii libsmbios1 0.13.10-1 Provide access to (SM)BIOS informa
ii libstdc++6 4.2.2-4 The GNU Standard C++ Library v3
ii libusb-0.1-4 2:0.1.12-8 userspace USB programming library
ii libvolume-id00.114-2 libvolume_id shared library
ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip
ii mount2.13-13 Tools for mounting and manipulatin
ii pciutils 1:2.2.4-1.1 Linux PCI Utilities
ii pm-utils 0.99.2-3utilities and scripts for power ma
ii udev 0.114-2 /dev/ and hotplug management daemo
ii usbutils 0.73-5 Linux USB utilities
Versions of packages hal recommends:
ii eject 2.1.5-6ejects CDs and operates CD-Changer
ii libsmbios-bin 0.13.10-1 Provide access to (SM)BIOS informa
-- no debconf information
diff -ur clean/hald/linux/addons/addon-input.c hal-0.5.10/hald/linux/addons/addon-input.c
--- clean/hald/linux/addons/addon-input.c
+++ hal-0.5.10/hald/linux/addons/addon-input.c
@@ -300,8 +300,14 @@
static void
destroy_data (InputData *data)
{
+ GIOChannel *channel;
+
HAL_DEBUG ((Removing GIOChannel for'%s', data-udi));
+ channel = g_hash_table_lookup(inputs, data-udi);
+ if (channel)
+ g_io_channel_unref (channel);
+
/* Null out the GIOChannel in the hash table, but
* leave the key in for DeviceRemoved
*/
Bug#457946: aptitude: Incorrect plural in commandline status
On Thursday 27 December 2007, Daniel Burrows wrote: Hm, I wonder if this works in all languages. Christian, do you have any idea? Can we get away with ngettext() on the first item in a comma-separated list? My understanding is that fragf is printf-like, and the %F allows languages to format things correctly. I could be wrong though. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457946: aptitude: Incorrect plural in commandline status
Package: aptitude
Version: 0.4.10-1
Severity: minor
Tags: patch
After doing an upgrade the following message was displayed:
There are now 1 update [-63].
Note incorrect use of the plural are. Attached patch fixes this.
I have double checked the following cases:
There is now 1 update [-63].
There are now 3 updates [-2].
There are now 0 broken [-1], 1 update [-1].
Paul
-- Package-specific info:
Terminal: xterm
$DISPLAY is set.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages aptitude depends on:
ii apt [libapt-pkg-libc6.6-6 0.7.9 Advanced front-end for dpkg
ii libc6 2.7-5 GNU C Library: Shared libraries
ii libcwidget1 0.5.6.1-2 high-level terminal interface libr
ii libgcc1 1:4.2.2-4 GCC support library
ii libncursesw5 5.6+20071215-1 Shared libraries for terminal hand
ii libsigc++-2.0-0c2a2.0.17-2 type-safe Signal Framework for C++
ii libstdc++64.2.2-4The GNU Standard C++ Library v3
Versions of packages aptitude recommends:
pn aptitude-doc-en | aptitude-do none (no description available)
pn libparse-debianchangelog-perl none (no description available)
-- no debconf information
diff -ur clean/src/cmdline/cmdline_util.cc
aptitude-0.4.10/src/cmdline/cmdline_util.cc
--- clean/src/cmdline/cmdline_util.cc 2007-12-16 19:43:06.0 +
+++ aptitude-0.4.10/src/cmdline/cmdline_util.cc 2007-12-27 12:50:04.0
+
@@ -258,6 +258,7 @@
{
using cw::fragf;
using cw::util::ssprintf;
+int nthings = 0;
std::vectorcw::fragment * fragments;
@@ -273,6 +274,7 @@
final.get_num_broken() - initial.get_num_broken());
fragments.push_back(cw::text_fragment(change));
+ nthings += final.get_num_broken();
}
if(show_all ||
@@ -287,6 +289,7 @@
final.get_num_upgradable() - initial.get_num_upgradable());
fragments.push_back(cw::text_fragment(change));
+ nthings += final.get_num_upgradable();
}
if(show_all ||
@@ -301,11 +304,17 @@
final.get_num_new() - initial.get_num_new());
fragments.push_back(cw::text_fragment(change));
+ nthings += final.get_num_new();
}
if(fragments.size() 0)
{
- cw::fragment *f = fragf(_(There are now %F.),
+ if (fragments.size() 1)
+ nthings += fragments.size();
+
+ cw::fragment *f = fragf(ngettext(There is now %F.,
+There are now %F.,
+nthings),
cw::join_fragments(fragments, L, ));
update_screen_width();
Bug#457487: kdm: Remote XDMCP login broken (segfault)
Package: kdm
Version: 4:3.5.8.dfsg.1-2
Severity: important
Tags: patch
When logging in on a remote xterminal via XDMCP kdm segfaults, causing the
session to die and the greeter to be redisplayed.
A backtrace of the crash (below) shows that we crash trying to create a
bogus DBUS entry. Further investigation indicates the d-remoteHost is
NULL. It looks like there are two different types of nonlocal session:
Localy manged X servers that connect to a remote XDMCP server, and remote X
terminals logging into this host via XDMCP. remoteHost is only set in
the former case.
The patch below fixes the crash by only adding the dbus attribute if
remoteHost is known.
Paul
diff -ur clean/kdm/backend/consolekit.c
kdebase-3.5.8.dfsg.1/kdm/backend/consolekit.c
--- clean/kdm/backend/consolekit.c 2007-12-22 18:11:56.0 +
+++ kdebase-3.5.8.dfsg.1/kdm/backend/consolekit.c 2007-12-22
17:58:37.0 +
@@ -461,7 +461,7 @@
add_param_string (iter_struct, x11-display, d-name);
add_param_boolean (iter_struct, is-local, ((d-displayType
d_location) == dLocal));
#ifdef XDMCP
- if ((d-displayType d_location) != dLocal) {
+ if ((d-displayType d_location) != dLocal d-remoteHost) {
add_param_string (iter_struct, remote-host-name,
d-remoteHost);
}
#endif
#0 0x2b44640e4fc0 in strlen () from /lib/libc.so.6
...
#4 0x0040a772 in add_param_string (iter_struct=0x7fff47acec60,
key=0x41be0a remote-host-name, value=0x0)
at kdm/backend/consolekit.c:131
#5 0x0040aac7 in open_ck_session (pwent=value optimized out,
d=0x62aea0)
at kdm/backend/consolekit.c:465
#6 0x00416a1d in ManageSession (d=0x62aea0)
at kdm/backend/session.c:634
#7 0x0040d81d in StartDisplayP2 (d=0x62aea0)
at kdm/backend/dm.c:1395
#8 0x00419cda in manage (from=0x7fff47acef90, fromlen=28,
length=value optimized out, fd=9)
at kdm/backend/xdmcp.c:948
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages kdm depends on:
ii debconf [debconf-2.0] 1.5.17 Debian configuration management sy
ii kdebase-bin 4:3.5.8.dfsg.1-2 core binaries for the KDE base mod
ii kdebase-data4:3.5.8.dfsg.1-2 shared data files for the KDE base
ii kdelibs4c2a 4:3.5.8.dfsg.1-4 core libraries and binaries for al
ii libc6 2.7-5GNU C Library: Shared libraries
ii libdbus-1-3 1.1.2-1 simple interprocess messaging syst
ii libgcc1 1:4.2.2-4GCC support library
ii libpam-runtime 0.99.7.1-5 Runtime support for the PAM librar
ii libpam0g0.99.7.1-5 Pluggable Authentication Modules l
ii libqt3-mt 3:3.3.7-9Qt GUI Library (Threaded runtime v
ii libstdc++6 4.2.2-4 The GNU Standard C++ Library v3
ii libx11-62:1.0.3-7X11 client-side library
ii libxau6 1:1.0.3-2X11 authorisation library
ii libxdmcp6 1:1.0.2-2X11 Display Manager Control Protoc
ii libxtst62:1.0.3-1X11 Testing -- Resource extension
ii xbase-clients 1:7.3+8 miscellaneous X clients - metapack
Versions of packages kdm recommends:
ii logrotate 3.7.1-3Log rotation utility
ii xserver-xorg 1:7.3+8the X.Org X server
-- debconf information:
kdm/stop_running_server_with_children: false
* shared/default-x-display-manager: kdm
kdm/daemon_name: /usr/bin/kdm
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383853: Subject: rred is some extraction mechanism?
Incremental apt updates use ed style diffs. i.e. the pdiff is a script suitable for feeding into the ed line editor. Conventionally there is also a restricted versions of ed called red which implements only a safe subset of ed commands. Apt includes a partial (Reduced/even more Restricted?) implementation of this, hence rred. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#447407: nfs-kernel-server: Segfault in exportfs
Package: nfs-kernel-server Version: 1:1.1.1-1 Severity: important Running exportfs -r segfaults if any warnings or errors are emitted. For example, if /etc/exports contains: / 127.0.0.1 Normally this would display a warning about missing sync arguments. Now it segfaults. Similar segfaults occur with missing subtree_check options and unrecognised options. Backtrace below. Paul #0 0x2b3ad8b89a90 in strlen () from /lib/libc.so.6 #1 0x2b3ad8b5819a in vfprintf () from /lib/libc.so.6 #2 0x2b3ad8b59083 in ?? () from /lib/libc.so.6 #3 0x2b3ad8b549be in vfprintf () from /lib/libc.so.6 #4 0x00406fb6 in xlog_backend (kind=1024, fmt=0x4095e8 No options for %s %s: suggest %s(sync) to avoid warning, args=0x7fffd23bb4e0) at xlog.c:175 #5 0x00407216 in xlog (kind=673720360, fmt=0x4095f7 %s %s: suggest %s(sync) to avoid warning) at xlog.c:189 #6 0x00406586 in getexportent (fromkernel=value optimized out, fromexports=1) at exports.c:177 #7 0x00403cdc in export_read (fname=value optimized out) at export.c:37 #8 0x00402471 in main (argc=2, argv=0x7fffd23bc988) at exportfs.c:115 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages nfs-kernel-server depends on: ii libblkid1 1.40.2-1 block device id library ii libc6 2.6.1-6GNU C Library: Shared libraries ii libcomerr21.40.2-1 common error description library ii libgssglue1 0.1-1 mechanism-switch gssapi library ii libkrb53 1.6.dfsg.3~beta1-2 MIT Kerberos runtime libraries ii libnfsidmap2 0.20-0 An nfs idmapping library ii librpcsecgss3 0.16-1 allows secure rpc communication us ii libwrap0 7.6.dbs-14 Wietse Venema's TCP wrappers libra ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip ii nfs-common1:1.1.1-1 NFS support files common to client ii ucf 3.003 Update Configuration File: preserv nfs-kernel-server recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444187: man-db: MANPATH containing + do not work
Package: man-db
Version: 2.4.4-4
Severity: normal
Manpaths containing a plus character ('+') are broken. They are not
searched when looking for manpages.
To reproduce:
$ mkdir man++
$ cd man++
$ mkdir man1
$ cp /usr/share/man/man1/man.1.gz man1
$ man -M `pwd` man
No manual entry for man
See 'man 7 undocumented' for help when manual pages are not available.
Relevant parts of -d output are:
adding /home/paul/man++ to manpathlist
*manpath search path* = /home/paul/man++
--priv_drop_count = 0
++priv_drop_count = 1
searching in /home/paul/man++, section 1
trying section 1 with globbing
Layout is GNU (1)
update_directory_cache /home/paul/man\+\+/man1: miss
can't open directory /home/paul/man\+\+/man1: No such file or directory
directory cache update failed
update_directory_cache /home/paul/man\+\+/cat1: miss
can't open directory /home/paul/man\+\+/cat1: No such file or directory
directory cache update failed
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages man-db depends on:
ii bsdmainutils 6.1.7 collection of more utilities from
ii debconf [debconf-2.0]1.5.14 Debian configuration management sy
ii dpkg 1.14.6 package maintenance system for Deb
ii groff-base 1.18.1.1-13 GNU troff text-formatting system (
ii libc62.6.1-5 GNU C Library: Shared libraries
ii libgdbm3 1.8.3-3 GNU dbm database routines (runtime
man-db recommends no packages.
-- debconf information excluded
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440838: manpages-dev: longjmp(3) does not mention that it may clobber local variables
Package: manpages-dev Version: 2.62-1 Severity: normal Tags: patch The longjmp(3) function may cause unexpected things to happen to local varables modified after the call to setjmp(). I've encountered this issue several times, so it seems worthy of a mention in the manpage. Attached patch adds this, using wording similar to the POSIX spec. Paul -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.20-1-xen-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages manpages-dev depends on: ii manpages 2.62-1 Manual pages about using a GNU/Lin manpages-dev recommends no packages. -- no debconf information diff -ur clean/man3/longjmp.3 manpages-2.62/man3/longjmp.3 --- clean/man3/longjmp.32007-05-18 09:43:42.0 +0100 +++ manpages-2.62/man3/longjmp.32007-09-04 18:29:23.0 +0100 @@ -85,6 +85,21 @@ If you want to save and restore signal masks, use .BR siglongjmp (). .P +The values of objects of automatic storage durations are unspecified after +the call to +.BR longjmp () +if they meet all the following criteria: +.IP \(bu +They are local to the function containing the corresponding +.BR setjmp () +invocation. +.IP \(bu +They do not have volatile-qualified type. +.IP \(bu +They are changed between the setjmp() invocation and +.BR longjmp () +call. +.P .BR longjmp () and .BR siglongjmp ()
Bug#398381: apt: Is extremely slow because calls gettimeofday too much
Package: apt Version: 0.6.46.3 Severity: important Tags: patch The Building dependency tree... takes an extremely long time on may arm machine. Firther investigation shows this is spending most of its time in gettimeofday(), which is quite a slow function on this machine. apt calls OpProgress::CheckChange very frequently during this process. Estimates from a faster machine indicate it is called many thousands of times. Consider the case where we have just completed the first 1% progress. CheckChange is called, and the value to be displayed is different, so we call gettimeofday to figure out how log ago that was. It wasn't very long ( 0.7 sec), so we return false. Note that LastPercent is not modified. After the next extremely small piece of work we the same is still true. We continue making extremely slow progress, spending most of our time in gettimeofday. After 0.7 seconds has passed we return true and update LastPercent. Annother 0.9%ish occurs quickly because CheckChange returns immediately, until we get to 3% complete, at which point we start calling gettimeofday again. Thus the whole process takes well over a minute instead of a few seconds. On a other machines the same occurs, but gettimeofday is sufficiently fast that calling it 25 thousand times isn't so noticable. The patch below modifies CheckChange to only try and update update when the progress crosses a percentage boundary, rather than when 1% progress since the last update. Only updating when crossing a boundry means that under extreme circumstances the displayed value may lag behind the actual state by one update. Under normal curcumstances (slow or steady progress) the displayed value will be just as accurate. It's only a progress bar :-) On my amd64 machine the patch reduces the time taken to run apt-get install apt from 0.33 sec to 0.27 sec. On my slower arm machine it goes from 55 sec to 28 sec. Paul diff -ur apt/apt-pkg/contrib/progress.cc apt/apt-pkg/contrib/progress.cc --- apt-clean/apt-pkg/contrib/progress.cc 2006-03-02 14:27:13 +++ apt-0.6.46.3/apt-pkg/contrib/progress.cc2006-11-13 02:20:39 @@ -116,6 +116,8 @@ if ((int)LastPercent == (int)Percent) return false; + LastPercent = Percent; + if (Interval == 0) return false; @@ -126,6 +128,5 @@ if (Diff Interval) return false; LastTime = Now; - LastPercent = Percent; return true; } -- Package-specific info: -- (no /etc/apt/preferences present) -- -- (/etc/apt/sources.list present, but not submitted) -- -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-xen-amd64-k8 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages apt depends on: ii debian-archive-keyring 2006.01.18 GnuPG archive keys of the Debian a ii libc62.3.6.ds1-7 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-19 GCC support library ii libstdc++6 4.1.1-19The GNU Standard C++ Library v3 apt recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397048: gtk-gnutella: FTBFS on ARM
Package: gtk-gnutella
Version: 0.96.1svn12109-1
Severity: serious
Tags: patch
Justification: no longer builds from source
Build fails on ARM with STATIC_ASSERT failures. The ARM ABI padds
structudes to 4-byte boundaries by default. The attached patch adds
__attribute__((packed)) to inhibit this on structures that need to be
a funny size.
Paul
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: arm (armv5tejl)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-rc7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
diff -ur gtk-gnutella-clean/src/core/gnutella.h gtk-gnutella-0.96.1svn12109/src/core/gnutella.h
--- gtk-gnutella-clean/src/core/gnutella.h 2006-10-16 00:01:09.0 +0100
+++ gtk-gnutella-0.96.1svn12109/src/core/gnutella.h 2006-11-04 15:07:19.0 +
@@ -48,25 +48,25 @@
struct gnutella_msg_init {
struct gnutella_header header;
/** GGEP data may follow */
-};
+} __attribute__((packed));
struct gnutella_init_response {
guchar host_port[2];
guchar host_ip[4];
guchar files_count[4];
guchar kbytes_count[4];
-};
+} __attribute__((packed));
struct gnutella_msg_init_response {
struct gnutella_header header;
struct gnutella_init_response response;
/** GGEP data may follow */
-};
+} __attribute__((packed));
struct gnutella_search {
guchar speed[2];
/** query string follows */
-};
+} __attribute__((packed));
struct gnutella_search_results {
guchar num_recs;
@@ -76,41 +76,41 @@
/* record data follows */
/* Last 16 bytes = client_id */
-};
+} __attribute__((packed));
struct gnutella_msg_search {
struct gnutella_header header;
struct gnutella_search search;
-};
+} __attribute__((packed));
struct gnutella_push_request {
guchar guid[16];
guchar file_id[4];
guchar host_ip[4];
guchar host_port[2];
-};
+} __attribute__((packed));
struct gnutella_msg_push_request {
struct gnutella_header header;
struct gnutella_push_request request;
/** GGEP data may follow */
-};
+} __attribute__((packed));
struct gnutella_bye {
guchar code[2];
/** message string follows */
-};
+} __attribute__((packed));
struct gnutella_qrp_reset {
guchar variant; /** 0x00 */
guchar table_length[4]; /** little endian */
guchar infinity;
-};
+} __attribute__((packed));
struct gnutella_msg_qrp_reset {
struct gnutella_header header;
struct gnutella_qrp_reset data;
-};
+} __attribute__((packed));
struct gnutella_qrp_patch {
guchar variant; /** 0x01 */
@@ -118,29 +118,29 @@
guchar seq_size;
guchar compressor;
guchar entry_bits;
-};
+} __attribute__((packed));
struct gnutella_msg_qrp_patch {
struct gnutella_header header;
struct gnutella_qrp_patch data;
-};
+} __attribute__((packed));
struct gnutella_vendor {
guchar vendor[4]; /** For example, GTKG */
guchar selector_id[2]; /** Message selector ID, little endian */
guchar version[2]; /** Message version number, little endian */
/* payload follows */
-};
+} __attribute__((packed));
struct gnutella_msg_vendor {
struct gnutella_header header;
struct gnutella_vendor data;
-};
+} __attribute__((packed));
struct gnutella_msg_hsep_data {
struct gnutella_header header;
guchar triple[3 * sizeof(guint64)];
-};
+} __attribute__((packed));
#endif /* _core_gnutella_h_ */
diff -ur gtk-gnutella-clean/src/core/qhit.c gtk-gnutella-0.96.1svn12109/src/core/qhit.c
--- gtk-gnutella-clean/src/core/qhit.c 2006-10-16 00:01:09.0 +0100
+++ gtk-gnutella-0.96.1svn12109/src/core/qhit.c 2006-11-04 16:16:38.0 +
@@ -677,7 +677,7 @@
struct {
gchar ipv4[4];
gchar port[2];
-} alt;
+} __attribute__((packed)) alt;
STATIC_ASSERT(sizeof alt == 6);
poke_be32(alt.ipv4, host_addr_ipv4(hvec[i].addr));
diff -ur gtk-gnutella-clean/src/if/core/gnutella.h gtk-gnutella-0.96.1svn12109/src/if/core/gnutella.h
--- gtk-gnutella-clean/src/if/core/gnutella.h 2006-10-16 00:01:09.0 +0100
+++ gtk-gnutella-0.96.1svn12109/src/if/core/gnutella.h 2006-11-04 15:03:09.0 +
@@ -62,7 +62,7 @@
guchar ttl;
guchar hops;
guchar size[4];
-};
+} __attribute__((packed));
#define GTA_HEADER_SIZE sizeof(struct gnutella_header)
Bug#389292: gnome-presence-applet: Also fails on i386 and arm
Package: gnome-presence-applet Version: 0.3.1-1+b1 Followup-For: Bug #389292 Package also FTBFS on arm and i386. The problem seems to be GalagoList. Google suggests this should be defined in galago-list.h. However this header does not exist in the libgalago-dev package. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-xen-amd64-k8 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397080: linuxlogo: FTBFS on ARM
Package: linuxlogo Version: 4.14-4 Severity: serious Tags: patch Justification: no longer builds from source Build fails on arm with: make[3]: Entering directory `/build/buildd/linuxlogo-4.14/libsysinfo-0.1.0/Linux' make[3]: *** No rule to make target `armv4l', needed by `cpuinfo.o'. Stop. Where armv4l varies depending on the exact machine. Patch below fixes the makefile to recognice all arm variants from uname -m. --- libsysinfo-0.1.0/Linux/Makefile.clean 2006-11-05 00:13:03 +++ libsysinfo-0.1.0/Linux/Makefile 2006-11-05 00:23:23 @@ -20,6 +20,9 @@ ifeq ($(ARCH),parisc64) ARCH := parisc endif +ifeq ($(findstring arm,$(ARCH)),arm) + ARCH := arm +endif -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: arm (armv5tejl) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-rc7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387804: Bug #387804
This problem seems to have resolved itself. I don't know which change fixed it, but it works ok now. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394703: gcc-4.1: #pragma pack broken on ARM
Package: gcc-4.1 Version: 4.1.1-16 Severity: important Tags: patch #pragma pack(1) doesn't work properly on ARM. eg. #pragma pack(1) struct (char c;} S; sizeof(S) is 4, not 1. This breaks schism (and possibly other packages). http://buildd.debian.org/~jeroen/status/package.php?p=schisma=arm Patch to fix this is available at http://gcc.gnu.org/ml/gcc-patches/2006-10/msg01115.html Paul -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: arm (armv5tejl) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-rc3 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages gcc-4.1 depends on: ii binutils 2.16.1cvs20060413-1 The GNU assembler, linker and bina ii cpp-4.1 4.1.1-16The GNU C preprocessor ii gcc-4.1-base 4.1.1-16The GNU Compiler Collection (base ii libc62.3.6-13GNU C Library: Shared libraries ii libgcc1 1:4.1.1-16 GCC support library ii libssp0 4.1.1-16GCC stack smashing protection libr Versions of packages gcc-4.1 recommends: ii libc6-dev 2.3.6-13 GNU C Library: Development Librari ii libmudflap0-dev 4.1.1-16 GCC mudflap support libraries (dev -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394728: paintlib: FTBFS on ARM
Package: paintlib Version: 2.6.2-7 Severity: important Tags: patch Justification: fails to build from source Build on ARM fails with: pliff85dec.cpp: In member function 'virtual void PLIFF85Decoder::Open(PLDataSource*)': pliff85dec.cpp:182: error: size of array is negative The culprit is struct ColorRegister which contains 3 single byte members. The ARM ABI normally pads this to 4. Patch below marks it as a packed structure to prevent this happening. Paul diff -urp paintlib-2.6.2/common/pliff85.h paintlib-new/common/pliff85.h --- paintlib-2.6.2/common/pliff85.h 2004-04-29 19:01:52.0 +0100 +++ paintlib-new/common/pliff85.h 2006-10-22 17:09:19.0 +0100 @@ -143,7 +143,7 @@ namespace PLIFF85 UBYTE red; // red intensity 0..255. UBYTE green;// green intensity 0..255. UBYTE blue; // blue intensity 0..255. - }; + } __attribute__((packed)); // typedef ColorRegister ColorMap[n]; /* size = 3n bytes */ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: arm (armv5tejl) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-rc3 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394741: klic: FTBFS on ARM
Package: klic Version: 3.003-gm1-4 Severity: serious Tags: patch Justification: no longer builds from source On ARM the buildd is failing because it times out while running the configure script. The patch below increases the timeout by a healthy margin to avoid this. Paul --- klic-clean/debian/configure.expect 2006-10-22 20:11:34.0 +0100 +++ klic-3.003-gm1/debian/configure.expect 2006-10-22 20:07:40.0 +0100 @@ -1,4 +1,4 @@ #!/usr/bin/expect -- -set timeout 10 +set timeout 60 spawn ./Configure -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: arm (armv5tejl) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-rc3 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#393310: Not a bug in paintlib.
This assumes that WORD is 2 bytes. This is not true on arm - it is 4 bytes. WORD needs to be defined to be 2 bytes, or uint_16 used instead of WORD throughout. Wrong. WORD is a typedef for uint16_t, which is 2 bytes. This is a gcc bug, pragma pack(1) doesn't. See #394703 Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394764: pnet: FTBFS on ARM
Package: pnet Version: 0.7.4-1 Severity: serious Tags: patch Justification: no longer builds from source Build fails on ARM with Error: Rn must not overlap other operands -- `swp r3,r4,[r3]' The error is correct. This is coming from a broken inline assembly statement. Patch below fixes it. Paul --- pnet-0.7.4/libgc/include/private/gc_locks.h.old 2006-10-22 21:24:06 +0100 +++ pnet-0.7.4/libgc/include/private/gc_locks.h 2006-10-22 21:25:57 +0100 @@ -244,7 +244,7 @@ * this code will likely need to be updated. */ /* See linuxthreads/sysdeps/arm/pt-machine.h in glibc-2.1 */ __asm__ __volatile__(swp %0, %1, [%2] -: =r(oldval) +: =r(oldval) : r(1), r(addr) : memory); return oldval; -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: arm (armv5tejl) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-rc3 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394778: mrxvt: FTBFS on ARM
Package: mrxvt Version: 0.5.2-1 Severity: serious Tags: patch Justification: no longer builds from source Unlike many other targets, ARM does not allow $ symbols in identifiers. The only use of these appears to be for some third parts syayic code analysis system. The patch below disables it on arm, allowing the package to build. Paul --- mrxvt-clean/src/rxvt.h 2006-10-01 22:50:38.0 +0100 +++ mrxvt-0.5.2/src/rxvt.h 2006-10-23 00:04:38.0 +0100 @@ -488,7 +488,7 @@ * turn is unsafe without checking. Untainted defines the type of data that is * safe. */ -#ifdef __GNUC__ +#if defined(__GNUC__) !defined(__arm__) # define $tainted # define $untainted # define TAINTED$tainted -- System Information: Debian Release: testing/unstable Architecture: arm (armv5tejl) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-rc3 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388787: /etc/init.d/sysklogd reload is broken
Package: sysklogd Version: 1.4.1-19 Severity: important Tags: patch /etc/init.d/sysklogd reload gives the following error: start-stop-daemon: unrecognized option `--quiet--signal' Try `start-stop-daemon --help' for more information. This command is used by (and fails from) the daily sysklogd cron job. Looks like a typo in the initscript. Patch below. Paul --- debian/rc.old 2006-09-22 15:16:55.0 +0100 +++ debian/rc 2006-09-22 15:17:02.0 +0100 @@ -87,7 +87,7 @@ ;; reload|force-reload) log_begin_msg Reloading system log daemon... -start-stop-daemon --stop --quiet--signal 1 --pidfile $pidfile --name syslogd +start-stop-daemon --stop --quiet --signal 1 --pidfile $pidfile --name syslogd log_end_msg $? ;; restart) -- 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.16-2-xen-amd64-k8 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages sysklogd depends on: ii klogd [linux-kernel-log-daem 1.4.1-19Kernel Logging Daemon ii libc62.3.6.ds1-4 GNU C Library: Shared libraries sysklogd recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387804: xserver-xorg-video-nv: Extermely slow xv output
Package: xserver-xorg-video-nv Version: 1:1.0.1.5-2 Severity: normal XV output is extremely slow when using the nv driver. When playing a video with xine or vlc using xv output the Xorg process uses a large amount of CPU. With videos larger than about 640x480 it hits 100% CPU (2GHz amd64) and output becomes choppy. CPU use seems to be proprtional to the size of the source image, not the size of the displayed overlay. Other graphical operations also seem equally slow, but the painfully slow xv is the one that effects me most. The xine xshm ouptut driver is even slower. Same behavior observed with and without Xen. Also same problems with a 32-bit userspace + 64-bit kernel. Running 32-bit x86 kernel+userspace also works ok, 64-bit kernel seems to be the common factor in the slowness. Selected excepts from xorg.conf: Section Module Loadbitmap Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadtype1 Loadv4l Loadvbe EndSection Section Screen Identifier Default Screen Device Nvidia (nv) Monitor Generic Monitor DefaultDepth24 SubSection Display Depth 24 Modes 1600x1200 1280x1024 1024x768 800x600 640x480 EndSubSection EndSection Section Device Identifier Nvidia (nv) Driver nv EndSection -- no debconf information -- 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.16-2-xen-amd64-k8 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages xserver-xorg-video-nv depends on: ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii xserver-xorg-core2:1.0.2-10 X.Org X server -- core server xserver-xorg-video-nv recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382590: debian-installer: sparc testing images missing 32-bit isofs
Package: debian-installer Severity: important The sparc boot image on the etch beta-3 businesscard and netinst CDs does not contain the isofs module for 32-bit kernels. This makes the cds effectively useless on 32-bit sparc machines as teh installer can't mount the cd. The SCSI drivers load fine, just no iso9660 filesystem driver. The latest daily builds also have the same problem. I haven't tested the full images, it's possible they suffer from the same problem. -- System Information: sun4m (qemu) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#381632: vde: Fails to install
Package: vde Version: 1.5.11-1 Severity: grave Justification: renders package unusable Installation fails with: Setting up vde (1.5.11-1) ... useradd: invalid numeric argument 'vde-net' adduser: `/usr/sbin/useradd -d /home/vde-net -g vde-net -s /bin/false -u 109 vde-net' returned error code 3. Exiting. dpkg: error processing vde (--configure): subprocess post-installation script returned error exit status 1 grep /proc/group vde gives: vde-net:x:122: -- 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.16-2-xen-amd64-k8 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages vde depends on: ii adduser 3.96 Add and remove users and groups ii libc6 2.3.6-18 GNU C Library: Shared libraries vde recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#381299: yaird: fails in Xen DomU
Package: yaird
Version: 0.0.12-15
Severity: normal
When run inside a Xen DomU yaird fails with:
yaird error: unrecognised device: /sys/devices/xen
yaird error: unrecognised device: /sys/devices/xen/vbd-768
The patch below fixes this by ignoring xen devices. Debian xen kernels
build xen devices into the kernel, so no additional modules are needed.
Paul
--- Hardware.pm.old 2006-08-03 15:22:00.0 +0100
+++ Hardware.pm 2006-08-03 15:22:33.0 +0100
@@ -216,6 +216,11 @@
elsif ($abspath =~ m!/floppy.\d+$!) {
$modules = [ floppy ];
}
+ elsif ($abspath =~ m!/xen!) {
+ # While this can be build as a module it's
+ # almost alway built into the kernel
+ # $modules = [ xenblk ];
+ }
else {
# NOTE: We may want to avoid duplicate messages
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-xen-amd64-k8
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages yaird depends on:
ii cpio 2.6-16 GNU cpio -- a program to manage ar
ii dash 0.5.3-3 The Debian Almquist Shell
ii libc62.3.6-16GNU C Library: Shared libraries
ii libhtml-template-perl2.8-1 HTML::Template : A module for usin
ii libparse-recdescent-perl 1.94.free-3 Generates recursive-descent parser
ii perl 5.8.8-6 Larry Wall's Practical Extraction
yaird recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#379352: mdadm: checkarray --all gives error on mixed RAID system.
Package: mdadm Version: 2.5.2-7 Severity: normal Tags: patch checkarray --all gives the following error on a system with both RAID1 and RAID0 arrays: checkarray: E: /sys/block/md4/md/sync_action not writeable. Patch below fixes this by making --all only select devices that have md/sync_action. Paul --- checkarray 2006-07-23 01:20:44.0 +0100 +++ checkarray.old 2006-07-23 01:17:37.0 +0100 @@ -96,7 +96,7 @@ exit 3 fi -[ $all = 1 ] devices=$(ls -1 /sys/block/md*/md/sync_action | cut -d/ -f4) +[ $all = 1 ] devices=$(ls -d1 /sys/block/md* | cut -d/ -f4) for dev in $devices; do SYNC_ACTION_CTL=/sys/block/$dev/md/sync_action --- /proc/mdstat: Personalities : [raid1] [raid0] md4 : active raid0 md2[0] md3[1] md3 : active raid1 hda5[0] sdc1[1] md2 : active raid1 sda2[0] sdb1[1] md1 : active raid1 sdb2[0] sdc2[1] --- initrd.img-2.6.17-w64: --- /proc/modules: dm_mod 62992 6 - Live 0x88029000 raid0 8704 1 - Live 0x88025000 raid1 24640 3 - Live 0x8801d000 md_mod 83420 6 raid0,raid1, Live 0x88007000 --- volume detail: -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-w64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages mdadm depends on: ii debconf [debconf-2.0] 1.5.2 Debian configuration management sy ii libc6 2.3.6-15 GNU C Library: Shared libraries ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip ii makedev 2.3.1-82 creates device files in /dev Versions of packages mdadm recommends: ii postfix [mail-transport-agent 2.3.0-1A high-performance mail transport -- debconf information: * mdadm/autostart: false mdadm/initrdstart: all * mdadm/warning: * mdadm/start_daemon: true * mdadm/mail_to: paul * mdadm/autocheck: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366487: manpages-dev: ftruncate(2) may fail to extend
Package: manpages-dev Version: 2.28-1 Severity: normal The man page for ftruncate(2) says: If the file previously was shorter, it is extended, However this is not always true. The glibc documentation says: The POSIX standard leaves it implementation defined what happens if the specified new LENGTH of the file is bigger than the original size. The `ftruncate' function might simply leave the file alone and do nothing Empirical evidence shows that Linux returns EPERM and leaves the file unchanged when trying to extend files on a vfat filesystem. Paul -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-w64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages manpages-dev depends on: ii manpages 2.28-1 Manual pages about using a GNU/Lin manpages-dev recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356502: manpages-dev: sendmsg(2) and recvmsg(2) incorrct description of struct msghdr
Package: manpages-dev
Version: 2.19-1
Severity: normal
The sendmsg(2) and recvmsg(2) contain an incorrect desctiption of
struct msghdr.
The manpage says:
socklen_tmsg_controllen; /* ancillary data buffer len */
Whereas the actual implementaton (from {x86_64-linux-gnu/,}bits/socket.h) is:
size_t msg_controllen; /*...*/
Ths makes a difference on 64-bit targets.
Paul
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-w64
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages manpages-dev depends on:
ii manpages 2.19-1 Manual pages about using a GNU/Lin
manpages-dev recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#352619: FTBFS: undefined reference to `XF86VidModeQueryVersion'
The missing symbols are defined in libXxf86vm.a kdegraphics certainly builds here, and the most recent upload built fine on the buildds. We depend on libxxf86vm-dev, so everything should be available. I'm not sure why you would get a different result on your machine. Are you running X.Org from experimental? I'm running unstable last updated yesterday. I do have libxxf86vm-dev installed, but for some reason kpovmodeller is not trying to link against it. ii libxxf86vm-dev 6.9.0.dfsg.1-4 X Video Mode selection library development f ii xserver-xorg 6.9.0.dfsg.1-4 the X.Org X server Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#352619: FTBFS: undefined reference to `XF86VidModeQueryVersion'
Package: kpovmodeler Version: 4:3.5.1-2 Severity: serious Tags: patch Justification: no longer builds from source Build fails on i386 with g++ -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -g -Wall -O2 -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -o .libs/kpovmodeler main.o -L/usr/lib -L/usr/share/qt3/lib -L/usr/X11R6/lib ./.libs/libkpovmodeler.so -lm ./.libs/libkpovmodeler.so: undefined reference to `XF86VidModeQueryVersion' ./.libs/libkpovmodeler.so: undefined reference to `XF86VidModeGetModeLine' collect2: ld returned 1 exit status The missing symbols are defined in libXxf86vm.a Adding $(LIBVM) to libkpovmodeler_la_LIBADD seems to fix the build. Patch below. I'm not sure if this is the correct solution or if this is really an xlibmesa-gl-dev/autoconf bug. Paul diff -urp kdegraphics-3.5.1/kpovmodeler/Makefile.am kdegraphics-fixed/kpovmodeler/Makefile.am --- kdegraphics-3.5.1/kpovmodeler/Makefile.am 2005-09-10 09:18:54.0 +0100 +++ kdegraphics-fixed/kpovmodeler/Makefile.am 2006-02-12 23:39:11.0 + @@ -110,7 +110,7 @@ libkpovmodeler_la_SOURCES = pmpart.cpp p pmpartiface.skel libkpovmodeler_la_LDFLAGS = $(all_libraries) -version-info 0:0:0 -no-undefined $(LIBFREETYPE_RPATH) -libkpovmodeler_la_LIBADD = $(LIBFREETYPE_LIBS) $(LIB_KPARTS) $(GLLIB) -lXmu -lXi +libkpovmodeler_la_LIBADD = $(LIBFREETYPE_LIBS) $(LIB_KPARTS) $(GLLIB) $(LIBVM) -lXmu -lXi METASOURCES = AUTO noinst_HEADERS = pmpart.h pmfactory.h pmview.h pmshell.h pmobjectdrag.h \ diff -urp kdegraphics-3.5.1/kpovmodeler/Makefile.in kdegraphics-fixed/kpovmodeler/Makefile.in --- kdegraphics-3.5.1/kpovmodeler/Makefile.in 2006-02-12 23:40:46.0 + +++ kdegraphics-fixed/kpovmodeler/Makefile.in 2006-02-12 23:39:40.0 + @@ -857,7 +854,7 @@ #- libkpovmodeler_la_LDFLAGS = $(all_libraries) -version-info 0:0:0 -no-undefined $(LIBFREETYPE_RPATH) #+ 1 libkpovmodeler_la_LDFLAGS = $(all_libraries) -version-info 0:0:0 -no-undefined $(KDE_NO_UNDEFINED) $(LIBFREETYPE_RPATH) -libkpovmodeler_la_LIBADD = $(LIBFREETYPE_LIBS) $(LIB_KPARTS) $(GLLIB) -lXmu -lXi +libkpovmodeler_la_LIBADD = $(LIBFREETYPE_LIBS) $(LIB_KPARTS) $(GLLIB) $(LIBVM) -lXmu -lXi #- METASOURCES = AUTO noinst_HEADERS = pmpart.h pmfactory.h pmview.h pmshell.h pmobjectdrag.h \ pmtreeview.h pmtreeviewitem.h pmmessage.h \ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-w64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kpovmodeler depends on: ii kdelibs4c2a 4:3.5.1-2 core libraries for all KDE applica ii libc6 2.3.5-13 GNU C Library: Shared libraries an ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libgcc1 1:4.0.2-8 GCC support library ii libglu1-xorg [libglu1]6.9.0.dfsg.1-4 Mesa OpenGL utility library [X.Org ii libqt3-mt 3:3.3.5-3 Qt GUI Library (Threaded runtime v ii libstdc++64.0.2-8The GNU Standard C++ Library v3 ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li ii libxi66.9.0.dfsg.1-4 X Window System Input extension li ii libxmu6 6.9.0.dfsg.1-4 X Window System miscellaneous util ii xlibmesa-gl [libgl1] 6.9.0.dfsg.1-4 Mesa 3D graphics library [X.Org] ii zlib1g1:1.2.3-9 compression library - runtime kpovmodeler recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349764: vim: Does not autodetect svk patches
Package: vim
Version: 1:6.4-006+2
Severity: minor
Tags: patch
The SVK version control system generates patches in a slightly different
format to CVS and SVN. Vim does not autodetect these as patch files.
A typical svk generated patch looks something like:
=== arm-dis.c
==
--- arm-dis.c (revision 1826)
+++ arm-dis.c (local)
The attached patch adds a pattern for this to syntax.vim
Paul
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-w64
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages vim depends on:
ii libc62.3.5-12GNU C Library: Shared libraries an
ii libgpmg1 1.19.6-21 General Purpose Mouse - shared lib
ii libncurses5 5.5-1 Shared libraries for terminal hand
ii vim-common 1:6.4-006+2 Vi IMproved - Common files
ii vim-runtime 1:6.4-006+2 Vi IMproved - Runtime files
vim recommends no packages.
-- no debconf information
--- vim/runtime/scripts.vim.old 2006-01-25 02:46:10.0 +
+++ vim/runtime/scripts.vim 2006-01-25 02:50:16.0 +
@@ -180,10 +180,12 @@
- *** in first line and --- in second line (context diff).
- # It was generated by makepatch in the second line (makepatch diff).
- Index: filename in the first line (CVS file)
+ - === , line of =, ---, +++ (SVK diff)
elseif s:line1 =~ '^\(diff\\|Only in \|\d\+\(,\d\+\)\=[cda]\d\+\\|# It was
generated by makepatch \|Index:\s\+\f\+$\|= \f\+ \d\+\.\d\+ vs edited\|
//\f\+#\d\+\)'
\ || (s:line1 =~ '^--- ' s:line2 =~ '^+++ ')
\ || (s:line1 =~ '^\* looking for ' s:line2 =~ '^\* comparing to ')
\ || (s:line1 =~ '^\*\*\* ' s:line2 =~ '^--- ')
+ \ || (s:line1 =~ '^=== ' s:line2 =~ '^=\{66\}' s:line3 =~ '^--- '
s:line4 =~ '^+++')
set ft=diff
PostScript Files (must have %!PS as the first line, like a2ps output)
Bug#348569: ksirc: Ctrl-V does not paste
Package: ksirc Version: 4:3.5.0-3 Severity: normal Pressing Ctrl-V used to paste the contents of the clipboard into the test entry box. Now it does nothing. Selecting Edit/Paste from the menu works fine. Ctrl-X and Ctrl-C also work. Ctrl-V works in other KDE applications (kmail, konqueror), but not ksirc. I don't remember exactly when this broke, but it may have been during the kde3.4-3.5 upgrade. Paul -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-w64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages ksirc depends on: ii kdelibs4c2a 4:3.5.0-3 core libraries for all KDE applica ii libc6 2.3.5-12 GNU C Library: Shared libraries an ii libgcc1 1:4.0.2-7 GCC support library ii libstdc++64.0.2-7The GNU Standard C++ Library v3 ii perl 5.8.7-10 Larry Wall's Practical Extraction Versions of packages ksirc recommends: pn libio-socket-ssl-perl none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348266: bzip2: Patch for #348266
Package: bzip2 Version: 1.0.3-1.1 Followup-For: Bug #348266 Patch below fixes this for me. Paul diff -ur bzip2-1.0.3/debian/docbase bzip2/debian/docbase --- bzip2-1.0.3/debian/docbase 2006-01-16 01:31:24.0 + +++ bzip2/debian/docbase2006-01-16 01:27:00.0 + @@ -9,6 +9,7 @@ Section: Apps/Tools Format: html +Index: /usr/share/doc/bzip2/manual.html Files: /usr/share/doc/bzip2/manual.html Format: postscript -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345233: knetload: Broken on 64-bit kernels
Package: knetload Version: 2.3-3.1 Severity: important Tags: patch Some kernels use 64-bit counters for network traffic. This means /sys/class/net/*/statistics/[rt]x_bytes can contain a number that doesn't fit in an unsigned int. The attached patch fixes this by reading the counter into a 64-bit variable. I've truncated this to 32 bits before assigning to currIn/currOut so it wraps properly and remains accurate with large traffic counts (currIn/currOut are only single precision floats). The %Ld scanf format specificer is glibc specific, but that should be ok because this is linux only code. Tested with i386 userland on x86_64 kenrel. Paul -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-rc6-w64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages knetload depends on: ii kdelibs4c2a 4:3.4.3-2 core libraries for all KDE applica ii libart-2.0-2 2.3.17-1Library of functions for 2D graphi ii libaudio21.7-3 The Network Audio System (NAS). (s ii libc62.3.5-9 GNU C Library: Shared libraries an ii libfontconfig1 2.3.2-1.1 generic font configuration library ii libfreetype6 2.1.10-1FreeType 2 font engine, shared lib ii libice6 6.8.2.dfsg.1-11 Inter-Client Exchange library ii libidn11 0.5.18-1GNU libidn library, implementation ii libjpeg626b-11 The Independent JPEG Group's JPEG ii libpng12-0 1.2.8rel-5 PNG library - runtime ii libqt3-mt3:3.3.5-3 Qt GUI Library (Threaded runtime v ii libsm6 6.8.2.dfsg.1-11 X Window System Session Management ii libx11-6 6.8.2.dfsg.1-11 X Window System protocol client li ii libxcursor1 1.1.3-1 X cursor management library ii libxext6 6.8.2.dfsg.1-11 X Window System miscellaneous exte ii libxft2 2.1.7-1 FreeType-based font drawing librar ii libxi6 6.8.2.dfsg.1-11 X Window System Input extension li ii libxinerama1 6.8.2.dfsg.1-11 X Window System multi-head display ii libxrandr2 6.8.2.dfsg.1-11 X Window System Resize, Rotate and ii libxrender1 1:0.9.0-2 X Rendering Extension client libra ii libxt6 6.8.2.dfsg.1-11 X Toolkit Intrinsics ii zlib1g 1:1.2.3-9 compression library - runtime Versions of packages knetload recommends: ii kicker4:3.4.3-3 desktop panel for KDE -- no debconf information diff -ur knetload-2.3/knetload/knetproc.cpp clean/knetload/knetproc.cpp --- knetload-2.3/knetload/knetproc.cpp 2005-12-29 19:46:38.0 + +++ clean/knetload/knetproc.cpp 2004-07-01 12:48:00.0 +0100 @@ -157,15 +157,15 @@ #ifdef Q_OS_LINUX static FILE* fd; -static unsigned long long tmp; +static unsigned int tmp; static char *fn; asprintf(fn, /sys/class/net/%s/statistics/rx_bytes, device.latin1()); if ( (fd = fopen(fn, r)) == 0 ) return; -fscanf(fd, %Lu, tmp); -currIn = (unsigned int)tmp; +fscanf(fd, %u, tmp); +currIn = tmp; fclose(fd); fn[strlen(fn)-8] = 't'; // /sys/class/net/%s/statistics/tx_bytes @@ -173,8 +173,8 @@ if ( (fd = fopen(fn, r)) == 0 ) return; -fscanf(fd, %Lu, tmp); -currOut = (unsigned int)tmp; +fscanf(fd, %u, tmp); +currOut = tmp; fclose(fd); free(fn);
Bug#343477: gdb: segfault when delete pressed
Package: gdb Version: 6.3.90.20051119-1 Severity: normal After upgrading from libreadline5 5.0-11 to libreadline5 5.1-1 gdb segfaults when the delete key is pressed. To reproduce load gdb and press the delete key twice. Backtrace below Paul #0 0xb7f74f6d in _rl_dispatch_callback () from /lib/libreadline.so.5 #1 0xb7f8854a in rl_callback_read_char () from /lib/libreadline.so.5 #2 0x0810cbbb in delete_timer () #3 0x0810c3e2 in delete_file_handler () #4 0x0810be87 in standard_macro_lookup () #5 0x0810c761 in gdb_do_one_event () #6 0x08109a03 in catch_errors () #7 0x080b8c03 in _initialize_tui_hooks () #8 0x08109cdd in current_interp_command_loop () #9 0x08077a3b in main () -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.4-w64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages gdb depends on: ii libc6 2.3.5-8.1 GNU C Library: Shared libraries an ii libncurses5 5.5-1 Shared libraries for terminal hand ii libreadline5 5.1-1 GNU readline and history libraries gdb recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335528: subversion: svn+ssh breaks will automatic ssh connection caching
Package: subversion Version: 1.2.3a-1 Severity: normal The combination of svn+ssh and automatic ssh connection caching is broken. In my ~/.ssh/config I have ControlPath /tmp/.ssh-%h-%p-%r ControlMaster auto The first svn command succeeds, the second fails with Control socket connect(/tmp/.ssh-jay-22-paul): Connection refused ControlSocket /tmp/.ssh-jay-22-paul already exists svn: Connection closed unexpectedly Looking at strace output it appears that svn very rudely terminates its child processes with SIGKILL. This makes ssh leave stray connection state files lying around. Arguably this is a ssh bug (separate bug filed), but svn really should give the child process chance to exit gracefully. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.4-w64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages subversion depends on: ii db4.2-util 4.2.52-20 Berkeley v4.2 Database Utilities ii libapr02.0.54-5 the Apache Portable Runtime ii libc6 2.3.5-7 GNU C Library: Shared libraries an ii libdb4.2 4.2.52-20 Berkeley v4.2 Database Libraries [ ii libexpat1 1.95.8-3 XML parsing C library - runtime li ii libldap2 2.1.30-12 OpenLDAP libraries ii libneon24 0.24.7.dfsg-2 An HTTP and WebDAV client library ii libssl0.9.70.9.7g-5 SSL shared libraries ii libsvn01.2.3a-1 shared libraries used by Subversio ii libxml22.6.22-1 GNOME XML library ii patch 2.5.9-2 Apply a diff file to an original ii zlib1g 1:1.2.3-6 compression library - runtime subversion recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335531: openssh-client: Automatic connection caching broken after SIGKILL
Package: openssh-client Version: 1:4.2p1-5 Severity: normal Automatic connections caching breaks after ssh is terminated with SIGKILL. This frequently happens when ssh is invoked as a subprocess of some other (arguably buggy) application, eg. subversion (separate bug already filed for that). My ~/.ssh/config contains ControlPath /tmp/.ssh-%h-%p-%r ControlMaster auto If I then do: $ ssh jay swith to different terminal $ kill -KILL pid of ssh process $ ssh jay Control socket connect(/tmp/.ssh-jay-22-paul): Connection refused ControlSocket /tmp/.ssh-jay-22-paul already exists $ The only way to make it work again to manually rm /tmp/.ssh-jay-22-paul -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.4-w64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages openssh-client depends on: ii adduser 3.73 Add and remove users and groups ii debconf [debconf-2. 1.4.58 Debian configuration management sy ii dpkg1.13.11.0.1 package maintenance system for Deb ii libc6 2.3.5-7 GNU C Library: Shared libraries an ii libcomerr2 1.38-2 common error description library ii libedit22.9.cvs.20050518-2.2 BSD editline and history libraries ii libkrb531.3.6-5 MIT Kerberos runtime libraries ii libncurses5 5.5-1Shared libraries for terminal hand ii libselinux1 1.26-1 SELinux shared libraries ii libssl0.9.8 0.9.8a-2 SSL shared libraries ii zlib1g 1:1.2.3-6compression library - runtime openssh-client recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#335337: kpdf: Excessive pixmap memory usage
Package: kpdf Version: 4:3.4.2-2 Severity: normal When viewing large pdf files kpdf seems to use an unreasonably large amount of X pixmap resources. After loading iand paging through a large file (eg the IA32 SDM http://www.intel.com/design/pentium4/manuals/index_new.htm ) xrestop reports that kpdf is using almost 700MB of pixmaps (machine has 2GB physical RAM). I have the performance/memory usage option to Normal, so this seems excessive. Changing this setting to Aggressive makes no noticable differece. Changing to Low fixes the excessive pixmap use, but with a fairly severe performance hit. Also tried on a machine with less physical ram, and the limit seems to be one third of physical ram. I don't know if this limit is imposed by kpdf or Xorg. Paul -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.2-w64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages kpdf depends on: ii kdelibs4c24:3.4.2-4 core libraries for all KDE applica ii libc6 2.3.5-7GNU C Library: Shared libraries an ii libfontconfig12.3.2-1.1 generic font configuration library ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libgcc1 1:4.0.2-2 GCC support library ii libjpeg62 6b-10 The Independent JPEG Group's JPEG ii libpaper1 1.1.14-3 Library for handling paper charact ii libqt3-mt 3:3.3.5-1 Qt GUI Library (Threaded runtime v ii libstdc++64.0.2-2The GNU Standard C++ Library v3 ii libx11-6 6.8.2.dfsg.1-9 X Window System protocol client li ii libxft2 2.1.7-1FreeType-based font drawing librar ii libxrender1 1:0.9.0-2 X Rendering Extension client libra ii xlibs 6.8.2.dfsg.1-9 X Window System client libraries m ii zlib1g1:1.2.3-6 compression library - runtime Versions of packages kpdf recommends: ii kghostview4:3.4.2-2 PostScript viewer for KDE -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#330996: ksirc: dishighlight state is not restored
Package: ksirc Version: 4:3.4.2-3 Severity: minor Tags: patch After joining channels /dishighlight is automatically switched off, i.e. highlighting is enabled: *lol* becomes lol in bold. Although /dishighlight mentions that the state will be saved. Any chance of getting the fix for this included in the Debian packages? Upstream bug report, including patch: https://bugs.kde.org/show_bug.cgi?id=74387 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.2-w64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages ksirc depends on: ii kdelibs4c24:3.4.2-4 core libraries for all KDE applica ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libgcc1 1:4.0.2-1 GCC support library ii libstdc++64.0.2-1The GNU Standard C++ Library v3 ii perl 5.8.7-5Larry Wall's Practical Extraction Versions of packages ksirc recommends: pn libio-socket-ssl-perl none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300267: nload: Patch for #300267
Package: nload
Version: 0.6.0-2
Tags: patch
Followup-For: Bug #300267
The attached patch should fix this bug. It makes nload use 64-bit
counters for total traffic, even on 32-bit hosts.
Per-interval measurememnts will probably still wrap at 2^32 but that's
harmless, and a much more invasive fix.
Tested on i386 userland/amd64 kernel.
Paul
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.2-w64
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages nload depends on:
ii libc6 2.3.5-6GNU C Library: Shared libraries an
ii libgcc1 1:4.0.1-8 GCC support library
ii libncurses5 5.4-9 Shared libraries for terminal hand
ii libstdc++51:3.3.6-10 The GNU Standard C++ Library v3
nload recommends no packages.
-- no debconf information
diff -ur nload-0.6.0/src/proc.cpp nload-fixed/src/proc.cpp
--- nload-0.6.0/src/proc.cpp 2005-09-22 23:30:00.0 +0100
+++ nload-fixed/src/proc.cpp 2005-09-22 23:08:09.0 +0100
@@ -126,7 +126,7 @@
void Proc::readLoad( unsigned long in, unsigned long out )
{
- unsigned long total_new[2] = { 0, 0 };
+ long long total_new[2] = { 0, 0 };
int curr_time = 0;
struct timeval time;
@@ -181,7 +181,7 @@
if( ! strcmp( m_dev, dev ) )
{
-sscanf( tmp, %lu %*u %*u %*u %*u %*u %*u %*u %lu, total_new[0], total_new[1] );
+sscanf( tmp, %llu %*u %*u %*u %*u %*u %*u %*u %llu, total_new[0], total_new[1] );
if( total_new[0] m_total[0] )
in = total_new[0] - m_total[0];
@@ -513,12 +513,12 @@
return m_elapsed_time;
}
-unsigned long Proc::totalIn()
+long long Proc::totalIn()
{
return m_total[0];
}
-unsigned long Proc::totalOut()
+long long Proc::totalOut()
{
return m_total[1];
}
diff -ur nload-0.6.0/src/proc.h nload-fixed/src/proc.h
--- nload-0.6.0/src/proc.h 2003-12-04 17:31:34.0 +
+++ nload-fixed/src/proc.h 2005-09-22 23:08:23.0 +0100
@@ -36,8 +36,8 @@
void readLoad( unsigned long in, unsigned long out );
- unsigned long totalIn();
- unsigned long totalOut();
+ long long totalIn();
+ long long totalOut();
int getElapsedTime();
@@ -51,7 +51,7 @@
char m_ip[16];
- unsigned long m_total[2];
+ long long m_total[2];
};
diff -ur nload-0.6.0/src/status.cpp nload-fixed/src/status.cpp
--- nload-0.6.0/src/status.cpp 2003-12-04 21:48:41.0 +
+++ nload-fixed/src/status.cpp 2005-09-22 23:09:03.0 +0100
@@ -30,7 +30,7 @@
}
//new traffic measurement has been made = update statistics
-void Status::update( unsigned long new_value, unsigned long new_total )
+void Status::update( unsigned long new_value, long long new_total )
{
m_cur = new_value;
@@ -44,7 +44,9 @@
*the /proc/net/dev file
*(the total bytes value reaches 4GB and then switches to 0)
*/
- if( new_total ( m_total % UINT_MAX ) )
+ if (new_total = UINT_MAX )
+ m_total = new_total;
+ else if( new_total ( m_total % UINT_MAX ) )
m_total = ( ( m_total / UINT_MAX ) + 1 ) * UINT_MAX + new_total;
else
m_total = ( m_total / UINT_MAX ) * UINT_MAX + new_total;
diff -ur nload-0.6.0/src/status.h nload-fixed/src/status.h
--- nload-0.6.0/src/status.h 2003-12-03 19:30:44.0 +
+++ nload-fixed/src/status.h 2005-09-22 23:09:12.0 +0100
@@ -52,7 +52,7 @@
gigabyte = 7
};
- void update( unsigned long, unsigned long );
+ void update( unsigned long, long long);
void print( Window, int, int, status_format traff_format, status_format data_format );
void resetTrafficData();
Bug#329292: vim-full: Kde open with menu entry broken
Package: vim-full Version: 1:6.3-086+1 Severity: normal Tags: patch The file /usr/share/applications/gvim.desktop launches gvim without -f. This breaks using gvim as the default text editor, or via open with from other kde applications. Typically these will write to a temporary file, spawn gvim, then delete the temporary file when gvim exits. When launched without -f gvim detaches immediately, so the controlling process deletes the temporary file before gvim gets chance to read it. The fix is to add -f to the gvim commandline. Attached patch does this. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.2-w64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages vim-full depends on: ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-0 1.10.3-1 The ATK accessibility toolkit ii libbonobo2-0 2.10.1-1 Bonobo CORBA interfaces library ii libbonoboui2-02.10.1-1 The Bonobo UI library ii libc6 2.3.5-6GNU C Library: Shared libraries an ii libgconf2-4 2.10.1-2 GNOME configuration database syste ii libglib2.0-0 2.8.0-1The GLib library of C routines ii libgnome2-0 2.10.1-1 The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.10.2-2 A powerful object-oriented display ii libgnomeui-0 2.10.1-1 The GNOME 2 libraries (User Interf ii libgnomevfs2-02.10.1-5 The GNOME virtual file-system libr ii libgpmg1 1.19.6-21 General Purpose Mouse - shared lib ii libgtk2.0-0 2.6.10-1 The GTK+ graphical user interface ii libice6 6.8.2.dfsg.1-7 Inter-Client Exchange library ii libncurses5 5.4-9 Shared libraries for terminal hand ii liborbit2 1:2.12.2-3 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.8.2-2Layout and rendering of internatio ii libperl5.85.8.7-5Shared Perl library ii libpopt0 1.7-5 lib for parsing cmdline parameters ii libruby1.81.8.2-9Libraries necessary to run Ruby 1. ii libsm66.8.2.dfsg.1-7 X Window System Session Management ii libx11-6 6.8.2.dfsg.1-7 X Window System protocol client li ii libxml2 2.6.22-1 GNOME XML library ii libxt66.8.2.dfsg.1-7 X Toolkit Intrinsics ii python2.3 2.3.5-8An interactive high-level object-o ii tcl8.48.4.11-1 Tcl (the Tool Command Language) v8 ii vim 1:6.3-086+1Vi IMproved - enhanced vi editor ii xlibs 6.8.2.dfsg.1-7 X Window System client libraries m ii zlib1g1:1.2.3-4 compression library - runtime vim-full recommends no packages. -- no debconf information --- gvim.desktop.old2005-09-20 23:55:04.0 +0100 +++ gvim.desktop2005-09-20 23:55:15.0 +0100 @@ -69,7 +69,7 @@ Comment[wa]=Asspougnî des fitchîs tecses Comment[zh_CN]=编辑文本文件 Comment[zh_TW]=編輯文字檔 -Exec=gvim %U +Exec=gvim -f %U Terminal=false Type=Application Icon=/usr/share/pixmaps/vim.svg
Bug#322344: Use qvm86 instead
I took a quick look at your qvm86 source tarball (daily snapshot from dad-answers). It's currently intended to be bundled directly into qemu. Is it possible to unbundle it somewhat? The idea is: - Only kqemu.h will be needed to build qemu with qvm86 support. - qemu-qvm86-miniminal.patch does only as few mods to the qemu tree as necessary. This probably means basicly checking for kqemu.h existing, defining ENABLE_KQEMU in config.h, and changing device names. - The qvm86 tree itself can be used standalone to build the kernel module. Ok, I'll look into this. The current patch is already does the minimum necessary. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320280: autossh: Ignores --
On Thursday 15 September 2005 09:46, you wrote: tags +pending thanks On Thu, Jul 28, 2005 at 03:16:12AM +0100, Paul Brook wrote: Autossh doesn't handle -- properly when parsing commandling options. It checks for and eats the first --, but it still parses the subsequent commandline arguments. Attached patch fixes this. Any arguemnts after -- are passed verbaitum to ssh. This allows use of the ssh -M option when using autossh. thanks for the patch, while passing -M to ssh makes sense, it doesn't with -f since the command will be launched with no controlling ttys (in case of interactive programs) and will be relaunched whenever autossh detects connection failure, and this is not good :) This is the first reason I can think of, please feel free to provide another use case where using autossh -- -f ssh host command can be useful I don't see how this is relevant. It's standard behaviour for -- to disable parsing of subsequent - options, and I've show a case where this is useful. The current behaviour is just plain broken. May patch makes the behaviour consistent with pretty much every other commandline utility you could care to mention. I agree that -- -f isn't useful. However I don't think that's reason enough to reject the patch. There are many other ways for a dumb user to shoot themselves in the foot, why bother about this particular one? Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#322344: Use qvm86 instead
qvm86 support would be more appropriate. qvm86 is a GPL replacement for kqemu. http://www.qvm86.org/ Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301274: ksynaptics: Alternative patch
Package: ksynaptics
Version: 0.2.0-1.1
Followup-For: Bug #301274
Better patch which keeps TouchPad::coastingSpeedThreshold
as a static data member.
Paul
--- ksynaptics-0.2.0.orig/ksynaptics/src/touchpad.cpp
+++ ksynaptics-0.2.0/ksynaptics/src/touchpad.cpp
@@ -31,6 +31,7 @@
TouchPad *TouchPad::m_self = 0;
static KStaticDeleterTouchPad staticTouchPadDeleter;
+const double TouchPad::coastingSpeedThreshold;
static int finger_low[] = { 53, 38, 25, 18, 10 };
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324213: amd64-libs: libgcc_s.so.1 is missing
On Monday 22 August 2005 19:58, Daniel Jacobowitz wrote:
On Sun, Aug 21, 2005 at 01:23:56AM +0100, Paul Brook wrote:
Package: amd64-libs
Version: 1.2
Severity: normal
Neither amd64-libs nor the biarch gcc-4.0 packages contain a 64-bit
libgcc_s.so.1
Hi Paul,
It should be in lib64gcc1. I see this as produced by gcc-4.0 4.0.1-3.
Is that package broken?
Ah, so it is. Installing that package does the trick.
apt-cache search libgcc didn't find that.
Maybe that package should be suggests/depends from amd64-libs{,-dev}?
Paul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324213: amd64-libs: libgcc_s.so.1 is missing
Package: amd64-libs Version: 1.2 Severity: normal Neither amd64-libs nor the biarch gcc-4.0 packages contain a 64-bit libgcc_s.so.1 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13-rc6-w Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324040: bash: Error during completion of LVM LV and PV names
Package: bash
Version: 3.0-15
Severity: normal
Tags: patch
Command completion for LVM Physical Volume and Logical Volume names is
broken. For example lvdisplay /dev/tab gives:
awk: ^ syntax error
awk: {if ($2 ~ /^/dev//) print $2}
awk: ^ unterminated regexp
awk: cmd. line:1: {if ($2 ~ /^/dev//) print $2}
awk: cmd. line:1: ^ unexpected newline or end of
string
Device names typically contain forward slash characters (/).
These need escaping before embedding them in awk patterns.
Patch attached.
Paul
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13-rc6-w
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages bash depends on:
ii base-files 3.1.6Debian base system miscellaneous f
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libncurses5 5.4-8Shared libraries for terminal hand
ii passwd 1:4.0.3-37 change and administer password and
bash recommends no packages.
-- no debconf information
--- bash_completion.old 2005-08-19 23:19:02.0 +0100
+++ bash_completion 2005-08-19 23:27:43.0 +0100
@@ -6762,13 +6762,13 @@
_physicalvolumes()
{
COMPREPLY=( $( pvscan | \
- awk '/PV/ {if ($2 ~ /^'$cur'/) print $2}' ) )
+ awk '/PV/ {if ($2 ~ /^'${cur//\//\\\/}'/) print $2}' ) )
}
_logicalvolumes()
{
COMPREPLY=( $( lvscan 2/dev/null | \
- awk -F' '{if ($2 ~ /^'$cur'/) print $2}' ) )
+ awk -F' '{if ($2 ~ /^'${cur//\//\\\/}'/) print $2}' ) )
}
_units()
Bug#323062: manpages-dev: clone(2) CLONE PARENT SETTID description incorrect
On Tuesday 16 August 2005 09:25, Michael Kerrisk wrote: Hello Paul, You may have found a fault in the man page, but I believe the fault may be the converse of what you think. ... The following note on the same page implies that this behavior is intentional, and the documentation incorrect: the parent thread ID will be written in case CLONE_PARENT_SETTID It is the above part of the manual page that I believe is incorrect. When I look again, your analysis seems correct. I'm working on a linux syscall emulator (qemu). I thought I was getting glibc assertion failures because of this issue. However I can't reproduce those failures now. Sorry about the misleading bug report. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#323037: Compile error in apt-cacher-cleanup.pl
Package: apt-cacher Version: 1.0.6 Severity: important Running apt-cacher-cleanup.pl (as run by the cron script) gives the error below: /usr/share/apt-cacher/apt-cacher-cleanup.pl -q Global symbol @stat requires explicit package name at /usr/share/apt-cacher/apt-cacher-cleanup.pl line 183. Execution of /usr/share/apt-cacher/apt-cacher-cleanup.pl aborted due to compilation errors. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages apt-cacher depends on: ii bzip2 1.0.2-8high-quality block-sorting file co ii libwww-perl 5.803-4WWW client/server library for Perl ii perl 5.8.7-4Larry Wall's Practical Extraction apt-cacher recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#323062: manpages-dev: clone(2) CLONE_PARENT_SETTID description incorrect
Package: manpages-dev Version: 2.02-2 Severity: normal Tags: patch The clone(2) manpage incorrectly states that CLONE_PARENT_SETTID stores the child TID. In fact it stores the parent TID (verified on a live system). The following note on the same page implies that this behavior is intentional, and the documentation incorrect: the parent thread ID will be written in case CLONE_PARENT_SETTID Patch below. Paul --- man2/clone.2.old2005-08-14 14:29:18.0 +0100 +++ man2/clone.22005-08-14 14:29:40.0 +0100 @@ -360,7 +360,7 @@ .TP .BR CLONE_PARENT_SETTID (since Linux 2.5.49) -Store child thread ID at location +Store parent thread ID at location .I parent_tidptr in parent and child memory. (In Linux 2.5.32-2.5.48 there was a flag CLONE_SETTID that did this.) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.3-w Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages manpages-dev depends on: ii manpages 2.02-2 Manual pages about using a GNU/Lin manpages-dev recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320280: autossh: Ignores --
Package: autossh
Version: 1.3-3
Severity: normal
Tags: patch
Autossh doesn't handle -- properly when parsing commandling options. It
checks for and eats the first --, but it still parses the subsequent
commandline arguments.
Attached patch fixes this. Any arguemnts after -- are passed verbaitum
to ssh. This allows use of the ssh -M option when using autossh.
Paul
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.3-w
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages autossh depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii openssh-client [ssh-client] 1:4.1p1-6Secure shell client, an rlogin/rsh
autossh recommends no packages.
-- no debconf information
--- autossh.c.old 2005-07-28 02:04:16.0 +0100
+++ autossh.c 2005-07-28 02:04:34.0 +0100
@@ -396,13 +396,14 @@
}
done_fwds = 1;
}
-if (argv[i][0] == '-' argv[i][1] == 'M') {
+if (!sawargstop argv[i][0] == '-' argv[i][1] == 'M') {
if (argv[i][2] == '\0')
i++;
continue;
}
/* look for -f in option args and strip out */
- strip_arg(argv[i], 'f', OPTION_STRING);
+ if (!sawargstop)
+ strip_arg(argv[i], 'f', OPTION_STRING);
add_arg(argv[i]);
}
Bug#296242: freeglut: Also FTBFS on i386
Package: freeglut
Followup-For: Bug #296242
This package now FTBFS on i386 with the same error. Alternative patch
below.
diff -u clean/freeglut_callbacks.c ./freeglut_callbacks.c
--- clean/freeglut_callbacks.c 2004-03-30 09:37:27.0 +0100
+++ ./freeglut_callbacks.c 2005-07-16 11:30:17.0 +0100
@@ -41,7 +41,7 @@
#define SET_CALLBACK(a) \
if( fgStructure.Window == NULL ) \
return; \
-FETCH_WCB( ( *( fgStructure.Window ) ), a ) = callback;
+SET_WCB( ( *( fgStructure.Window ) ), a, callback);
/*
* Sets the Display callback for the current window
diff -u clean/freeglut_internal.h ./freeglut_internal.h
--- clean/freeglut_internal.h 2004-03-30 09:37:27.0 +0100
+++ ./freeglut_internal.h 2005-07-16 11:29:52.0 +0100
@@ -373,6 +373,17 @@
/*
+ * SET_WCB() is used as:
+ *
+ * SET_WCB( window, Visibility, val);
+ *
+ * ...where {window} is the freeglut window to set the callback on,
+ * {Visibility} is the window-specific callback to fetch.
+ */
+#define SET_WCB(window,cbname,val) \
+((window).CallBacks[CB_ ## cbname]) = (void *)val
+
+/*
* FETCH_WCB() is used as:
*
* FETCH_WCB( window, Visibility );
diff -u clean/freeglut_structure.c ./freeglut_structure.c
--- clean/freeglut_structure.c 2004-03-30 09:37:27.0 +0100
+++ ./freeglut_structure.c 2005-07-16 11:30:31.0 +0100
@@ -209,7 +209,7 @@
{
void *destroy = FETCH_WCB( *window, Destroy );
fgClearCallBacks( window );
-FETCH_WCB( *window, Destroy ) = destroy;
+SET_WCB( *window, Destroy, destroy);
}
}
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.2-f
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317098: Kmail segfaults at startup after minor upgrade of kdelibs4
Rebuilding the kdepim source package, and installing the resulting lib*.deb fixed the problem for me. Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300942: uptimed: cgi output uses broken colorscheme
Package: uptimed Version: 1:0.3.3-2.2 Severity: normal Tags: patch The provided HTML headers for teh cgi output set the background color, but not the text color. Thi smakes the output illegible when using an inverse (while-on-black) color scheme. Patch below fixes this. Paul --- uprecords.header.old2005-03-22 19:57:05.0 + +++ uprecords.header2005-03-22 19:57:22.0 + @@ -2,7 +2,7 @@ head titleUptime records for this host/title /head -body bgcolor=#ff +body bgcolor=#ff text=#00 h1Uptime records for this host/h1 This host runs a cool program called buptimed/b to log uptime records. It comes with a nice program to examine the logs and display them in a -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.11-jay Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages uptimed depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libuptimed 1:0.3.3-2.2 Library for uptimed -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
