mrt add collectionFS fails #97

Rebolon · 2013-10-28T10:56:48Z

Trying to add collectionFS to a new project :
mrt create testApp
mrt add collectionFS

✓ cfs-public-folder
tag: https://github.com/nooitaf/meteor-cfs-public-folder.git#v0.0.3

/home/action/.nvm/v0.10.11/lib/node_modules/meteorite/lib/sources/git.js:151
hrow "There was a problem checking out " + self.checkoutType + ": " + (self.co
^
There was a problem checking out tag: v0.0.3

I also have the problem on previous installed app : collectionFS and cfs-public-folder are listed in packages folder but mrt always return the same problem.
When i edit the cfs-public-folder/smart.json of that app it shows me i'm on v0.0.2 and not in v0.0.3, so it seems that update fails sinc some time ago.

nooitaf · 2013-10-28T11:32:34Z

~~try mrt remove --system~~

~~this will remove all mrt files on your system..~~

~~and then mrt update in the folder of your app..~~

Rebolon · 2013-10-28T12:24:26Z

i did a mrt remove --system in one folder
then mrt update in app folder
But i have the same error

nooitaf · 2013-10-28T13:24:49Z

i'm sorry .. it's mrt uninstall --system
then mrt update

if that doesnt work try npm install -g meteorite or the sudo equvalent sudo -H npm install -g meteorite

Rebolon · 2013-10-28T14:50:31Z

ok it works,
thx

Rebolon · 2013-10-28T14:50:39Z

Ok it works correctly now

Benjamin RICHARD
about.me/benjamin.richard/

2013/10/28 nooitaf [email protected]

i'm sorry .. it's mrt uninstall --system
then mrt update

if that doesnt work try npm install -g meteorite or the sudo equvalent sudo
-H npm install -g meteorite

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/97#issuecomment-27210653
.

nooitaf · 2013-10-28T15:02:45Z

nice, ... i hope the next version bump will be smoother..

pnunn · 2014-01-16T04:45:31Z

I can't get collectionFS to install. I did mrt install cfs-public-folder first as I thought it was a dependancy, but then I got the error above when I tried to do mrt install collectionFS. I tried the mrt uninstall and update step, which simply re-installes roles, iron-router and errors that I had installed previously, then when I do mrt install collectionFS I don't get any errors, but the package is still not installed.
Any ideas?

copleykj · 2014-01-16T04:49:48Z

Use mrt add collectionFS instead of mrt install

pnunn · 2014-01-16T05:24:22Z

How embarrassing... :( My excuse, its 43 C here today.. thanks

copleykj · 2014-01-17T01:27:40Z

lol, its all good.. I think we've all had those moments :)

pnunn · 2014-03-20T05:34:28Z

Updated meteor to 0.7.2 then mrt update, but I'm getting errors from collectionFS.

Problem installing collectionFS
✘ [branch: https://github.com/CollectionFS/Meteor-CollectionFS.git#devel] conflicts with [latest]
Can't resolve dependencies! Use --force if you don't mrt taking a wild guess and running your app anway.

I tried mrt uninstall --system and mrt update, but same issue. Any ideas?

raix · 2014-03-20T05:53:01Z

@pnunn good question, we had to publish the new version to get tests working on travis. I'm guessing you are on the "old" api? Could try editing your app smart.json pointing collectionFS to the Master and tag v0.0.3? (I'm not a mrt expert) we will add a message/guide on the readme and meteor talk.

We are pushing the new version to Master before april.

There are massive speed and Security improvements in the new api, so when Ready we will recommend moving to the new api.

pnunn · 2014-03-20T06:06:54Z

Ok, I've added {"tag": "master/v0.0.3" } to collectionFS (also tried "master/0.0.3"), uninstall --system, mrt update but same error still. Not sure what you mean by "old" and "new" api's but is it easier to just update to what's new? Has it changed much?

raix · 2014-03-20T07:57:35Z

Its changed a lot - for the better, hope you guys agree - the new api should be more powerful, easy much faster since we are piping streams of data and more secure because we have a real rest point rigged - adding download to allow/deny rules - we do set headers now for forcing saveAs.

It also has a more flexible storage capability since you can easily switch between the current 3 storage adapters:

FS.Store.FileSystem
FS.Store.GridFS - (note that we use real GridFS now)
FS.StoreS3

We've made it fairly easy for others to create new storage adapters (I'm personally looking forward to storage adapters for stuff like dropbox/drive etc.)

We have added a FS.File object for handling files - this has many advantages:

We have a direct api on the file object making it easier to work with
We are ready for Blaze since a file contains helper oriented functions like {{url}}, {{url store="thumbnail"}, {{url download=true}}
If you add a FS.File to a document in a normal Meteor.Collection its converted to a ejson reference - when retrieved from the Meteor.Collection its converted back again to FS.File with api and all (may require that the FS.Collection is actually published for the user)
You can easily attachData like: file/blob/buffer/url/path (works at direct insert to a FS.Collection too)
Easy access to the streaming api etc.

We are writing the last parts of the transformation streams api - its basically file handlers / beforeSave but for streams - again making it possible to use gm streaming api or crypting/decrypting data etc.

The most important part: The new api already got more tests rigged that the old (it had no tests)

We are not releasing until we have a fair amount of test coverage - The last week of this month (March)/next week is test writing week - so the final api will be done this week.

But theres a bunch of devs already using/testing it - and we are close to a stable api - basically just the transform that is missing.

We are super low on documentation at the moment - but we have a place where early adapters can add comments what parts needs documentation #206

But when all is said - users should be able to use the old api if they want to, I'm sure its possible - I hope the new package system will resolve version dependencies better in the future.

Hmm, not 0.0.3 it should be 0.3.7 Maybe try:

{
  "meteor": {
    "tag": "v0.7.2"
  },
  "packages": {
    "collectionFS": "0.3.7",
  }
}

Feedback is much welcome

pnunn · 2014-03-20T09:01:25Z

Sounds really interesting raix, looking forward to trying it all out.
smart.json as it is just has { packages: { "collectionFS" : {} in it,
changing this to, as you suggested, "collectionFS: "0.3.7" seems to have done the trick (interestingly smart.lock already had 0.3.7 in it.. but there you go).

raix · 2014-03-20T09:43:56Z

Cool - I'll update the master readme - Thanks!!

lap123 · 2014-03-21T15:50:55Z

fyi, I am on the devel branch and I have the same conflict problem as described earlier. Happened when I upgraded to meteor 0.7.2.

raix · 2014-03-21T16:11:00Z

ok, edit your smart.json use version: "collectionFS: "0.3.7"

lap123 · 2014-03-21T16:29:55Z

huum, I have no intention to use the old api, thanks.
Just wanted to emphasize that the problem is not isolated.

raix · 2014-03-21T17:03:53Z

@lap123 sorry - whats the reference in smart.json? (we use mtr on the travis test server - so it should work)
@aldeed I think the problem you had to workaround could be related to this? (I think we can remove the smart.lock again - this issue is isolated to the smart.json files...)

raix · 2014-03-21T17:30:13Z

@aldeed I'm getting this result when trying mtr:

$ mrt add collectionFS
✓ cfs-base-package
    branch: https://github.com/CollectionFS/Meteor-cfs-base-package.git#master
✓ cfs-file
    branch: https://github.com/CollectionFS/Meteor-cfs-file.git#master
✓ cfs-ejson-file
    branch: https://github.com/CollectionFS/Meteor-cfs-ejson-file.git#master
✓ cfs-collection
    branch: https://github.com/CollectionFS/Meteor-cfs-collection.git#master
✓ cfs-access-point
    branch: https://github.com/CollectionFS/Meteor-cfs-access-point.git#master
✓ cfs-worker
    branch: https://github.com/CollectionFS/Meteor-cfs-worker.git#master
✓ cfs-upload-http
    branch: https://github.com/CollectionFS/Meteor-cfs-upload-http.git#master
✓ cfs-filesaver
    branch: https://github.com/CollectionFS/Meteor-cfs-filesaver.git#master
✓ cfs-storage-adapter
    branch: https://github.com/CollectionFS/Meteor-cfs-storage-adapter.git#master
✓ http-methods
    branch: https://github.com/CollectionFS/Meteor-http-methods.git#master
✓ cfs-upload-ddp
    branch: https://github.com/CollectionFS/Meteor-cfs-upload-ddp.git#master
✓ http-publish
    branch: https://github.com/CollectionFS/Meteor-http-publish.git#master
✓ cfs-gridfs
    branch: https://github.com/CollectionFS/Meteor-cfs-gridfs.git#master
✓ cfs-tempstore
    branch: https://github.com/CollectionFS/Meteor-cfs-tempstore.git#master

Problem installing collectionFS
  ✘ [branch: https://github.com/CollectionFS/Meteor-CollectionFS.git#devel] conflicts with [latest]
Can`t resolve dependencies! Use --force if you don`t mind mrt taking a wild guess and running your app anyway.

@lap123 is it the same result you get?

lap123 · 2014-03-21T17:37:59Z

yes I get the same results. Sorry I should have pasted it from the beginning.
My smart.json is:

  "packages": {
    "collection2": {},
    "bootstrap-3": {},
    "moment": {},
    "iron-router": {},
    "collectionFS": {
      "git": "https://github.com/CollectionFS/Meteor-CollectionFS.git",
      "branch": "devel"
    },
    "cfs-gridfs": {
      "git": "https://github.com/CollectionFS/Meteor-cfs-gridfs.git",
      "branch": "master"
    },
    "cfs-filesystem": {
      "git": "https://github.com/CollectionFS/Meteor-cfs-filesystem.git",
      "branch": "master"
    },
    "cfs-handlebars": {
      "git": "https://github.com/CollectionFS/Meteor-cfs-handlebars.git",
      "branch": "master"
    },
    "bootstrap-wysiwyg": {}
  }

aldeed · 2014-03-21T17:56:59Z

@lap123, if I'm understanding what's been happening correctly, you just need to change it to "collectionFS": {} and that should resolve your issues.

@raix, our issues with travis testing are a bit more complicated. As I said, we need to do mrt update --force and then commit the updated smart.lock.

raix · 2014-03-21T18:00:51Z

I can't add via mtr... Ive bumped all packages to make sure everything is up to date - and now its failing at cfs-file... This is a mtr issue right? (the new package system hopefully resolves this)

aldeed · 2014-03-21T18:01:13Z

To put it clearly, as of right now, the correct way to use each collectionFS version right now is:

0.4.0 (new API) smart.json:

"collectionFS": {}

0.3.7 (old API) smart.json:

"collectionFS": "0.3.7"

Which also means that simply doing mrt add collectionFS adds 0.4.0.

raix · 2014-03-21T18:01:26Z

ughh - I have removed 2 smart.lock files in attept to debug..

aldeed · 2014-03-21T18:03:51Z

It should work with mrt update --force. I will try out. I don't think this is really an issue with anything. It's just that we have a bit of a double dependency when running tests, and the testing dependency says to use "local" while our smart.json in collectionFS pkg says to use the master branch. So meteorite doesn't know which is correct.

By using --force, we tell it it's OK to use the "local" files for both dependencies, and then we lock that decision in the smart.lock file.

raix · 2014-03-21T18:06:49Z

mtr should be able to handle that packages may have same deps?

aldeed · 2014-03-21T18:08:06Z

For an app, I don't think --force should be necessary, but for running tests it is. For an app, we just need to make sure everyone is using "collectionFS": {} in smart.json. The easy way to fix would be to do mrt remove collectionFS and then mrt add collectionFS.

raix · 2014-03-21T18:10:12Z

Ok, mrt is not actually checking or too clever, now I get:

Problem installing collectionFS
  ✘ [latest] conflicts with [branch: https://github.com/CollectionFS/Meteor-CollectionFS.git#devel];
keeping [branch: https://github.com/CollectionFS/Meteor-CollectionFS.git#devel]

its kinda exactly the same...
Edit: I'm using --force

aldeed · 2014-03-21T18:11:30Z

Maybe we have some packages that still point to the devel branch in their smart.json. That should be changed.

raix · 2014-03-21T18:12:59Z

Nope checked all packages, none of them are doing circular references to collectionFS. Maybe do a cross check to see if there are circular deps between packages?

raix · 2014-03-21T18:17:29Z

Should we add --force to the read me?

aldeed · 2014-03-21T18:18:20Z

Actually, not quite true. I just checked and found that the cfs-worker pkg was still referencing the devel branch. I changed it to reference the latest release, and that fixed this issue (for me).

aldeed · 2014-03-21T18:19:33Z

So, no, --force should not be in the readme, unless you want to document how to run the tests in the contributor section.

nooitaf · 2014-03-21T18:20:04Z

just created a testapp, looks good:

This project is already at Meteor 0.7.2, the latest release.

$ mrt add collectionFS
✓ cfs-base-package
    branch: https://github.com/CollectionFS/Meteor-cfs-base-package.git#master
✓ cfs-file
    branch: https://github.com/CollectionFS/Meteor-cfs-file.git#master
✓ cfs-ejson-file
    branch: https://github.com/CollectionFS/Meteor-cfs-ejson-file.git#master
✓ cfs-collection
    branch: https://github.com/CollectionFS/Meteor-cfs-collection.git#master
✓ cfs-access-point
    branch: https://github.com/CollectionFS/Meteor-cfs-access-point.git#master
✓ cfs-worker
    branch: https://github.com/CollectionFS/Meteor-cfs-worker.git#master
✓ cfs-upload-http
    branch: https://github.com/CollectionFS/Meteor-cfs-upload-http.git#master
✓ cfs-filesaver
    branch: https://github.com/CollectionFS/Meteor-cfs-filesaver.git#master
✓ cfs-storage-adapter
    branch: https://github.com/CollectionFS/Meteor-cfs-storage-adapter.git#master
✓ http-methods
    branch: https://github.com/CollectionFS/Meteor-http-methods.git#master
✓ cfs-upload-ddp
    branch: https://github.com/CollectionFS/Meteor-cfs-upload-ddp.git#master
✓ http-publish
    branch: https://github.com/CollectionFS/Meteor-http-publish.git#master
✓ cfs-gridfs
    branch: https://github.com/CollectionFS/Meteor-cfs-gridfs.git#master
✓ cfs-tempstore
    branch: https://github.com/CollectionFS/Meteor-cfs-tempstore.git#master
✓ power-queue
    branch: https://github.com/CollectionFS/Meteor-power-queue.git#master
✓ reactive-list
    branch: https://github.com/CollectionFS/Meteor-reactive-list.git#master
✓ reactive-property
    branch: https://github.com/CollectionFS/Meteor-reactive-property.git#master
✓ micro-queue
    branch: https://github.com/CollectionFS/Meteor-micro-queue.git#master
✓ collectionFS
    tag: https://github.com/CollectionFS/Meteor-CollectionFS.git#devel#v0.4.1

Done installing smart packages

raix · 2014-03-21T18:55:47Z

@aldeed no no, btw good catch ive been looking at all smart.json too,
@nooitaf sounds good

raix · 2014-03-21T19:41:23Z

Yeah, it works here too - thanks guys!!
@aldeed tests are failing on travis, Ill test some more on this using mbr locally

aldeed · 2014-03-21T21:19:53Z

I think the cfs-access-point tests are failing because you removed smart.lock. It was working yesterday after I committed smart.lock.

aldeed · 2014-03-21T21:24:04Z

This is what worked for me:

$ mrt update --force
If `smart.lock` is changed:
$ git add smart.lock
$ git commit -m "message"

After you run mrt update --force, you will be able to run tests locally with mrt test-packages ./ and they will pass on travis as long as you commit the updated smart.lock.

raix · 2014-03-21T21:35:15Z

but we should not have to include smart.lock... I rather have it work like normal. Im thinking this issue we are experiencing could be due to the fact that we include info about git and branch - it should be ok to remove? e.g. like collectionFS: {} could perhaps work in general?

raix · 2014-03-21T21:43:27Z

Im turning in - I've refactored the transformWrite/read - it works when just piping the readStream and writeStream in the transform - so thats good news - its saved correctly etc. but the fileobj is not updated with an extra store (my qa got org + transform) - later...

raix · 2014-03-22T21:23:44Z

@aldeed I've fixed travis test script - Ive updated all .travis scripts to use our own version for this - using your mtr update --force

aldeed · 2014-03-22T22:24:34Z

OK, nice. Yeah, I don't think that removing the git and branch references would help, because it still evaluates as "latest" whereas the tests try to use "local" of the package being tested. Since "latest" != "local", mrt doesn't know what to do. But I could be wrong, have been once or twice in my life. :)

raix · 2014-03-22T23:08:37Z

I still have smart.json open for all packages, I'll revert - it doesnt make any difference, modifying the test script solved it.

nooitaf · 2014-03-23T15:00:25Z

Did the same thing i did 2 days ago, but now it throws this error..

$ meteor create cfs-test
$ cd ctf-test
$ meteor --version
Release 0.7.2
$ mrt add collectionFS
Problem installing cfs-base-package
✘ [branch: https://github.com/CollectionFS/Meteor-cfs-base-package.git#master] conflicts with [latest]
Can't resolve dependencies! Use --force if you don't mrt taking a wild guess and running your app anway.

.. should i use the --force ?

raix · 2014-03-23T16:07:45Z

@nooitaf hmmm, maybe I did this? I did remove the git#master reference while testing making travis work - so I guess mrt tracks that as latest? I have then reverted to the git# reference creating a conflict?
So I think mrt update --force should solve it? (I'm not a mrt user, hope meteor will soon have real package support... should happen soon)

Let me know if it works - I'll add it to the readme.md

nooitaf · 2014-03-23T17:05:13Z

@raix the --force doesn't seem to solve it.. well, it goes on installing and i can start it but then it complains about an undefined function FS.Store.Filesystem(..

just a little side thought .. shouldn't those packages have tag numbers instead of #master?
i see tags as "stable" snapshots of the master, and i assume mrt gets confused when the same "branch/tag" changes.

$ mrt update --force
✓ cfs-base-package
    branch: https://github.com/CollectionFS/Meteor-cfs-base-package.git#master
✓ cfs-filesaver
    branch: https://github.com/CollectionFS/Meteor-cfs-filesaver.git#master
✓ cfs-storage-adapter
    branch: https://github.com/CollectionFS/Meteor-cfs-storage-adapter.git#master
✓ cfs-collection
    branch: https://github.com/CollectionFS/Meteor-cfs-collection.git#master
✓ http-methods
    branch: https://github.com/CollectionFS/Meteor-http-methods.git#master
✓ cfs-file
    branch: https://github.com/CollectionFS/Meteor-cfs-file.git#master
✓ cfs-filesaver
    branch: https://github.com/CollectionFS/Meteor-cfs-filesaver.git#master
✓ cfs-storage-adapter
    branch: https://github.com/CollectionFS/Meteor-cfs-storage-adapter.git#master
✓ cfs-collection
    branch: https://github.com/CollectionFS/Meteor-cfs-collection.git#master
✓ http-methods
    branch: https://github.com/CollectionFS/Meteor-http-methods.git#master
✓ cfs-upload-ddp
    branch: https://github.com/CollectionFS/Meteor-cfs-upload-ddp.git#master
✓ cfs-upload-http
    branch: https://github.com/CollectionFS/Meteor-cfs-upload-http.git#master
✓ http-publish
    branch: https://github.com/CollectionFS/Meteor-http-publish.git#master
✓ cfs-gridfs
    branch: https://github.com/CollectionFS/Meteor-cfs-gridfs.git#master
✓ cfs-tempstore
    branch: https://github.com/CollectionFS/Meteor-cfs-tempstore.git#master
✓ cfs-access-point
    branch: https://github.com/CollectionFS/Meteor-cfs-access-point.git#master
✓ http-publish
    branch: https://github.com/CollectionFS/Meteor-http-publish.git#master
✓ cfs-gridfs
    branch: https://github.com/CollectionFS/Meteor-cfs-gridfs.git#master
✓ cfs-tempstore
    branch: https://github.com/CollectionFS/Meteor-cfs-tempstore.git#master
✓ power-queue
    branch: https://github.com/CollectionFS/Meteor-power-queue.git#master
✓ reactive-list
    branch: https://github.com/CollectionFS/Meteor-reactive-list.git#master
✓ reactive-property
    branch: https://github.com/CollectionFS/Meteor-reactive-property.git#master
✓ micro-queue
    branch: https://github.com/CollectionFS/Meteor-micro-queue.git#master
Problem installing cfs-base-package
  ✘ [branch: https://github.com/CollectionFS/Meteor-cfs-base-package.git#master] conflicts with [latest]; overriding with [branch: https://github.com/CollectionFS/Meteor-cfs-base-package.git#master]
Problem installing cfs-collection
  ✘ [branch: https://github.com/CollectionFS/Meteor-cfs-collection.git#master] conflicts with [latest]; overriding with [branch: https://github.com/CollectionFS/Meteor-cfs-collection.git#master]
Problem installing cfs-file
  ✘ [branch: https://github.com/CollectionFS/Meteor-cfs-file.git#master] conflicts with [latest]; overriding with [branch: https://github.com/CollectionFS/Meteor-cfs-file.git#master]
Problem installing cfs-upload-http
  ✘ [branch: https://github.com/CollectionFS/Meteor-cfs-upload-http.git#master] conflicts with [latest]; overriding with [branch: https://github.com/CollectionFS/Meteor-cfs-upload-http.git#master]
Problem installing cfs-access-point
  ✘ [branch: https://github.com/CollectionFS/Meteor-cfs-access-point.git#master] conflicts with [latest]; overriding with [branch: https://github.com/CollectionFS/Meteor-cfs-access-point.git#master]
✓ collectionFS
    tag: https://github.com/CollectionFS/Meteor-CollectionFS.git#v0.4.3
✓ cfs-ejson-file
    tag: https://github.com/CollectionFS/Meteor-cfs-ejson-file.git#v0.0.5
✓ cfs-worker
    tag: https://github.com/CollectionFS/Meteor-cfs-worker.git#v0.0.11

Done installing smart packages

raix · 2014-03-23T17:42:29Z

FS.FileSystem

nooitaf · 2014-03-23T19:02:10Z

Your example gist https://gist.github.com/raix/9720064 said FS.Store.Filesystem... which seems to be working now. I just forgot to install the cfs-filesystem, also using the --force ofc :D

mrt add collectionFS --force throws problems, but seems to be the wonder call
mrt add cfs-filesystem --force throws problems, but adds that missing function of mine

i made a little repo of the working thingy. https://github.com/nooitaf/meteor-cfs-example-image-upload

raix · 2014-03-23T19:42:01Z

Yep, sorry was on iPhone, FS.Store.FileSystem (with cap. "S") but true one have to add the storage adapter packages, I'll just put a note in the gist about it.
Yep mrt is not clever enough to resolve correctly.

raix · 2014-03-23T19:51:27Z

Cool about the repo, we should link from the readme :)
And, the api is not likly to change, we need some work in the fileworker area and test writing, but the api should be ok.

solshark · 2014-05-30T12:28:22Z

I have similar issue.
It just doing nothing.

$ mrt add collectionFS

and silens. No errors. No messages. Nothing.

--force

helpless too

aldeed · 2014-05-30T12:48:27Z

@solshark, I think that sometimes happens temporarily due to network issues. Maybe see if it works later.

solshark · 2014-05-30T13:00:04Z

Might be, but all the rest of atmosphere packages installs ok.

solshark · 2014-05-30T13:00:48Z

And magically it works now :)

Rebolon closed this as completed Oct 28, 2013

mcrider mentioned this issue Dec 3, 2013

Instructions to install from git in do not work mcrider/azimuth#67

Closed

ViktorNova mentioned this issue Feb 8, 2014

Install mrt problem mcrider/azimuth#74

Closed

raix mentioned this issue Mar 25, 2014

api documentation updates - devel branch #206

Open

mrt add collectionFS fails #97

mrt add collectionFS fails #97

Comments

Rebolon commented Oct 28, 2013

nooitaf commented Oct 28, 2013

Rebolon commented Oct 28, 2013

nooitaf commented Oct 28, 2013

Rebolon commented Oct 28, 2013

Rebolon commented Oct 28, 2013

nooitaf commented Oct 28, 2013

pnunn commented Jan 16, 2014

copleykj commented Jan 16, 2014

pnunn commented Jan 16, 2014

copleykj commented Jan 17, 2014

pnunn commented Mar 20, 2014

raix commented Mar 20, 2014

pnunn commented Mar 20, 2014

raix commented Mar 20, 2014

pnunn commented Mar 20, 2014

raix commented Mar 20, 2014

lap123 commented Mar 21, 2014

raix commented Mar 21, 2014

lap123 commented Mar 21, 2014

raix commented Mar 21, 2014

raix commented Mar 21, 2014

lap123 commented Mar 21, 2014

aldeed commented Mar 21, 2014

raix commented Mar 21, 2014

aldeed commented Mar 21, 2014

raix commented Mar 21, 2014

aldeed commented Mar 21, 2014

raix commented Mar 21, 2014

aldeed commented Mar 21, 2014

raix commented Mar 21, 2014

aldeed commented Mar 21, 2014

raix commented Mar 21, 2014

raix commented Mar 21, 2014

aldeed commented Mar 21, 2014

aldeed commented Mar 21, 2014

nooitaf commented Mar 21, 2014

raix commented Mar 21, 2014

raix commented Mar 21, 2014

aldeed commented Mar 21, 2014

aldeed commented Mar 21, 2014

raix commented Mar 21, 2014

raix commented Mar 21, 2014

raix commented Mar 22, 2014

aldeed commented Mar 22, 2014

raix commented Mar 22, 2014

nooitaf commented Mar 23, 2014

raix commented Mar 23, 2014

nooitaf commented Mar 23, 2014

raix commented Mar 23, 2014

nooitaf commented Mar 23, 2014

raix commented Mar 23, 2014

raix commented Mar 23, 2014

solshark commented May 30, 2014

aldeed commented May 30, 2014

solshark commented May 30, 2014

solshark commented May 30, 2014