Processing commands for [EMAIL PROTECTED]:
> retitle 318719 tecnoballz: Segfaults on startup on 64-bit machines
Bug#318719: tecnoballz: Segfaults on startup
Changed Bug title.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system admini
tag 367872 patch
thanks
Hello, Daniel!
The bfd_hash_table_init function now expects an additional entsize
argument for the hash entry size. This doesn't seem to be documented
yet, but you can check the way it's used in src/bfd in the binutils
source. The following patch allows lush to compile c
Processing commands for [EMAIL PROTECTED]:
> tag 367872 patch
Bug#367872: FTBFS: too few arguments to function 'bfd_hash_table_init'
There were no tags set.
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(a
Processing commands for [EMAIL PROTECTED]:
> tag 209496 + fixed
Bug#209496: The package description does not follow Debian policy
There were no tags set.
Tags added: fixed
> tag 217266 + fixed
Bug#217266: Incorrect regex in fte startup script
Tags were: patch
Tags added: fixed
> tag 346284 + fix
Package: postgresql
Version: 7.4.7-6sarge2
Severity: grave
Justification: renders package unusable
Hi Matt,
I've just done a security upgrade and bumped into this:
Setting up postgresql (7.4.7-6sarge2) ...
pg_hba.conf contains a field after the authentication specification;
the file is corrupt
Hello,
I'm doing an NMU of fte to fix #209496, #217266, #346284, #362912,
#363527, and #368101; diff attached.
Thanks,
Matej
diff -Nru /tmp/wgHyQebD7F/fte-0.50.0/debian/changelog
/tmp/PQJo4szkUb/fte-0.50.0/debian/changelog
--- /tmp/wgHyQebD7F/fte-0.50.0/debian/changelog 2006-01-07 00:16:55.
Processing commands for [EMAIL PROTECTED]:
> tag 366456 + fixed
Bug#366456: polgen-doc: missing /usr/share/polgen/src fobids polgen-doc from
being installed
There were no tags set.
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
Processing commands for [EMAIL PROTECTED]:
> # Makes fte-xwindow uninstallable with X11R7.
> severity 362912 grave
Bug#362912: fte-xwindow: please follow xorg migration
Severity set to `grave' from `normal'
>
End of message, stopping processing here.
Please contact me if you need assistance.
De
Processing commands for [EMAIL PROTECTED]:
> package fte-terminal
Ignoring bugs not assigned to: fte-terminal
> severity 346284 grave
Bug#346284: fte-terminal segfaults at startup
Severity set to `grave' from `normal'
> merge 346284 368101
Bug#346284: fte-terminal segfaults at startup
Bug#368101
Pierre Habouzit wrote:
> what is the point of not supporting tail +n syntax, does it breaks
> anything ?
A conforming POSIX 1003.1-2001 implementation is supposed to treat
arguments with a leading "+" as a file name, not as an option. Some
people do actually start file names with a "+" sign. (O
Your message dated Sun, 04 Jun 2006 21:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#338833: fixed in bison 1:2.2.dfsg-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
close 370403
thanks
> At Sun, 04 Jun 2006 21:38:57 -0500,
> > The newest cupsys update breaks all of KDE Printing subsystem in all
> > versions of 3.x. This is because KDE uses private interfaces which
> > existed in version 1.1.x; those interfaces have been remove in CUPS
> > 1.2.1. Upstream has
Hello,
I'm doing an NMU of polgen-doc-non-dfsg to fix #366456; diff attached.
Thanks,
Matej
diff -u polgen-doc-non-dfsg-1.3/debian/changelog
polgen-doc-non-dfsg-1.3/debian/changelog
--- polgen-doc-non-dfsg-1.3/debian/changelog
+++ polgen-doc-non-dfsg-1.3/debian/changelog
@@ -1,3 +1,13 @@
+polge
Your message dated Sun, 04 Jun 2006 20:47:33 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#367882: fixed in skim 1.4.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
Processing commands for [EMAIL PROTECTED]:
> close 370403
Bug#370403: cupsys breaks all of KDE printing
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug closed, send any further explanations to Jason Clinton <[EMAIL PROTECTED]>
> thanks
Stopping processing here.
Pleas
Processing commands for [EMAIL PROTECTED]:
> reassign 370403 kdeprint
Bug#370403: cupsys breaks all of KDE printing
Bug reassigned from package `cupsys' to `kdeprint'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administ
reassign 370403 kdeprint
thanks
At Sun, 04 Jun 2006 21:38:57 -0500,
Jason Clinton wrote:
> Package: cupsys
> Version: 1.2.1-1
> Severity: grave
> Justification: renders package unusable
>
> The newest cupsys update breaks all of KDE Printing subsystem in all
> versions of 3.x. This is because KDE
On Sun, Jun 04, 2006 at 08:16:24AM -0700, Walter Landry wrote:
> Package: sun-java5-jre
> Version: 1.5.0-06-1
> Severity: serious
> In the Distributor License for Java, there is the clause
> (c) you do not combine, configure or distribute the Software to
> run in conjunction with any addi
Package: cupsys
Version: 1.2.1-1
Severity: grave
Justification: renders package unusable
The newest cupsys update breaks all of KDE Printing subsystem in all
versions of 3.x. This is because KDE uses private interfaces which
existed in version 1.1.x; those interfaces have been remove in CUPS
1.2.
--On Sunday, June 04, 2006 7:36 PM -0700 Steve Langasek <[EMAIL PROTECTED]>
wrote:
On Sun, Jun 04, 2006 at 07:28:14PM -0700, Quanah Gibson-Mount wrote:
> On Mon, Jun 05, 2006 at 12:42:57AM +0200, Steinar H. Gunderson wrote:
>> OK, the problem doesn't show up at -O0, which supports the theo
On Sun, Jun 04, 2006 at 07:28:14PM -0700, Quanah Gibson-Mount wrote:
> >On Mon, Jun 05, 2006 at 12:42:57AM +0200, Steinar H. Gunderson wrote:
> >>OK, the problem doesn't show up at -O0, which supports the theory that
> >>it's some kind of overflow issue. I'm starting a build with -O2 now --
> >>pe
On Sun, Jun 04, 2006 at 04:47:31PM +0200, Matthias Klose wrote:
> Falk Hueffner writes:
> > Steve Langasek <[EMAIL PROTECTED]> writes:
> > > Hi Matthias,
> > >> works for me.
> > > Have you tried building it with prctl --unaligned=signal? This is not
> > > the default on hppa, but it's used on
Your message dated Mon, 05 Jun 2006 11:04:37 +0900
with message-id <[EMAIL PROTECTED]>
and subject line CUPS 1.2.1 is uploaded into unstable, so it fixes
fixed-in-experimental bugs and some others
has caused the attached Bug report to be marked as done.
This means that you claim that the problem
--On Monday, June 05, 2006 1:58 AM +0200 "Steinar H. Gunderson"
<[EMAIL PROTECTED]> wrote:
On Mon, Jun 05, 2006 at 12:42:57AM +0200, Steinar H. Gunderson wrote:
OK, the problem doesn't show up at -O0, which supports the theory that
it's some kind of overflow issue. I'm starting a build with
Your message dated Mon, 05 Jun 2006 11:04:37 +0900
with message-id <[EMAIL PROTECTED]>
and subject line CUPS 1.2.1 is uploaded into unstable, so it fixes
fixed-in-experimental bugs and some others
has caused the attached Bug report to be marked as done.
This means that you claim that the problem
Your message dated Mon, 05 Jun 2006 11:04:37 +0900
with message-id <[EMAIL PROTECTED]>
and subject line CUPS 1.2.1 is uploaded into unstable, so it fixes
fixed-in-experimental bugs and some others
has caused the attached Bug report to be marked as done.
This means that you claim that the problem
Your message dated Mon, 05 Jun 2006 11:04:37 +0900
with message-id <[EMAIL PROTECTED]>
and subject line CUPS 1.2.1 is uploaded into unstable, so it fixes
fixed-in-experimental bugs and some others
has caused the attached Bug report to be marked as done.
This means that you claim that the problem
On Sun, Jun 04, 2006 at 02:56:07AM -0700, Walter Landry wrote:
> Package: sun-java5-jre
> Version: 1.5.0-06-1
> Severity: serious
> In the copyright file there is the phrase
> Export or reexport to countries subject to U.S. embargo or to
> entities identified on U.S. export exclusion lists, i
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> # ack this
> close 369959 2.1.2-1.1
Bug#369959: amule-utils: missing Replaces: amule-common (<< 2.1.2-1)
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug
Your message dated Sun, 04 Jun 2006 17:17:37 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370068: fixed in amule 2.1.2-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 Sun, 04 Jun 2006 17:17:37 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369995: fixed in amule 2.1.2-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
reassign 370138 libprintsys
thanks
On Sat, Jun 03, 2006 at 11:47:38AM -0400, Daniel Schepler wrote:
> ...
> /bin/sh ../libtool --tag=CXX --mode=link g++-4.0 -g -O2 -L/usr/lib -lglib
> -o libprinterconf.la -rpath /usr/lib -version-info 2:0:0 printerconf.lo
> snmpinter.lo parport.lo -lprintsys
Processing commands for [EMAIL PROTECTED]:
> reassign 370138 libprintsys
Bug#370138: libprinterconf: FTBFS: Cannot find /usr/lib/libglib2.0.la
Bug reassigned from package `libprinterconf' to `libprintsys'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug t
Your message dated Mon, 05 Jun 2006 09:39:33 +0900
with message-id <[EMAIL PROTECTED]>
and subject line #343682: cupsys: dummy bug to block current cupsys goes testing
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 i
On Mon, Jun 05, 2006 at 12:42:57AM +0200, Steinar H. Gunderson wrote:
> OK, the problem doesn't show up at -O0, which supports the theory that it's
> some kind of overflow issue. I'm starting a build with -O2 now -- perhaps it
> can be caught using valgrind on a slightly faster platform, though...
Your message dated Sun, 04 Jun 2006 16:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370231: fixed in gnokii 0.6.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 yo
* Julien Delange [Sat, 03 Jun 2006 18:33:07 +0200]:
> I don't want you teach me anithing. I juste want somebody who can help
> me when I have no time to maintain it and resolve bugs :-) So, if you
> can, great !
Okay. Then I'll take care of amule maintenance starting today, and we'll
get back to
Hello,
On Fri, Jun 02, 2006 at 01:54:31PM -0400, Aaron M. Ucko wrote:
> Package: libcamomile-ocaml-dev
> Version: 0.6.3-3+b1
> Severity: grave
> Justification: renders package unusable (uninstallable)
>
> libcamomile-ocaml-dev's debian/control entry specifies a strict
> dependency on libcamomile-
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> block 311188 with 370319 370324 370332 370337 370338 370339 370340 370342
> 370343 370344 370346 370347 370348 370349 370350 370351 370393
Bug#311188: debian-edu-config: Messes "prog
Hello,
On Thu, Jun 01, 2006 at 09:45:05AM +0200, Bastian Blank wrote:
> Package: mldonkey
> Version: 2.7.3-2+b1
> Severity: serious
>
> There was an error while trying to autobuild your package:
>
> > Automatic build of mldonkey_2.7.3-2+b1 on debian01 by sbuild/s390 85
> [...]
> > ** Using build
Package: graveman
Version: 0.3.12-4-2.1
Followup-For: Bug #364736
I also experience crashes when first starting the application (when it
searches for new devices). The above mentioned
G_SLICE=always-malloc graveman
does the trick. On subsequent invocations (when graveman has already
"found" my
On Sun, 4 Jun 2006, Javier Fern?ndez-Sanguino Pe?a wrote:
It looks like there is no libmysqclient-dev that Snort-mysql could use. It
seems reasonable, however, as the different versions probably provide
incompatible APIs.
Hm, the build-depends of the original snort_2.3.3-6 package say:
libmysq
Steve Langasek wrote:
> Sorry, but how in the world does this address a bug report that claims the
> *gtkhtml* backend is broken?
While working with 1.0.12 I apparently, closed the bug accidently.
Thanks for reopening.
--
David Moreno Garza <[EMAIL PROTECTED]> | http://www.damog.net/
Your message dated Sun, 04 Jun 2006 15:47:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370130: fixed in manpages-fr 2.31.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 n
Your message dated Sun, 04 Jun 2006 15:17:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#351711: fixed in python-kde3 3.15.2+20060422-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 cas
On Sun, Jun 04, 2006 at 10:19:44PM +0200, Steinar H. Gunderson wrote:
> I'm currently compiling a noopt/nostrip-version, but at 133MHz ARM it's going
> to take a while.
OK, the problem doesn't show up at -O0, which supports the theory that it's
some kind of overflow issue. I'm starting a build wit
Your message dated Sun, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370157: fixed in dpkg 1.13.21
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, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370210: fixed in dpkg 1.13.21
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, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369958: fixed in dpkg 1.13.21
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, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370157: fixed in dpkg 1.13.21
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, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369928: fixed in dpkg 1.13.21
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, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369928: fixed in dpkg 1.13.21
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, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369958: fixed in dpkg 1.13.21
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, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369928: fixed in dpkg 1.13.21
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, 04 Jun 2006 14:40:29 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370263: fixed in update-manager 0.42.2ubuntu22-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 c
Your message dated Sun, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370210: fixed in dpkg 1.13.21
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, 04 Jun 2006 14:37:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362217: fixed in lirc 0.8.0-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
Processing commands for [EMAIL PROTECTED]:
> severity 352197 important
Bug#352197: eclipse: locally installed plugins vanished
Severity set to `important' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administ
Your message dated Sun, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370157: fixed in dpkg 1.13.21
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
severity 357301 normal
thanks
the justification given (renders package unusable) is
wrong. the bug submitter uses a runtime not included in Debian. the
package works fine using java-gcj-compat or sun-java5-bin.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troub
Your message dated Sun, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369958: fixed in dpkg 1.13.21
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, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369958: fixed in dpkg 1.13.21
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]:
> severity 355104 normal
Bug#355104: eclipse: doesn't start
Severity set to `normal' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database
severity 352197 important
thanks
the justification given (causes non-serious data loss) is
wrong. there's no "data loss", and the extensions are still available,
but not accessible. upgrade problem only.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Con
Your message dated Sun, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369928: fixed in dpkg 1.13.21
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
- Forwarded message from Andrew Maier <[EMAIL PROTECTED]> -
From: Andrew Maier <[EMAIL PROTECTED]>
To: Duncan Findlay <[EMAIL PROTECTED]>
Subject: Re: Bug#370357: after upgrade, spamassassin give every mail a score of
0 (and thus autolearns the mail as ham)
On Sun, Jun 04, 2006 at 03:59:
Your message dated Sun, 04 Jun 2006 14:35:39 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370250: fixed in gst0.10-python 0.10.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 i
Olivier Berger wrote:
> As a workaround, one may install :
> http://releases.mozilla.org/pub/mozilla.org/firefox/releases/1.5.0.3/linux-i686/xpi/fr.xpi
> or the likes...
I'll be uploading mozilla-firefox-locale-all 1.5.0.3-1 tonight.
--
David Moreno Garza <[EMAIL PROTECTED]> | http://www.dam
severity 355104 normal
thanks
the justification given (renders package unusable) is
wrong. the bug submitter uses a runtime not included in Debian. the
package works fine using java-gcj-compat or sun-java5-bin.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Troub
Your message dated Sun, 04 Jun 2006 14:37:22 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370236: fixed in mod-mime-xattr 0.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 n
Your message dated Sun, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370210: fixed in dpkg 1.13.21
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, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370157: fixed in dpkg 1.13.21
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, 04 Jun 2006 14:34:56 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370210: fixed in dpkg 1.13.21
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]:
> severity 357301 normal
Bug#357301: eclipse randomly crashes, usually at startup
Severity set to `normal' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator
Your message dated Sun, 04 Jun 2006 14:38:14 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#367833: fixed in numlockx 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 it is now you
Processing commands for [EMAIL PROTECTED]:
> tag 316883 + fixed
Bug#316883: lvm2: creates device nodes as root:root 600, breaking amanda
There were no tags set.
Bug#329409: group and perms wrong in /dev/mapper
Bug#341901: udev: Ownership and permissions incorrect for device-mapper devices
and dir
Processing commands for [EMAIL PROTECTED]:
> tag 322317 + fixed
Bug#322317: INTL:vi Vietnamese translation for towitoko_2.0.7-4
Tags were: l10n patch
Tags added: fixed
> tag 330945 + fixed
Bug#330945: towitoko: [INTL:sv] Swedish debconf templates translation
Tags were: l10n patch
Tags added: fixe
ll newly installed packages:
> Source-dependencies not satisfied; skipping gtkballs
> **
> Finished at 20060604-0034
> Build needed 00:00:00, 0k disk space
bastian
--
A father doesn't destroy his ch
As more direct examples than Jython:
gjdoc implements javadoc. If a user installs a
non-natively-gcj-compiled gjdoc and the Sun Java packages, and then runs
gjdoc, it will run gjdoc with the Sun Java packages. That looks very
much like a violation of DLJ clause 2 (c).
jikes-sun implements a jav
Your message dated Sun, 04 Jun 2006 14:34:42 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368202: fixed in dia 0.95.0-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
Package: xcolors
Version: 1.5a-3
Severity: serious
This package needs to be updated for new X.
> Automatic build of xcolors_1.5a-3 on swarm by sbuild/mipsel 0.45
...
> + mkdir -p debian/xcolors/usr/share/man/man1
> install -c -m 0444 xcolors._man debian/xcolors/usr/share/man/man1/xcolors.1x
> in
Your message dated Sun, 04 Jun 2006 14:40:35 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362296: fixed in x-ttcidfont-conf 23
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
Your message dated Sun, 4 Jun 2006 14:06:44 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370284: guitar: Conflicts with x11-common about
/usr/X11R6/bin
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Package: cryptonit
Version: 0.9.6c-3
Severity: serious
> Automatic build of cryptonit_0.9.6c-3 on hulk by sbuild/alpha 0.45
...
> checking how to hardcode library paths into programs... immediate
> appending configuration tag "F77" to libtool
> ./configure: line 21082: syntax error near unexpected
Package: dokuwiki
Severity: critical
I just got this notice via freshmeat. Arbitrary code execution,
remotely exploitable. No assigned CVE number, yet.
Cheers,
-Hilko
Start of forwarded message
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: [
Your message dated Sun, 04 Jun 2006 13:36:50 -0700
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #351693,
regarding guile-1.6 FTBFS on ia64
to be marked as having been forwarded to the upstream software
author(s) [EMAIL PROTECTED]
(NB: If you are a system administrator and h
Package: skippy
Version: 0.5.1rc1-4
Severity: grave
Justification: renders package unusable
Whenever the Skippy hotkey is pressed, it dies with the "keybinding
conflict" error message ("Skippy could not grab the specified keysym and
will die now..."). However, this does not appear to be a keybindi
On Sun, Jun 04, 2006 at 01:17:51PM -0700, Quanah Gibson-Mount wrote:
> Is it possible to reproduce in 2.3.24? Or just the rather old 2.2.x
> version?
2.3.24.
I'm currently compiling a noopt/nostrip-version, but at 133MHz ARM it's going
to take a while.
/* Steinar */
--
Homepage: http://www.se
I could say that I think you're seriously underestimating the problem
here, but you probably think I'm seriously overestimating it, and
we're not going to get anywhere playing is-not, is-so games.
Instead, I'll ask again: What do you see as the advantage of removing
support for these older comman
On Sun, Jun 04, 2006 at 09:24:41PM +0200, Andrew Maier wrote:
> I just upgraded spamassasin, and since then have been flooed with spam.
> It appears that all mail is classified with a spam score of 0. Event
> worse, it then autolearns the mail as ham
Looks like SpamAssassin can't find your rules f
Package: valgrind
Version: 1:3.1.1-1
Severity: grave
I had the previous version of valgrind working fine. That version doesn't
seem to be available anymore. It may be that valgrind is incompatible
with the latest C library, which was probably upgraded at the same time.
The package is obviously "u
Hi,
It looks like problem on sbuild side - missing support
for architecture wildcards - in dpkg since 1.13.12.
Temporary workaround might be to use
libbluetooth1-dev [!hurd-i386 !kfreebsd-i386 !kfreebsd-amd64].
Petr
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe"
--On Sunday, June 04, 2006 9:15 PM +0200 "Steinar H. Gunderson"
<[EMAIL PROTECTED]> wrote:
On Sun, Jun 04, 2006 at 08:43:47PM +0200, Steinar H. Gunderson wrote:
I'm completely unable to reproduce this.
Scrap that; I can reproduce it now. I just didn't see that slapd
segfaulted... Debuggin
Hi.
As a workaround, one may install :
http://releases.mozilla.org/pub/mozilla.org/firefox/releases/1.5.0.3/linux-i686/xpi/fr.xpi
or the likes...
Best regards,
--
Olivier BERGER <[EMAIL PROTECTED]>
Ingénieur Recherche - Dept INF
INT Evry (http://www.int-evry.fr)
OpenPGP-Id: 1024D/6B829EEC
tags 370257 moreinfo
thanks
On Sun, 04 Jun 2006 14:34:27 +0300
Juha Jäykkä <[EMAIL PROTECTED]> wrote:
> Package: sylpheed-claws-gtk2
> Version: 2.2.0-1
> Severity: serious
> Justification: Policy 10.7.5 and possibly 9.1.1
>
>
> Under certain circumstances, sylpheed-claws-gtk2 stores its "dotfil
Processing commands for [EMAIL PROTECTED]:
> tags 370257 moreinfo
Bug#370257: sylpheed-claws-gtk2 does not obey $HOME
There were no tags set.
Tags added: moreinfo
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator
Package: spamassassin
Version: 3.1.1-1
Severity: grave
Justification: renders package unusable
Hello,
I just upgraded spamassasin, and since then have been flooed with spam.
It appears that all mail is classified with a spam score of 0. Event
worse, it then autolearns the mail as ham
I have app
severity 370257 important
thanks
On Sun, Jun 04, 2006 at 02:34:27PM +0300, Juha Jäykkä wrote:
> Version: 2.2.0-1
> Severity: serious
> Justification: Policy 10.7.5 and possibly 9.1.1
> Under certain circumstances, sylpheed-claws-gtk2 stores its "dotfiles"
> outside of $HOME. The Debian Policy d
Processing commands for [EMAIL PROTECTED]:
> severity 370257 important
Bug#370257: sylpheed-claws-gtk2 does not obey $HOME
Severity set to `important' from `serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administra
severity 370308 important
tags 370308 + pending
thanks
not yet the default compiler.
Martin Michlmayr writes:
> Source: gcc-4.1
> Version: 4.1.1-1
> Severity: grave
>
> After 4.1.1 was released, an error check was fixed in SVN that, as a
> side effect, rejects valid code. This breaks lots of pa
1 - 100 of 220 matches
Mail list logo
