sce-update, possible quick check feature

[nitram]

Solid. Tested a few times with reboots. No errors reported. Running  sce-update  then selecting items leaves DEBINX untouched. Running  sce-update -a  updates extensions as required and updates OLDDEBINX. Re-testing  sce-update -a  after system fully up to date exits quickly with 'no updates available'.

The new DEBINX system for sce-update -a is sweet. When no potential updates available, even on slow hardware takes only ~5 seconds to report 'No updates'. Only tweak might be to reduce the sleep command upon exit to get cursor back faster.

Thanks for your hard work Jason

[Jason W]

Good news all appears to be working.  I think the sleep command can be removed, will do so next cut.

[netnomad]

I can confirm it as flawless for me.

[Jason W]

I think we are good for a release, this one is surely as or more stable than the current relase.

[jls]

Hi
is the old / new debix thingh eliminated if one after an sce-update -a does a sce-update only on some or one sce?, so a subequent sce-update -a doesn't use old/new debinx and instead check all the sces?
thanks

[Jason W]

'sce-update -a' updates any SCEs needing updating, whether one or all.  Either way, all are up to date with the NEWDEBINX, which is then copied to OLDDEBINX after the updating is complete. 

All 'sce-update -a' sessions use the old/new debinx checking.  And the NEWDEBINX is copied to old only after the updating of any needed SCEs is complete.

I actually have a plan to make this quick check available to all SCEs with any use of sce-update by the use of a 'packagename'.sce.debinx file containing the md5sum of the debinx it was created with, which would be checked against the NEWDEBINX.   

[Jason W]

New RC uploaded that now creates on sce-import packagename.sce.debinx files that contain the md5sum of the NEWDEBINX data they were created with.  This way, when the .debinx file exists, any SCE gets a quick update check with any use of sce-update.

[nitram]

Why is development slowing, 24 hours from stable release to new RC! Appears to work well. New sce-import creates an *.sce.debinx file. Running  sce-update  then selecting that SCE for update check gets almost immediate 'No updates available...' message. Just cosmetic, output indicates no updates available twice.

Code: [Select]

nano
 
You are about to check for updates to the above SCEs. y to continue, n to exit. (y/N): y
 
Checking for updates for nano.sce..
nano is up to date.
No updates available for main or dependency SCEs.
 
No updates available for chosen SCEs at this time.


[Jason W]

lol.  Cosmetic fixes to sce-update now in the latest RC.  Hopefully all is good, we will know when there are updates available to the dCore port we are testing with.   But being a simple md5sum check, the quick just be working.  And the updating aside from that when there are package updates hopefully is now solid.

[nitram]

New RC uploaded that now creates on sce-import packagename.sce.debinx files that contain the md5sum of the NEWDEBINX data they were created with.  This way, when the .debinx file exists, any SCE gets a quick update check with any use of sce-update.

This new packagename.sce.debinx system seems pretty good, but as described only gets created with a fresh import. Haven't had any recent updates, if an SCE gets updated then it presumably gets re-imported along with a fresh packagename.sce.debinx file?

If so that's great. Would there be any value or even possible to also create this packagename.sce.debinx file when an individual SCE is simply update checked, then rechecking again should be instant. Maybe irrelevant as new dCore users will build new SCEs with the helpful *.sce.debinx files already in place. More an issue for existing users that haven't needed to update or import the extension recently. Just wondering...

[Jason W]

A new *.sce.debinx file gets created with any import whether from 'sce-import filename' or an update that includes re-importing when running 'sce-update'. 

I will look into creating an *.sce.debinx when a successful update check is run and there are no updates available, makes sense.

[Jason W]

This would involve a bit of code change inside of loops and involving SCE dependencies.  Would probably as with any code change  introduce bugs and mean time for us spent in testing, fixes, etc.  Since this is a temporary situation, the lack of .sce.debinx files, probably better to leave the code alone and soon the missing .sce.debinx files will work itself out.  And then we can spend our time on other issues that won't just work themselves out.  Thanks for the input, and as always, keep the ideas coming.

Oh, and what I did was a similar below command to create the needed .sce.debinx files to in the future update quickly with though it takes some machine power:

for I in `ls /etc/sysconfig/tcedir/sce/*.sce`; do D=`basename "$I" .sce`; sce-import -n "$D"; done

[nitram]

No problem, thanks for checking it out, keeping it simple probably better.

[nitram]

Interesting experimented, wanted to share. Slowly been re-importing SCEs, couple every reboot, to produce the new /sce/*.sce.debinx files. Last SCE without a debinx was Iceweasel:

Iceweasel update check old way/without debinx file:

Code: [Select]

time sce-update iceweasel
.
No updates available for iceweasel.sce or dependency SCEs.
real    4m 11.78s
user    2m 40.74s
sys     0m 57.27s


Re-importing Iceweasel (local DEBs re-merged/no updates available):

Code: [Select]

time sce-import -n iceweasel
.
Finished importing iceweasel.sce.
real    4m 53.10s
user    2m 15.04s
sys     1m 26.07s


Icweasel update check after iceweasel.sce.debinx created:

Code: [Select]

time sce-update iceweasel
.
iceweasel.sce is up to date.
real    0m 5.39s
user    0m 0.92s
sys     0m 1.27s


The results speak for themselves, thanks again Jason for your hard work. Though re-importing was marginally slower than the old update check, once the *.sce.debinx file is created the re-import process has already paid for itself before a 2nd update check can be completed (if no updates available). Maybe Jason knows of a quicker way to produce this debinx, i don't and this works well. Possible reasons to hold off on re-imports:

- it doesn't matter, you never check for updates
- DEBs are not stored locally, re-downloading would slow process and eat bandwidth
- you're expecting a pending update anyway, then just wait

[Jason W]

*,sce.debinx files created upon successful sce-update with or without having to re-import.  On further looking it was just adding 2 or 3 lines to importupdatecheck.  Also found a couple bugs while testing.  Available in new RC.