Scott Weikart created JENKINS-12773:
---------------------------------------
Summary: moving-hudson: don't delete ~hudson if it's the same as
~jenkins
Key: JENKINS-12773
URL: https://issues.jenkins-ci.org/browse/JENKINS-12773
Project: Jenkins
Issue Type: Bug
Components: regexemail
Affects Versions: current
Environment: CentOS-6.2
Reporter: Scott Weikart
Assignee: justinedelson
Priority: Critical
Executive summary: during yum update, don't try to move ~hudson to ~jenkins if
the two paths are the same!
Details ...
I ran "yum install jenkins" to switch our installation from hudson to jenkins.
I can't remember where the old data lived when I did this, because I rebuilt
the server at the same time; my memory is that I put it in ~hudson, but copied
it by hand to ~jenkins after the install because the install didn't copy it
even though ~jenkins/.moving-hudson was created. At some point (afterwards?) I
modified the password entry for hudson to have the same home directory as
jenkins, so that ~hudson in scripts would still work.
Today I did "yum update", and it tried to move ~hudson to ~jenkins (mv
complained that the files were the same, of course), and then it tried to
delete ~hudson which was the same as ~jenkins?! Luckily, ~jenkins was a file
system mount point, so the delete failed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
