[cas_migrateconf 0004543]: Configuration migration doesn't work properly if a directory is given

Mon Mar 24 00:50:57 CET 2014

A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4543 
====================================================================== 
Reported By:                yann
Assigned To:                maciej
====================================================================== 
Project:                    cas_migrateconf
Issue ID:                   4543
Category:                   regular use
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2010-09-03 14:54 CEST
Last Modified:              2014-03-24 00:50 CET
====================================================================== 
Summary:                    Configuration migration doesn't work properly if a
directory is given
Description: 
Hi,

According to the wiki page, cswclassutils cswmigrateconf class action
script can migrate a whole directory: "If a path specified in MIGRATE_FILES
is a directory, the whole directory tree is going to be copied." [1]

However I was not able to use this mode successfully with vsftpd. 
It seems that before doing the migration, the script always tries to test
the existence of /etc/opt/csw/vsftpd.CSW which is not applicable in the
directory case:

  # If there's a sample configuration file, remove the copied one.
  __sample_conf="${__dest_file_name}.CSW"
  if [ -r "${__sample_conf}" ]; then
    if files_are_identical "${__sample_conf}" "${__dest_file_name}"; then
      return "${__do_copy}"
    else
      return "${__do_not_copy}"
    fi
  fi

Have I done something wrong or is it a bug ?

Thanks in advance for your answer.

[1] http://wiki.opencsw.org/cswclassutils-package#toc15
====================================================================== 

---------------------------------------------------------------------- 
 (0010783) maciej (manager) - 2014-03-24 00:50
 https://www.opencsw.org/mantis/view.php?id=4543#c10783 
---------------------------------------------------------------------- 
There is no point in waiting for this bug to be fixed. If you want it
fixed, you (yes, you the reader) need to fix it yourself. If you're not
already a package maintainer at OpenCSW, you can look at the 35 minute long
tutorial[1] to get started - then you can offer your patch to package
maintainers. You can find OpenCSW people on the users mailing list[2] and
on the #opencsw channel on IRC on Freenode[3].

[1] Packaging tutorial http://youtu.be/JWKCbPJSaxw
[2] OpenCSW users mailing list
https://lists.opencsw.org/mailman/listinfo/users
[3] #opencsw on Freenode http://www.opencsw.org/support/irc-channel/