Package: twinkle
Version: 1:0.9-5
Followup-For: Bug #402509
Twinkle also freezes when receiving a call with this message:
twinkle: ERROR: Server sent error -1: Received invalid XML
markup: unexpected character at 2:2
Hope it helps because it's a great SIP softphone, perhaps the best for
Linux.
digikam 0.9.0 (final) is currently available in the experimental
distribution. I would suggest that you both upgrade to 0.9.0 and advise
if this issue is still a problem
Is there a version of digikamimageplugins that
can be used with digikam 0.9.0 and libexiv2-0.12?
Thanks,
Yitz
--
To UNSUBSC
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> # bogus severity justification, who runs vlc as root? :P
> severity 405425 grave
Bug#405425: FrSIRT/ADV-2007-0026: vlc: "cdio_log_handler()" and
"vcd_log_handler()" Format String Vul
On Wed, 2007-01-03 at 13:10 -0800, Jason Cutting wrote:
> How does one install gzip 1.3.9-2 while apt is broken?
The phrase "while apt is broken" doesn't really convey much useful
information, so I'm not at all sure what problem you're trying to
overcome.
Generally, you can download a specific .d
This one time, at band camp, Jason Cutting said:
> How does one install gzip 1.3.9-2 while apt is broken?
wget, ar, and tar. Although you may have to do the uncompression on
another machine.
--
-
| ,''`.
Processing commands for [EMAIL PROTECTED]:
> severity 382252 important
Bug#382252: ImportError: No module named bdiff
Severity set to `important' from `serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
severity 382252 important
thanks
On Wed, Jan 03, 2007 at 01:04:37PM +0100, Pierre Habouzit wrote:
> # sorry pal but mishandling *.pyc files is a policy violation.
> severity 382252 serious
> thanks
> > > $ ls -l /usr/lib/python*/site-packages/mercurial/
> > [.. lots of *.pyc ..]
> > > Can you
Processing commands for [EMAIL PROTECTED]:
> tags 403346 + pending
Bug#403346: installation-report: Creates mails that are way too big and never
make the list
There were no tags set.
Tags added: pending
> tags 405102 + pending
Bug#405102: installation-report: Include info on which PCI device is
Processing commands for [EMAIL PROTECTED]:
> severity 405354 important
Bug#405354: inn2: contains non-free files
Severity set to `important' from `serious'
> severity 405363 important
Bug#405363: openswan: contains non-free files
Severity set to `important' from `serious'
> thanks, bot
Unknown c
severity 405354 important
severity 405363 important
thanks, bot
Given the clarification provided at
http://www.ietf.org/ietf/IPR/RSA-MD-all , and after discussion with
vorlon on irc, I am downgrading these to important (I actually believe
they are not problems at all, but I will let the respective
Your message dated Thu, 04 Jan 2007 01:17:02 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#393387: fixed in libgcgi 0.9.5.dfsg-2
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is n
Package: aptitude
Version: 0.4.4-1
Severity: grave
aptitude goes dead shortly after etch installed; entire etch
installation appears useless.
I was unable to use aptitude to determine version number; I installed
version number obtained by reading the filename
aptitude_0.4.4-1_i386.deb on pool
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Hommey wrote:
| And what happens if you try this again?
I haven't tried yet.
If there is a need for it I would do further testing. Please tell me
specifically, what kind of information you want me to provide.
caspar
-BEGIN PGP SIGNATURE-
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> severity 405506 important
Bug#405506: aptitude cannot parse package file
Severity set to `important' from `grave'
> # corrupted database, no one else reporting this - fs problem?
> t
On Thursday 04 January 2007 10:19, Yitzchak Gale wrote:
> > digikam 0.9.0 (final) is currently available in the experimental
> > distribution. I would suggest that you both upgrade to 0.9.0 and advise
> > if this issue is still a problem
>
> Is there a version of digikamimageplugins that
> can be u
Package: eog
Version: 2.16.2-1
Severity: grave
Tags: security
Justification: user security hole
This is a user security hole only on systems where the package is
built. Sorry if this doesn't qualify it for the grave severity.
The build process of eog sets the perms of the entire eog-$VERSION
subd
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.27
> severity 405510 important
Bug#405510: Build process sets the eog-$VER directory perms to 777
Severity set to `important' from `grave'
>
End of message, stopping processing here.
Ple
On Thu, Jan 04, 2007 at 02:36:36AM +0100, Caspar Bothmer <[EMAIL PROTECTED]>
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Mike Hommey wrote:
> | And what happens if you try this again?
>
> I haven't tried yet.
>
> If there is a need for it I would do further testing. Please tel
On Wed, Jan 03, 2007 at 11:49:51AM +0100, Marco d'Itri wrote:
> Are there other drivers in this situation?
hey Marco,
Mark Salyzyn's reply on LKML suggests that this problem maybe more
widespread and possibly difficult audit on the kernel side. Could
we do something like change the default block/
101 - 119 of 119 matches
Mail list logo
