[asterisk-bugs] [Asterisk 0012049]: Leftover modules from 1.4 will crash 1.6 ..

[noreply at bugs.digium.com]

The following issue has been REOPENED. 
====================================================================== 
http://bugs.digium.com/view.php?id=12049 
====================================================================== 
Reported By:                drmessano
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12049
Category:                   Core-General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0-beta1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-22-2008 01:15 CST
Last Modified:              02-22-2008 02:14 CST
====================================================================== 
Summary:                    Leftover modules from 1.4 will crash 1.6 ..
Description: 
The following modules, leftover from 1.4, will crash 1.6 on startup:

app_hasnewvoicemail.so
app_lookupblacklist.so
app_lookupcidname.so
app_random.so
app_realtime.so
app_setcdruserfield.so
app_settransfercapability.so
func_language.so
func_moh.so
res_features.so

====================================================================== 

---------------------------------------------------------------------- 
 drmessano - 02-22-08 02:14  
---------------------------------------------------------------------- 
Considering that these were not 3rd party modules, but an actual part of
1.4, they should be addressed differently than the canned warning.  There's
no reason that KNOWN, formerly included modules, can't be addressed, with
3rd party modules left to the user to sort out.

If you are going to address a handful of older modules with noload
statements in modules.conf, and now pass off leftover modules from 1.4 with
"there's a warning", then you're creating an inconsistency. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-22-08 02:14  drmessano      Note Added: 0082764                          
======================================================================