Bug#370600: reportbug: Inexperienced Python Code

2006-06-06 Thread Synx
print; __END__ -- Package-specific info: ** Environment settings: EDITOR="gvim -f" ** /home/admin/.reportbugrc: reportbug_version "3.20" mode novice ui text realname "Synx" email "[EMAIL PROTECTED]" -- System Information: Debian Release: testing/unstable APT

Bug#369828: inkscape: Same problem w/ Futex on testing 0.43-4 and unstable 0.43-5

2006-06-07 Thread Synx
Package: inkscape Version: 0.43-5 Followup-For: Bug #369828 The glibc people deny this is their bug (of course) but suggest that the cause is someone forgetting to unlock a mutex or something. "Uses the synchronization primitives incorrectly" they say (without suggesting how it might be incorrec

Bug#443032: Patch to enable the pixman package

2007-10-12 Thread Synx
I was shocked to see the wacom input driver hadn't been compiled for the latest ABI, so I went and compiled it myself, fixed the problems that were stopping it from compiling. pixman (whatever that is) is a pkg-config package in the new xorg system, so anything that uses it (aka wacom-tools) has t

Bug#443032: Patch to enable the pixman package

2007-10-12 Thread Synx
Julien Cristau wrote: That patch is (mostly) wrong. wacom should indeed use pkg-config to get the necessary cflags, but it doesn't have to care about pixman. The file linuxwacom/src/xdrv/xf86Wacom.c includes the file xf86.h, which is part of the xorg package. However down the chain of include

Bug#584585: To remove the conflicting packages

2010-06-05 Thread Synx
It looks like an old version of libbind is left installed, which depends on an old version of libdns which depends on the conflicting version of libisc. So basically what I did is I looked at what packages conflicted when trying to remove libisc50, and removed them as well. That normally can quick