BL4.5-32bit - Moksha outdated?
 

Today, my old netbook keeps telling me, Moksha is outdated and I'm asked to update my system packages to install Moksha 0.17.4.

I'm offered to be reminded later or never again or just hit OK.

I already tried OK and later, but the message is coming back again after a while.

I did a global update for Bodhi in the terminal, but everything seems to be up to date.

So, what am I supposed to do about this, now, please?

It's happening on 5.0.0 64-bit too and started today as well

It's telling me (on Bodhi 5.0 64bit) that my version of Enlightenment is outdated.

Yes, Enlightenment is mentioned in this message here, as well.

EDIT:
I just refreshed synaptic.
Not sure, yet, if it helped.

My 32-bit 5.0 machine woke itself from sleep to put that message on the screen this morning.

And it's here on my 5.0 64-bit with test version of moksha/efl.

Here's a screenshot of the msg, although my guess is every one already saw this today...
https://i.imgur.com/Ek1rZsS.jpg

Seems like refreshing synaptic is the solution for that.
After doing this, the message didn't return, so far.

Here as well, both computers.

Interesting

The same here with BL 3.2.1 with Moksha 0.2.0. We need to check the code. Unfortunately I am on holidays with family. Probably Robert will look at that sooner than me. Anyway we can use "never tell me" option.

http://www.enlightenment.org/ss/e-5d...8.88960503.jpg

EDIT: some first info. At this link you can find the source with update functions
https://github.com/JeffHoogland/moks...bin/e_update.c

Moksha is connecting the e server
url_up = ecore_con_url_new("http://www.enlightenment.org/update.php");
to check the version

Not sure why we can see this for the first time.

Stefan

I already used the "Never tell me" option, but after some two hours that dialog box appears again :-(

Really?

So we need to change the code for removing timer completely.

Stefan

EDIT: moment, I ve just checked the code. The timer is deleted.
if (update_timer) ecore_timer_del(update_timer);
update_timer = NULL;

This is odd indeed

Yes, same here.
Obviously, refreshing synaptic didn't fix anything.

What can an ordinary user do to get rid if this message permanently, please?

well i have been using my laptop on and off since 4 am and this just popped up too. wondering if maybe it could be a hack or some such or contaminated from this site or some such - ya i know - i read too much alien stuff. man this is weird.... Hopefully Ylee can figure this out while stefan in on vacation - enjoy the vaca Stefan!

We need to check if item update.check in config file is set to 0 and saved correctly. Unfortunately I am not able to find how to decode eet file (need Robert). Anyway, I pressed "bother me later" 3 hours ago and I am still without the message.

Stefan

EDIT: success with eet file decoding. Let me look at that.

OK, this is the method

go to .e/e/config/your_profile_name

eet -d e.cfg config output.txt

now open output.txt in editor and lookup at items at the bottom:
value "update.check" uchar: 1;
value "update.later" uchar: 1;

The first one means the update check will happen and the second one if you pressed "bother me later" or not. Having update.later 0 could be fine. Please check it. Anyway we can change both items to zero values and compile back to e.cfg file.

eet -e e2.cfg config output.txt 1

Try to follow this link for another info
https://it.toolbox.com/blogs/jeffhoo...t-files-101915

This is the only thing I can do in this situation.

Stefan

updated laptops yesterday yesterday and this situation just started late afternoon. not sure what caused this.