enet_1.1-2_amd64.changes uploaded successfully to localhost
along with the files:
enet_1.1-2.dsc
enet_1.1-2.diff.gz
libenet1_1.1-2_amd64.deb
libenet1-dev_1.1-2_amd64.deb
libenet-dev_1.1-2_all.deb
Greetings,
Your Debian queue daemon
Your message dated Thu, 20 Sep 2007 10:41:42 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#443217: lincity-ng: please provide a .desktop-file
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
Accepted:
ri-li-data_2.0.0-4_all.deb
to pool/main/r/ri-li/ri-li-data_2.0.0-4_all.deb
ri-li_2.0.0-4.diff.gz
to pool/main/r/ri-li/ri-li_2.0.0-4.diff.gz
ri-li_2.0.0-4.dsc
to pool/main/r/ri-li/ri-li_2.0.0-4.dsc
ri-li_2.0.0-4_amd64.deb
to pool/main/r/ri-li/ri-li_2.0.0-4_amd64.deb
Override
Your message dated Thu, 20 Sep 2007 09:02:27 +
with message-id [EMAIL PROTECTED]
and subject line Bug#442029: fixed in opencity 0.0.4stable-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, 20 Sep 2007 09:02:08 +
with message-id [EMAIL PROTECTED]
and subject line Bug#414348: fixed in enet 1.1-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 Thu, 20 Sep 2007 09:02:23 +
with message-id [EMAIL PROTECTED]
and subject line Bug#440909: fixed in lincity-ng 1.1.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
Your message dated Thu, 20 Sep 2007 09:02:27 +
with message-id [EMAIL PROTECTED]
and subject line Bug#442034: fixed in opencity 0.0.4stable-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, 20 Sep 2007 09:02:47 +
with message-id [EMAIL PROTECTED]
and subject line Bug#432171: fixed in ri-li 2.0.0-4
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
Accepted:
opencity_0.0.4stable-3.diff.gz
to pool/main/o/opencity/opencity_0.0.4stable-3.diff.gz
opencity_0.0.4stable-3.dsc
to pool/main/o/opencity/opencity_0.0.4stable-3.dsc
opencity_0.0.4stable-3_amd64.deb
to pool/main/o/opencity/opencity_0.0.4stable-3_amd64.deb
Override entries for your
Accepted:
lincity-ng-data_1.1.1-1_all.deb
to pool/main/l/lincity-ng/lincity-ng-data_1.1.1-1_all.deb
lincity-ng_1.1.1-1.diff.gz
to pool/main/l/lincity-ng/lincity-ng_1.1.1-1.diff.gz
lincity-ng_1.1.1-1.dsc
to pool/main/l/lincity-ng/lincity-ng_1.1.1-1.dsc
lincity-ng_1.1.1-1_amd64.deb
to
Package: pixfrogger
Version: 1.0-1
Severity: wishlist
Hello,
after having played pixfrogger, I've in my $HOME:
=
[EMAIL PROTECTED]:~$ ls ~/ | grep PiX
PiXJuegos
[EMAIL PROTECTED]:~$ find ~/PiXJuegos
/home/luca/PiXJuegos
/home/luca/PiXJuegos/PiXFrogger
Hello,
I managed to get the backtrace. This bug is annoying, as it means that
I cannot do any mission in the game. I'll have to do some trading and
exploration while you have a look :)
Note that when vegastrike is in that state, killing it normally wouldn't
work. I tried a number of signals,
Package: vegastrike-data
Version: 0.4.3-3
Severity: minor
Tags: patch
Hello,
I experienced the following error:
=
/etc/cron.daily/man-db:
mandb: warning: /usr/share/man/man1/vslauncher.1 is a dangling symlink
mandb: warning: /usr/share/man/man1/vsinstall.1 is a dangling symlink
mandb:
Processing commands for [EMAIL PROTECTED]:
block 360149 by 421632
Bug#421632: Unsafe handling of unicode in wxGetUserName
Bug#360149: scorched3d: Segmentation fault on AMD64
Was not blocked by any bugs.
Bug#441823: scorched3d: SEGFAULT on start
Blocking bugs of 360149 added: 421632
block
Your message dated Fri, 21 Sep 2007 00:35:19 +0200
with message-id [EMAIL PROTECTED]
and subject line openarena-data: New upstream release 0.7.0
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
15 matches
Mail list logo