On 11:10, Wed 24 Oct 07, Michal Čihař wrote:
> On Tue, 23 Oct 2007 21:28:24 +0200
> Ruben Pollan <[EMAIL PROTECTED]> wrote:
>
> > It breaks at start:
> >
> > [EMAIL PROTECTED]:~$ wammu
> > Traceback (most recent call last):
> > File "/usr/bin/wammu", line 31, in ?
> > import Wammu.Locales
>
Your message dated Wed, 24 Oct 2007 09:31:57 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#447833: kde-i18n-es: Version 4%3a3.5.8-1 breaks the es
keyboard layout
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt wit
I have a Logitech Cordless Internet Pro keyboard and mouse, both connect
to the same USB port. The interesting thing is that some keyboard
events are transmitted via the mouse (it seems rather braindead to me,
but that's the case). This is part of my /proc/bus/input/devices:
I: Bus=0003 Vendor
reassign 447794 wammu
quit
Please do not simply reassign grave bugs to another package arbitrarily
without even bothering to confirm if they are bugs in that package or not.
You've given no evidence that this is a bug in another package and
didn't even bother to wait for further information from
Package: python-apt
Severity: critical
Justification: breaks unrelated software
Wajig was deleted because it depends on python-apt, which in turn is
dependent on libapt-pkg-libc6.6-6-4-4, which is not installable.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT polic
On Wed, Oct 24, 2007 at 09:16:27AM +0200, Ruben Pollan wrote:
> On 11:10, Wed 24 Oct 07, Michal Čihař wrote:
> > It looks like python-wxgtk2.6 package is somehow broken. What does show
> > output of 'update-alternatives --display wx.pth'?
> >
>
> edelweiss:~# update-alternatives --display wx.pt
>
Processing commands for [EMAIL PROTECTED]:
> reassign 447794 wammu
Bug#447794: wammu: error at start
Bug reassigned from package `python-wxgtk2.6' to `wammu'.
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debi
On Wed, 24 Oct 2007 09:16:27 +0200
Ruben Pollan <[EMAIL PROTECTED]> wrote:
> On 11:10, Wed 24 Oct 07, Michal Čihař wrote:
> > It looks like python-wxgtk2.6 package is somehow broken. What does show
> > output of 'update-alternatives --display wx.pth'?
> >
>
> edelweiss:~# update-alternatives --d
[snip]
An alternative would be, to use a hal fdi file
/etc/hal/fdi/policy/x11-input.fdi like this.
de
nodeadkeys
This has worked for me.
We are currently discussing, if xserver-xorg will generate such a file
automatically in the future.
Ok,
Thx for the tip!
Hi
On Wed, 24 Oct 2007 17:49:11 +0930
Ron <[EMAIL PROTECTED]> wrote:
> Please do not simply reassign grave bugs to another package arbitrarily
> without even bothering to confirm if they are bugs in that package or not.
Well in fact I even did not notice this is a grave bug.
> You've given no e
On 23/10/07 at 17:47 +0800, Andrew Lee wrote:
> Lucas Nussbaum wrote:
> > During a rebuild of all packages in sid, your package failed to build on
> > i386.
>
> Strange, I can build the package without problem on my i386 sid even
> with pbuilder.
>
> Looks like I accidently enabled espeak in las
Hi Martin!
On Wed, 24 Oct 2007 08:17:44 +0200 "Michael Biebl" <[EMAIL PROTECTED]> wrote:
> this bug has been reported already several times. Please check the bts
> first next time.
Nothing was reported on hal, and it was the only package under discussion which
changed.
> It's actually not a bu
Hi all!
On Wed, 24 Oct 2007 08:17:44 +0200 "Michael Biebl" <[EMAIL PROTECTED]> wrote:
> this bug has been reported already several times. Please check the bts
> first next time.
Nothing was reported against hal and that was the only packag which
> It's actually not a bug in hal, but an xorg inpu
Processing commands for [EMAIL PROTECTED]:
> package reprepro
Ignoring bugs not assigned to: reprepro
> close 440535 1.3.1+1-1
Bug#440535: reprepro: Not properly checking signatures of repositories updating
from
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked
On 17:10, Wed 24 Oct 07, Michal Čihař wrote:
> On Wed, 24 Oct 2007 09:16:27 +0200
> Ruben Pollan <[EMAIL PROTECTED]> wrote:
>
> > On 11:10, Wed 24 Oct 07, Michal Čihař wrote:
> > > It looks like python-wxgtk2.6 package is somehow broken. What does show
> > > output of 'update-alternatives --displa
On Wed, Oct 24, 2007 at 05:25:09PM +0900, Michal Čihař wrote:
> On Wed, 24 Oct 2007 17:49:11 +0930
> Ron <[EMAIL PROTECTED]> wrote:
>
> Well Wammu does depend on python-wxgtk2.6 and 'import wx' fails. I
> simply do not see how problem could be in Wammu.
>
> > You didn't even bother to simply try:
On Tue, Oct 23, 2007 at 08:17:10PM -0400, ext David Nusinow wrote:
> On Tue, Oct 23, 2007 at 10:02:35PM +0300, Daniel Stone wrote:
> > On Tue, Oct 23, 2007 at 08:02:31PM +0200, ext Michael Biebl wrote:
> > > Whenever xorg input hotplugging kicks in, the evdev driver is used. The
> > > kbd keyboard
Your message dated Wed, 24 Oct 2007 11:02:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#447293: fixed in simple-cdd 0.3.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 y
Package: libopenh323-1.19.1-dbg,libopenh323-dbg
Severity: serious
Justification: policy violation
hi,
both libopenh323-1.19.1-dbg and libopenh323-dbg ship
`/usr/lib/debug/usr/bin/simph323'
but do neither conflict, nor add a diversion, thus fail to be installed
in the same environment:
> Unpac
Package: simph323-titan, simph323
Severity: serious
Justification: policy violation
hi,
both simph323-titan and simph323 ship /usr/bin/simph323 but do neither
conflict, nor add a diversion, thus fail to be installed in the same
environment:
> Unpacking simph323-titan (from .../simph323-titan_1.
Processing commands for [EMAIL PROTECTED]:
> severity 447327 serious
Bug#447327: please add "Conflicts: ja-trans"
Severity set to `serious' from `normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian
Package: libtext-bidi-perl,text-bidi
Severity: serious
Justification: policy violation
hi,
both libtext-bidi-perl and text-bidi ship
`/usr/lib/perl5/auto/Text/Bidi/private/private.so'
but do neither conflict, nor add a diversion, thus fail to be installed
in the same environment:
> Unpacking
Hi,
I've observed the same problem in my installation. Changing
/usr/share/sympa/db/install-pg-db so that the sympa user has createdb
rights doesn't help. The problem seems to be that the database gets
created by one of the installation scripts, and create_db.Pg tries to
create the database agai
Dne Wed, 24 Oct 2007 11:58:12 +0200
Ruben Pollan <[EMAIL PROTECTED]> napsal(a):
> You are right, sorry. Again:
>
> edelweiss:/home/meskio# update-alternatives --display wx.pth
> wx.pth - el estado es manual.
> el enlace apunta actualmente a /usr/lib/wx/config/wx2.4.pth
> /usr/lib/wx/python/wx2.4
Package: hal
Version: 0.5.10-1
Severity: serious
This is serious because dpkg fails to upgrade hal, since the init.d
script exits with code 1. Here is what's going on:
piper$ sudo /etc/init.d/hal stop
Stopping Hardware abstraction layer: hald.
piper$ ps aux | grep hal
piper$ sudo hald --daemon=
Hi
Dne Wed, 24 Oct 2007 19:42:06 +0930
Ron <[EMAIL PROTECTED]> napsal(a):
> Well clearly something is different as wx installed from sid does
> not do this on its own -- so it would seem to be an issue with either
> wammu or the user's system. I presume you also can't reproduce this,
> even with
Norbert Preining schrieb:
> Hi Martin!
>
> On Wed, 24 Oct 2007 08:17:44 +0200 "Michael Biebl" <[EMAIL PROTECTED]> wrote:
>> this bug has been reported already several times. Please check the bts
>> first next time.
>
> Nothing was reported on hal, and it was the only package under discussion
> w
Your message dated Wed, 24 Oct 2007 11:32:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#447327: fixed in net-tools 1.60-17.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 no
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.9
> severity 446851 important
Bug#446851: Please package new upstream version which includes x11-input.fdi
Severity set to `important' from `critical'
>
End of message, stopping processi
Hi everyone !
As a French user, I've experienced such troubles, and spent more than 3
hours to spot the real issue.
Even if at the end I disabled evdev, I didn't understand why the startx (or
in my case startxfce4) works correctly and do NOT load evdev.
Try to log in in a console and run this com
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.9
> merge 447841 447666 447676
Bug#447666: hal: don't have the right xkb_layout anymore...just us keyboard
Bug#447676: latest hal causes problems with keyboard
Bug#447841: keyboard layout
Package: kismet
Version: 2007-10-R1-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of kismet_2007-10-R1-1 on peri by sbuild/hppa 98
> Build started at 20071023-1607
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhel
On Tue, Oct 23, 2007 at 20:02:31 +0200, Michael Biebl wrote:
> You were right, Julien. It was because of hal (specifically the file
> /usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi) that the evdev
> driver was enabled.
>
BTW, should we change the fdi to load synaptics instead of evdev when
On Wed, Oct 24, 2007 at 02:47:06PM +0200, ext Julien Cristau wrote:
> On Tue, Oct 23, 2007 at 20:02:31 +0200, Michael Biebl wrote:
> > You were right, Julien. It was because of hal (specifically the file
> > /usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi) that the evdev
> > driver was enable
On Wed, Oct 24, 2007 at 15:54:05 +0300, Daniel Stone wrote:
> On Wed, Oct 24, 2007 at 02:47:06PM +0200, ext Julien Cristau wrote:
> > On Tue, Oct 23, 2007 at 20:02:31 +0200, Michael Biebl wrote:
> > > You were right, Julien. It was because of hal (specifically the file
> > > /usr/share/hal/fdi/pol
Your message dated Wed, 24 Oct 2007 15:27:56 +0200
with message-id <[EMAIL PROTECTED]>
and subject line zipper.app: FTBFS:
/usr/lib/GNUstep/System/Library/Makefiles/GNUstep.sh: No such file or directory
has caused the attached Bug report to be marked as done.
This means that you claim that the pr
Your message dated Wed, 24 Oct 2007 14:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#447841: fixed in hal 0.5.10-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 Wed, 24 Oct 2007 14:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#447676: fixed in hal 0.5.10-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 Wed, 24 Oct 2007 14:17:03 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#447841: fixed in hal 0.5.10-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]:
> tags 446906 security
Bug#446906: gnome-screensaver does not grab keyboard input
Tags were: patch upstream confirmed
Tags added: security
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administr
tags 446906 security
thanks
Hi
Attached you will find an NMU patch to fix this problem.
Please also note that CVE-2007-3920 was assigned for this issue.
Cheers
Steffen
diff -u gnome-screensaver-2.20.0/debian/changelog gnome-screensaver-2.20.0/debian/changelog
--- gnome-screensaver-2.20.0/debian/
Processing commands for [EMAIL PROTECTED]:
> tags 447889 fixed-upstream
Bug#447889: MUC is broken
There were no tags set.
Tags added: fixed-upstream
> severity 447889 normal
Bug#447889: MUC is broken
Severity set to `normal' from `grave'
>
End of message, stopping processing here.
Please contac
Your message dated Wed, 24 Oct 2007 16:32:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#446906: fixed in gnome-screensaver 2.20.0-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
Your message dated Wed, 24 Oct 2007 18:32:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#443129: fixed in fglrx-driver 8.42.3-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
Your message dated Wed, 24 Oct 2007 18:32:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#443129: fixed in fglrx-driver 8.42.3-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
Your message dated Wed, 24 Oct 2007 18:32:16 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#441710: fixed in hol88 2.02.19940316-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
Your message dated Wed, 24 Oct 2007 18:32:07 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#443129: fixed in fglrx-driver 8.42.3-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
Processing commands for [EMAIL PROTECTED]:
> tag 445803 patch
Bug#445803: xtm does not work with parse::recdescent 1.95
Tags were: wontfix upstream
Tags added: patch
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administra
tag 445803 patch
thanks
On Wed, Oct 24, 2007 at 04:16:29PM +1000, Alexander Zangerl wrote:
> further evaluation of the test-and-thus-build failure shows that
> the parser doesn't work properly anymore; tests like 05merge now fail
> with error messages like this one:
>
>ERROR (line 1):
Debian Bug Tracking System a écrit :
Do you take us for idiots !
It's the second time you close a bug after only upload the amd64 package!
Please upload at least one x86 package or reopen the bug.
--
Encolpe DEGOUTE
http://encolpe.degoute.free.fr/
Logiciels libres, hockey sur glace et autres ac
Le Wednesday 24 October 2007 21:27:45 Encolpe Degoute, vous avez écrit :
> Do you take us for idiots !
Please retain you language, I'm not here to read such things.
> It's the second time you close a bug after only upload the amd64 package!
>
> Please upload at least one x86 package or reopen the
On Sun, Oct 21, 2007 at 10:45:34PM +0200, Rene Wunderlich wrote:
> Hi,
>
> i tink it is an amd64 bug
>
> i have a 32bit and a 64bit system and the bug is only on the 64bit system
> (sid)
>
> the init on a clean homedir fail and eclipse crashes ;/
Hmm, I develop the package on x86_64 and it wor
Romain Beauxis a écrit :
> Le Wednesday 24 October 2007 21:27:45 Encolpe Degoute, vous avez écrit :
>
>> It's the second time you close a bug after only upload the amd64 package!
>>
>> Please upload at least one i386 package or reopen the bug.
>
> Seems you don't understand the way package upload
Le Wednesday 24 October 2007 22:13:03 Encolpe Degoute, vous avez écrit :
> For last version it was not. The i386 packages were made lately (See
> #440186).
> Then you should wait that these packages have been generated before to
> close one bug.
> Or you can just said that the bug is fixed upstream
The text-bidi binary package wasn't meant to be accept into the archive
and should be removed automatically due to the fact that the text-bidi
source package doesn't build the text-bidi binary package (as of 0.03-2).
If this doesn't happen fast enough, I'll reassign this bug to
ftp.debian.org to m
Your message dated Wed, 24 Oct 2007 20:53:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#433736: fixed in php5 5.2.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]:
> severity 421490 important
Bug#421490: Causes massive CPU load when enabled
Severity set to `important' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
Your message dated Wed, 24 Oct 2007 20:53:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#443637: fixed in php5 5.2.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]:
> tags 447821 experimental
Bug#447821: xmms-singit: Depends on removed libssl0.9.7
There were no tags set.
Tags added: experimental
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(a
Package: xmms2
Version: 0.2DrJekyll-4
Severity: serious
Justification: no longer builds from source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With libmac installed, the configure script automatically builds the
Monkey's Audio plugin, resulting in the following error:
dh_install: debian/tmp/u
tags 447821 experimental
thanks
Hello Alban,
thanks for your bugreport.
On Wed, Oct 24, 2007 at 12:42:45AM +0200, Alban Browaeys wrote:
> Package: xmms-singit
> Severity: grave
> Justification: renders package unusable
>
> The package depends on non available libssl0.9.7. Could it be upgraded
Le mercredi 24 octobre 2007 à 22:50 +0200, Florian Ernst a écrit :
> > The package depends on non available libssl0.9.7. Could it be upgraded
> > to use libssl0.9.8 ?
>
> Well, it could. However, xmms-singit has been removed from
> testing/unstable, and personally I'm currently not eager to brin
Package: gramps
Severity: serious
Version: 2.2.9-1
debhelper should be in Build-depends not in Build-depends-indep since
debhelper scripts are called in the clean target.
According to the policy:
===8<
Build-Depends, Build-Conflicts
The Build-Depends and Build-Conflicts fields must be sa
Anders Lagerås wrote:
> Package: licq-plugin-msn
> Version: 1.3.4-3
> Severity: grave
> Justification: causes non-serious data loss
>
> I can only send one message, then I have to restart licq to be able
> to send more messages
How does this lose data?
It needs libxv-dev on Depends: to make this work =)
--
Marco Rodrigues
http://Marco.Tondela.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: fop
Version: 1:0.93.dfsg.1-2
Severity: grave
[It is possible that fop works for other people, in which case this
would merely be important. Feel free to adjust.]
When transforming the attached file, I get the following messages:
Oct 24, 2007 10:15:23 PM org.apache.fop.apps.FopFactor
severity 447951 important
kthxbye
On Wed, Oct 24, 2007 at 10:31:26PM +, brian m. carlson wrote:
This problem can be trivially reproduced with
fop -fo an-orange-in-flight.fo -pdf an-orange-in-flight.pdf
I determined that using draft.mode=no in the DocBook FO stylesheets
allows this to wo
Processing commands for [EMAIL PROTECTED]:
> severity 447951 important
Bug#447951: fop: NullPointerException whilst transforming
Severity set to `important' from `grave'
> kthxbye
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(admin
I have added NEWS.Debian information about this change to the svn
repository for the package.
In order to fix this, please migrate to static context IDs, to do this
simply stop your guest, echo an unique number to
/etc/vservers//context and then start your guest.
Micah
--
To UNSUBSCRIBE, em
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: aptitude
Version: 0.4.6.1-1.1
Severity: grave
Justification: renders package unusable
there is a dependency problem with the new apt version (0.7.7) for
libapt-pkg-libc6.6-6-4.4 which results that aptitude wants to remove
itself unless i put
On Wed, Oct 24, 2007 at 01:53:40PM +0300, Daniel Stone wrote:
> On Tue, Oct 23, 2007 at 08:17:10PM -0400, ext David Nusinow wrote:
> > On Tue, Oct 23, 2007 at 10:02:35PM +0300, Daniel Stone wrote:
> > > On Tue, Oct 23, 2007 at 08:02:31PM +0200, ext Michael Biebl wrote:
> > > > Whenever xorg input h
David Nusinow schrieb:
> On Wed, Oct 24, 2007 at 01:53:40PM +0300, Daniel Stone wrote:
>> On Tue, Oct 23, 2007 at 08:17:10PM -0400, ext David Nusinow wrote:
>>> On Tue, Oct 23, 2007 at 10:02:35PM +0300, Daniel Stone wrote:
On Tue, Oct 23, 2007 at 08:02:31PM +0200, ext Michael Biebl wrote:
Your message dated Thu, 25 Oct 2007 00:05:34 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#447872: fixed in kismet 2007-10-R1-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 no
Hi Michael,
On Tue, 23 Oct, 2007 at 11:38:29AM +0200, Michael Koch wrote:
> This is cause by a bug in dak (e.g. #232730). A possible workaround is
> to do a complete update with a new orig tarball. This means a new
> version number. If upstream is not releasing soon you can do something
> like nam
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.9
> tags 447458 + pending
Bug#447458: libtritonus-java: FTBFS:
/build/user/libtritonus-java-20070428/build.xml:23: Compile failed; see the
compiler error output for details.
There were
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.9
> tags 447455 + pending
Bug#447455: entagged: FTBFS: source not available
There were no tags set.
Tags added: pending
>
End of message, stopping processing here.
Please contact me if
Your message dated Wed, 24 Oct 2007 21:26:21 -0600 (MDT)
with message-id <[EMAIL PROTECTED]>
and subject line believed fixed in current version
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
Package: deskbar-applet
Version: 2.20.0-1
Severity: grave
Deskbar-applet 2.20 has no in-panel command line any more, which for a
lot of users is a severe regression from 2.18.
It should therefore be kept out of testing (thus Severity: grave).
References:
Fixing this is *the* top item on the GNOM
severity 447980 wishlist
quit
"Johan Walles" <[EMAIL PROTECTED]> writes:
> Deskbar-applet 2.20 has no in-panel command line any more, which for a
> lot of users is a severe regression from 2.18.
> It should therefore be kept out of testing (thus Severity: grave).
Sorry but this just doesn't mak
Processing commands for [EMAIL PROTECTED]:
> severity 447980 wishlist
Bug#447980: deskbar-applet 2.20 has no in-panel command line :-(
Severity set to `wishlist' from `grave'
> quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(adm
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.9
> package libportaudio2 libportaudiocpp0 portaudio19 portaudio19-dev
> portaudio19-doc
Ignoring bugs not assigned to: portaudio19-doc portaudio19 portaudio19-dev
libportaudiocpp0 libp
Your message dated Thu, 25 Oct 2007 06:17:08 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#447819: fixed in portaudio19 19+svn20071022-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
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.10.9
> package wammu
Ignoring bugs not assigned to: wammu
> severity 447794 normal
Bug#447794: wammu: error at start
Severity set to `normal' from `grave'
>
End of message, stopping proces
On 24/10/07 at 07:18 +1000, Jamie Wilkinson wrote:
> This one time, at band camp, Lucas Nussbaum wrote:
> >On 09/10/07 at 14:52 +0530, Kartik Mistry wrote:
> >> On 10/9/07, Lucas Nussbaum <[EMAIL PROTECTED]> wrote:
> >> > > >
> >> > > >This should probably be replaced by
> >> > > >http://jdolan.dy
84 matches
Mail list logo
