I finally figured out how to do git on my Windows XP machine and when I downloaded it, everything was there, but previously I had been trying to download the tarball from the direct link on the site (http://insoshi.com/home/tarball). I just tried direct downloading the most recent version and the plugins are still missing (as described above).
I am unknowing in the ways of checksum, so I can't confirm whether they are different sizes are not, but I experienced the same thing with the earlier release, so whatever's breaking is doing it consistently. I'm using stuffit to unpack the tarball on Windows XP. Not sure if that would make a difference. On May 17, 1:52 pm, "Long Nguyen" <[EMAIL PROTECTED]> wrote: > The tarball for the 5/16 release is > > insoshi-insoshi-e1fd8b8e440c9f3ab34161d4e87de78e956c1012.tar.gz > > and should be 4195494 bytes. > > Running cksum on the file gives > > 2685466488 4195494 > insoshi-insoshi-e1fd8b8e440c9f3ab34161d4e87de78e956c1012.tar.gz > > When did you download the imcomplete tarball? And does the filesize and > checksum match up? > > > > On Sat, May 17, 2008 at 8:57 AM, Michael Hartl <[EMAIL PROTECTED]> wrote: > > > I just downloaded the tarball from GitHub and everything appears to be > > there. > > > Michael > > > On Sat, May 17, 2008 at 6:50 AM, Fountain <[EMAIL PROTECTED]> wrote: > > > > Any reason the tarball seems to have an incomplete collection of the > > > plugins? (it only has 'acts_as_ferret' and 'annotate_models' & > > > 'attachment_fu' is incomplete. > > > > On May 16, 6:33 pm, "Michael Hartl" <[EMAIL PROTECTED]> wrote: > > >> The Insoshi release for today includes email notifications for common > > >> activities (contact requests, new messages, wall comments, and blog > > >> comments), together with fine-grained user preferences for these > > >> notifications (available to everyone) to complement the global email > > >> notifications setting (available only to admins). The deployment of > > >> these features on Tuesday scared up some bugs, which were quickly > > >> squashed. > > > >> We also received a couple of nice fixes from new contributor > > >> 'valodzka', who polished off a nagging iPhone issue > > >> ( > >http://insoshi.lighthouseapp.com/projects/9331/tickets/39-validate-pa...) > > >> and also catalyzed the fix of a terribly subtle 'authorization token' > > >> bug that showed up intermittently in the logs but was infuriatingly > > >> hard to reproduce. > > > >> Moving forward, we have a long list of tickets at Lighthouse > > >> representing a slew of enhancements. In the short run, we'll be > > >> focusing on these and related issues as we polish up the current > > >> features before moving on to add new ones. We also have a couple of > > >> performance issues to address, especially the quite slow activity feed > > >> generation. (Possibilities include modifying the code to use more > > >> optimized SQL, spawning off a BackgrounDRb process, or both.) > > > >> Finally, we'll soon be organizing an initial Basecamp group focused on > > >> Insoshi architectural issues and refactoring. Interested participants > > >> should message me at the developer site. > > > >> Cheers, > > > >> Michael > > -- > Long Nguyen > [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ Insoshi developer site: http://dogfood.insoshi.com/ Insoshi documentation: http://docs.insoshi.com/ You received this message because you are subscribed to the Google Groups "Insoshi" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/insoshi?hl=en -~----------~----~----~----~------~----~------~--~---
