Package: gfpoken
version: 0.30-5
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080103 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on amd64.
Relevant part:
checking whether we are cross compiling
Hi,
Thanks for reporting this. However, I don't understand what's wrong. I
hope you have some of the logs from the build process, or can regenerate
them (in particular config.log).
On Thu, Jan 03, 2008 at 01:11:22PM +0100, Lucas Nussbaum wrote:
checking for imlib-config...
a7xpg_0.11.dfsg1-3_amd64.changes uploaded successfully to localhost
along with the files:
a7xpg_0.11.dfsg1-3.dsc
a7xpg_0.11.dfsg1-3.diff.gz
a7xpg_0.11.dfsg1-3_amd64.deb
a7xpg-data_0.11.dfsg1-3_all.deb
Greetings,
Your Debian queue daemon
titanion_0.3.dfsg1-2_amd64.changes uploaded successfully to localhost
along with the files:
titanion_0.3.dfsg1-2.dsc
titanion_0.3.dfsg1-2.diff.gz
titanion_0.3.dfsg1-2_amd64.deb
titanion-data_0.3.dfsg1-2_all.deb
Greetings,
Your Debian queue daemon
Accepted:
titanion-data_0.3.dfsg1-2_all.deb
to pool/main/t/titanion/titanion-data_0.3.dfsg1-2_all.deb
titanion_0.3.dfsg1-2.diff.gz
to pool/main/t/titanion/titanion_0.3.dfsg1-2.diff.gz
titanion_0.3.dfsg1-2.dsc
to pool/main/t/titanion/titanion_0.3.dfsg1-2.dsc
titanion_0.3.dfsg1-2_amd64.deb
tumiki-fighters_0.2.dfsg1-2_amd64.changes uploaded successfully to localhost
along with the files:
tumiki-fighters_0.2.dfsg1-2.dsc
tumiki-fighters_0.2.dfsg1-2.diff.gz
tumiki-fighters_0.2.dfsg1-2_amd64.deb
tumiki-fighters-data_0.2.dfsg1-2_all.deb
Greetings,
Your Debian queue
val-and-rick_0.1a.dfsg1-2_amd64.changes uploaded successfully to localhost
along with the files:
val-and-rick_0.1a.dfsg1-2.dsc
val-and-rick_0.1a.dfsg1-2.diff.gz
val-and-rick_0.1a.dfsg1-2_amd64.deb
val-and-rick-data_0.1a.dfsg1-2_all.deb
Greetings,
Your Debian queue daemon
Accepted:
a7xpg-data_0.11.dfsg1-3_all.deb
to pool/main/a/a7xpg/a7xpg-data_0.11.dfsg1-3_all.deb
a7xpg_0.11.dfsg1-3.diff.gz
to pool/main/a/a7xpg/a7xpg_0.11.dfsg1-3.diff.gz
a7xpg_0.11.dfsg1-3.dsc
to pool/main/a/a7xpg/a7xpg_0.11.dfsg1-3.dsc
a7xpg_0.11.dfsg1-3_amd64.deb
to
Accepted:
gunroar-data_0.15.dfsg1-3_all.deb
to pool/main/g/gunroar/gunroar-data_0.15.dfsg1-3_all.deb
gunroar_0.15.dfsg1-3.diff.gz
to pool/main/g/gunroar/gunroar_0.15.dfsg1-3.diff.gz
gunroar_0.15.dfsg1-3.dsc
to pool/main/g/gunroar/gunroar_0.15.dfsg1-3.dsc
gunroar_0.15.dfsg1-3_amd64.deb
to
Accepted:
mu-cade-data_0.11.dfsg1-2_all.deb
to pool/main/m/mu-cade/mu-cade-data_0.11.dfsg1-2_all.deb
mu-cade_0.11.dfsg1-2.diff.gz
to pool/main/m/mu-cade/mu-cade_0.11.dfsg1-2.diff.gz
mu-cade_0.11.dfsg1-2.dsc
to pool/main/m/mu-cade/mu-cade_0.11.dfsg1-2.dsc
mu-cade_0.11.dfsg1-2_amd64.deb
to
torus-trooper_0.22.dfsg1-2_amd64.changes uploaded successfully to localhost
along with the files:
torus-trooper_0.22.dfsg1-2.dsc
torus-trooper_0.22.dfsg1-2.diff.gz
torus-trooper_0.22.dfsg1-2_amd64.deb
torus-trooper-data_0.22.dfsg1-2_all.deb
Greetings,
Your Debian queue daemon
Your message dated Thu, 03 Jan 2008 13:32:07 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458638: fixed in mu-cade 0.11.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:32:03 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458277: fixed in a7xpg 0.11.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:32:08 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458637: fixed in titanion 0.3.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:32:08 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458283: fixed in titanion 0.3.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:32:07 +
with message-id [EMAIL PROTECTED]
and subject line Bug#449449: fixed in mu-cade 0.11.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:32:05 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458278: fixed in gunroar 0.15.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:32:08 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458283: fixed in titanion 0.3.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:32:08 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458637: fixed in titanion 0.3.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:32:07 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458282: fixed in mu-cade 0.11.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:47:06 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458280: fixed in tumiki-fighters 0.2.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:47:06 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458280: fixed in tumiki-fighters 0.2.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:47:08 +
with message-id [EMAIL PROTECTED]
and subject line Bug#456024: fixed in val-and-rick 0.1a.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:47:05 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458642: fixed in torus-trooper 0.22.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:47:05 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458642: fixed in torus-trooper 0.22.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:47:06 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458633: fixed in tumiki-fighters 0.2.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:47:05 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458279: fixed in torus-trooper 0.22.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:47:05 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458279: fixed in torus-trooper 0.22.dfsg1-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
Your message dated Thu, 03 Jan 2008 13:47:06 +
with message-id [EMAIL PROTECTED]
and subject line Bug#458633: fixed in tumiki-fighters 0.2.dfsg1-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
Hi!
I think this new release is important because it will bring us with the new
nvidia-cg-toolkit 2.0 when updated in Debian (I already filed a bug about it).
* Added setDebugOutputEnabled function to Log class
* gcc 4.3 fix - needs C stdlib includes explicitly now where used
Dependencies
Is there a way prepared, to allow some different Tests (short words)?
___
Pkg-games-devel mailing list
Pkg-games-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
wormux_0.8beta4-1_powerpc.changes uploaded successfully to localhost
along with the files:
wormux_0.8beta4-1.dsc
wormux_0.8beta4.orig.tar.gz
wormux_0.8beta4-1.diff.gz
wormux-data_0.8beta4-1_all.deb
wormux_0.8beta4-1_powerpc.deb
Greetings,
Your Debian queue daemon
Accepted:
wormux-data_0.8beta4-1_all.deb
to pool/main/w/wormux/wormux-data_0.8beta4-1_all.deb
wormux_0.8beta4-1.diff.gz
to pool/main/w/wormux/wormux_0.8beta4-1.diff.gz
wormux_0.8beta4-1.dsc
to pool/main/w/wormux/wormux_0.8beta4-1.dsc
wormux_0.8beta4-1_powerpc.deb
to
33 matches
Mail list logo