"Davide G. M. Salvetti" <[EMAIL PROTECTED]> wrote:
>> fant == Frank Küster [2006-10-26]
>
> fant> Davide, I hope I don't interfere while you are just about to
> fant> upload your own version. But since we haven't heard anything from
> fant> you, I am not willing to wait.
>
> No problem for m
tags 395425 fixed-upstream
stop
I tested the new upstream release (0.99.12) using `uupdate` and it fixes
this problem.
-Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing commands for [EMAIL PROTECTED]:
> tags 395425 fixed-upstream
Bug#395425: gnomeicu: Very very bizarre error when connecting
There were no tags set.
Tags added: fixed-upstream
> stop
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administ
On Thu, Oct 26, 2006 at 08:15:21PM -0400, Camm Maguire wrote:
> Greetings, and thanks so much! Now that this is in, would you kindly
> mind requeueing gclcvs again?
FWIW, after tracking down the last header problem on alpha I let the test
build continue on through to see if there were any other p
Package: xserver-xorg-video-i810-modesetting
Version: 1.6.5.git20061014-1~1
Severity: serious
This is a policy pseudobug to keep xserver-xorg-video-i810-modesetting
from entering testing/etch.
The i810 modesetting branch is a development version of the i810 intel
video driver. It is not particul
I don't have an unstable version of debian set up anywhere, so I've gotten stuck trying to compile gaim beta4, but my guess is that this patch should fix the error:--- gtk-dialog.c.bak 2006-10-26 21:51:08.0
-0500+++ gtk-dialog.c 2006-10-26 21:52:59.0 -0500@@ -30,7 +30,7 @
Processing commands for [EMAIL PROTECTED]:
> severity 395411 normal
Bug#395411: debian-installer: [daily 20061026] fails to set up route + fails to
see mirrors
Severity set to `normal' from `critical'
>
End of message, stopping processing here.
Please contact me if you need ass
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.22
> tags 384243 - patch
Bug#384243: FTBFS (alpha): assembly syntax errors
Tags were: patch
Tags removed: patch
>
End of message, stopping processing here.
Please contact me if you need
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> tags 359232 - fixed
Bug#359232: libcrypt-cbc-perl security update broken.
Tags were: fixed sarge
Tags removed: fixed
>
End of message, stopping processing here.
Please contact me if
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> tags 292231 - fixed
Bug#292231: [NONFREE-DOC:GFDL1.1] making the entire manpage invariant is not
consistent with the DFSG
Tags were: fixed fixed-upstream
Tags removed: fixed
>
End o
On Mon, 23 Oct 2006, Thijs Kinkhorst wrote:
> I propose binutils-h8300-hms to be removed, for the following reasons:
>
> * Orphaned for two monts without any sign of interest;
> * Has an RC bug (non-free docs);
> * Last MU four years (!) ago;
> * Very few users in popcon (4 votes).
Current packag
On Thursday 26 October 2006 19:39, you wrote:
> Did you see the new version i attached :
No, initially I did not see this. Reason is simple: I had already applied
your original patch and closed the BR, so I looked in the original bug
report instead of in your new mail. Is that my mistake, maybe.
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.22
> severity 395228 important
Bug#395228: Requires internet access during build
Severity set to `important' from `serious'
>
End of message, stopping processing here.
Please contact me
Bonjour Michel,
On Thu, Sep 28, 2006 at 12:05:36 +0200, Michel Quercia wrote:
> Seems to be some micmac with local symbols that are unexpectedly
> promoted to the dynamic status. Would it be possible to give a try
> without the "-fPIC" gcc option before I rewrite all local computed jumps
> (I
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.21
> # also fixed in current version
> close 384263 2:1.1.1-4
Bug#384263: ati: module ABI major version (0) doesn't match the server's
version (1)
'close' is deprecated; see http://www.de
Processing commands for [EMAIL PROTECTED]:
> # the following bugs are closed by packages in NEW
> #
> tags 340144 pending
Bug#340144: ITP: kde-guidance -- collection of KDE system administration tools
for GNU/Linux
Tags were: fixed-in-experimental
Tags added: pending
> tags 375443 pending
Bug#37
Greetings, and thanks so much! Now that this is in, would you kindly
mind requeueing gclcvs again?
Thanks!
Take care,
Steve Langasek <[EMAIL PROTECTED]> writes:
> Package: linux-kernel-headers
> Version: 2.6.18-3
> Severity: serious
> Tags: patch
>
> On Tue, Oct 24, 2006 at 09:31:42AM -0400,
Package: gaim-otr
Followup-For: Bug #394299
There needs to be another change in order to fix the following error:
gtk-dialog.c:33:22: error: gtkstock.h: No such file or directory
This need to be changed on line 33.
-#include "gtkstock.h"
+#include "gtk/gtkstock.h"
regards
-- System Information:
Your message dated Thu, 26 Oct 2006 16:17:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#395319: fixed in amanda 1:2.5.1p1-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 Thu, 26 Oct 2006 15:47:18 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#395378: fixed in kbibtex 0.1.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 yo
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #364031 in the xtoolwait
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than clo
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #366581 in the libvorbisfile-ruby
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365189 in the bidentd
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than close
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #364080 in the xpaint
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #364894 in the xstarfish
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than clo
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #364522 in the vacation
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than clos
Upload is done. Your upload didn't actually close this bug though I
noticed, after running dput :-(. Probably should do though I think?
Alan.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #366574 in the libnora-ruby
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than
Steve Langasek wrote:
> On Thu, Oct 26, 2006 at 11:05:18AM -0700, Kevin B. McCarty wrote:
>> Attached please find my proposed NMU patch for this bug. Feel free to
>> take over it and include it in a maintainer upload. However, if I don't
>> hear from you within the next several days (let's say, b
Processing commands for [EMAIL PROTECTED]:
> # Hi,
> #
> # Now that the BTS supports version-tracking, bugs that were
> # fixed in NMUs but never acknowledged can be marked as
> # closed in the relevant version. In the case of the bugs listed
> # below, they're marked as release-critical in the ve
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #364379 in the pcmanx-gtk2
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than c
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #366571 in the libimage-size-ruby
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365157 in the multi-aterm
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than c
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365163 in the pload
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365195 in the ircd-ircu
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than clo
Processing commands for [EMAIL PROTECTED]:
> # Hi,
> #
> # Now that the BTS supports version-tracking, bugs that were
> # fixed in NMUs but never acknowledged can be marked as
> # closed in the relevant version. In the case of the bugs listed
> # below, they're marked as release-critical in the ve
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365182 in the gnustep-netclasses
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #366389 in the wmdate
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365168 in the sendpage-common
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather th
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #364338 in the initrd-tools
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #366005 in the textopo
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than close
Package: gnomeicu
Version: 0.99.10-2
Severity: serious
Everytime i try to connect it shows me "Very very bizarre error when
connecting". So, it absolutely unusable for me. It worked brilliant till last
10 days or so. Gaim and windows' icq works still with no problems.
I have:
Architecture: am
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #369866 in the gthumb
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365285 in the fvwm95
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365225 in the usbmount
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than clos
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365158 in the wmcalc
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #363072 in the pyopengl
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than clos
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365260 in the pixmap
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365198 in the zenirc
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365286 in the vtwm
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #363009 in the libsub-uplevel-perl
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rathe
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365335 in the mozilla-firefox-adblock
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" r
On Thu, Oct 26, 2006 at 11:05:18AM -0700, Kevin B. McCarty wrote:
> Attached please find my proposed NMU patch for this bug. Feel free to
> take over it and include it in a maintainer upload. However, if I don't
> hear from you within the next several days (let's say, by November 3rd)
> I will up
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #366527 in the xmon
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #365284 in the clips
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Your message dated Thu, 26 Oct 2006 14:47:35 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#391237: fixed in liquidwar 5.6.3-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
Justification: renders package unusable
What evidence do you have that kdeprint is unusable?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #368182 in the zope-zwiki
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than cl
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #367045 in the rezound
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than close
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #357228 in the adduser-ng
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than cl
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #369479 in the udev
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #359688 in the gtkglext
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than clos
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #357780 in the webut
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #362406 in the xtel
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #368207 in the mp3info
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than close
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #367838 in the wnn6-sdk
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than clos
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #359645 in the camelbones
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than cl
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #357919 in the rekall
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #369094 in the avifile
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than close
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #384057 in the mesa
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #367850 in the xoids
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #357465 in the irmp3
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #367830 in the ibm-3270
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than clos
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #356114 in the aspell-it
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than clo
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #364029 in the olvwm
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #368274 in the xinput
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #367645 in the regexxer
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than clos
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #364127 in the latex-beamer
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #368017 in the xmon
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
tags 395319 +pending
thanks
On Thu, 2006-10-26 at 11:55 +0100, Alex Owen wrote:
> Package: amanda-client
> Version: 2.5.1-1
> Severity: grave
>
> Justification: "makes the package in question unusable or mostly so,
> or causes data loss"
Feels like grossly over-inflated severity to me, but since
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #361372 in the statd
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #363476 in the pmud-utils
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than cl
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #361004 in the carpaltunnel
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #356014 in the openexr
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than close
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #356044 in the dict-foldoc
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than c
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #369523 in the xmovie
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #374264 in the libcinepaint0
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #359737 in the libreadline-java
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather t
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #358287 in the twutils
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than close
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #369621 in the ysm
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Processing commands for [EMAIL PROTECTED]:
> tags 395319 +pending
Bug#395319: /sbin/dump: illegal density error - fixed upstream in amanda 2.5.1p1
There were no tags set.
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Your message dated Thu, 26 Oct 2006 14:02:34 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#394296: fixed in gaim-hotkeys 0.2.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
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #362288 in the xzgv
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #363425 in the bluez-pin
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than clo
Your message dated Thu, 26 Oct 2006 14:06:31 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#394981: fixed in mlton 20061026-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
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #358540 in the wmaker
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed
Your message dated Thu, 26 Oct 2006 14:17:20 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#355733: fixed in strace 4.5.14-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
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #367843 in the xinput
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #368562 in the mesa
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
Hi,
You should have recently received (or will soon receive) an e-mail
telling you that I've closed Debian bug #357849 in the cvsnt
package, which you reported.
Due to the fact that the package was uploaded by someone who does not
normally do so, the bug was marked as "fixed" rather than closed.
1 - 100 of 479 matches
Mail list logo
