Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Your message dated Wed, 2 Aug 2000 15:17:16 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closed in debian-policy 3.2.0.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 now your res
Processing commands for [EMAIL PROTECTED]:
> severity 15709 fixed
Bug#15709: packaging-manual dwww entry
Severity set to `fixed'.
> severity 17369 fixed
Bug#17369: Additional info to packaging 8.3.
Severity set to `fixed'.
> severity 22935 fixed
Bug#22935: [REJECTED] Do not make hardlinks to con
Can I ask a question ?
In <[EMAIL PROTECTED]>, on Thu, 27 Jul 2000 00:21:54 -0500,
Branden Robinson <[EMAIL PROTECTED]> wrote:
> It has to do with app-defaults files. Current Debian policy says these
> can't be conffiles, so they go in /usr/X11R6/lib/X11/app-defaults.
>
> Well, upstream has c
24 matches
Mail list logo