Is luckybackup 0.4.9 ready for qt5? Today I have compiled it fine with qt5 and I have made also a personal archlinux package. In "about" is written qt4 but, to be sure, I have checked that the real dependency is qt5 with ldd.
Last edit: hifi25nl 2017-01-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
well, if LB 0.4.9 was ready at all, it sure would be ready for qt5 !!
Please excuse my sense of humour hifi :)
The development of LB has been frozen for good since 0.4.8.
There's been some (well, a lot actually) code contribution that makes LB compatible with qt5 and that is available at the project's git as luckybackup-0.4.9-rc3: https://sourceforge.net/p/luckybackup/code/ci/master/tree/
but I haven't been able to thoroughly test it yet.
Is it this version you compiled ?
If yes, could you please provide some feedback ?
I'm just interested in knowing if the features you used before (eg normal run, scheduling, emails, logs), work ok.
I should make an official 0.4.9 release
(now i'm just talking loudly to myself)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes I compiled that version. The applcation start normally, menus are working fine, but I have not tested a real backup with schedule.
Ok, I will try to test in the next days.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did this happen via a scheduled or a normal run ?
did the task run at all ?
Normaly, if the task is scheduled and the option "skip critical" is enabled, the task should not run if destination is not mounted.
An email should be sent though, letting the user know that the task did not run.
Nevertheless, LB does not do that. I have confirmed, that if a profile is scheduled, it includes one task and that won't run for a reason (eg destination is not mounted), an email is not sent to let the user know.
This is a general LB issue, not a 0.4.9 one and I will have it fixed.
Thank you for poining that out hifi :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It was scheduled, the task did run with some error about destination not found, but not email.
Now I am backing daily from 2 computers. No other problems that I can see. Good work!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is luckybackup 0.4.9 ready for qt5? Today I have compiled it fine with qt5 and I have made also a personal archlinux package. In "about" is written qt4 but, to be sure, I have checked that the real dependency is qt5 with ldd.
Last edit: hifi25nl 2017-01-18
well, if LB 0.4.9 was ready at all, it sure would be ready for qt5 !!
Please excuse my sense of humour hifi :)
The development of LB has been frozen for good since 0.4.8.
There's been some (well, a lot actually) code contribution that makes LB compatible with qt5 and that is available at the project's git as luckybackup-0.4.9-rc3:
https://sourceforge.net/p/luckybackup/code/ci/master/tree/
but I haven't been able to thoroughly test it yet.
Is it this version you compiled ?
If yes, could you please provide some feedback ?
I'm just interested in knowing if the features you used before (eg normal run, scheduling, emails, logs), work ok.
I should make an official 0.4.9 release
(now i'm just talking loudly to myself)
Yes I compiled that version. The applcation start normally, menus are working fine, but I have not tested a real backup with schedule.
Ok, I will try to test in the next days.
Ok, I have tested already!
Backup and schedule fine
Email fine, but option emailBody=Logfile: %l not working
Result
Profile: default
Date: Friday, January 20, 2017
Time: 14:39:26
Errors found: 0
Logfile: %l
Configuration:
[email]
emailCommand=sendEmail
emailArguments= -o tls=yes -f myemail@gmail.com -t myemail@fastmail.fm -s smtp.gmail.com:587 -xu myemail@gmail.com -xp password -u "Luckybackup report" -m %b
emailSubject=
emailNever=0
emailError=0
emailSchedule=0
emailTLS=0
emailFrom=
emailTo=
emailSMTP=
emailBody=Profile: %p
emailBody=Date: %d
emailBody=Time: %i
emailBody=Errors found: %e
emailBody=Logfile: %l
Last edit: hifi25nl 2017-01-20
thank you very much for the (quite fast) feedback hifi.
I appreciate it.
Should you notice anything else if you continue using this version, please le me know :)
Loukas
I have discovered that, if destination is not avalilable (in my case usb hard disk was not mounted) email is not sent.
Did this happen via a scheduled or a normal run ?
did the task run at all ?
Normaly, if the task is scheduled and the option "skip critical" is enabled, the task should not run if destination is not mounted.
An email should be sent though, letting the user know that the task did not run.
Nevertheless, LB does not do that. I have confirmed, that if a profile is scheduled, it includes one task and that won't run for a reason (eg destination is not mounted), an email is not sent to let the user know.
This is a general LB issue, not a 0.4.9 one and I will have it fixed.
Thank you for poining that out hifi :)
It was scheduled, the task did run with some error about destination not found, but not email.
Now I am backing daily from 2 computers. No other problems that I can see. Good work!