Your message dated Mon, 04 Aug 2003 18:02:27 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#203854: fixed in evas 0.6.0-5
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:
evas-demo_0.6.0-5_i386.deb
to pool/main/e/evas/evas-demo_0.6.0-5_i386.deb
evas_0.6.0-5.diff.gz
to pool/main/e/evas/evas_0.6.0-5.diff.gz
evas_0.6.0-5.dsc
to pool/main/e/evas/evas_0.6.0-5.dsc
libevas0-dev_0.6.0-5_i386.deb
to pool/main/e/evas/libevas0-dev_0.6.0-5_i386.deb
libevas0_0
There are disparities between your recently accepted upload and the
override file for the following file(s):
libevas0-dev_0.6.0-5_i386.deb: package says section is devel, override says
libdevel.
Either the package or the override file is incorrect. If you think
the override is correct and the p
Processing commands for [EMAIL PROTECTED]:
> tag 203854 +pending
Bug#203854: evas doesn't build from source
There were no tags set.
Tags added: pending
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bu
tag 203854 +pending
thanks
Just building up. It missed an automake dependency.
--
Francesco P. Lovergine
Your message dated Mon, 04 Aug 2003 16:47:10 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#165842: fixed in kforth 1:1.0.14-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 Mon, 04 Aug 2003 16:47:10 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#103445: fixed in kforth 1:1.0.14-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 Mon, 04 Aug 2003 16:47:10 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#190803: fixed in kforth 1:1.0.14-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
Dear Debian QA Group
I'm sending you this mail because you are the maintainer of 'egon',
which claims a dependency on Xaw3d library. I'm the maintainer of that lib,
which has now a new upstream, after more than 5 years of inactivity.
The upstream merged almost all Debian patches and did some
Dear Debian QA Group
I'm sending you this mail because you are the maintainer of
'siagoffice-common',
which claims a dependency on Xaw3d library. I'm the maintainer of that lib,
which has now a new upstream, after more than 5 years of inactivity.
The upstream merged almost all Debian patche
Dear Debian QA Group
I'm sending you this mail because you are the maintainer of
'siagoffice-plugins',
which claims a dependency on Xaw3d library. I'm the maintainer of that lib,
which has now a new upstream, after more than 5 years of inactivity.
The upstream merged almost all Debian patch
Dear Debian QA Group
I'm sending you this mail because you are the maintainer of 'xpw',
which claims a dependency on Xaw3d library. I'm the maintainer of that lib,
which has now a new upstream, after more than 5 years of inactivity.
The upstream merged almost all Debian patches and did some
Dear Debian QA Group
I'm sending you this mail because you are the maintainer of 'xsiag',
which claims a dependency on Xaw3d library. I'm the maintainer of that lib,
which has now a new upstream, after more than 5 years of inactivity.
The upstream merged almost all Debian patches and did som
13 matches
Mail list logo
