Package: xfonts-knickers
Version: 0.0.1-4
Severity: grave
Unpacking replacement xfonts-knickers ...
usage error: one or more font directories must be specified
Usage: update-fonts-alias DIRECTORY ...
update-fonts-alias { -h | --help }
This program combines X font alias information from
Package: php-net-dime
Version: 0.3-2
Severity: grave
Justification: renders package unusable
/usr/share/php/Net/DIME.php missing from package in stable release (0.3-1)
However, the file is present in the current package in testing (0.3-2).
As this file contains the actual code in this php
Hi Tim,
On Tuesday 20 of November 2007, Tim Richardson wrote:
your new packages do not demonstrate the bug. I successfully opened a
file; it was not destroyed.
Good - now could you please test if the file is correctly saved?
- open the file
- do a slight modification
- save
Is it OK after
Please close this bug.
I have reset the password following the advice on the page
http://www.trustix.org/wiki/index.php/MySQL_recover_root_password
After it I was able to complete dpkg-reconfigure sympa.
After upgrading I've noticed several new problems, but I will report
them later as
Mouse still moves... sounds like my problem:
Holy moly, now Hold down ALT, press TAB locks the whole system.
Even the linux-doc-2.6.*/Documentation/sysrq.txt.gz keys can't break
out of it very well often.
At the the time I was in
-xdm
`-sh /home/jidanni/.xsession
|-icewm-session
Package: syslog-ng
Version: 1.6.5-2.2
Severity: grave
Justification: renders package unusable
Hi,
I'm using syslog-ng to have a bunch of webservers log to remote
syslog-servers. I have defined them on the webservers like this;
destination remote_logging { tcp(10.10.10.1 port(1999)); };
I downgraded as the reporter did, and the problem went away.
So get rid of that new version fast please.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I downgraded as the reporter did, and the problem went away.
So get rid of that new version fast please.
No, this new version fixes lots of other problems.
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Well, I'm glad that it fixes so many other problems.
Me and the other fellow cannot use it.
Therefore there are grave customer satisfaction issues raised.
Good thing I am now going on a trip and will see what is cooked up
upon my return.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Dan Jacobson wrote:
Well, I'm glad that it fixes so many other problems.
Me and the other fellow cannot use it.
Therefore there are grave customer satisfaction issues raised.
Good thing I am now going on a trip and will see what is cooked up
upon my return.
Please stop filling people bug
Hi,
Bugs #442866 (in package gnump3d) and #442869 (in package listadmin)
were caused by bug #377385 in package perl-modules. This has been
since fixed and closed (in version 5.8.8-9), and therefore these bugs
should probably be closed too.
Thanks,
Vasilis
--
Vasilis Vasaitis
A man is well
Package: audacious
Version: 1.4.0-1
Severity: grave
Currently audacious plays a song for 30s or something like that and then
die with:
Xlib: sequence lost (0x27e9b 0x183ff) in reply type 0x0!
The program 'audacious' received an X Window System error.
This probably reflects a bug in the program.
Package: xserver-xorg
Version: 1:7.2-5
Severity: serious
--- Please enter the report below this line. ---
I use unstable and in some recent upgrade (I think yesterday, or the day
before that), all fonts became unreadable. When I start xterm in
.xsession, the font is readable, but whenever I
At 1195655903 time_t, Julien Danjou wrote:
Currently audacious plays a song for 30s or something like that and then
die with:
Xlib: sequence lost (0x27e9b 0x183ff) in reply type 0x0!
The program 'audacious' received an X Window System error.
This probably reflects a bug in the program.
The
Your message dated Wed, 21 Nov 2007 16:13:16 +0100
with message-id [EMAIL PROTECTED]
and subject line
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
Bug
Ondrej Certik wrote:
Package: xserver-xorg
Version: 1:7.2-5
Severity: serious
I use unstable and in some recent upgrade (I think yesterday, or the day
before that), all fonts became unreadable. When I start xterm in
.xsession, the font is readable, but whenever I start gnome-session, or
kde, or
reassign 452268 xserver-xorg-video-intel 2:2.2.0-1
forcemerge 439210 452268
kthxbye
On Wed, Nov 21, 2007 at 15:19:45 +0100, Ondrej Certik wrote:
I use unstable and in some recent upgrade (I think yesterday, or the day
before that), all fonts became unreadable. When I start xterm in
.xsession,
Processing commands for [EMAIL PROTECTED]:
reassign 452268 xserver-xorg-video-intel 2:2.2.0-1
Bug#452268: all fonts are unreadable
Bug reassigned from package `xserver-xorg' to `xserver-xorg-video-intel'.
forcemerge 439210 452268
Bug#439210: Display corruption with EXA
Bug#452268: all fonts
It seems this is a result of ABI changes in Audacious 1.4, and a new
upstream version of xmms-crossfade (v0.3.13) has been released to
address this.
http://www.eisenlohr.org/xmms-crossfade/news.html
Bye,
--
jonathaN
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Your message dated Wed, 21 Nov 2007 15:17:06 +
with message-id [EMAIL PROTECTED]
and subject line Bug#451505: fixed in erlang 1:11.b.5dfsg-10
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
And how does that relate to my report?
On Wednesday 21 November 2007 16:18:04 Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the kvm-source package:
#438995: kvm-source: needs CONFIG_HIGHMEM64G in kernel
It has been
On Wed, 2007-11-21 at 16:48 +0100, Johannes Graumann wrote:
And how does that relate to my report?
You should be able to compile kvm modules for the debian stock kernels
now, because it no longer needs CONFIG_HIGHMEM64G set in the kernel.
Perhaps i've misunderstood your bugreport. Do you need
Processing commands for [EMAIL PROTECTED]:
severity 452262 serious
Bug#452262: dpkg-shlibdeps: Undefined subroutine main::capit.
Severity set to `serious' from `important'
quit
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Hi Jan. A small modification works. The file was saved successfully and
reopens just fine.
By the way, the bug I saw was not that files were zeroed out (ie, they
were not filled with zero bytes), but that the file was replaced with a
0 byte length file.
On Wed, 2007-11-21 at 10:47 +0100, Jan
Package: lastfmsubmitd
Version: 0.36-1
Severity: serious
Tags: patch
Subject says all, I'm attaching a trivial patch.
File /home/adeodato/bin/lastfm_submit_files, line 52, in main
client.submit_many(tracks)
File /var/lib/python-support/python2.4/lastfm/client.py, line 73, in
submit_many
Processing commands for [EMAIL PROTECTED]:
package azureus
Ignoring bugs not assigned to: azureus
tag 449176 confirmed
Bug#449176: azureus: Downloads very slowly with GIJ JVM
There were no tags set.
Tags added: confirmed
severity 449176 serious
Bug#449176: azureus: Downloads very slowly with
Processing commands for [EMAIL PROTECTED]:
severity 449002 important
Bug#449002: postgresql-8.3_8.3~beta2-1(alpha/experimental): FTBFS: test failures
Severity set to `important' from `serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
I note your original report shows a version of 0.4.0-7+b1. I don't
recognize the +b1 - what does that signify?
No idea. That's more .deb packaging detail than I know.
I also see you're running a 64 bit system, whereas I have a 32 bit
system, and I suspect that's the real problem.
Likely
severity 449002 important
thanks
Hi!
I fixed the FTBFS, but the actual cause of the math errors is still
unfixed and under investigation. It's apparently regressions in glibc
and gcc-4.2 on alpha. I should get access to an alpha box soon to do
some further investigations. Until then I keep this
Adeodato Simó writes:
Thanks, and sorry I didn't find time to test lastfmsubmitd before it
migrated to testing.
I should have had something to test with that *doesn't* already use the
marshaller... oops. What are you working on, anyway? (Feel free to reply
off-bug.)
--
things change.
[EMAIL
Package: libvlc0-dev
Version: 0.8.6.c-3+b1
Severity: grave
Justification: renders package unusable
Hi,
It's impossible to build the tuto found here :
http://doc.qtfr.org/post/2007/02/21/Integration-de-VLC
make
g++ -o tuto_vlc tuto_vlc.o-L/usr/lib -lvlc -lQtGui -lQtCore -lpthread
* Daniel Smolik [EMAIL PROTECTED] [2007-11-20 11:35]:
I read this bug report, but I mean that this is problem nfsd.
I just transfered 9 GB from my PC to the N2100 without any problems.
I used an unreleased kernel (2.6.23 plus some patches) though.
Can you tell me a) how much data you usually
package: iceweasel
version: 2.0.0.9-1
severity: serious
I noticed a build failure on the mips buildd build and it appeared to
be to be much the same issue that broke other mozilla related apps.
I tried to reproduce in my amd64 sid chroot but instead of the failure
from the buildd I got a
Your message dated Wed, 21 Nov 2007 20:47:05 +
with message-id [EMAIL PROTECTED]
and subject line Bug#451902: fixed in empathy 0.21.2-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
* Martin Michlmayr [EMAIL PROTECTED] [2007-11-21 21:43]:
I just transfered 9 GB from my PC to the N2100 without any problems.
I used an unreleased kernel (2.6.23 plus some patches) though.
OK, I see it with 2.6.22... and it happens quite often too.
--
Martin Michlmayr
http://www.cyrius.com/
Martin Michlmayr napsal(a):
* Daniel Smolik [EMAIL PROTECTED] [2007-11-20 11:35]:
I read this bug report, but I mean that this is problem nfsd.
I just transfered 9 GB from my PC to the N2100 without any problems.
I used an unreleased kernel (2.6.23 plus some patches) though.
Great, can you
* Decklin Foster [Wed, 21 Nov 2007 15:16:11 -0500]:
I should have had something to test with that *doesn't* already use the
marshaller... oops.
Hehe.
What are you working on, anyway? (Feel free to reply off-bug.)
I use lastfmsubmitd for Minirok, a music player I've written.
Martin Michlmayr napsal(a):
* Daniel Smolik [EMAIL PROTECTED] [2007-11-21 22:00]:
I just transfered 9 GB from my PC to the N2100 without any problems.
I used an unreleased kernel (2.6.23 plus some patches) though.
Great, can you give me link to this patchset ?
Only if you have (or can make)
Martin Michlmayr napsal(a):
* Martin Michlmayr [EMAIL PROTECTED] [2007-11-21 21:43]:
I just transfered 9 GB from my PC to the N2100 without any problems.
I used an unreleased kernel (2.6.23 plus some patches) though.
OK, I see it with 2.6.22... and it happens quite often too.
And with
Processing commands for [EMAIL PROTECTED]:
close 367730 0.99-3
Bug#367730: libroxen-imho: must use invoke-rc.d
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug marked as fixed in version 0.99-3, send any further explanations to Lars
Wirzenius [EMAIL PROTECTED]
quit
* Daniel Smolik [EMAIL PROTECTED] [2007-11-21 22:00]:
I just transfered 9 GB from my PC to the N2100 without any problems.
I used an unreleased kernel (2.6.23 plus some patches) though.
Great, can you give me link to this patchset ?
Only if you have (or can make) a serial console for your
Your message dated Wed, 21 Nov 2007 21:17:10 +
with message-id [EMAIL PROTECTED]
and subject line Bug#447366: fixed in zsnes 1.510-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
Package: git-core
Version: 1:1.5.3.4-1
Severity: grave
Justification: renders package unusable
uprading git-core gives me this error message:
E: /var/cache/apt/archives/git-core_1%3a1.5.3.6-1_i386.deb: trying to overwrite
`/usr/share/perl5/Error.pm', which is also in package liberror-perl
I
* Daniel Smolik [EMAIL PROTECTED] [2007-11-21 22:03]:
I used an unreleased kernel (2.6.23 plus some patches) though.
OK, I see it with 2.6.22... and it happens quite often too.
And with 2.6.23 is it OK ?
Yes, seems to work with an unpatched 2.6.23.
--
Martin Michlmayr
http://www.cyrius.com/
Your message dated Wed, 21 Nov 2007 22:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#451407: fixed in bitpim 1.0.2.dfsg.1-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
Processing commands for [EMAIL PROTECTED]:
tags 451415 + pending
Bug#451415: emile: FTBFS: Syntax error before struct
There were no tags set.
Tags added: pending
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
Your message dated Wed, 21 Nov 2007 22:46:32 +
with message-id [EMAIL PROTECTED]
and subject line Bug#451400: fixed in cwidget 0.5.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
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.11
forcemerge 452111 452324
Bug#452111: git-core provides an existing file - uninstallable package
Bug#452324: git-core upgrade conflicts with perl package
Bug#452077: git-core: could
Your message dated Wed, 21 Nov 2007 22:32:07 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452234: fixed in xfonts-knickers 0.0.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
Your message dated Wed, 21 Nov 2007 22:49:27 +
with message-id [EMAIL PROTECTED]
and subject line Bug#448508: fixed in glibc 2.7-0exp9
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 Wed, 21 Nov 2007 22:49:27 +
with message-id [EMAIL PROTECTED]
and subject line Bug#449198: fixed in glibc 2.7-0exp9
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
It FTBFS on ia64 arch:
http://buildd.debian.org/fetch.cgi?pkg=libfoundation1.0;ver=1.0.84-2;arch=ia64;stamp=1195344917
Please fix it. Thanks!
--
Marco Rodrigues
http://Marco.Tondela.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
On Thursday 22 November 2007, Marco Rodrigues wrote:
It FTBFS on ia64 arch:
http://buildd.debian.org/fetch.cgi?pkg=libfoundation1.0;ver=1.0.84-2;arch=i
a64;stamp=1195344917
Please fix it. Thanks!
You forgot to add your patch.
/Sune
--
Man, how might I do for debugging the shell from
Processing commands for [EMAIL PROTECTED]:
# Automatically generated email from bts, devscripts version 2.10.9
severity 452338 serious
Bug#452338: dpkg-dev: should ignore private libraries
Severity set to `serious' from `normal'
End of message, stopping processing here.
Please contact me if
Package: dpkg-dev
Version: 1.14.9
Severity: serious
From my build log:
dh_compress -pkzenexplorer -X .dcl -X .docbook -X -license -X .tag -X .sty -X
.el
dh_fixperms -pkzenexplorer
dh_makeshlibs -pkzenexplorer
dh_installdeb -pkzenexplorer
dh_perl -pkzenexplorer
dh_shlibdeps -pkzenexplorer
Your message dated Thu, 22 Nov 2007 00:32:01 +
with message-id [EMAIL PROTECTED]
and subject line Bug#418312: fixed in phpix 2.0.2-7
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 Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452078: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452080: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452077: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452078: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452080: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452078: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452324: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452077: fixed in git-core 1:1.5.3.6-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
Any schedule on when this fix will be included in debian? This is preventing a
security fix on ardour [1]. Note that there is no explicit mention in the bug
log but there was some talk at debian-multimedia about it (scons fails while
checking for pkgconfig).
[1] http://bugs.debian.org/446597
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452078: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452111: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452111: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452111: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452080: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452080: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452111: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452077: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452111: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452080: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452077: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452078: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452324: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452324: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452324: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452077: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 00:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#452324: fixed in git-core 1:1.5.3.6-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
Your message dated Thu, 22 Nov 2007 01:17:02 +
with message-id [EMAIL PROTECTED]
and subject line Bug#449163: fixed in gnustep-base 1.14.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
On Mon, Nov 19, 2007 at 08:55:16PM +0100, Arthur de Jong wrote:
On Mon, 2007-11-19 at 20:33 +0100, Brice Goglin wrote:
Does it help if you add
Option AccelMethod XAA
in the above section? EXA is enabled by default in 2.2.0.
But there is at least one known problem with fonts and EXA.
Your message dated Thu, 22 Nov 2007 03:47:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#445935: fixed in filelight 1.0-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 Wed, 21 Nov 2007 21:47:58 -0800
with message-id [EMAIL PROTECTED]
and subject line Bugs accidentally left open.
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, 21 Nov 2007 21:47:58 -0800
with message-id [EMAIL PROTECTED]
and subject line Bugs accidentally left open.
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
Package: cfengine2
Version: 2.1.22-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: proposed-orphan
Hi,
While reviewing packages that were not included in Etch, your package came
up as a package that should maybe be orphaned by its maintainer, because:
* several release critical bugs
Processing commands for [EMAIL PROTECTED]:
severity 452102 serious
Bug#452102: remove this package as its useless today?
Severity set to `serious' from `normal'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator,
Processing commands for [EMAIL PROTECTED]:
severity 452355 serious
Bug#452355: libgdal1-1.4.0: GDAL 1.4.3 retracted contains an ABI incompatability
Severity set to `serious' from `normal'
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
Processing commands for [EMAIL PROTECTED]:
tags 451432 +patch
Bug#451432: ifplugd: FTBFS on amd64: Conflicting types for loff_t
There were no tags set.
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
tags 451432 +patch
thanks
Adapting a patch from Ubuntu (which was likely tested on AMD64). I
don't have a non-i386 sid, it would be good if someone can give this a
spin and comment here. Please feel free to do an NMU if you can test
this (not just for the FTBFS, but an 'install and use' test).
Your message dated Thu, 22 Nov 2007 08:20:46 +0100
with message-id [EMAIL PROTECTED]
and subject line Bug#452311: libvlc0-dev: build failed because of libtheora
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
93 matches
Mail list logo
