Bug#332216: kismet: depends on unavailable libmagick6 package

Package: kismet Version: 2005.08.R1-1 Severity: grave Justification: renders package unusable Hello, kismet is uninstallable in sid because libmagick6 isn't available anymore. libmagick9 is in unstable so changing build-deb to libmagick9-dev and rebuilding should fix this bug. -- System Informa

Bug#321956: marked as done (firestring_0.9.12-2(m68k/unstable/poseidon): FTBFS on m68k)

Your message dated Tue, 04 Oct 2005 23:02:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#321956: fixed in firestring 0.9.12-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#332215: uw-imapd: [CAN-2005-2933] Buffer overflow in Netmailbox Name Parsing

Package: uw-imapd Version: 7:2002edebian1-11 Severity: critical Tags: security patch Hi! There is an exploitable buffer overflow in the UW-IMAP server. Details and the patch is at http://www.idefense.com/application/poi/display?id=313&type=vulnerabilities This got assigned CAN-2005-2933, plea

Bug#332199: apt-move: fails building Packages file

Package: apt-move Version: 4.2.24-1 Severity: grave Justification: renders package unusable As of today, apt-move fails to build the packages file. It worked yesterday. There are two packages starting with "xfce4-syst" but none named that, so it appears something is trunkating a package name. m

Processed: reassigning bugs from imlib+png2 to imlib

Processing commands for [EMAIL PROTECTED]: > reassign 285025 imlib11 Bug#285025: imlib1: CAN-2004-0817 is not fixed. Bug reassigned from package `imlib1' to `imlib11'. > reassign 154690 gdk-imlib11 Bug#154690: gdk-imlib1: does not support PPMs with maxval = 1 Bug reassigned from package `gdk-imli

Bug#307085: marked as done (davfs2: FTBFS, at least the second time)

Your message dated Tue, 04 Oct 2005 23:13:58 -0300 with message-id <[EMAIL PROTECTED]> and subject line Has been fixed for ages, but I forgot to close has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#331694: marked as done (qtorrent: Can't save file; is unusable)

Your message dated Tue, 04 Oct 2005 18:32:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331694: fixed in qtorrent 2.9.1-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#312058: marked as done (ttf-larabie-uncommon: upgrade fails due to missing dependency)

Your message dated Tue, 04 Oct 2005 18:32:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#312058: fixed in ttf-larabie 1:20011216-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#331080: FTBFS: Error checking examples

On 4 October 2005 at 08:23, Matt Kraai wrote: | On Tue, Oct 04, 2005 at 06:17:27AM -0500, Dirk Eddelbuettel wrote: | > | > On 3 October 2005 at 21:59, Matt Kraai wrote: | > | > | > I disabled a few of these tests on other packages formerly provided by | > | > | > r-recommended, and I guess I nee

Bug#331080: FTBFS: Error checking examples

On Tue, Oct 04, 2005 at 06:17:27AM -0500, Dirk Eddelbuettel wrote: > > On 3 October 2005 at 21:59, Matt Kraai wrote: > | > | > I disabled a few of these tests on other packages formerly provided by > | > | > r-recommended, and I guess I need to disable it here too. > | > | > | > | This was on i38

Bug#331661: extensions/*.jar ship without source code, shipped jar files are installed

Matthias Klose wrote: Package: docbook-xsl Version: 1.68.1 Severity: serious The extensions contains many jar files, without having the sources in the source package, the problematic files seem to be: saxon644.jar saxon65.jar saxon651.jar saxon652.jar saxon653.jar I don't change wha

Bug#331618: scim-chinese still not installable

Fair enough. Case closed. Looking forward to the update. 2005/10/4, Ming Hua <[EMAIL PROTECTED]>: > On Tue, Oct 04, 2005 at 03:33:36PM -0700, Wilmer Lau wrote: > > However, you don't sound very 'welcoming' to a newbie like me to > > participate in the Debian process in the future. I've heard pr

Bug#331618: scim-chinese still not installable

On Tue, Oct 04, 2005 at 03:33:36PM -0700, Wilmer Lau wrote: > However, you don't sound very 'welcoming' to a newbie like me to > participate in the Debian process in the future. I've heard problems > with Debian's community being somewhat exclusive, not friendly, and > welcoming. If you were me,

Bug#298714: marked as done (nsmon: FTBFS (amd64/gcc-4.0): array type has incomplete element type)

Your message dated Tue, 04 Oct 2005 16:02:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#298714: fixed in nsmon 2.3e-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#329246: Another patch

Hello, Thank you very much for your message, Andree - you really deserved your vacation ;-) I had seen the bug on mindi, but I had not paid enough attention to it. So, I looked at it again and tried the patch, on both a Sarge system (on which it worked before) and a recent one (on which it did

Bug#329090: util-vserver: barrier not working, but chroot escape does

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 These bug reports are very confusing, I am performing my own tests to help clarify. Andrew Lee wrote: > The VCI shouldn't be if you have setup /dev/loop4 correctly, I > did same thing and got same errors when I forgot to setup the /dev/ > loop4 aft

Bug#286478: marked as done (isic: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment)

Your message dated Tue, 04 Oct 2005 15:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#286478: fixed in isic 0.05-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#331618: scim-chinese still not installable

If I had known the proper 'process', I would have done so. Thanks for informing me now. I won't do so in the future. However, you don't sound very 'welcoming' to a newbie like me to participate in the Debian process in the future. I've heard problems with Debian's community being somewhat exclu

Bug#329468: More info

Some more info on the issue: If trying to execute the failing command by hand one gets the following error message: /tmp/chroottest$ sudo chroot /tmp/chroottest/woody dpkg --force-depends --install var/cache/apt/archives/base-files_3.0.2_i386.deb var/cache/apt/archives/base-passwd_3.4.1_i386.deb

Bug#258640: marked as done (elvis-tiny: FTBFS with gcc-3.4: conflicting types for 'malloc')

Your message dated Tue, 04 Oct 2005 14:17:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#258640: fixed in elvis-tiny 1.4-19 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#331710: marked as done (php4-lasso is uninstallable due to phpapi-20020918 dependency)

Your message dated Tue, 04 Oct 2005 14:17:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331710: fixed in lasso 0.6.3-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#326927: marked as done (tcpick: implicitly converted pointers)

Your message dated Tue, 04 Oct 2005 14:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#326927: fixed in tcpick 0.2.1-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#258460: marked as done (asmem: FTBFS with gcc-3.4: label at end of compound statement)

Your message dated Tue, 04 Oct 2005 14:02:04 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#258460: fixed in asmem 1.9-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your r

Bug#327327: marked as done (tcpick: does not run on ppc)

Your message dated Tue, 04 Oct 2005 14:02:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#327327: fixed in tcpick 0.2.1-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now you

Bug#331710: php4-lasso is uninstallable due to phpapi-20020918 dependency

Package: php4-lasso Severity: grave Depends: phpapi-20020918 phpapi-20020918 isn't provided by anything. phpapi-20050606 is, however. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked t

Bug#328420: marked as done (ABI breakage through non-versioned shlib dependency)

Your message dated Tue, 04 Oct 2005 13:17:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#328420: fixed in gtksourceview 1.4.2-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#331699: marked as done (lasso: FTBFS: lasso_wrap.c:4647: error: invalid type argument of '->')

Your message dated Tue, 04 Oct 2005 13:17:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331699: fixed in lasso 0.6.3-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#318723: marked as done (javascript crasher)

Your message dated Tue, 4 Oct 2005 16:16:57 -0400 with message-id <[EMAIL PROTECTED]> and subject line closing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen th

Bug#331699: lasso: FTBFS: lasso_wrap.c:4647: error: invalid type argument of '->'

Kurt Roeckx wrote: > It's not only a cleaner log, but it also changes the generated > code. This can be the difference between something that works or > not. Thanks for the information; I didn't know this. Frederic -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "u

Bug#331699: lasso: FTBFS: lasso_wrap.c:4647: error: invalid type argument of '->'

On Tue, Oct 04, 2005 at 09:41:09PM +0200, Frederic Peters wrote: > > > It's also giving _alot_ of warning of this type: > > warning: dereferencing type-punned pointer will break strict-aliasing rules > > You can probably use -fno-strict-aliasing as a workaround for > > this. > > Those are from S

Bug#331699: lasso: FTBFS: lasso_wrap.c:4647: error: invalid type argument of '->'

> Your package is failing to build with the following error: > lasso_wrap.c:4647: error: invalid type argument of '->' > lasso_wrap.c:4647: error: syntax error before ')' token > [...] > lasso_wrap.c:5148: error: invalid type argument of '->' > lasso_wrap.c:5148: error: syntax error before ')' toke

Bug#331699: lasso: FTBFS: lasso_wrap.c:4647: error: invalid type argument of '->'

Kurt Roeckx wrote: > Hi, > > Your package is failing to build with the following error: > lasso_wrap.c:4647: error: invalid type argument of '->' > lasso_wrap.c:4647: error: syntax error before ')' token > [...] > lasso_wrap.c:5148: error: invalid type argument of '->' > lasso_wrap.c:5148: error:

Bug#331699: lasso: FTBFS: lasso_wrap.c:4647: error: invalid type argument of '->'

Package: lasso Version: 0.6.3-1 Severity: serious Hi, Your package is failing to build with the following error: lasso_wrap.c:4647: error: invalid type argument of '->' lasso_wrap.c:4647: error: syntax error before ')' token [...] lasso_wrap.c:5148: error: invalid type argument of '->' lasso_wrap

Bug#319411: marked as done (rebuild for gxx transition)

Your message dated Tue, 04 Oct 2005 10:47:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#319411: fixed in libmusicbrainz-2.1 2.1.1-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case i

Bug#316584: marked as done (libmusicbrainz-2.1: FTBFS with g++-4.0: cast from 'char*' to 'int' loses precision)

Your message dated Tue, 04 Oct 2005 10:47:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#316584: fixed in libmusicbrainz-2.1 2.1.1-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case i

Processed: Forgot to retitle

Processing commands for [EMAIL PROTECTED]: > retitle 331396 libmysqlclient15: contains libcdbclient.so.* shared library > also in libmysqlclient14-dev Bug#331396: mysql-query-browser: package dependencies conflict with mysql-server-5.0 Changed Bug title. > thanks Stopping processing here. Plea

Bug#331696: FTBFS when upx-ucl-beta is installed

Package: dar Version: 2.2.2-1 Severity: serious [...] strip: debian/dar-static/usr/bin/dar_static: File format not recognized dh_strip: command returned error code 256 make: *** [binary-arch] Error 1 dar's configure script detects upx is installed and uses it to generate "compressed" (but broken)

Bug#331694: qtorrent: Can't save file; is unusable

Package: qtorrent Version: 2.9.1-3 Severity: grave Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 The same bugs as in 330563 is also in line 138 of the same file. It doesn't do anything with respect to asking about where to save, and is therefore quite unusable. You can replace

Bug#327963: (no subject)

This problem is actually caused by a problem with libfwbuilder 2.0.7-4 which is already corrected in 2.0.7-5 which was uploaded last night as part of the fix for Bug#331575. Regards, Jeremy Michael Setzer wrote: Hi, I just installed the Debian unstable packages: ii fwbuilder

Bug#323350: marked as done (egroupware: Another XMLRPC vulnerability)

Your message dated Tue, 4 Oct 2005 17:59:20 +0200 with message-id <[EMAIL PROTECTED]> and subject line (no subject) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reop

Processed: Tag bug 324808 pending

Processing commands for [EMAIL PROTECTED]: > # Forgot 324808 > tags 324808 pending Bug#324808: scim-chinese: sicm-chinese uninstallable with scim 1.4.1 There were no tags set. Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking sy

Processed: Re: Bug#331618: scim-chinese still not installable

Processing commands for [EMAIL PROTECTED]: > merge 324268 331618 Bug#324268: Uninstallable scim-chinese package Bug#331618: scim-chinese still not installable Merged 324268 331618. > tags 324268 pending Bug#324268: Uninstallable scim-chinese package There were no tags set. Bug#331618: scim-chines

Processed: Fixed in NMU of egroupware 1.0.0.007-2.dfsg-2sarge2

Processing commands for [EMAIL PROTECTED]: > tag 323350 + fixed Bug#323350: egroupware: Another XMLRPC vulnerability Tags were: sid etch sarge security Tags added: fixed > quit Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administ

Bug#331618: scim-chinese still not installable

merge 324268 331618 tags 324268 pending tags 331618 pending tags 297975 pending thanks On Tue, Oct 04, 2005 at 01:08:45AM -0700, Wilmer Lau wrote: > > Scim-chinese is not installable since early October. Would someone > out there be kind enough to provide a fix for this? This bug has > already

Processed: #293667 not fixed by recent update

Processing commands for [EMAIL PROTECTED]: > found 293667 4.41.3-2 Bug#293667: Mailscanner Wont Upgrade Or Install After Removing Old Version Bug marked as found in version 4.41.3-2. > found 293667 4.46.2-1 Bug#293667: Mailscanner Wont Upgrade Or Install After Removing Old Version Bug marked as f

Bug#293667: #293667 not fixed by recent update

found 293667 4.41.3-2 found 293667 4.46.2-1 thanks [EMAIL PROTECTED] BCCed Uhm, how does adding a Depends on debconf (>= 0.5) | debconf-2.0 resolve the problem of simply not sourcing the debconf library before using a debconf function? (Ref.

Bug#311983: marked as done (libflash-mozplugin: a couple of segfaults)

Your message dated Tue, 04 Oct 2005 07:17:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#311983: fixed in libflash 0.4.13-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#331669: issue in streamripper 1.61.14

--- Michael Ablassmeier <[EMAIL PROTECTED]> wrote: > hi Greg, > > On Tue, Oct 04, 2005 at 06:22:01AM -0700, Gregory Sharp wrote: > > Just wanted to warn you of a new bug in the latest > > streamripper (1.61.14). The symptom is that they > > will get an error of "SR_ERROR_BUFFER_EMPTY", and t

Bug#331669: issue in streamripper 1.61.14

Hi Michael, Just wanted to warn you of a new bug in the latest streamripper (1.61.14). The symptom is that they will get an error of "SR_ERROR_BUFFER_EMPTY", and then streamripper will exit. This only happens with certain streams, and/or with certain splitpoint settings. The only known fix

Bug#330827: IP vetting is weak, allowing targetted DoS via usernames

On Mon, Oct 03, 2005 at 10:20:23PM -0700, Joshua Rodman wrote: > What was done before was the line was scanned for anything which > resembles an IP address. What I am suggesting is a regex which > specifies where in the line the IP address should be. how would you specify "where"? if you are thi

Bug#330733: twiki: INCLUDE function allows arbitrary shell command execution

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yes, defiantly I have not found any way to exploit the debian package using any thus far found methods. Florians patch get in the way every time :) Sven micah wrote: > > Does this mean that the twiki (20040902-3) in Debian is not vulnerable > and t

Bug#330733: twiki: INCLUDE function allows arbitrary shell command execution

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Does this mean that the twiki (20040902-3) in Debian is not vulnerable and this bug report can be closed? Micah Sven Dowideit wrote: > while I think its very reasonable for you to send along these > advisories, and even doing so as a BTS bug wothout

Bug#331669: 1.61.14 should not enter testing

Package: streamripper Severity: serious versions of streamripper, greater than 1.61.11 contain new buffering code and therefore may be too buggy for testing. Lets keep them out until the bugs are fixed. bye, - michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubsc

Bug#325993: NMU and patch

On 04/10/2005 Bartosz Fenski aka fEnIo wrote: > On Mon, Oct 03, 2005 at 12:29:38AM +0200, Jonas Meurer wrote: > > i just uploaded a NMU to fix that bug into the DELAYED-5 queue on gluck. > > the patch is attached. > > I doubt it was DELAYED-5 since it's now available in archive. > Anyway thanks fo

Bug#325993: NMU and patch

On Mon, Oct 03, 2005 at 12:29:38AM +0200, Jonas Meurer wrote: > i just uploaded a NMU to fix that bug into the DELAYED-5 queue on gluck. > the patch is attached. I doubt it was DELAYED-5 since it's now available in archive. Anyway thanks for fixing it, cause I'm rather busy now. regards fEnIo --

Bug#331661: extensions/*.jar ship without source code, shipped jar files are installed

Package: docbook-xsl Version: 1.68.1 Severity: serious The extensions contains many jar files, without having the sources in the source package, the problematic files seem to be: saxon644.jar saxon65.jar saxon651.jar saxon652.jar saxon653.jar It looks like the source for saxon643.jar a

Bug#319042: mysql-dfsg still FTBFS for me

Hello On 2005-10-04 Daniel Schepler wrote: > According to the bug log, you thought you'd fixed the FTBFS in > mysql-dfsg, but I can still reproduce it in version 4.0.24-10 using a > pbuilder chroot created just today: Please report the exact version you tried and on which architecture (`dpkg-arch

Processed: mysql-dfsg still FTBFS for me

Processing commands for [EMAIL PROTECTED]: > package mysql-dfsg Ignoring bugs not assigned to: mysql-dfsg > reopen 319042 Bug#319042: linux-kernel-headers: #include fails from C++ due to function parameter called "new" Bug reopened, originator not changed. > severity 319042 serious Bug#319042:

Bug#260846: marked as done (xmcpustate: FTBFS with gcc-3.4: conflicting types for 'malloc')

Your message dated Tue, 04 Oct 2005 05:32:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#260846: fixed in xmcpustate 3-12 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#294392: marked as done (xmcpustate: FTBFS (amd64/gcc-4.0): invalid storage class for function 'update_display')

Your message dated Tue, 04 Oct 2005 05:32:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#294392: fixed in xmcpustate 3-12 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#263209: marked as done (xwit: FTBFS with gcc-3.4: conflicting types for 'malloc')

Your message dated Tue, 04 Oct 2005 05:02:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#263209: fixed in xwit 3.4-7 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your re

Bug#330603: marked as done (gbatnav: FTBFS: missing automake1.9 dep, GNOME1 currently FUBAR)

Your message dated Tue, 04 Oct 2005 04:32:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#330603: fixed in gbatnav 1.0.4cvs20051004-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case i

Bug#297967: Intention to NMU

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Attached the patch for the version I intend to upload. Please respond if you don't want this NMU to happen, if you are working yourself on a patch or if you think that the attached patch won't work. Cheers Luk -BEGIN PGP SIGNATURE- Vers

Processed: Fixed in NMU of python-soappy 0.11.3-1.3

Processing commands for [EMAIL PROTECTED]: > tag 331601 + fixed Bug#331601: python-soappy: python 2.4 is not the default in debian's python-defaults yet. please do not depend on python >= 2.4 There were no tags set. Tags added: fixed > tag 331607 + fixed Bug#331607: python-soappy: FTBFS: Missing

Bug#331080: FTBFS: Error checking examples

On 3 October 2005 at 21:59, Matt Kraai wrote: | > | > I disabled a few of these tests on other packages formerly provided by | > | > r-recommended, and I guess I need to disable it here too. | > | | > | This was on i386. | > | > Odd, so how does that square with my pbuilder logs showing that it

Bug#327963: (no subject)

Hi, I just installed the Debian unstable packages: ii fwbuilder 2.0.7-2Firewall administration tool GUI ii fwbuilder-common 2.0.7-2Firewall administration tool GUI (common fil ii fwbuilder-linux 2.0.7-2

Bug#331565: marked as done (missing build-dependency on fdupes)

Your message dated Tue, 04 Oct 2005 03:17:51 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331565: fixed in openclipart 0.17+dfsg-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it i

Processed: Re: Bug#331630: libsilc-1.0.2: Libraries missing

Processing commands for [EMAIL PROTECTED]: > reassign 331630 libsilc-1.0-2 Bug#331630: libsilc-1.0.2: Libraries missing Warning: Unknown package 'libsilc-1.0.2' Bug reassigned from package `libsilc-1.0.2' to `libsilc-1.0-2'. > -- Stopping processing here. Please contact me if you need assistance

Bug#331634: Clean upgrade fails

Package: libpt-dev Severity: serious S'està desempaquetant el reemplaçament de libpt-dev ... dpkg: s'ha produït un error en processar /net/mirror/debian/pool/main/p/pwlib/libpt-dev_1.8.7-1_i386.deb (--unpack): s'està intentant sobreescriure «/usr/lib/libpt.so.1», que també està en el paquet lib

Bug#331630: libsilc-1.0.2: Libraries missing

Package: libsilc-1.0.2 Severity: grave Justification: renders package unusable Jeesh, the libraries are missing. I rebuilt from source, still no libraries in the built package. Same with libsilc-1.0.2-dev. ---snip--- $ dpkg -L libsilc-1.0-2 /. /usr /usr/share /usr/share/doc /usr/share/doc/libsilc

Processed: Re: Bug#331620: uim: privilege escalation before 0.4.9.1

Processing commands for [EMAIL PROTECTED]: > tags 331620 patch Bug#331620: uim: privilege escalation before 0.4.9.1 Tags were: security Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian

Bug#331620: uim: privilege escalation before 0.4.9.1

tags 331620 patch thanks I made the patch from uim-0.4.9 and uim-0.4.9.1. With this patch, update-uim-config prints some warning messages(Broken Pipe), but this will fix the security problem. In Debian, mlterm is installed with setgid, and I'm afraid mlterm is affected with this bug. Best regar

Processed: Re: Bug#331540: eperl: fails to work in nph mode

Processing commands for [EMAIL PROTECTED]: > severity 331540 normal Bug#331540: eperl: fails to work in nph mode Severity set to `normal'. > tags 331540 unreproducible Bug#331540: eperl: fails to work in nph mode There were no tags set. Tags added: unreproducible > thanks Stopping processing her

Bug#331540: eperl: fails to work in nph mode

severity 331540 normal tags 331540 unreproducible thanks On Tue, Oct 04, 2005 at 12:14:18AM +0200, Denis Barbier wrote: > On Mon, Oct 03, 2005 at 04:53:38PM -0500, Carter Wiggins wrote: > [...] > > gives only: > > > > DOCUMENT_ROOT="/var/www" > > HTTP_ACCEPT="text/xml,application/xml,application/

Bug#331627: python-visual: not installable in sid

Package: python-visual Version: 3.2.1-1 Severity: grave Justification: renders package unusable Hi, here is the problem: # apt-get install python-visual Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an

Bug#331050: ..

hi again, please note that the patch does still not prevent raggle from crashing: [EMAIL PROTECTED]:/# raggle Raggle: Loading config... Raggle: Loading feed list... /usr/lib/ruby/1.8/yaml.rb:133:in `transfer': allocator undefined for Bignum (TypeError) from /usr/lib/ruby/1.8/yaml.rb:

Processed: patch

Processing commands for [EMAIL PROTECTED]: > tags 331050 + patch Bug#331050: libruby 1.8.3 yaml bignum issues Tags were: sid upstream Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bu

Bug#331050: patch

tags 331050 + patch thanks hi, attached patch fixes this issue, i dont know if its a clean solution, it seems to work: [EMAIL PROTECTED]:/# ruby -ryaml -e 'puts YAML.load(YAML.dump(1234567890))' 1234567890 bye, - michael --- ruby1.8-1.8.3/ruby-1.8.3/lib/yaml/rubytypes.rb 2005-09-20

Bug#320270: marked as done (FTBFS: Invalid lvalues in assignments)

Your message dated Tue, 04 Oct 2005 01:02:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#320270: fixed in brutefir 1.0f-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#317185: marked as done (libjack0.80.0-0 removed from unstable; rebuild required)

Your message dated Tue, 04 Oct 2005 01:02:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#317185: fixed in brutefir 1.0f-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#331620: uim: privilege escalation before 0.4.9.1

Package: uim Severity: serious Tags: security All uim releases before 0.4.9.1 have a security bug, which causes privilege escalation if applications linked to libuim is set setuid/setgid. For more detail, please see: http://lists.freedesktop.org/pipermail/uim/2005-September/001346.html Best rega

Bug#331618: scim-chinese still not installable

Package: scim-chinese Version: 0.4.2-2 Severity: grave Justification: renders package unusable Scim-chinese is not installable since early October. Would someone out there be kind enough to provide a fix for this? This bug has already been reported but it seems like a fix is a recompile to newer

Bug#76918: Discounted software store

Downloadable software http://Galilee.okmac.com/ May no portent of evil be attached to the words I say. Opinions founded on prejudice are always sustained with the greatest of violence. It's not practice that makes perfectbut perfect practice that makes perfect. It's innocence when it

Bug#76918: Microsoft Digital Image Suite Pro v10.0 - $19.95

Adobe Creative Suite for MAC - $59.95 http://maintains.okmac.com/ It's not the voting that's democracy, it's the counting. Popularity is neither fame nor greatness. Nothing emboldens sin so much as mercy. If little else, the brain is an educational toy. Et tu, Brute!

Bug#316593: Intention to NMU

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Attached the patch for the version I intend to upload. Please respond if you don't want this NMU to happen, if you are working yourself on a patch or if you think that the attached patch won't work. Cheers Luk -BEGIN PGP SIGNATURE- Vers

Bug#328350: marked as done (libgdk-pixbuf2: please rebuild against latest libpng)

Your message dated Tue, 04 Oct 2005 00:32:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#328350: fixed in gdk-pixbuf 0.22.0-9 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no

Bug#331615: galago-sharp: FTBFS: Missing Build-Depends on 'dpatch'

Package: galago-sharp Version: 0.3.2-1 Severity: serious Tags: patch When building 'galago-sharp' in a clean 'unstable' chroot, I get the following error: debian/rules clean debian/rules:14: /usr/share/dpatch/dpatch.make: No such file or directory make: *** No rule to make target `/usr/share/dpa

Bug#331612: [NONFREE-DOC] non-free documentation in dokuwiki

Package: dokuwiki Version: 0.0.20050922-4 Severity: serious Justification: Policy 2.1 The content provided in the data directory--one png image and three text files--are licensed with a Creative Commons Attribution-NonCommercial-ShareAlike License Version 2.0 [1] which is non-free (as a result of

Bug#330733: twiki: INCLUDE function allows arbitrary shell command execution

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 while I think its very reasonable for you to send along these advisories, and even doing so as a BTS bug wothout testing them I think its incredibly rude to do so without saying that you have not tested it out. please, if you enter a bug report, tell