Hi, My production environment has been messed up by this bug [2] today. May I know when this fix will be released to rubygems.org?
[1] https://github.com/capistrano/capistrano/pull/422 On Fri, Mar 29, 2013 at 5:02 PM, Boško Ivanišević <bosko.ivanise...@gmail.com> wrote: > You are right. Task implementation is readable and I believe problem was in > the fact REQUIRED_ASSETS file was not sorted. I created pull request > https://github.com/capistrano/capistrano/pull/422 that should fix this > problem. > >> You could write a simple task to fix the timestamps as appropriate, or >> take a look at the implementation of the task that cleaned them up, it >> should be quite readable. >> >> Lee Hambley >> -- >> http://lee.hambley.name/ >> >> >> On 28 March 2013 15:10, Boško Ivanišević <bosko.iv...@gmail.com> wrote: >>> >>> I wonder if I am the only one facing this problem. Does anyone has at >>> least some suggestion where to look in order to solve this? >>> >>>> After upgrading Capistrano from 2.13.5 to 2.14.2 I noticed that on each >>>> deploy some of my asset files are deleted in :clean_expired task with >>>> message "Remove unneeded asset:...". Digging around I found a cause but I'm >>>> not sure what is right way to fix this. >>>> >>>> I'm using Git as SCM and deploy is created via :remote_cache. Since I >>>> haven't changed some asset files for more than 2 months their timestamp on >>>> the target server is 31st January. Git does not change timestamp of these >>>> files and these files are considered as expired. I guess I'm doing >>>> something >>>> wrong but cannot figure out what. I doubt I have to constantly change >>>> expire_assets_after in order to keep assets not changed for a long time. >>>> >>>> All deleted assets are listed in manifest.yml file and >>>> assets_manifest.yml files. >>>> >>>> Bosko >>>> >>> -- >>> -- >>> * You received this message because you are subscribed to the Google >>> Groups "Capistrano" group. >>> * To post to this group, send email to capis...@googlegroups.com >>> * To unsubscribe from this group, send email to >>> capistrano+...@googlegroups.com For more options, visit this group at >>> http://groups.google.com/group/capistrano?hl=en >>> >>> --- >>> You received this message because you are subscribed to the Google Groups >>> "Capistrano" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to capistrano+...@googlegroups.com. >>> >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >> >> > -- > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" group. > * To post to this group, send email to capistrano@googlegroups.com > * To unsubscribe from this group, send email to > capistrano+unsubscr...@googlegroups.com For more options, visit this group > at http://groups.google.com/group/capistrano?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Capistrano" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to capistrano+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > -- Huiming -- -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to capistrano@googlegroups.com * To unsubscribe from this group, send email to capistrano+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/capistrano?hl=en --- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
