Package: morse
Version: 2.1-1
Severity: serious
You're missing a build-depends on libx11-dev:
> Automatic build of morse_2.1-1 on bigsur by sbuild/mips 1.94
...
> The following NEW packages will be installed:
> debhelper file gettext html2text intltool-debian libmagic1 po-debconf
> 0 upgraded,
On 3/17/06, Eric Evans <[EMAIL PROTECTED]> wrote:
> When run with no arguments, ifplugd defaults to interface eth0.
Ah, I see. Of course.
> > Here are the non-commented contents of /etc/default/ifplugd:
> >
> > INTERFACES=""
> > HOTPLUG_INTERFACES="all"
> > ARGS="-q -f -u0 -d10 -w -I"
> > SUSPEND
Package: synfig
Version: 0.61.05-1
Severity: serious
synfig FTBFS on all architectures because of the following
build-dependency: libetl-dev | etl-dev
The buildds do not consider the alternative package. Since libetl-dev
does not (yet) exist, synfig cannot be built by the buildds.
A fix is bein
Hi,
This is about RC bug report on:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285198
I looked back bug situation on BTS. It seems we did funny dependency to
work around tetex version issue.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357036
But from PTS;
[2006-02-10] tetex-bin
Hi,
I am the recent NMU person of cjk-latex. I understand Anthony is around
but quite busy. I have not heard from him after I did NMU with just a
short notification. My last upload was also to fix RC bug which enabled
to get this package into Etch testing. Now it is in!
Since cjk-bin depends
On Fri, Mar 17, 2006 at 11:11:38PM +0200, Yavor Doganov wrote:
> Package: open.app
> Version: 0.1cvs20051128-1
> Severity: grave
> In an attempt to install the package the following error occurs:
> (Reading database ... 314494 files and directories currently installed.)
> Unpacking open.app (from
Processing commands for [EMAIL PROTECTED]:
> retitle 357368 FTBFS: missing build-depends on libxft-dev and libxinerama-dev
Bug#357368: FTBFS: missing build-depends on libxft-dev
Changed Bug title.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking s
retitle 357368 FTBFS: missing build-depends on libxft-dev and libxinerama-dev
thanks
* Teemu Ikonen <[EMAIL PROTECTED]> [2006-03-17 01:27]:
> > Are you sure? I'm fairly sure I tried a full compliation with
> > libxft-dev installed and it worked.
>
> Yes, with a freshly updated pbuilder sid chroo
Package: fcitx
Version: 3.1.1-1.1
Severity: grave
Justification: renders package unusable
After upgrading to 3.1.1-1.1, fcitx can be launched as usual. However after
pressing ctrl+space to activate Chinese input, fcitx exits when I press any
key with the following message:
FCITX -- Get Signal No.
Processing commands for [EMAIL PROTECTED]:
> severity 352811 important
Bug#352811: emacs21: Font problem - characters displayed as boxes
Severity set to `important'.
> tag 352811 unreproducible
Bug#352811: emacs21: Font problem - characters displayed as boxes
There were no tags set.
Tags added: u
On Tue, 04 Oct 2005, Mark Johnson wrote:
> 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.
severity 352811 important
tag 352811 unreproducible
thanks
I am unable to reproduce this with emacs21 21.4a-3.
Don Armstrong
--
"I was thinking seven figures," he said, "but I would have taken a
hundred grand. I'm not a greedy person." [All for a moldy bottle of
tropicana.]
-- Sammi Hadzovic
Your message dated Fri, 17 Mar 2006 16:02:12 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#346643: fixed in conky 1.4.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 your
Your message dated Fri, 17 Mar 2006 15:02:23 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#347109: fixed in stardict 2.4.5-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 Fri, 17 Mar 2006 14:47:42 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#350650: fixed in timps 0.25-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
Processing commands for [EMAIL PROTECTED]:
> tag 339845 + fixed
Bug#339845: ERROR: /bin/cp failed.
Tags were: moreinfo
Tags added: fixed
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
Your message dated Fri, 17 Mar 2006 14:32:53 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#356596: fixed in console-data 20060317
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
Processing commands for [EMAIL PROTECTED]:
> tag 316693 + fixed
Bug#316693: openswan_1/2.2.0-10
Tags were: l10n patch
Tags added: fixed
> tag 339390 + fixed
Bug#339390: openswan: [INTL:sv] Swedish debconf templates translation
Tags were: l10n patch
Tags added: fixed
> tag 352050 + fixed
Bug#3520
Processing commands for [EMAIL PROTECTED]:
> found 357526 3.2.9-22
Bug#357526: db3-doc: doc package is not DFSG-free
Bug marked as found in version 3.2.9-22.
> found 357526 3.2.9-23
Bug#357526: db3-doc: doc package is not DFSG-free
Bug marked as found in version 3.2.9-23.
> found 357527 2.1.19-1
Yavor Doganov wrote:
> Package: open.app
> Version: 0.1cvs20051128-1
> Severity: grave
>
> In an attempt to install the package the following error occurs:
>
> (Reading database ... 314494 files and directories currently installed.)
> Unpacking open.app (from .../open.app_0.1cvs20051128-1_i386.de
Can users of big-endian machines please verify this
with mhash 0.9.6, which has been released with
big-endian bugfixes applied. The problem may now be
fixed, but I want to be certain of that.
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best
Processing commands for [EMAIL PROTECTED]:
> reassign 357384 gsasl
Bug#357384: FTBFS: undefined reference to `gss_init_sec_context'
Bug#357223: libvmime: FTBFS: /usr/lib/libgsasl.so missing
Bug reassigned from package `gsasl' to `gsasl'.
>
End of message, stopping processing here.
Please contact
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.4
> merge 357384 357223
Bug#357223: libvmime: FTBFS: /usr/lib/libgsasl.so missing
Bug#357384: FTBFS: undefined reference to `gss_init_sec_context'
Merged 357223 357384.
>
End of message,
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.4
> close 357384 0.2.12-1
Bug#357384: FTBFS: undefined reference to `gss_init_sec_context'
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in v
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.4
> reassign 357384 gsasl
Bug#357384: FTBFS: undefined reference to `gss_init_sec_context'
Bug reassigned from package `msmtp' to `gsasl'.
>
End of message, stopping processing here.
Ple
Package: db4.2-doc
Version: 4.2.52-24
Severity: serious
Justification: Policy 2.1
docs/sleepycat/legal.html contains the following text:
"This product and publication is protected by copyright and distributed under
licenses restricting its use, copying and distribution. Permission to use this
p
Package: cyrus-sasl2
Severity: serious
Justification: Policy 2.1
The cyrus-sasl source package contains a dlcompat-20010505 subdirectory, whose
contents are licensed under the Apple Public Source License 1.1.
None of these files appear to be used during a build, so it should be safe
to just remov
Processing commands for [EMAIL PROTECTED]:
> reopen 354847
Bug#354847: FTBFS: 1.15.1-4 fails 2 tests on amd64
Bug reopened, originator not changed.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debi
severity 355097 important
thanks
On Thu, 02 Mar 2006 18:51:13 -0600
Robert Thompson <[EMAIL PROTECTED]> wrote:
> Package: uw-imapd
> Version: 7:2002edebian1-11sarge1
> Severity: grave
> Justification: causes non-serious data loss
I fail to understand how this can cause loss of data. Please clari
Package: tar
Version: 1.14-2
Followup-For: Bug #354847
Hi,
the buildd failed again for the same reason but different part. Some
of tars output goes to stderr and that is affected by the reordering
as well. The attached patch redirects that output to stdout and
thereby sorts that as well.
MfG
Hi Jesus,
I haven't heard anything back about this bug (#346322), which is a serious
security vulnerability affecting unstable and testing.
I've checked the latest upstream release (2.3.2) and compared it to 2.3.0
currently in Debian, and the following patch fixes this vulnerability and
another s
Package: db3-doc
Version: 3.2.9-23
Severity: serious
Justification: Policy 2.1
docs/sleepycat/legal.html contains the following text:
"This product and publication is protected by copyright and distributed under
licenses restricting its use, copying and distribution. Permission to use this
publ
Package: open.app
Version: 0.1cvs20051128-1
Severity: grave
In an attempt to install the package the following error occurs:
(Reading database ... 314494 files and directories currently installed.)
Unpacking open.app (from .../open.app_0.1cvs20051128-1_i386.deb) ...
Leaving `diversion of /usr/bin
Processing commands for [EMAIL PROTECTED]:
> found 357259 1.15.1-6
Bug#357259: tar: GFDL documentation with unmodifiable sections
Bug marked as found in version 1.15.1-6.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(admin
FWIW, This patch looks interesting, and looks like it might solve the
problem with the newer binutils. I still haven't figured out an easy
way to get a ia32 EFI machine up and running to test on (for some
reason, qemu hangs about 30sec after booting the EFI floppy image). But
it might be worth pa
On Fri, Mar 17, 2006 at 01:43:24PM -0700, Brett Johnson wrote:
> FWIW, This patch looks interesting, and looks like it might solve the
> problem with the newer binutils. I still haven't figured out an easy
> way to get a ia32 EFI machine up and running to test on (for some
> reason, qemu hangs abo
* Javier Fernández-Sanguino Peña <[EMAIL PROTECTED]> [2006-03-08 20:55]:
> Hi Arm porters, I received a Cron bug report recently (#355878) . It
> seems that the build of the latest cron release in arm didn't
> include the init.d script (as shown in the package files listed in
> [1]), however, previ
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.15
> # Already uploaded, but in NEW queue
> tags 343805 pending
Bug#343805: Please upgrade build depends to libmysqlclient15-dev
Tags were: patch
Tags added: pending
>
End of message, st
On Fri, Mar 17, 2006 at 06:52:39PM +0100, Steinar H. Gunderson wrote:
> On Fri, Mar 17, 2006 at 05:31:01PM +, Martin Michlmayr wrote:
> > reopen 356302
> > thanks
> > Sorry, Steinar, but your fix didn't work.
> Hm, that's odd; it did here (but I'm not using mips). How can this be?
> Settin
Hi,
I solved RC bugs against VBA, and I maybe this bug was solved.
Please try to compile VBA again.
Regards
Jose Carlos
Your message dated Fri, 17 Mar 2006 10:32:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#357259: fixed in tar 1.15.1-6
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 Fri, 17 Mar 2006 18:18:26 +
with message-id <[EMAIL PROTECTED]>
and subject line fixed
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 the
Your message dated Fri, 17 Mar 2006 10:17:35 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#350036: fixed in polyglot 1.4-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 you
reopen 356302
thanks
Sorry, Steinar, but your fix didn't work.
> Automatic build of thrust_0.89c-3.3 on bigsur by sbuild/mips 1.94
...
> thrust_0.89c-3.3_mips.changes:
> Format: 1.7
> Date: Sat, 11 Mar 2006 03:39:02 +0100
> Source: thrust
> Binary: thrust
> Architecture: mips
> Version: 0.89c-3.3
* Steinar H. Gunderson <[EMAIL PROTECTED]> [2006-03-17 18:52]:
> > Sorry, Steinar, but your fix didn't work.
> Hm, that's odd; it did here (but I'm not using mips). How can this be?
I don't know, but look at
http://buildd.debian.org/build.php?arch=&pkg=thrust and you'll see
that it fails on all ar
On Fri, 17, Mar, 2006 at 05:36:25PM +, Mark Hymers spoke thus..
> As Steve said, this is a bug in liblo0 which has been fixed in 0.23-1.
> I think the control commands should deal with it properly...
For the record, I of course meant 0.23-2.
Mark
--
Mark Hymers <[EMAIL PROTECTED]>
"I've ha
On Fri, Mar 17, 2006 at 05:31:01PM +, Martin Michlmayr wrote:
> reopen 356302
> thanks
>
> Sorry, Steinar, but your fix didn't work.
Hm, that's odd; it did here (but I'm not using mips). How can this be?
Setting up libxext-dev (6.9.0.dfsg.1-4) ...
(...)
checking for X... no
checking
tags 357456 confirmed pending
stop
Julien Danjou wrote:
> The postinst script of alsa-utils is not writtent correctly:
You're right---thanks for the report. Fixed in svn.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PRO
Processing commands for [EMAIL PROTECTED]:
> severity 357183 serious
Bug#357183: FTBFS: doesn't build the binary
Severity set to `serious'.
> reassign 357183 liblo0-dev 0.23-1
Bug#357183: FTBFS: doesn't build the binary
Bug reassigned from package `dssi' to `liblo0-dev'.
> close 357183 0.23-2
Bu
severity 357183 serious
reassign 357183 liblo0-dev 0.23-1
close 357183 0.23-2
thanks
As Steve said, this is a bug in liblo0 which has been fixed in 0.23-1.
I think the control commands should deal with it properly...
Mark
--
Mark Hymers <[EMAIL PROTECTED]>
"The older I grow, the more I distrus
Your message dated Fri, 17 Mar 2006 08:48:42 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#355775: fixed in multipath-tools 0.4.7-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 i
Your message dated Fri, 17 Mar 2006 08:48:42 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#337081: fixed in multipath-tools 0.4.7-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 i
Hi
I do not experience any problems with the
0.8.4.debian-2+b1 version of this program on debian
unstable.
Could this bug be closed?
regards
Tibor
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: shfs-source
Version: 0.35-5
Followup-For: Bug #342522
I experienced this bug at least with 2.6.14, 2.6.15.1 and 2.6.15.6.
The system issues an OOPS some time after a mount. Apparently, multiple
processes accessing the remote fs at the same time seem to stimulate the
problem.
After the
Your message dated Fri, 17 Mar 2006 07:54:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#347632: fixed in libchipcard2 1.9.19.99+1.9.20beta-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 t
Your message dated Fri, 17 Mar 2006 07:54:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#347632: fixed in libchipcard2 1.9.19.99+1.9.20beta-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 t
Your message dated Fri, 17 Mar 2006 07:54:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#347632: fixed in libchipcard2 1.9.19.99+1.9.20beta-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 t
Processing commands for [EMAIL PROTECTED]:
> tags 357456 confirmed pending
Bug#357456: error in postinst script
Tags were: patch
Tags added: confirmed, pending
> stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Deb
Processing commands for [EMAIL PROTECTED]:
> tags #357194 + confirmed
Bug#357194: the sync is broken after I upgrade to latest in sid(not sure if it
is svn lib or svk)
There were no tags set.
Tags added: confirmed
> block #357194 by #356894
Bug#357194: the sync is broken after I upgrade to lates
tags #357194 + confirmed
block #357194 by #356894
stop
Hi,
On Thu, Mar 16, 2006, [EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED]:~$ for i in `svk list //mirror`; do svk sync
> //mirror/$i; done
(I used to do that, I now use svk sync -a)
> Retrieving log information from 1008 to 1009
> Typ
Your message dated Fri, 17 Mar 2006 16:17:30 +0100
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #357259,
regarding tar: GFDL documentation with unmodifiable sections
to be marked as having been forwarded to the upstream software
author(s) [EMAIL PROTECTED]
(NB: If you are a
On Fri, Mar 17, 2006 at 02:44:44PM +0100, Giuseppe Sacco wrote:
> Right, but where did you use it? testing or unstable? I would like to
> get the same environmnet you have in order to reproduce the error.
/etc/init.d/hylafax fails if /etc/hylafax/setup.cache don't exist.
Bastian
--
Beam me up,
Your message dated Fri, 17 Mar 2006 17:01:08 +0200
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 t
Your message dated Fri, 17 Mar 2006 07:17:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#354847: fixed in tar 1.15.1-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
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.15
> tags 357392 patch
Bug#357392: beagle: Security issue - shell script checks "."
Tags were: security
Tags added: patch
>
End of message, stopping processing here.
Please contact me if
Hi,
It took me some time to realize this program was killing my resolv.conf
symlink :-)
I think until named-manager/nm-named-manager.c is updated to check
existance of /sbin/resolvconf and start using it, this package should
put conflict with resolvconf.
Nontheless, I wish this will be updated
Your message dated Fri, 17 Mar 2006 06:33:47 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#347332: fixed in mozilla-stumbleupon 2.6-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
Processing commands for [EMAIL PROTECTED]:
> merge 357457 356984 357024 357067 357159 357160 357290
Bug#356984: openoffice.org-gcj: Uninstallable because of missing gcj symlink
Bug#357024: openoffice.org-gcj: post-installation script fails
Bug#357067: openoffice.org-gcj: installation problems: gcj
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.15
> tags 356177 patch
Bug#356177: FTBFS: ./configure: line 2778: syntax error near unexpected token
`('
Tags were: patch
Tags added: patch
>
End of message, stopping processing here.
P
merge 357457 356984 357024 357067 357159 357160 357290
thanks
Hi,
Am Freitag 17 März 2006 15:01 schrieb Max Gilead:
> Post-installation breaks with this error message:
> Setting up openoffice.org-gcj (2.0.2-1) ...
> /var/lib/dpkg/info/openoffice.org-gcj.postinst: line 7:
> /usr/lib/jvm/java-gcj/b
On Fri, Mar 17, 2006 at 02:33:50PM +0100, Thomas Kulessa wrote:
> Package: reppu
> Version: 0.1-3
> Severity: grave
> Justification: renders package unusable
>
> I started a reppu on the local machine. The client successfully connects
> to the server, but the server fails to render with the messa
Matt Kraai <[EMAIL PROTECTED]> writes:
> On Fri, Mar 17, 2006 at 09:47:35AM +0100, Falk Hueffner wrote:
>> Matt Kraai <[EMAIL PROTECTED]> writes:
>>
>> > The attached patch adds build-dependencies on libxt-dev and
>> > libxpm-dev, which fixes the build.
>>
>> Actually, both of them shouldn't act
Package: irmp3
Version: 0.5.7pre2-1
Severity: serious
Your package fails to build in unstable. (A number of other packages
had similar problems; I can point you to bug reports if you want to
find out how they fixed it.)
> Automatic build of irmp3_0.5.7pre2-1 on bigsur by sbuild/mips 1.94
...
>
Package: openoffice.org-gcj
Version: 2.0.2-1
Severity: grave
Justification: renders package unusable
Post-installation breaks with this error message:
Setting up openoffice.org-gcj (2.0.2-1) ...
/var/lib/dpkg/info/openoffice.org-gcj.postinst: line 7:
/usr/lib/jvm/java-gcj/bin/gcj: No such file o
Bastian Blank ha scritto:
On Fri, Mar 17, 2006 at 12:46:21PM +0100, Giuseppe Sacco wrote:
Are you working on testing or unstable?
According to the db of ftp-master, both have the same version.
Right, but where did you use it? testing or unstable? I would like to
get the same environmnet y
Package: alsa-utils
Version: 1.0.10-1
Severity: serious
Tags: patch
Hello,
The postinst script of alsa-utils is not writtent correctly:
% sh postinst abort-upgrade "1"; echo $?
postinst called with unknown argument `abort-upgrade'
1
According to chapter 6 of Debian policy, it should exit with a
Your message dated Fri, 17 Mar 2006 05:17:11 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#353432: fixed in partman-base 79
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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#344347: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
I also had this problem, despite my statically assigned ip addresses,
and thought my static address had been replaced.
Though, Anand is right, I was using:
$ ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:D0:B7:17:9A:8F
inet addr:169.254.116.34 Bcast:0.0.0.0 Mask:255.255.0.0
t
Package: reppu
Version: 0.1-3
Severity: grave
Justification: renders package unusable
I started a reppu on the local machine. The client successfully connects
to the server, but the server fails to render with the message
"Executing blender failed".
-- System Information:
Debian Release: 3.1
Ar
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#352033: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#352033: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#352033: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#352033: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#352033: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#352033: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#352033: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349359: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349359: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349359: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349359: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349359: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349359: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#349359: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#348710: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#348710: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#348710: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#348710: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#348710: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
Your message dated Fri, 17 Mar 2006 05:07:08 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#348710: fixed in mozilla-firefox-locale-all
1.5.0.1lang20060301-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
1 - 100 of 162 matches
Mail list logo
