It is the package libkpathsea6. I re-imported that same 100-desktop-jessie package showing the .15 MB to download though updatesce said no updates, and when importing it yet again and then rebooting it showed 00.00 size to download on a subsequent import.

Lets keep our eye out for any other time that updatesce says no updates yet there is a new deb downloaded upon importing.

Oh, and I will consider an expert option of not creating md5sum files for the imported SCEs. Would be simple and not disrupt things, can be put in /etc/sysconfig/sceconfig for persistence.

Evidently there is an issue with the updatesce checking of the 000-base-jessie type of SCEs. Will check into it. Most likely the issue with the above mentioned deb that was to be updated.

I saw that on a 1.9 GB SCE extension on my usb key, it takes 1 min 36 sec to simply md5sum check it. Since there can be a performance hit that not everyone wants when using loadsce, I added a boot code "nomd5" that will let loadsce load SCEs without md5sum checking them which can save a bit of time if they are large. This is an expert option, and assuming there is any trouble when using this that the first thing to do is run an md5sum check on the SCE directory. I used a boot code since this way importsce will create the proper md5sum file that can later be used to check the integrity of the extension later, and since an option in /etc/sysconfig/sceconfig has to be backed up and restoring the backup occurs after extensions are loaded at boot.

Uploaded a bug fix, changing contents of sce.dep files wheither manually or by re-importing using the -d option will now cause SCEs that depend on the one with the changed .dep file to report needing an update when updatesce is run.

Simply importing the SCEs that depend on the changed one already accounts for any missing or changed entries in dep files.

100-desktop-jessie, 200-multimedia-jessie, libreoffice and vbox are based on 000-base-jessie,so after an update of 000-base-jessie all other packages need to be re-imported?this happened for me... just one little package in 000-base-jessie needed an update,so all other packages that are based on this base-packages were re-imported.

after the re-import and the reboot,"update -a -c" results in following message:

Basically that is the desired behavior. It sounds like overkill, but lets say you specify libtiff-tools as a package in the list of 000-base-jessie, and it depends on liblzma5. If dependencies change of libtiff-tools and it no longer depends on liblzma5, then if 100-desktop-jessie has a package that depends on liblzma5 and it was originally satisfied by that SCE depending on 000-base-jessie, after the update 100-desktop-jessie is now broken. Dependencies don't often change but the sometimes do especially when a Debian release is still in the "testing" stage.