Archived Forum

is there any feature- or change-list available? Did not find anything like this. 

Nope, I don't think so.

You can have a look at the commit messages in the logs. Move to your emoncms (or raspberrypi module) folder and

git diff origin/master

or

git difftool origin/master

(I configured difftool to use vim -d which makes the diff more readable, editable, etc)

origin/master is a guess. On my config, origin is my github fork and I refer to emoncms repo as upstream, so it is upstream/master. But if you just cloned the emoncms repo on your rasp, I think origin is the default.

You can also browse the log history on github:

https://github.com/emoncms/emoncms/commits/master

https://github.com/emoncms/raspberrypi/commits/master

Basically, the code has been rearchitectured, so there is a lot of under-the-hood improvements you might not notice. There's also a wholeset of more or less minor improvements and bugfixes. I can't tell more about emoncms.

Partial list for the raspberrypi module in particular:

- Broadcast time to synchronize emonGLCD (can cause errors (workaround coming), use with caution, disabled by default)

- The RFM2Pi Gateway python script was integrated in master but in a way that did not make it really usable. It is now functional. See readme for usage instructions if you're interested.

Sorry for not being able to present it in a way that would make you eager to update... But the update is recommended anyway. At least to provide some feedback and benefit from the bugfixes.

I plan to write a change list soon and blog about the release.

The documentation needs looking at too.  canary50 in http://openenergymonitor.org/emon/node/2148 doesn't even appear to be able to find it, and is confused.

[Edit] ... confused because he can't save the name given to an input.

Is there any possibility to implement a function in Emoncms that shows it's actual version and maybe the newest version available via git?

For me it's not possible to check what Emoncms version I use.

If you installed via git, from the emoncms folder, run;

$ git whatchanged -5

and it should show you the last 5 commits & ID's (press 'q' to exit)

But I agree, a changelog would be a welcome addition as the changes to the master branch are coming thick & fast.

Paul

Hi

Trying to upgrade. Cleared cache.

Running database update results in this error:-

Fatal error: Call to a member function fetch_object() on a non-object in /var/www/emoncms/Modules/admin/update_class.php on line 76

Any ideas what is wrong and more important how to fix?

Regards

Ian

I'd like to see the build or version number on the admin page. Now I had to guess if this update was meant for me.

It's easy to add a major version number in the admin page (I suppose).

It's a bit more heavy to change minor version each time a minor commit gets integrated.

Trystan is trying to define a workflow that would be a good tradeoff between stability and reactivity.

https://github.com/emoncms/raspberrypi/issues/21#

I think this versioning issue is connected to the stable/dev branch debate.

Hi

I did the "git pull" in emoncms directory. This is worked many times before but now I cant log in anymore. Red stripe came below the password box.

I tried that as well : http://emoncms.org/site/docs/upgrading

EDIT: OK now i got the database update running this was on wrong place:

$updatelogin = true;

Now nothing is updating.

Fatal error: Cannot use object of type Route as array in /var/www/emoncms/Modules/raspberrypi/raspberrypi_controller.php on line 22

EDIT: git pull in rasperrypi directory fixed this.

Good to hear you got it fixed Tomis.

Ian, the error I think you have is one I fixed with an update on saturday morning, is there a chance that your latest download was friday?

The error refers to update_class.php not being able to find the record field in the input table which should have been created in the first step of the upgrade process the database schema update. The saturday fix made sure that it had updated the database before getting to that second part.

Good idea about displaying the version number. Ilde and I have been discussing and making the first steps towards an upgrade process where there is an version number for every change to the database, where the version number is used by emoncms to determine what changes to apply, so once that is added displaying it should not be too hard.

The latest upgrade applies to all installations of emoncms that contains a Modules folder in the base directory rather than the older version that had separate controller, view, model folders (that version was called emoncms v3). After emoncms v3 came "Modular emoncms" which was just a name that described the change of application structure. When thinking about what to call the latest version my thinking was that if emoncms "Modular" is in effect the 4th release then this latest version is v5.

Trystan

To add: Id say if there's any doubt about what minor update version your on, ie changes day to day since last wednesday and your experiencing bugs or just curious if there's been an update then a good rule of thumb would be: if in doubt do a:

git pull origin master

Git will then tell you if your already up to date or not.

You can do a

git fetch origin

if you just want to know if there's been change but don't want to update yet. This will download all new commits in all branches, so if you see something, it does not mean master branch itself was changed. The change can be in dev branch.

After the fetch, you can see a diff of your version and latest master:

git diff origin/master

or

git difftool origin/master

If I run $ git status it returns # On branch dev

I run updates by $ git pull origin master and it updates from the master branch OK, but (in simple terms) how can I change the default from the 'dev' branch to 'master'.

I've tried to read the git book, but it might as well be written in a foreign language!!

$ git branch -a

tells you which branches are available and which one is currently selected

$ git checkout branch_name

allows you to select the one you want.

I suppose at some point you chose to use the dev branch. If you want to use the latest revision in master, you can

$ git fetch origin

$ git checkout origin/master

You will be in a state the git manual refers to as "detached HEAD". (Don't ask...)

Or, to stick to the "usual way" that is suggested in the docs here and that people expect from you when trying to help you with a command you may as well select your local master branch, then pull the changes.

$ git checkout master

$ git pull (I think origin master is the default for the pull command)

Thanks Jérôme, I tried 'the usual way' and it worked great!

Paul