You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "David M. Syzdek (Created) (JIRA)" <ji...@apache.org> on 2012/01/24 02:11:43 UTC

[jira] [Created] (DIRSERVER-1688) using rm -d is not portable to Slackware

using rm -d is not portable to Slackware
----------------------------------------

                 Key: DIRSERVER-1688
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1688
             Project: Directory ApacheDS
          Issue Type: Bug
          Components: installer-plugin
    Affects Versions: 1.5.7, 2.0.0-M3
         Environment: Slackware Linux 13.37 32bit
            Reporter: David M. Syzdek


The command "rm" does not recognize "-d" on Slackware.  I was able to fix the problem by changing the commands from "rm -fd" to "rm -rf":

syzdek@slack131$ diff apacheds-2.0.0-M3-32bit.bin apacheds.bin 
271c271
< rm -rd instance
---
> rm -rf instance
273c273
< rm -rd server
---
> rm -rf server
syzdek@slack131$

--
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] [Commented] (DIRSERVER-1688) Using rm -d is not portable to Slackware

Posted by "Pierre-Arnaud Marcelot (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DIRSERVER-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13191979#comment-13191979 ] 

Pierre-Arnaud Marcelot commented on DIRSERVER-1688:
---------------------------------------------------

Thanks for reporting this and providing the fix.
                
> Using rm -d is not portable to Slackware
> ----------------------------------------
>
>                 Key: DIRSERVER-1688
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1688
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: installer-plugin
>    Affects Versions: 2.0.0-M3, 1.5.7
>         Environment: Slackware Linux 13.37 32bit
>            Reporter: David M. Syzdek
>            Assignee: Pierre-Arnaud Marcelot
>              Labels: installation, installer
>
> The command "rm" does not recognize "-d" on Slackware.  I was able to fix the problem by changing the commands from "rm -fd" to "rm -rf":
> syzdek@slack131$ diff apacheds-2.0.0-M3-32bit.bin apacheds.bin 
> 271c271
> < rm -rd instance
> ---
> > rm -rf instance
> 273c273
> < rm -rd server
> ---
> > rm -rf server
> syzdek@slack131$

--
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] (DIRSERVER-1688) Using rm -d is not portable to Slackware

Posted by "Pierre-Arnaud Marcelot (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre-Arnaud Marcelot resolved DIRSERVER-1688.
-----------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0-M5

Applied David's fix at commit 1235154.

http://svn.apache.org/viewvc?rev=1235154&view=rev
                
> Using rm -d is not portable to Slackware
> ----------------------------------------
>
>                 Key: DIRSERVER-1688
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1688
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: installer-plugin
>    Affects Versions: 2.0.0-M3, 1.5.7
>         Environment: Slackware Linux 13.37 32bit
>            Reporter: David M. Syzdek
>            Assignee: Pierre-Arnaud Marcelot
>              Labels: installation, installer
>             Fix For: 2.0.0-M5
>
>
> The command "rm" does not recognize "-d" on Slackware.  I was able to fix the problem by changing the commands from "rm -fd" to "rm -rf":
> syzdek@slack131$ diff apacheds-2.0.0-M3-32bit.bin apacheds.bin 
> 271c271
> < rm -rd instance
> ---
> > rm -rf instance
> 273c273
> < rm -rd server
> ---
> > rm -rf server
> syzdek@slack131$

--
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] [Updated] (DIRSERVER-1688) Using rm -d is not portable to Slackware

Posted by "Pierre-Arnaud Marcelot (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre-Arnaud Marcelot updated DIRSERVER-1688:
----------------------------------------------

    Assignee: Pierre-Arnaud Marcelot
     Summary: Using rm -d is not portable to Slackware  (was: using rm -d is not portable to Slackware)
    
> Using rm -d is not portable to Slackware
> ----------------------------------------
>
>                 Key: DIRSERVER-1688
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1688
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: installer-plugin
>    Affects Versions: 2.0.0-M3, 1.5.7
>         Environment: Slackware Linux 13.37 32bit
>            Reporter: David M. Syzdek
>            Assignee: Pierre-Arnaud Marcelot
>              Labels: installation, installer
>
> The command "rm" does not recognize "-d" on Slackware.  I was able to fix the problem by changing the commands from "rm -fd" to "rm -rf":
> syzdek@slack131$ diff apacheds-2.0.0-M3-32bit.bin apacheds.bin 
> 271c271
> < rm -rd instance
> ---
> > rm -rf instance
> 273c273
> < rm -rd server
> ---
> > rm -rf server
> syzdek@slack131$

--
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