Your message dated Sun, 06 Feb 2005 08:24:32 +
with message-id <[EMAIL PROTECTED]>
and subject line closing; fixed in NMU upload
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 respo
Your message dated Sun, 06 Feb 2005 08:24:32 +
with message-id <[EMAIL PROTECTED]>
and subject line closing; fixed in NMU upload
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 respo
Processing commands for [EMAIL PROTECTED]:
> reassign 293710 debconf
Bug#293710: extranious quote in dpkg-preconfigure kills package configuration
Bug#293733: python2.2-iconvcodec: Install reports compilation errors
Bug reassigned from package `dpkg' to `debconf'.
> severity 293710 grave
Bug#2937
> Please make sure that when you adjust bug severities, there's a clear
> rationale visible in the bug log (rationales embedded in messages to control
> require digging to get at from the webpage, and are not sent to the
> maintainer).
I prefer to put rationale in the control message unless it's i
On Sat, Feb 05, 2005 at 03:26:42PM +0100, Mike Hommey <[EMAIL PROTECTED]> wrote:
> On Sat, Feb 05, 2005 at 03:15:14PM +0100, Guus Sliepen <[EMAIL PROTECTED]>
> wrote:
> > On Sat, Feb 05, 2005 at 02:37:36PM +0100, Mike Hommey wrote:
> >
> > > Mm it *could* be due to the new libxml2 upload. An
Processing commands for [EMAIL PROTECTED]:
> severity 290916 important
Bug#290916: gdm always stops working altogether after a few days (no response
to xdmcp)
Severity set to `important'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system ad
severity 290916 important
thanks
On Sun, Feb 06, 2005 at 09:33:55AM +0100, Thomas Hood wrote:
> > Do you use XDMCP?
> It is used at my site.
Thank you; now that I have this all-important piece of information, I agree
that the bug should be downgraded.
--
Steve Langasek
postmodern programmer
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.5
> tags 291603 sid
Bug#291603: zapping: FTBFS: Using static non fPIC lib to make a shared lib.
There were no tags set.
Tags added: sid
>
End of message, stopping processing here.
Please
Processing commands for [EMAIL PROTECTED]:
> reassign 293845 debconf
Bug#293845: Syntax error in dpkg-preconfigure
Bug reassigned from package `dpkg' to `debconf'.
> severity 293845 grave
Bug#293845: Syntax error in dpkg-preconfigure
Severity set to `grave'.
> close 293845
Bug#293845: Syntax err
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.10
> close 189552
Bug#189552: [DPKG] some files from xlibs_4.2.1-6_i386.deb and
magicfilter_1.2-53_i386.deb not installed
'close' is deprecated; see http://www.debian.org/Bugs/Developer#c
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.10
> reopen 189552
Bug#189552: [DPKG] some files from xlibs_4.2.1-6_i386.deb and
magicfilter_1.2-53_i386.deb not installed
Bug#189555: [DPKG] some files from xlibs_4.2.1-6_i386.deb and
m
Processing commands for [EMAIL PROTECTED]:
> reassign 293568 libgtk2.0-0
Bug#293568: gnome-themes-extras: no compressed archive icon in Nuvola theme
Bug reassigned from package `gnome-themes-extras' to `libgtk2.0-0'.
> severity 293568 serious
Bug#293568: gnome-themes-extras: no compressed archive
Processing commands for [EMAIL PROTECTED]:
> severity 206796 grave
Bug#206796: /usr/bin/distributed-net has wrong endianness on mips-linux
Severity set to `grave'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrato
Processing commands for [EMAIL PROTECTED]:
> reopen 293574
Bug#293574: clearsilver-dev depends on unavailable package clearsilver1
Bug reopened, originator not changed.
> retitle 293574 clearsilver-dev depends on unavailable package clearsilver
Bug#293574: clearsilver-dev depends on unavailable p
reopen 293574
retitle 293574 clearsilver-dev depends on unavailable package clearsilver
thanks,
Hi again :)
Unfortunately, it seems that this bug it's not solved by changing
clearsilver-dev to depends on clearsilver, as clearsilver package is
not built by any source package anymore.
I've built
Package: openmcl
Version: 0.14.2.p1
Severity: grave
Justification: renders package unusable
Installing openmcl causes the following error on my system:
--- snip ---
(#:~)- aptitude install openmcl
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initiali
Processing commands for [EMAIL PROTECTED]:
> tags 293353 pending
Bug#293353: preview-latex: preview-latex does not preserve local configuration
changes during upgrade
There were no tags set.
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian
tags 293353 pending
thanks
Hi.
From: Frank Küster <[EMAIL PROTECTED]>
Subject: Bug#293353: preview-latex: preview-latex does not preserve local
configuration changes during upgrade
Date: Wed, 02 Feb 2005 18:54:35 +0100
> When the configuration file /etc/emacs/site-start.d/51preview-latex.el
>
replying to myself to add more info:
the problem seems to go away, if i apt-get source openmcl, build the
package locally and install that one. as far as i can tell, things
work fine now. let me know if i can do anything to help you reproduce
this.
cheers
fabian
--
.''`. fabian linzberger
Processing commands for [EMAIL PROTECTED]:
> tags 206796 +woody
Bug#206796: /usr/bin/distributed-net has wrong endianness on mips-linux
There were no tags set.
Tags added: woody
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
tags 206796 +woody
thanks
Andreas Barth wrote:
severity 206796 grave
thanks
Hi,
that a package has wrong endianness is at least grave, as the package
cannot be used at all. Another issue is that the information on which
platforms the package should be built is contradictory. Please decide on
which
Processing commands for [EMAIL PROTECTED]:
> tag 283171 + fixed
Bug#283171: clisp: FTBFS on mipsel: testsuite failure
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Deb
Subject: FTBFS: Should disable mono bindings.
Package: clearsilver
Severity: serious
Justification: no longer builds from source
tags +patch
Hi!
I tried to build clearsilver on my host, and got a FTBFS:
gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall
-Wstrict-prototypes -fPIC -I../ -I/u
Why not use last version instead of downgrade ?
Yep... mdadm 1.9 is there near your at
http://www.cse.unsw.edu.au/~neilb/source/mdadm/
Regards,
--
Jean-Yves LENHOF <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROT
Your message dated Sun, 06 Feb 2005 10:40:46 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#293711: fixed in gtk+2.0 2.6.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 now yo
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.10
> tags 293872 + unreproducible
Bug#293872: /usr/lib/common-lisp/bin/openmcl.sh segfaults on installation
There were no tags set.
Tags added: unreproducible
>
End of message, stopping p
fabian linzberger wrote:
> ? /usr/lib/common-lisp/bin/openmcl.sh: line 13: 27196 Segmentation fault
> $EXEC --image-name /usr/lib/openmcl/PPCCL-clean --batch --no-init <
Fabian Linzberger wrote:
> the problem seems to go away, if i apt-get source openmcl, build the
> package locally and install that one. as far as i can tell, things
> work fine now. let me know if i can do anything to help you reproduce
> this.
That's odd as the package should be identical (save f
Your message dated Sun, 06 Feb 2005 11:33:06 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#211341: fixed in synopsis 0.5.0-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 y
Processing commands for [EMAIL PROTECTED]:
> tags 293880 + patch
Bug#293880: FTBFS: Should disable mono bindings.
There were no tags set.
Tags added: patch
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrat
Subject: clearsilver-dev package is empty
Package: clearsilver-dev
Severity: grave
Justification: Renders package unusable
Hi!
When building clearsilver I noticed that clearsilver-dev is empty, as
can be seen in
http://packages.debian.org/cgi-bin/search_contents.pl?searchmode=filelist&word=clea
This problem is fixed in the new upstream version (0.92).
Please, upload a new package in order to fix this problem.
--
Bruno Barrera C.
Debian Developer
signature.asc
Description: This is a digitally signed message part
Your message dated Sun, 6 Feb 2005 18:28:54 +0100
with message-id <[EMAIL PROTECTED]>
and subject line The bug didn't work?
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
Processing commands for [EMAIL PROTECTED]:
> close 266044
Bug#266044: php4-gd2 is obsoleted by php4-gd, see #261186
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Jeroen van Wolffelaar <[EMAIL
PROTECTED]>
> close 264828
Bug#2
Package: postfix
Version: 2.1.5-4
Severity: serious
On fresh installation postfix _silently_ does not write alias for root.
That is, it installs with /etc/aliases like
# /etc/aliases
mailer-daemon: postmaster
postmaster: root
nobody: root
hostmaster: root
usenet: root
news: root
webmaster: root
w
tag +patch
thanks,
Hi, I've made an install file for clearsilver-dev, but I think it's not
ok, because you only package the python bindings:
--- /dev/null 2005-02-06 11:13:22.673574392 +0100
+++ clearsilver-dev.install 2005-02-06 18:19:48.597010136 +0100
@@ -0,0 +1,4 @@
+debian/tmp/usr/inc
Your message dated Sun, 06 Feb 2005 12:47:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#249481: fixed in libgtk-perl 0.7009-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 n
Your message dated Sun, 06 Feb 2005 12:47:35 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#245440: fixed in libopengl-perl 0.54.alan1-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
i installed hotplug-utils and rebooted, and now it works. so i guess you may
close the bug please.
__
Do you Yahoo!?
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250
--
To UNSUBSCRIBE, email to [EMA
Your message dated Sun, 6 Feb 2005 18:28:49 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:26:51 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:27:16 +
with message-id <[EMAIL PROTECTED]>
and subject line removed
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
Your message dated Sun, 6 Feb 2005 18:25:57 +
with message-id <[EMAIL PROTECTED]>
and subject line lsbdev removed
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 re
Your message dated Sun, 6 Feb 2005 18:25:57 +
with message-id <[EMAIL PROTECTED]>
and subject line lsbdev removed
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 re
Your message dated Sun, 6 Feb 2005 18:25:57 +
with message-id <[EMAIL PROTECTED]>
and subject line lsbdev removed
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 re
Your message dated Sun, 6 Feb 2005 18:25:57 +
with message-id <[EMAIL PROTECTED]>
and subject line lsbdev removed
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 re
Your message dated Sun, 6 Feb 2005 18:28:49 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:27:39 +
with message-id <[EMAIL PROTECTED]>
and subject line removed
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
Your message dated Sun, 6 Feb 2005 18:30:03 +
with message-id <[EMAIL PROTECTED]>
and subject line removed
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
Processing commands for [EMAIL PROTECTED]:
> severity #271033 important
Bug#271033: mdadm - is not able to properly assemble multipath device
Severity set to `important'.
> stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(adminis
Your message dated Sun, 6 Feb 2005 18:49:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:47:27 +
with message-id <[EMAIL PROTECTED]>
and subject line removed
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
Your message dated Sun, 6 Feb 2005 18:48:17 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:35:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:43:09 +
with message-id <[EMAIL PROTECTED]>
and subject line removed
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
Your message dated Sun, 6 Feb 2005 18:42:48 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:41:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:36:34 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:33:26 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:44:02 +
with message-id <[EMAIL PROTECTED]>
and subject line removed
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
Your message dated Sun, 6 Feb 2005 18:31:41 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed from Debian
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
Your message dated Sun, 6 Feb 2005 18:43:34 +
with message-id <[EMAIL PROTECTED]>
and subject line removed
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
Your message dated Sun, 6 Feb 2005 18:37:40 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:30:57 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:35:48 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 06 Feb 2005 13:32:17 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#239186: fixed in jed 0.99.16-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 your
Your message dated Sun, 06 Feb 2005 13:32:17 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221338: fixed in jed 0.99.16-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 your
Your message dated Sun, 6 Feb 2005 18:30:57 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Package: firehol
Version: 1.214-3
Severity: grave
Tags: security
I'm afraid that recent fixes still missed some unsafe temporary
directory uses in firehol. In firehol-lib.sh I see:
${CAT_CMD} /proc/config >/tmp/kcfg.$$
Upstream patched this here:
http://cvs.sourceforge.net/viewcvs.py/fir
Your message dated Sun, 6 Feb 2005 18:41:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:47:07 +
with message-id <[EMAIL PROTECTED]>
and subject line removed
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
Your message dated Sun, 6 Feb 2005 18:38:17 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 06 Feb 2005 13:32:39 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#293091: fixed in lirc 0.7.1pre1-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 y
Your message dated Sun, 6 Feb 2005 18:37:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:34:27 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:32:38 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 06 Feb 2005 13:47:20 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#293406: fixed in mdadm 1.9.0-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 your
Your message dated Sun, 6 Feb 2005 18:30:57 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:42:24 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 06 Feb 2005 13:47:20 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#292282: fixed in mdadm 1.9.0-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 your
Your message dated Sun, 6 Feb 2005 18:52:36 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:52:36 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:50:54 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:57:44 +
with message-id <[EMAIL PROTECTED]>
and subject line removed
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
Your message dated Sun, 6 Feb 2005 18:58:11 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:30:57 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:56:25 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:42:24 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:30:57 +
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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
Your message dated Sun, 6 Feb 2005 18:43:34 +
with message-id <[EMAIL PROTECTED]>
and subject line removed
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
Package: libzip-ocaml-dev
Version: 1.01-13
Severity: grave
Files /usr/lib/ocaml/3.08/zip/zip.cmxa and /usr/lib/ocaml/3.08/unix.cmxa
make inconsistent assumptions over implementation Unix
Although interesting enough, this only occurs with the native code, not
byte code.
:-(
-- System Information
Package: phpgroupware
Version: 0.9.16.003-1
Severity: grave
Tags: security
CAN-2004-1385 describes multiple security holes in phpgroupware:
phpGroupWare 0.9.16.003 and earlier allows remote attackers to gain sensitive
information via (1) unexpected characters in the session ID such as shell
Your message dated Sun, 06 Feb 2005 14:35:07 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#293834: fixed in quodlibet 0.8.1-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
Package: squid
Version: 2.5.7-4
Severity: grave
Tags: security
CAN-2005-0174 describes some security holes in squid:
Squid 2.5 up to 2.5.STABLE7 allows remote attackers to poison the cache or
conduct certain attacks via headers that do not follow the HTTP specification,
including (1) multip
Package: isoqlog
Version: 2.2-0.2
Severity: grave
Justification: renders package unusable
the recent isoqlog upgrade is uninstallable on my system. I get as far
as answering the debconf questions, then it enters an infinite loop.
I purged the package and tried a fresh install, with the same prob
The new upstream release also fixes lots more security holes, which have
CAN numbers CAN-2004-1384 and CAN-2004-1383. Please reference all three
CAN numbers in your changelog.
--
see shy jo
signature.asc
Description: Digital signature
Processing commands for [EMAIL PROTECTED]:
> severity 293889 normal
Bug#293889: postfix: Fresh installation does not write alias for root
Severity set to `normal'.
> --
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, D
Hm... Thanks for build test of "all" packages. These are good
regression test on the TeX related tools :-)
If there is build error in Chinese (Simplified), there are few possible
root causes:
* something chenged in TEX/LATEX (Build system)
* I accidentaly broke some text encoding somewhere re
severity 293889 normal
--
> On fresh installation postfix _silently_ does not write alias for root.
> That is, it installs with /etc/aliases like
If /etc/aliases exists at install time, then it is left untouched, since
the admin obviously has what he wants there. Your /etc/aliases is not
from a
Package: ifp-line
Version: 0.2.4.5-1
Severity: grave
Justification: renders package unusable
ifp ls gives the following message when not root
Device is busy. (I was unable to claim its interface.)
It works perfectly as root.
I have installed pmp-common and add my user to plugdev -> no result
1 - 100 of 143 matches
Mail list logo
