Your message dated Tue, 15 Aug 2006 21:36:53 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Removed
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
package: xcircuit
severity: grave
Date: Wed, 31 May 2006 08:47:24 -0700
To: Debian QA Group <[EMAIL PROTECTED]>,
Tim Edwards <[EMAIL PROTECTED]>,
Michael Ablassmeier <[EMAIL PROTECTED]>
Subject: xcircuit 3.6.24-1 unusable on amd64
Hi -
I don't mean to complain, but the recent upload of xcircuit 3.6.24-1
to unstable is completely unusable for me on amd64. This is unlike
any previous version of xcircuit. I get segfaults or illegal
instruction crashes within half-a-dozen X actions.
This is true even when I rebuild from sources, either in or out
of the Debian package framework. I note a large number of 64-bit
concerns flagged by the compiler (gcc-4.0.4), about half of them
in the Xw widget set. I tried fixing some of the worst of these,
and using gdb to find details of the crash, but have not yet
succeeded in finding or fixing the problem(s).
This leaves me with a number of questions:
1. does anyone else see this behavior?
2. is xcircuit the only Debian package using Xw?
3. where did upstream (that's you, Tim) get that copy of Xw
(and are you maintaining that copy yourself)?
4. will upstream accept 64-bit cleanups (and do you have
access to a 64-bit machine to test them)?
5. will this be the kick in the pants I need to become
a Debian Developer and adopt this package?
- Larry
----- End forwarded message -----
bye,
- michael
--- End Message ---
--- Begin Message ---
xcircuit has been removed from Debian due to release-critical bugs and
lack of a maintainer. For details, see <http://bugs.debian.org/323678>.
--- End Message ---
