Package: mesa-common-dev
Version: 6.4.2-1
Severity: critical
Justification: breaks the whole system
The apt-get dist-upgrade failed on my system. I have tried doing an apt-get -f
install to fix the problem and also
tried removing the conflicting package to no avail. I hope the following
Your message dated Mon, 18 Sep 2006 23:32:17 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#385293: fixed in batik 1.6-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
Processing commands for [EMAIL PROTECTED]:
tags 388156 pending
Bug#388156: tex-common: purging the package fails (debconf is not available)
There were no tags set.
Tags added: pending
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
tags 388156 pending
thanks
Bill Allombert [EMAIL PROTECTED] wrote:
Package: tex-common
Version: 0.28
Severity: serious
Hello Debian TeX maintainers,
There is an error when attempting to purge the package:
Removing tex-common ...
Purging configuration files for tex-common ...
Processing commands for [EMAIL PROTECTED]:
severity 388067 serious
Bug#388067: *** [stampdir/patch-stamp] Error 2
Severity set to `serious' from `normal'
stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian
forcemerge 384057 388193
thanks
On Tue, Sep 19, 2006 at 03:48:09PM +1000, Matthew Byrne wrote:
The apt-get dist-upgrade failed on my system. I have tried doing an apt-get
-f install to fix the problem and also
tried removing the conflicting package to no avail. I hope the following
Processing commands for [EMAIL PROTECTED]:
tag 385382 + fixed
Bug#385382: Uses deprecated dbus function
Tags were: patch
Tags added: fixed
quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
Processing commands for [EMAIL PROTECTED]:
forcemerge 384057 388193
Bug#384057: mesa-common-dev: Missing Replaces: xlibosmesa-dev
Bug#388193: mesa-common-dev: apt-get dist-upgrade failed
Forcibly Merged 384057 388193.
thanks
Stopping processing here.
Please contact me if you need assistance.
Your message dated Tue, 19 Sep 2006 01:17:18 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#337443: fixed in logilab-common 0.19.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
Package: orca
Version: 0.2.3
Severity: grave
Justification: renders package unusable
On non-i386 architectures, the orca package doesn't actually contain the
orca binary, as seen at eg. [1]. This is because the tarball contains
i386 objects that don't get rebuilt, resulting in a link error. From
warning: Can't read pathname for load map: Input/output error.
warning: .dynamic section for /usr/lib/libasound.so.2 is not at the
expected address
warning: difference appears to be caused by prelink, adjusting
expectations
Two things here:
Your message dated Tue, 19 Sep 2006 01:17:19 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#353512: fixed in logilab-common 0.19.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
Hi,
FWIW, I managed to compile an SMP kernel (using gcc-4.0 since gcc-4.1 won't
compile it).
I decided to compile scsi disk (and driver etc) support in statically
and found out that some symbols called 'exit' are not found when linking
vmlinux together.
Based on some googling I commented out
Processing commands for [EMAIL PROTECTED]:
severity 388177 serious
Bug#388177: msntp: Policy fuckage (create files in /etc/)
Severity set to `serious' from `normal'
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
On 2006/09/19 09:07, Frank K?ster [EMAIL PROTECTED] wrote:
Strangely, I cannot reproduce this here (it happened exactly
once...). Maybe there's again some timeskew problem, but I doubt
it, since all these commands should take a while. Are you able to
reproduce this? If yes, please apply the
Package: cacti
Version: 0.8.6h-4
Severity: serious
Justification: Policy 7.2
Subject: cacti: config/postrm depends on non-essential packages
(dbconfig-common, probably ucf)
Package: cacti
Severity: serious
Justification: Policy 7.2
hi there,
it was recently brought to my attention that the
Package: cacti
Version: -I
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in
Hi
Thanks for the report. I'll contact upstream about this, and also
try to determine how it should be myself.
Regards,
// Ola
On Sat, Sep 16, 2006 at 05:22:49PM +0200, [EMAIL PROTECTED] wrote:
Package: vzctl
Version: 3.0.10-3
Severity: grave
(Sorry and thankful in advance this time ;)
Processing commands for [EMAIL PROTECTED]:
severity 387224 important
Bug#387224: program/unopkg: Could not find a Java Runtime Environment!
Severity set to `important' from `normal'
clone 387224 -1
Bug#387224: program/unopkg: Could not find a Java Runtime Environment!
Bug 387224 cloned as bug
Your message dated Tue, 19 Sep 2006 02:02:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#388156: fixed in tex-common 0.29
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
Processing commands for [EMAIL PROTECTED]:
close 388213
Bug#388213: config/postrm depends on non-essential packages (dbconfig-common,
probably ucf)
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Sean Finney [EMAIL PROTECTED]
Package: bacula-director-mysql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted
Package: acidbase
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject
Package: torrentflux
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: postfix-policyd
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: libdspam7-drv-pgsql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in
Package: bugzilla
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject
Package: tikiwiki
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject
Package: otrs2
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject of
Package: nagios-mysql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: nagios-text
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: libdspam7-drv-mysql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in
Package: webcalendar
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: phpgacl
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject
On Sun, Sep 17, 2006 at 03:15:50AM -0400, José Parrella wrote:
tags 385883 +patch
thank you
I have succesfully built a Debian package which updates the references
to three functions which changed in tinysnmp's API. While the
compilation still produces warnings, I've been able to run ORCA
Package: simba
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject of
Package: mydms
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject of
Package: steam
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject of
Package: zabbix-server-mysql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in
Package: bacula-director-pgsql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted
Processing commands for [EMAIL PROTECTED]:
package hs-plugins
Ignoring bugs not assigned to: hs-plugins
tags 384356 +patch
Bug#384356: hs-plugins: FTBFS: cannot open input file:
/build/buildd/drscheme-352/debian/drscheme/usr/lib/plt/collects/tex2page/tex2page-aux.ss
(No such file or
Package: nagios-pgsql
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the
Package: jffnms
Severity: serious
Justification: 7.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi there,
it was recently brought to my attention that the recommended method
for using dbconfig-common in a package's config and postrm scripts was not
policy compliant as hinted in the subject
Hi Sean,
Please look over the latest version uploaded a couple of weeks ago ago:
[..]
## Source debconf library
if [ -f /usr/share/debconf/confmodule ]; then
. /usr/share/debconf/confmodule
db_version 2.0
fi
# source dbconfig-common stuff
if [ -f
Processing commands for [EMAIL PROTECTED]:
severity 325588 important
Bug#325588: kile crashes on auto-save, incurring data loss
Severity set to `important' from `grave'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
hi radu,
On Tue, 2006-09-19 at 13:02 +0300, Radu Spineanu wrote:
[..]
## Source debconf library
if [ -f /usr/share/debconf/confmodule ]; then
. /usr/share/debconf/confmodule
db_version 2.0
fi
# source dbconfig-common stuff
if [ -f
Your message dated Tue, 19 Sep 2006 03:32:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#387482: fixed in banshee 0.10.12-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 message dated Tue, 19 Sep 2006 03:32:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#387313: fixed in banshee 0.10.12-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 message dated Tue, 19 Sep 2006 03:32:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#387482: fixed in banshee 0.10.12-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 message dated Tue, 19 Sep 2006 03:32:09 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#387313: fixed in banshee 0.10.12-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
There is another one, CVE-2006-4711:
http://mozdev.org/bugs/show_bug.cgi?id=15101
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
tags 388067 pending
Bug#388067: *** [stampdir/patch-stamp] Error 2
There were no tags set.
Tags added: pending
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian
Your message dated Tue, 19 Sep 2006 12:53:11 +0200
with message-id [EMAIL PROTECTED]
and subject line [Pkg-nagios-devel] Bug#388230: config/postrm depends on
non-essential packages (dbconfig-common, probably ucf)
has caused the attached Bug report to be marked as done.
This means that you claim
tags 388067 pending
thanks
Max Kellermann [EMAIL PROTECTED] wrote:
Please see build1.log and build2.log.
Thank you. I found the problem: The patch target deleted one of its
prerequisites, which therefore was always remade and newer than
patch-stamp. The only thing I do not understand is
tags 388149 +confirmed
thanks
Hi, just a quick note to acknowledge receipt of this bug report. Will
provide fix/further updates after work today.
Alan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Your message dated Tue, 19 Sep 2006 04:02:05 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#388234: fixed in serendipity 1.0.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
Your message dated Tue, 19 Sep 2006 12:52:54 +0200
with message-id [EMAIL PROTECTED]
and subject line fixed in latest package
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
Processing commands for [EMAIL PROTECTED]:
tags 388149 +confirmed
Bug#388149: CVE-2006-4712: Cross Context Scripting vulnerability in sage
Tags were: security
Tags added: confirmed
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
This issue does not seem to affect Tikiwiki 1.9.5. I will apply some security
checks from upstream anyway and make a new release.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sat, Sep 09, 2006 at 11:20:11PM +0200, Samuel Thibault wrote:
I don't remember exactly anymore, but when I looked at it yasm
didn't look very promising for porting loadlin to it.
Well, I remember now:
[EMAIL PROTECTED]:/tmp/loadlin/yasm$ yasm -p help
Available yasm parsers:
gas
Package: tinysnmp-agent
Version: 0.8.4
Severity: grave
Justification: renders package unusable
This is the same as #282260, but as that's already archived, I'm opening
a new bug.
The tinysnmpd daemon still doesn't start on sparc but gives a SIGBUS
instead. This is with a recompiled (with -O0, as
Your message dated Tue, 19 Sep 2006 04:17:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#388229: fixed in nagios 2:1.4-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
Your message dated Tue, 19 Sep 2006 04:17:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#388228: fixed in nagios 2:1.4-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
Package: fuse-utils
Version: 2.5.3-4.1
Severity: serious
The current fuse-utils is uninstallable (makedev 2.3.1-82, udev
0.100-1 installed):
Setting up fuse-utils (2.5.3-4.1) ...
creating fuse device node...
/sbin/MAKEDEV: don't know how to make device fuse
dpkg: error processing fuse-utils
Christian Aichinger, le Tue 19 Sep 2006 13:14:25 +0200, a écrit :
Yasm is just a generic assembler that supports both nasm and gas syntax,
and is almost ready for tasm.
I see you asked on yasm-devel about that already:
http://cvs.tortall.net/pipermail/yasm-devel/2006-May/000152.html
Are
Your message dated Tue, 19 Sep 2006 15:12:31 +0200
with message-id [EMAIL PROTECTED]
and subject line /sbin/MAKEDEV: don't know how to make device fuse
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
Hi Niko @2006.09.19_13:36:02_+0200
Thanks for the help. Can you send me your patch with the memmove()'s and
I'll have a look at it?
Package: tinysnmp-agent
Version: 0.8.4
Severity: grave
Justification: renders package unusable
This is the same as
Christian Aichinger, le Tue 19 Sep 2006 14:49:32 +0200, a écrit :
On Tue, Sep 19, 2006 at 02:29:40PM +0200, Samuel Thibault wrote:
Christian Aichinger, le Tue 19 Sep 2006 13:14:25 +0200, a écrit :
Yasm is just a generic assembler that supports both nasm and gas syntax,
and is almost
On Tue, Sep 19, 2006 at 02:29:40PM +0200, Samuel Thibault wrote:
Christian Aichinger, le Tue 19 Sep 2006 13:14:25 +0200, a écrit :
Yasm is just a generic assembler that supports both nasm and gas syntax,
and is almost ready for tasm.
How far are you?
Syntax is almost done: the last
n Mon, 18 Sep 2006, David Starner wrote:
Package: findimagedupes
Version: 0.1.3-7
Just to let you know the status quo: There is a completely rewritten
verison of findimagedupes in preparation which does not show the
problem (and closes the other open bugs). It will be released as
package
I wrote, in a somewhat addled fashion,
The ldconfig configuration files are installed in /lib/ldconfig.
Shouldn't they be installed in /etc/ld.so.conf.d? They're not being
picked up by ldconfig.
More correctly, ia32-libs installs links to the added directories
in /lib/ldconfig, which do not
Package: fglrx-control
Version: 8.28.8-0.1
Severity: grave
Justification: renders package unusable
fireglcontrol doesn't work it just gives Floating point exception
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.9.21
found 358575 2.1.5-8sarge3
Bug#358575: purge mailman deletes all ucf-managed conffiles
Bug marked as found in version 2.1.5-8sarge3.
End of message, stopping processing here.
Please
On Mon, Sep 18, 2006 at 09:31:15PM -0400, Chris Hanson wrote:
Bill Allombert wrote:
Yes, I know, this is why I wrote exactly what command I was using.
I ddes not occur if you omit a single package.
This is very strange and I doubt it has anything to do with mit-scheme.
If you look at
Package: ggz-gtk-games
Version: 0.0.13-1
Severity: critical
Justification: breaks unrelated software
Hi ;o)
I currently have ggz-gtk-games 0.0.13-1 installed and
I'm unable to remove it (post-installation: error code 255)
or upgrade (pre-removal: error code 255) to 0.0.13-3
so my whole
JackTheDipper wrote:
I currently have ggz-gtk-games 0.0.13-1 installed and
I'm unable to remove it (post-installation: error code 255)
or upgrade (pre-removal: error code 255) to 0.0.13-3
so my whole apt-get/dpkg-system is now broken.
If the whole apt-get dpkg system is broken because of one
Your message dated Tue, 19 Sep 2006 08:32:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#388122: fixed in tikiwiki 1.9.5+dfsg1-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
Package: samba
Version: 3.0.23c-1
Severity: grave
Justification: renders package unusable
When mounting share samba hangs with the following message in log.smbd
[2006/09/19 15:06:47, 0] lib/util.c:smb_panic(1592)
PANIC (pid 25177): substitutions failed
[2006/09/19 15:06:47, 0]
Your message dated Tue, 19 Sep 2006 08:32:11 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#388237: fixed in tikiwiki 1.9.5+dfsg1-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
Package: f-spot
Version: 0.2.0-1
Severity: grave
Justification: renders package unusable
F-spot cannot start anymore since the last update. Trying $f-spot --debug , I
have:
=
Got a SIGSEGV while executing native code. This usually
I have exactly the same problems on amd64 sid:
apt-get upgrade
[code]Reading package lists... Done
Building dependency tree... Done
You might want to run `apt-get -f install' to correct these.
The following packages have unmet dependencies:
ggz-gtk-games: Depends: ggz-gtk-game-data (= 0.0.13-1)
Setting up a specific ALPHA macro which is passed via CPPFLAGS to the
configure script in debian/rules is not elegant, because gcc has a
built-in __alpha__ macro to take care of it. Hence, here is the new
patch which will come in the 7.2.2-2 revision.
Cheers,
--
.''`. Aurélien GÉRÔME
: :' :
Thank you for this hint! ;o)
prerm contains this line: ggz-config --remove
--noregistry=/usr/share/ggz/modules/ggz-txt-client
a mkdir of this directory helped to remove ggz-gtk-games
this was needed because that directory is only provided by the debian
package ggz-txt-client which is _not_ a
Your message dated Tue, 19 Sep 2006 09:32:08 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#382576: fixed in docbook-xsl 1.71.0.dfsg.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
Package: libdc1394-13
Version: 1.1.0-3
Severity: grave
On a clean chroot:
[EMAIL PROTECTED]:~# apt-get install libdc1394-13
[snip]
The following packages have unmet dependencies:
libdc1394-13: Depends: libraw1394-5 but it is not installable
E: Broken packages
The package need to be rebuilded
I'm seeing the same errors on my sparc64 (log file looks the same too).
Cheers,
FJP
pgptNFeTOYX2A.pgp
Description: PGP signature
Your message dated Tue, 19 Sep 2006 10:17:08 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#386952: fixed in maildrop 2.0.2-10
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
Bill Allombert wrote:
This is very strange and I doubt it has anything to do with mit-scheme.
If you look at the maintainer scripts, you'll see that the code to
manipulate the emacs files is boilerplate, automatically generated by
debhelper. The mit-scheme package doesn't do any explicit
Your message dated Tue, 19 Sep 2006 10:17:12 -0700
with message-id [EMAIL PROTECTED]
and subject line Bug#387788: fixed in mit-scheme 7.7.90+20060906-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
Ok, I've had a further look into things, and it appears now that the
first injection problem (when allow HTML is unchecked) is with the function:
function htmlToText(aStr) {
varformatConverter =
Hi,
* Erik Schanze ([EMAIL PROTECTED]) [050925 13:13]:
Please feel free to ask for more info.
Can you try whether it works with the new version 3.95-4?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
Package: atftpd
Version: 0.7.dfsg-0.2
Severity: serious
Hello Ludovic,
There is an error when attempting to purge the package:
Removing atftpd ...
Purging configuration files for atftpd ...
/var/lib/dpkg/info/atftpd.postrm: line 4: update-inetd: command not found
dpkg: error processing
severity 388282 important
thanks
Quoting marcel aguilella ([EMAIL PROTECTED]):
Package: samba
Version: 3.0.23c-1
Severity: grave
Justification: renders package unusable
When mounting share samba hangs with the following message in log.smbd
Hangs? Or panics?
Please also provide the
On 9/19/06, Andreas Tille [EMAIL PROTECTED] wrote:
n Mon, 18 Sep 2006, David Starner wrote:
Package: findimagedupes
Version: 0.1.3-7
Just to let you know the status quo: There is a completely rewritten
verison of findimagedupes in preparation which does not show the
problem (and closes the
Processing commands for [EMAIL PROTECTED]:
severity 388282 important
Bug#388282: When trying to acces samba share from other computer PANIC appears
Severity set to `important' from `grave'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Processing commands for [EMAIL PROTECTED]:
severity 387798 grave
Bug#387798: libgutils1-dev: broken symlink (missing dep?)
Severity set to `grave' from `normal'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
Package: udev
Version: 0.100-1
Severity: serious
Justification: Policy 9.1
After upgrading to udev 0.100-1 and rebooting I noticed that the
isdnutils init script complained that /dev/MAKEDEV could not be found.
It looks like udev does not provide a MAKEDEV symlink anymore,
so /dev/MAKEDEV does
Your message dated Tue, 19 Sep 2006 20:56:57 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#346968: NMU patch for wmmount
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
Processing commands for [EMAIL PROTECTED]:
retitle 386478 Obsolete package: Etch will have only 2.6 kernels, 2.6 version
out of date
Bug#386478: kernel-patch-2.4-bluez: Obsolete package: Etch will have only 2.6
kernels
Changed Bug title.
severity 386478 grave
Bug#386478: Obsolete package:
retitle 385695 FTBFS on alpha: remove unused va_list
thanks
My previous patches were nonsense. This one fixes the issue.
Cheers,
--
.''`. Aurélien GÉRÔME
: :' :
`. `'` Free Software Developer
`- Unix Sys Net Admin
#! /bin/sh /usr/share/dpatch/dpatch-run
##
1 - 100 of 138 matches
Mail list logo
