Something went wrong while setting issue due date.
'fusiondirectory-insert-schema -m' should check if the specificed file exists
Closed
'fusiondirectory-insert-schema -m' should check if the specificed file exists
Yesterday I did @fusiondirectory-insert-schema -m path/file.schema@
while @file.schema@ didn't exist, which has resulted in a new zero length file at @path/file.ldif@
It seems correct that a ldif file is produced for further review as explained by Côme on IRC, but the existence of the original schema file should be checked in the first place.
(from redmine: issue id 4485, created on 2016-01-28, closed on 2016-01-28)
- Changesets:
- Revision 1747b2db by Côme Chilliet on 2016-01-28T09:06:20.000Z:
Fixes #4485 'fusiondirectory-insert-schema -m' should delete residual empty files
- Revision 64bee75d by Côme Chilliet on 2016-01-28T09:07:20.000Z:
Fixes #4485 'fusiondirectory-insert-schema -m' should delete residual empty files
- Revision 7c1258f2 by Côme Chilliet on 2016-01-28T09:07:33.000Z:
Fixes #4485 'fusiondirectory-insert-schema -m' should delete residual empty files
- Custom Fields:
- Bug in version: 1.0.9.2