Everything with 15-inject (TeamViewer) and 11-inject (Skype) scripts is OK. They are working and we do not have problem with dpkg database update at all.

Here is what happens with my system to make me so confuse.My IBM Netvista is not longer my testing machine. It has some troubles with the motherboard.Now I use Gateway E-1400 (650 Mhz Processor + 256 MB RAM). Unfortunately it needs firmware-linux package to get working internet connection. I have them in separate squash file which is not made like orphan package (how stupid of me ).So until TeamViewer is loaded after Firmware-linux squash everything is fine.When I inject TeamViewer in 02-FoxyDesktop my Firmware-linux package becomes last loaded and its /var/liv/dpkg/available is loaded on the fly last.This is the confusion which made me worry about the dpkg update.

No problem. Thanks for testing and then confirming that all is well - Good News indeed

I would have been very surprised (terrified) if you had found any issues with the dpkg sub-system. I really did put a lot of work into testing that to ensure it was rock-solid. It is something that I am very confidant with, and I'm also quite proud of what we've got in that area. It really is unique.

Can you give me some more info on the "firmware" package you need to load - perhaps a link ?

I will see what else it adds support for, and I may be able to make you something that will inject it into 01-FoyxRoxy for all 3 kernels, or perhaps see if I can find a way to make a script extension that will automate injecting (any) firmware package(s) into the base 01-FoxyRoxy

Thanks, Brenton!I'm proud with you as well! I still have some troubles to understand fully what you did to make dpkg able to read different file names for available and status files, but there is no doubt this is unique and it works 100% as the update dpkg database after an orphan package is injected.