Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> found 369479 0.062-3
Bug#369479: [BSP] implement debconf for the udev kernel-related upgrade
procedure.
Bug marked as found in version 0.062-3.
> notfound 369479 0.092-2
Bug#369479:
severity 369299 serious
severity 369478 serious
close 369478 1.0.11-7
merge 369478 369299
thanks
I believe this is a duplicate of #369299.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
> severity 369299 serious
Bug#369299: libasound2: pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default
Bug#369302: ALSA lib control.c:816:(snd_ctl_open_noupdate) Invalid CTL default
Bug#369309: libasound2: alsa fails to configure, mixer doesn't work, et
On Sun, 2006-05-28 at 22:11 +0100, Steve Kemp wrote:
> Uploaded.
Thanks! But... can't find the upload anywhere? Maybe something went
wrong or am I looking the wrong way?
Thijs
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, May 30, 2006 at 03:50:41AM -0400, Michael Furr wrote:
>
> On Tue, 30 May 2006, Sven Luther wrote:
> > reassign 369448 mkvmlinuz
> > thanks
> Um, methinks you missed a CC to [EMAIL PROTECTED]
Nope, i always bcc control, so people don't resend stuff to it when they
'g'-reply.
> > You are o
On Tue, 30 May 2006, Sven Luther wrote:
> reassign 369448 mkvmlinuz
> thanks
Um, methinks you missed a CC to [EMAIL PROTECTED]
> You are on a powermac system, and as thus, you should have goten the default
> reply of yaboot to the mkvmlinuz question. Please do a :
>
> dpkg-reconfigure mkvmlinuz
On Sun, May 28, 2006 at 11:17:03PM +0200, Adeodato Simó wrote:
> tag 362296 patch
> thanks
> * Steve Langasek [Sun, 21 May 2006 12:05:35 -0500]:
> > On Sun, May 21, 2006 at 07:37:50AM -0700, Ian Zimmerman wrote:
> > > With the fix by David Nusinow, systems that have not transitioned are
> > > br
ld-deb/build-stamp] Error 1
> **
> Build finished at 20060530-0258
> FAILED [dpkg-buildpackage died]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
rectory `/build/buildd/glibc-2.3.6/build-tree/s390-udeb'
> make: *** [/build/buildd/glibc-2.3.6/stamp-dir/build_udeb] Error 2
> **
> Build finished at 20060530-0803
> FAILED [dpkg-buildpackage died]
Bastian
Package: guile-1.6
Version: 1.6.8-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of guile-1.6_1.6.8-1 on debian01 by sbuild/s390 85
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: libtool, debhelper (>= 4), libncurses5-de
hi,
> (python:1695): Gdk-CRITICAL **: gdk_draw_drawable: assertion `src != NULL'
> failed "
> and it looks like it has entered into an infinite loop.
> No spe window appears.
> It looks like one missing dependency.
I cant reproduce this behavior. Although getting the same error, spe
starts and
severity 369478 important
merge 369299 369478
stop
On Tue, 30 May 2006 the mental interface of
Anders K. Madsen told:
> Package: libasound2
> Version: 1.0.11-6
> Severity: critical
>
> After upgrading to 1.0.11-6 everything having to do with sound started
> failing
> hard. E.g. alsamixer:
Pl
Processing commands for [EMAIL PROTECTED]:
> severity 369299 important
Bug#369299: libasound2: pcm.c:2146:(snd_pcm_open_noupdate) Unknown PCM default
Bug#369302: ALSA lib control.c:816:(snd_ctl_open_noupdate) Invalid CTL default
Bug#369309: libasound2: alsa fails to configure, mixer doesn't work,
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> merge 359861 359863
Bug#359861: files created by libquicktime0 not opened with same
Bug#359863: BOUNTY: files created by libquicktime0 not opened with same
Merged 359861 359863.
>
En
Your message dated Tue, 30 May 2006 01:47:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#286503: fixed in gerstensaft 0.2-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
severity 365110 important
thanks
As I cannot reproduce the bug on an etch system, and as I suspect this
bug to be closed in 2.6.6-1, I downgrade the severity of this bug in
order to let the package entering etch (which is actually the best way to
close it).
Thanks.
--
Alexis Sukrieh <[EMAIL PRO
Package: samhain
Version: 2.0.10a-4
Severity: serious
Hello,
There was an error while trying to autobuild your package:
> autoheader:
> autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
> autoheader: [Define if a function `main' is needed.])
> autoheader:
> autoheader: WARNING: M
Processing commands for [EMAIL PROTECTED]:
> severity 365110 important
Bug#365110: electricsheep: 2.6.5-1 fails to start in etch
Severity set to `important' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(admini
Package: fextremes
Version: 221.10065-1
Severity: serious
Hello,
There was an error while trying to autobuild your package:
> Loading required package: fMultivar
> Loading required package: mgcv
> This is mgcv 1.3-17
> Loading required package: nnet
>
> Rmetrics, (C) 1999-2005, Diethelm Wuertz
Package: printconf
Version: 0.7.4.18
Followup-For: Bug #364791
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Same here :(
On installing package:
*** glibc detected *** free(): invalid next size (normal): 0x081917a0 ***
Unable to read printer database. Please ensure the "foomatic-db" package is
Oh yes I'm sorry, I think I misread the messages. I think it was gajim
spawning this message about python-dbus (it doesn't do it anymore BTW).
I just don't know why quodlibet tries to start a jabber client on
startup. I removed the gajim package, quodlibet works fine and just prints*
sh: gajim-
On Tue, May 09, 2006 at 01:45:25AM -0700, Arias Hung wrote:
> On Tue, 09 May 2006, Sjoerd Simons delivered in simple text monotype:
>
> >On Mon, May 08, 2006 at 06:57:13PM -0700, Arias Hung wrote:
> >>On Mon, 08 May 2006, Sjoerd Simons delivered in simple text monotype:
> >>
> >Uhm, right the runn
* Aníbal Monsalve Salazar [Tue, 30 May 2006 16:18:59 +1000]:
> Alternatively, please add yourself to the uploaders list.
I'll do this.
Cheers,
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
* Steve Langasek [Tue, 30 May 2006 00:51:31 -0700]:
> But I guess your patch actually fixes this, so I'm not sure why you say it's
> "moot". :)
Because they say I know English, but it's only a malicious rumor. I
probably meant "settled". Just for fun:
http://www.bartleby.com/64/pages/page120.h
Quoting Michael Ablassmeier <[EMAIL PROTECTED]>:
> hi,
>
> > (python:1695): Gdk-CRITICAL **: gdk_draw_drawable: assertion `src != NULL'
> failed "
> > and it looks like it has entered into an infinite loop.
> > No spe window appears.
> > It looks like one missing dependency.
>
> I cant reproduce t
Your message dated Tue, 30 May 2006 03:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#288202: fixed in pornview 0.2pre1-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 message dated Tue, 30 May 2006 03:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#345100: fixed in pornview 0.2pre1-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 message dated Tue, 30 May 2006 03:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#356736: fixed in pornview 0.2pre1-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
* Stuart Anderson <[EMAIL PROTECTED]> [2006-05-26 11:09]:
> I have prepared fixes for all 3 of these grave bugs. Support for libxine
> is still enabled.
Ok, I've uploaded this now, thanks.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject o
Package: gnucash
Version: 1.9.6-3
Severity: grave
Justification: renders package unusable
gnucash does not start anymore.
after the splash disappears, the main window indicates that it is
loading the data file (the bottom-right "cursor" runs madly back and
forth), all disappears without any messa
Package: linux-image-2.6.16-1-alpha-smp
Version: 2.6.16-12
Severity: grave
Justification: renders package unusable
Hi,
I'm trying to upgrade from the (working) 2.6.15 to (current) 2.6.16 but
some modules fail to load, I get the messages shown below.
Since I can't get to any of my disks (on any
Your message dated Tue, 30 May 2006 03:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#356736: fixed in pornview 0.2pre1-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 message dated Tue, 30 May 2006 03:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#345100: fixed in pornview 0.2pre1-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 message dated Tue, 30 May 2006 03:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#345100: fixed in pornview 0.2pre1-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 message dated Tue, 30 May 2006 03:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#356736: fixed in pornview 0.2pre1-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 message dated Tue, 30 May 2006 03:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#288202: fixed in pornview 0.2pre1-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 message dated Tue, 30 May 2006 03:47:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#288202: fixed in pornview 0.2pre1-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
On Wed, 2006-05-24 at 09:54 -0400, Steve M. Robbins wrote:
> The SOVERSION will change. So, yes, I'm afraid it will require another
> recompilation.
Is there a chance to see an interim fix applied to the package until the
new gmp upstream revision is released. (Like upload of the RC version
with
Package: baobab
Version: 2.4.2-1
Severity: critical
Justification: breaks unrelated software
baobab has in its postinst:
gtk-update-icon-cache -q /usr/share/icons/hicolor
This has already been discussed in debian-gnome-gtk list, and I think it
should not.
All other gnome applications that install
severity 369516 wishlist
retitle 369516 sql-ledger: should automatically add plpgsql support to
postgresql at installation time
thanks
Hi,
On Tue, 30 May 2006, root wrote:
> I have installed sql-ledger on debian etch (2.6.10) I also have installed
> postresql-8.1
>
> After pointing my browser
On 30 May 2006 at 11:27, Frederik Schüler wrote:
| Package: fextremes
| Version: 221.10065-1
| Severity: serious
|
| Hello,
|
| There was an error while trying to autobuild your package:
|
| > Loading required package: fMultivar
| > Loading required package: mgcv
| > This is mgcv 1.3-17
| > Lo
On Thu, Jan 26, 2006 at 11:38:57AM -0500, sean finney wrote:
> severity 316321 serious
> tags 316321 patch
> thanks
>
> hi,
>
> revisiting this issue, and after having spoken with folks
> on -devel and -policy, the consensus is that this is in
> fact a policy violation, so i am changing the sever
Processing commands for [EMAIL PROTECTED]:
> severity 369516 wishlist
Bug#369516: sql-ledger: fails to install on postgresql 8.1
Severity set to `wishlist' from `grave'
> retitle 369516 sql-ledger: should automatically add plpgsql support to
> postgresql at installation time
Bug#369516: sql-ledg
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> package evince
Ignoring bugs not assigned to: evince
> tags 357262 + pending
Bug#357262: evince: Please switch to libkpathsea4-dev
Tags were: patch
Tags added: pending
>
End of mess
> Hello,
>
> according to the description "This packages contains the compiled XML
> documentation for the D-BUS CLI bindings". Unfortunately it doesn't
> contain anything useful, only[1]:
actually, those docs do not exists anymore upstream.
the monodoc-dbus-1-manual package just should be d
Hi,
I tried running gtk+ programs under valgrind.
(with crashable gtkrc-2.0)
$ valgrind gnumeric
~snip~
==10447== Invalid free() / delete / delete[]
==10447==at 0x401D048: free (vg_replace_malloc.c:235)
==10447==by 0x4B0715B: g_free (in /usr/lib/libglib-2.0.so.0.1000.2)
==10447==by 0x
* Steve Langasek [Sun, 21 May 2006 12:05:35 -0500]:
> Yes. Two bugs here. First, mkfontdir should be invoked as
> system('mkfontdir', ...)
> which is acceptable because perl's system() will honor path. This is a
> better option, IMHO, than adding further package relationships to enforce it
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> reassign 341045 apache-common
Bug#341045: php4-sqlite: Missing/bad dependency to apache
Bug reassigned from package `php4-sqlite' to `apache-common'.
>
End of message, stopping proce
Hello Uwe,
this bug is RC and has a patch since a long while. Would you mind uploading
this before someone NMU the package, please ?
Thanks, Mt.
On Fri, Apr 28, 2006 at 11:46:33AM +0200, Daniel Schepler wrote:
> Package: xbubble
> Version: 0.5.11.1-1
> Severity: serious
>
> From my pbuilder bui
Package: xmovie
Version: 1.9.12-1
Severity: serious
xmovie now fails to build on unstable:
g++ -c `cat i686/c_flags` filemov.C -o i686/filemov.o
filemov.C: In member function ‘virtual int FileMOV::read_frame(VFrame*, int,
int)’:
filemov.C:253: error: ‘quicktime_set_window’ was not declared in th
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.20
> package x-ttcidfont-conf
Ignoring bugs not assigned to: x-ttcidfont-conf
> tags 362296 + pending
Bug#362296: x-ttcidfont-conf: X11R7 transition
Tags were: patch
Tags added: pending
Package: spamassassin
Version: 3.1.1-1
Severity: serious
Tags: patch
Hello.
Polish locales contains invalid character and break RFC 2822.
The RFC 2822 standard specifies rules for forming internet messages.
It does not allow the use of characters with codes above 127 to be used
directly (non-enc
Your message dated Tue, 30 May 2006 15:31:45 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Ack'ing NMUs
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 reo
Hi,
It is urgent that this bug be fixed in a timely manner. We need to
upload a package that depends on and uses xmlstarlet, but can't do so if
the binary name is different on different architectures.
thanks,
Charles
--
The answer to
A shaver's dream
A greaseless
No brush
Shaving cream
Burma-Sh
I am strictly compliant with Gnome Policy about AppIcons:
http://live.gnome.org/GnomeGoals/AppIcon
It is hard to follow 2 diverging policies
Fabio Marzocca
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message dated Tue, 30 May 2006 15:31:45 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Ack'ing NMUs
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 reo
Pierre HABOUZIT wrote:
> Ping apache2-common maintainers ?
>
> is there any reason why that bug is rotting in a RC state for 4+
> monthes ?
>
> I may perform an NMU soon.
>
Yes, because I'm preparing a 2.0.58 upload which includes several
patches to the init scripts, not just this one, so
Processing commands for [EMAIL PROTECTED]:
> reassign 369527 libasound2 1.0.11-5
Bug#369527: amarok: crashes with libasound2 1.0.11-5
Bug reassigned from package `amarok' to `libasound2'.
> severity 369527 grave
Bug#369527: amarok: crashes with libasound2 1.0.11-5
Severity set to `grave' from `no
Le Mar 30 Mai 2006 15:52, Adam Conrad a écrit :
> Pierre HABOUZIT wrote:
> > Ping apache2-common maintainers ?
> >
> > is there any reason why that bug is rotting in a RC state for 4+
> > monthes ?
> >
> > I may perform an NMU soon.
>
> Yes, because I'm preparing a 2.0.58 upload which include
Greetings!
Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:
> On 26 May 2006 at 22:45, Frederik Schueler wrote:
> | Hi,
> |
> | On Fri, May 26, 2006 at 03:18:35PM -0500, Dirk Eddelbuettel wrote:
> | > All fine, but who depends on g77? For R, I make'em build-depend on
> | > r-base-dev, and that now
Your message dated Tue, 30 May 2006 07:02:22 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#346791: fixed in xboing 2.4-28
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, 30 May 2006 07:02:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#357262: fixed in evince 0.4.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 you
Your message dated Tue, 30 May 2006 07:02:22 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#367840: fixed in xboing 2.4-28
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
Greetings!
Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:
> On 26 May 2006 at 22:45, Frederik Schueler wrote:
> | Hi,
> |
> | On Fri, May 26, 2006 at 03:18:35PM -0500, Dirk Eddelbuettel wrote:
> | > All fine, but who depends on g77? For R, I make'em build-depend on
> | > r-base-dev, and that now
Hi again! =)
On 5/30/06, Steve McIntyre <[EMAIL PROTECTED]> wrote:
Just a heads-up; things are not as simple as I'd hoped. I've spent
several hours today trying to get old behaviour back, and so far it's
not working...
Indeed =( I've been held back by today's power blackout (I just got
back o
Your message dated Tue, 30 May 2006 07:02:22 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#174924: fixed in xboing 2.4-28
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, 30 May 2006 16:59:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368886: spe startup process crash
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
Package: gfortran
Version: 4:4.0.3-4
Severity: grave
Justification: renders package unusable
I'm not sure this is a bug but I could not find any documentation of
this anomalous behaviuor.
Below you find two programs:
qaz.f
zaq.f
qaz.f writes 3 integers in un unformatted file
zaq.f reads three i
Package: castle-combat
Version: 0.8.0-2
Severity: grave
Justification: renders package unusable
When two local players play the game it throws
set_movement succeeded for player 0
Unhandled error in Deferred:
Traceback (most recent call last):
File "/usr/share/games/castle-combat/scripts/state.p
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.15
> merge 358124 361230
Bug#358124: etherboot: FTBFS: newer mtools version not recognized
Bug#361230: etherboot: FTBFS: Mtools version detection problem/Wrong
Build-Depends on amd64
Merg
Processing commands for [EMAIL PROTECTED]:
> tags 342694 + pending
Bug#342694: /dev/ubd/1 missing
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 Bugs databas
tags 369513 + unreproducable,moreinfo
thanks
Alberto Maurizi <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 1.9.6-3
> Severity: grave
> Justification: renders package unusable
>
>
> gnucash does not start anymore.
> after the splash disappears, the main window indicates that it is
> l
Processing commands for [EMAIL PROTECTED]:
> tags 369513 + unreproducable,moreinfo
Unknown tag/s: unreproducable.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid
help security upstream pending sarge sarge-ignore experimental d-i confirmed
ipv6 lfs fixed-in-experiment
On Sun, May 21, 2006 at 06:46:05PM -0700, Richard A Nelson wrote:
> RC abuse of /etc/ssl/certs, rendering certificate validation
> inoperable.
Hi. Thanks for the report.
I'm currently trying to get an answer from the debian openssl
people as to the right place to put the key (/etc/ssl/private/?
/
Your message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#320794: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321652: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:12 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322882: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321652: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#320794: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:12 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322882: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#320656: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#320656: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#320621: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321509: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:12 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322882: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#320582: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321406: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321652: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321244: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:12 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322600: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321652: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321406: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:12 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322882: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#320621: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#320621: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:12 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322882: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#320582: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#320582: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:12 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322600: fixed in djvulibre 3.5.17-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 message dated Tue, 30 May 2006 09:17:11 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#321244: fixed in djvulibre 3.5.17-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
1 - 100 of 276 matches
Mail list logo
