Your message dated Sun, 31 Mar 2002 09:00:24 +1000
with message-id <[EMAIL PROTECTED]>
and subject line fixed in new maintainer upload
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 res
Your message dated Sun, 31 Mar 2002 08:54:36 +1000
with message-id <[EMAIL PROTECTED]>
and subject line closed in new maintainer upload
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 re
Your message dated Sat, 30 Mar 2002 17:03:04 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#136268: fixed in logtrend-snortagent 0.81-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 i
Your message dated Sat, 30 Mar 2002 17:02:43 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#135473: fixed in logtrend-linuxagent 0.81-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 i
Your message dated Sat, 30 Mar 2002 16:47:30 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#135532: fixed in logtrend-visuapache 0.81-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 i
Your message dated Sat, 30 Mar 2002 17:02:36 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#135471: fixed in logtrend-httpagent 0.81-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
Your message dated Sat, 30 Mar 2002 17:02:15 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#135468: fixed in logtrend-complexalarm 0.81-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
Your message dated Sat, 30 Mar 2002 17:02:57 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#135472: fixed in logtrend-snmpagent 0.81-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
Your message dated Sat, 30 Mar 2002 17:02:57 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#135106: fixed in logtrend-snmpagent 0.81-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
Your message dated Sat, 30 Mar 2002 17:02:50 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#135467: fixed in logtrend-mailbridge 0.81-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 i
Your message dated Sat, 30 Mar 2002 17:03:11 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134907: fixed in logtrend-storageserver 0.81-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 cas
Your message dated Sat, 30 Mar 2002 17:03:19 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134653: fixed in logtrend-visuengine 0.81-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 i
Your message dated Sat, 30 Mar 2002 17:02:43 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#133985: fixed in logtrend-linuxagent 0.81-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 i
Your message dated Sat, 30 Mar 2002 17:03:04 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#128197: fixed in logtrend-snortagent 0.81-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 i
Your message dated Sat, 30 Mar 2002 17:02:43 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#130985: fixed in logtrend-linuxagent 0.81-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 i
Accepted:
logtrend-doc_0.81-3.diff.gz
to pool/main/l/logtrend-doc/logtrend-doc_0.81-3.diff.gz
logtrend-doc_0.81-3.dsc
to pool/main/l/logtrend-doc/logtrend-doc_0.81-3.dsc
logtrend-doc_0.81-3_i386.deb
to pool/main/l/logtrend-doc/logtrend-doc_0.81-3_i386.deb
Announcing to debian-devel-changes@l
Your message dated Sat, 30 Mar 2002 06:32:09 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#140551: fixed in jikespg 1.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 now your
Accepted:
jikespg_1.3-1.diff.gz
to pool/main/j/jikespg/jikespg_1.3-1.diff.gz
jikespg_1.3-1.dsc
to pool/main/j/jikespg/jikespg_1.3-1.dsc
jikespg_1.3-1_i386.deb
to pool/main/j/jikespg/jikespg_1.3-1_i386.deb
jikespg_1.3.orig.tar.gz
to pool/main/j/jikespg/jikespg_1.3.orig.tar.gz
Announcing to
Package: jikespg
Version: 1.2-2
jikespg fails to build from source on i386, when doing a binary-all build.
I am just filing this bug to notify you that I failed to build your
package from source, using a very simplistic program called pbuilder.
at least debhelper is missing from build-depends f
19 matches
Mail list logo
