#654 √ resolved
twalpole

rake rails:freeze:edge not working

Reported by twalpole | July 18th, 2008 @ 03:41 PM | in 2.x

the zipfile http://dev.rubyonrails.org/archi... that the rake fails:freeze:edge task uses appears to not contain up to date code for rails edge. The last modified date on the zip is changing ( http://dev.rubyonrails.org/archi... ) so it is being regenerated but appears to conatin 2.0.991 all the time, and is not including new commits to rails edge

Comments and changes to this ticket

  • Clemens

    Clemens July 20th, 2008 @ 12:56 PM

      • → Tag changed from “edge” to “2.1 rake”

    I agree that it's a little annoying that a standard rake task doesn't work. But why not just clone the GitHub repository in vendor/rails?

    rails your_app_name

    cd your_app_name/vendor

    git clone git://github.com/rails/rails.git

    That's it.

  • twalpole

    twalpole July 20th, 2008 @ 01:48 PM

    While I agree that cloning the github repo is really simple, if thats going to be the recommended method then the rake take should be removed. Considering the rake task was changed to use the zip file when rails moved to github I think it should probably work too - I'm assuming its just a minor mistake in the script that generates the zip not actually pulling from the edge revision and should be relatively easy to fix. From the announcement about rails premiering n github

    "If you don’t have git, or don’t enjoy running it on your platform, you need not fear. We’ve set up an automated task to produce a zip file of Rails Edge that’ll be kept up to date all the time: http://dev.rubyonrails.org/archi.... This is also what we’ve made the new rake rails:freeze:edge use."

  • Dieter Komendera

    Dieter Komendera July 21st, 2008 @ 03:42 AM

      • → Tag changed from “2.1 rake” to “2.1 patch rake”

    I agree with twalpole, you should be able to use rails without using git. I think the rake task should download the files directly from github.com.

    Attached find a patch which modifies the rake task to use github as download source.

  • Clemens

    Clemens July 21st, 2008 @ 04:03 AM

    I don't have time to look at it right now but from looking at the source it looks good to me. So +1.

  • Pratik

    Pratik July 21st, 2008 @ 07:38 PM

      • → Assigned user changed from “” to “Jeremy Kemper”
  • Craig Buchek

    Craig Buchek July 25th, 2008 @ 05:04 PM

    +1. Nice job on getting the tag names correct in the doc string too. Better than the code I was planning on submitting before I came here and found an existing bug report.

  • Pratik

    Pratik July 26th, 2008 @ 09:13 AM

      • → State changed from “new” to “resolved”

    Koz said he fixed zip file generation http://groups.google.com/group/r...

Please Login or create a free account to add a new comment.

You can update this ticket by sending an email to from your email client. (help)

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Source available from github

The Git repository resides at http://github.com/rails

Check out the current development trunk (Edge Rails) with:

git clone git://github.com/rails/rails.git

The latest development for the 1.2.x and 2.0.x releases are on the 1-2-stable and 2-0-stable branches.

Creating a bug report

When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.

Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.

Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".

Shared Ticket Bins

Tags