Hello all,
I am currently woking in the lirc project and need up to date lirc
packages, as Tom Lees is somewhat MIA Martin Michlmayr sujested taking
the packages from him.
Then what should I do:
1) NMU: even though policy talks agains NMU's making big changes?
2) Adopt the package (what if Tom
Your message dated Mon, 16 Apr 2001 23:55:49 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closed in perforate 1.0-8.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 respon
Your message dated Mon, 16 Apr 2001 23:55:49 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closed in perforate 1.0-8.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 respon
Your message dated Mon, 16 Apr 2001 23:55:24 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closed in perforate 1.0-9
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 responsi
Your message dated Mon, 16 Apr 2001 23:55:49 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closed in perforate 1.0-8.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 respon
Your message dated Mon, 16 Apr 2001 23:55:24 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closed in perforate 1.0-9
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 responsi
On Mon, Apr 16, 2001 at 05:26:06PM +0100, Philip Blundell wrote:
> Package: zed
> Version: 1.0.5-3
> Severity: serious
>
> This package needs to Build-Depend on debmake.
>
> debstd README
> make: debstd: Command not found
> make: *** [binary-arch] Error 127
A fix is in Incoming.
Thanks,
Mate
Your message dated Mon, 16 Apr 2001 14:52:37 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#93210: fixed in ascii 3.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 re
Your message dated Mon, 16 Apr 2001 14:52:37 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#91375: fixed in ascii 3.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 re
Your message dated Mon, 16 Apr 2001 14:52:37 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#91375: fixed in ascii 3.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 re
Your message dated Mon, 16 Apr 2001 14:52:37 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#91110: fixed in ascii 3.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 re
Your message dated Mon, 16 Apr 2001 14:52:37 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#90947: fixed in ascii 3.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 re
Your message dated Mon, 16 Apr 2001 14:52:37 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#72489: fixed in ascii 3.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 re
Your message dated Mon, 16 Apr 2001 14:52:36 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#41184: fixed in ascii 3.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 re
tag 41700 + fixed
tag 89534 + fixed
quit
This message was generated automatically in response to a
non-maintainer upload. The .changes file follows.
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Mon, 16 Apr 2001 17:47:56 +0200
Source: perforate
Binary: perforate
Architecture: source i38
Installing:
perforate_1.0-9_i386.deb
to pool/main/p/perforate/perforate_1.0-9_i386.deb
perforate_1.0-9.dsc
to pool/main/p/perforate/perforate_1.0-9.dsc
perforate_1.0-9.diff.gz
to pool/main/p/perforate/perforate_1.0-9.diff.gz
Announcing to debian-devel-changes@lists.debian.org
Setting bugs to
There are disparities between your recently installed upload and the
override file for the following file(s):
perforate_1.0-9_i386.deb: section is overridden from misc to utils.
perforate_1.0-9_i386.deb: priority is overridden from extra to optional.
Either the package or the override file is inc
Package: zed
Version: 1.0.5-3
Severity: serious
This package needs to Build-Depend on debmake.
debstd README
make: debstd: Command not found
make: *** [binary-arch] Error 127
It does happen everytime when you mangle your userdb. How to reproduce with
a clean new install of kICQ:
1) Start kICQ. Select "old ICQ#", "LAN/firewall", "no socks" (I'm NATted),
"110201214", appropriate password, "save passwd". It will "register" your
ICQ# (what's there to register if you
19 matches
Mail list logo
