Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#38393 - [opensips] osipsconfig containts incorrect paths
Attached to Project:
Community Packages
Opened by Sean (graywind) - Monday, 06 January 2014, 08:38 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 10 January 2014, 10:51 GMT
Opened by Sean (graywind) - Monday, 06 January 2014, 08:38 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 10 January 2014, 10:51 GMT
|
DetailsDescription:
osipsconfig is unable to output a configuration file. After opening the binary with a text editor I found evidence that paths are being set incorrectly during the building process by seeing strings such as @etc/^@^@^@/build/opensips/pkg/opensips/usr/etc/opensips/ Steps to reproduce: Attempt to run osipsconfig to generate a configuration file. Inspect curses.out when that fails (Ctrl-C). Example curses.out: Initialized main window Failed to open [opensips_residential_def.m4]Failed to parse m4 for Residential Script Failed to get all script options QUIT RECEIVED Notes: Taking a look at how MENUCONFIG_CFG_PATH and MENUCONFIG_GEN_PATH are handled might give you a headstart but I just started to look into using opensips yesterday so I'm not completely sure. |
This task depends upon
Closed by Sergej Pupykin (sergej)
Friday, 10 January 2014, 10:51 GMT
Reason for closing: Fixed
Additional comments about closing: should be fixed in opensips-1.10.0-2
Friday, 10 January 2014, 10:51 GMT
Reason for closing: Fixed
Additional comments about closing: should be fixed in opensips-1.10.0-2