You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "SebastianWagner (Created) (JIRA)" <ji...@apache.org> on 2012/04/16 14:28:20 UTC
[jira] [Created] (OPENMEETINGS-174) CLI import of backup does not
work
CLI import of backup does not work
----------------------------------
Key: OPENMEETINGS-174
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-174
Project: Openmeetings
Issue Type: Bug
Affects Versions: 2.0 Apache Incubator Release
Reporter: SebastianWagner
Assignee: Maxim Solodovnik
Fix For: 2.0 Apache Incubator Release
The command to import a backup using the admin CLI does not work.
it always prints the message:
"File should be specified, and point the the existent zip file"
The file path to the ZIp does of course exist.
I tried with absolute and relative path, no chance.
I also tried to make the backup writeable or 777. Also no change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (OPENMEETINGS-174) CLI import of backup does not
work
Posted by "SebastianWagner (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
SebastianWagner reopened OPENMEETINGS-174:
------------------------------------------
Could you also fix the typo in the duplicated "the" in the error message:
"... and point the the existent zip ..."
> CLI import of backup does not work
> ----------------------------------
>
> Key: OPENMEETINGS-174
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-174
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
>
> The command to import a backup using the admin CLI does not work.
> it always prints the message:
> "File should be specified, and point the the existent zip file"
> The file path to the ZIp does of course exist.
> I tried with absolute and relative path, no chance.
> I also tried to make the backup writeable or 777. Also no change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (OPENMEETINGS-174) CLI import of
backup does not work
Posted by "SebastianWagner (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255379#comment-13255379 ]
SebastianWagner edited comment on OPENMEETINGS-174 at 4/17/12 7:04 AM:
-----------------------------------------------------------------------
Could you please also fix the typo in the duplicated "the" in the error message:
"... and point the the existent zip ..."
Thanks!
was (Author: swagner):
Could you also fix the typo in the duplicated "the" in the error message:
"... and point the the existent zip ..."
> CLI import of backup does not work
> ----------------------------------
>
> Key: OPENMEETINGS-174
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-174
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
>
> The command to import a backup using the admin CLI does not work.
> it always prints the message:
> "File should be specified, and point the the existent zip file"
> The file path to the ZIp does of course exist.
> I tried with absolute and relative path, no chance.
> I also tried to make the backup writeable or 777. Also no change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENMEETINGS-174) CLI import of backup does not
work
Posted by "Maxim Solodovnik (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik resolved OPENMEETINGS-174.
-------------------------------------------
Resolution: Fixed
> CLI import of backup does not work
> ----------------------------------
>
> Key: OPENMEETINGS-174
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-174
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
>
> The command to import a backup using the admin CLI does not work.
> it always prints the message:
> "File should be specified, and point the the existent zip file"
> The file path to the ZIp does of course exist.
> I tried with absolute and relative path, no chance.
> I also tried to make the backup writeable or 777. Also no change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENMEETINGS-174) CLI import of backup does not
work
Posted by "Maxim Solodovnik (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik resolved OPENMEETINGS-174.
-------------------------------------------
Resolution: Fixed
typo is fixed
> CLI import of backup does not work
> ----------------------------------
>
> Key: OPENMEETINGS-174
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-174
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
>
> The command to import a backup using the admin CLI does not work.
> it always prints the message:
> "File should be specified, and point the the existent zip file"
> The file path to the ZIp does of course exist.
> I tried with absolute and relative path, no chance.
> I also tried to make the backup writeable or 777. Also no change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OPENMEETINGS-174) CLI import of backup does not
work
Posted by "Maxim Solodovnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik closed OPENMEETINGS-174.
-----------------------------------------
Closing all old 'Resolved' issues
> CLI import of backup does not work
> ----------------------------------
>
> Key: OPENMEETINGS-174
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-174
> Project: Openmeetings
> Issue Type: Bug
> Affects Versions: 2.0 Apache Incubator Release
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.0 Apache Incubator Release
>
>
> The command to import a backup using the admin CLI does not work.
> it always prints the message:
> "File should be specified, and point the the existent zip file"
> The file path to the ZIp does of course exist.
> I tried with absolute and relative path, no chance.
> I also tried to make the backup writeable or 777. Also no change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira