[ralphy]

We can always send a package update for liteupgrade, can't we? If we hear noises about the upgrade we can jump right back at it.

I'd recommend not to wait until 3.6 and to come back to it right after releasing 3.4. I do not want to be a pain but I'm almost sure there will be issues. The things I changed at that time were not the result of my imagination Jerry, believe you me please... I'm gonna fire a 3.2 VM an try to upgrade it to see how that goes. 

Off topic:

I found more things that need fixing. (Network Share Settings)

* The first dialog Cancel button does not cancel the application.
* Network Shares Settings may benefit from yad so that we can use a needed 3rd button in the "Restart Service - Edit Again" dialog box
* Network Shares Settings litemanual documentation needs to be updated to include Firewall Rules. The firewall is enabled by default and here are no rules to allow SAMBA traffic IN. I would pay anyone in pure gold if they can connect to the share without adding the rule to the firewall :P
* Consider setting the netbios name = HOSTNAME on Network Share Settings first execution - To simplify the margin for errors in the config file, we could grep the machine hostname and sed it o the samba config file on Network Share Settings first execution after authentication. This makes life easier for users, one less setting for them to worry about.

I hate testing because I find things that haven't been taken care of and that pisses me off  ;D

[valtam]

Lets stay on topic here please, we can address separate applications in a separate thread. I need my information stream to be focused, no distractions.

We can ofc send an update for Lite Upgrade post 3.4. I've done it before.

Ralphy, listen to me, I don't doubt any of what you have said before, I don't think anything is in your imagination, if you think that I think that, then we still have much to learn about each other. I'm much smarter than that, and I have never accused you of doing such. You have to remember, I have many balls in the air with Linux Lite. I am not complaining, I love my workload, but those contributing need to be aware of that when we collaborate.

[valtam]

I have said recently, that I will take care of the LL Upgrade code. If you notice any bugs, please report them and I'll take care of it. Cheers :)

[ralphy]

Lets stay on topic here please, we can address separate applications in a separate thread. I need my information stream to be focused, no distractions.

We can ofc send an update for Lite Upgrade post 3.4. I've done it before.

Ralphy, listen to me, I don't doubt any of what you have said before, I don't think anything is in your imagination, if you think that I think that, then we still have much to learn about each other. I'm much smarter than that, and I have never accused you of doing such. You have to remember, I have many balls in the air with Linux Lite. I am not complaining, I love my workload, but those contributing need to be aware of that when we collaborate.

I understand you are under lots of pressure because of the workload ahead of you. Maybe what I've said have made it sound as if I'm being pushy instead of finding the best way to help you get through; please accept my apologies if that has been the case. I simply wanted to bring to your attention something that I considered a problem. So, allow me go back to the roots and be helpful. I'm sticking wth your last words... it is working... and if it is found broken at some point we will fix it. I need to run tests and find out that something doesn't work so it can be reported and addressed. Just saying that it was broken doesn't help any of us... I may just be completely wrong!

So, yeah... Keep pushing forward and ignore anything else not related to liteupgrade (I've taken notes to go back to those things later).

[valtam]

There's no need to apologize. Our understanding in time, will evolve, and the community and those new to linux will benefit from that.

[ralphy]

Here is the issue Larry...

https://unlockforus.com/downloads/linuxl...pgrade.mp4

And here is the fix dated January 1st: https://github.com/linuxlite/liteupgrade...367f228000

Let me know if I can be of any further help at this point. Cheers!

[valtam]

Now I see. I need to do some housekeeping on that next. Perms here are root:root for /etc/skel Regards, Larry :)

[ralphy]

Hey Larry... I mean [member=2]Jerry[/member],

Just fetched the latest liteupgrade commit from master:

Upgrade gave me just 2 errors so far...

1- Lite Welcome screen ... It does not have a check for lite_welcome.desktop and instead it throws an error saying that it might be already enabled... I recommend updating LITEWELCOME function as follow in lite-upgrade-series3 :

Code:

LITEWELCOME() {
if [ ! -f /home/$USER/.config/autostart/lite_welcome.desktop ]; then
  UPDATER=$( ln -s /usr/share/applications/lite_welcome.desktop /home/$USER/.config/autostart && sleep 2 |
  zenity --progress --percentage=20  --title="Setting Lite Welcome to autostart..." \
         --width=600 --auto-close)
   unset UPDATER
else :; fi 
}

The second error has to do with permissions... still it cannot copy something to /etc/skel but I think you're looking into that one.  Let me know when you have things in place so I can run some more tests.

Cheers!

[valtam]

What's the second error, do you have any specifics please?

[ralphy]

What's the second error, do you have any specifics please?

It seems the error happens in the HTOPTHEME() function: cannot create regular file '/etc/skel/.config/htop/htoprc': Permission denied (lite-upgrade-series3)