Your message dated Thu, 9 Jun 2011 18:31:23 +0100
with message-id <[email protected]>
and subject line close old bugs
has caused the Debian Bug report #199718,
regarding Addition of non-threaded perl to resolve problems with applications
like interchange
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.)
--
199718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=199718
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: perl
Version: 5.8.0-18
Severity: wishlist
Tags: sid
I presently use Interchange package and have found that the use of threaded perl
has caused many problems with it. I have tested on 3 systems that I have
recompiled
perl without threads and all of the required and recommened modules for
interchange
and no longer can reproduce the errors and problems that I have had. Some of
the
problems are basic premature end of script and database interactivity.
This message from the icdevgroup mail list communicates some of the issues
that relate to the concerns with enabling threads in perl.
http://www.icdevgroup.org/pipermail/interchange-users/2003-June/034173.html
I am asking that it be possible to create simular to what was done in 5.005's
perl-thread and add a perl-nothread to 5.8.
I understand that all modules that do use threads would have to recompiled to be
used with the un-threaded perl. This would require modules to modified to be
placed into the no-threaded perl lib directory.
I propose a standard that would allow perl modules in Debian to be built with
both threads and non-threads automagiclly in some fashion. I am not sure
how at this moment this could be accomplished but doing as most apps that
use or build debug versions this could be done simular.
For the moment just the addition of the non-threaded perl would allow IC
and many others that use perl heavily to be depenended on and the application
maintainer would or could build the modules that are neeeded to for the
app into the package.
Please, if you could follow some of the disscussions with the IC mail list
about the use of threaded perl to give you some idea of adding threads
have done just so apache2 can have use of it.
Thanks.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux starfire 2.4.21-1-k7 #1 Thu Jun 26 00:04:23 EDT 2003 i686
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages perl depends on:
ii libc6 2.3.1-17 GNU C Library: Shared libraries an
ii libdb4.0 4.0.14-1.2 Berkeley v4.0 Database Libraries [
ii libgdbm3 1.8.3-1 GNU dbm database routines (runtime
ii perl-base 5.8.0-18 The Pathologically Eclectic Rubbis
ii perl-modules 5.8.0-18 Core Perl modules.
-- no debconf information
--- End Message ---
--- Begin Message ---
As promised, closing these old bugs with no further action.
Dominic.
--
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
--- End Message ---
