Your message dated Fri, 21 Aug 2009 22:11:05 +0200
with message-id <[email protected]>
and subject line close
has caused the Debian Bug report #496052,
regarding factor out a separate package for edos-debcheck wrappers
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
496052: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496052
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: edos-debcheck
Version: 1.0-6+b2
Severity: wishlist

It might be a good idea to factor out a separate source-package with
the various edos-debcheck wrappers that are coming up (edos-builddebcheck,
file overwrites, strong non-installabilty, etc.).

-Ralf.
-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.utf8)
Shell: /bin/sh linked to /bin/bash

Versions of packages edos-debcheck depends on:
ii  libc6                         2.7-13     GNU C Library: Shared libraries

edos-debcheck recommends no packages.

edos-debcheck suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
I do not think any longer that it would be a good idea to cerate a separate
package for wrappers. The use of wrappers should be restricte anyway, for
reasons of speed we should try as much as possible to support extensions
natively in edos-debcheck (like, for instance, edos-builddebcheck which
could be made *much* faster when we got rid of the nasty python and
perl wrappers).


--- End Message ---

Reply via email to