apt-offline not working after synced

[semaka]

could you please help me to understand how apt-offline is not working with synced packages?
I performed the command below:

apt-offline install myarchive.zip
lot of packages listed as synced

but after I try to install packages from my archive I have the error below:

root@KVM:/tmp# apt-get install tigervnc-standalone-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package tigervnc-standalone-server

I mention that I'm not connected to internet and my sources.list is commented all lines. By the way, on another PC I was able to perform this action without any problem.

Why my package is not seen as soon as I have synced from apt-offline???

thank you,

[rickysarraf]

From what you have briefly described, it looks like you downloaded the package but the apt package update indices are not updated. But this is just my guess.

Can you share the sequence of commands and their console outputs, that you ran ?

[semaka]

your video advice is the happy case when everything works great. I can do the same with first PC which works like a charm but on the second PC in offline mode same packages not working with the error mentioned. I didn't ask you about how apt-offline to be used, because I succeed with it on one PC. I came to you with exactly a problem reported as Unable to locate package, why this happens if all my packages are synced but I have at the end the error: Path for keyring is invalid: /etc/apt/trusted.grg?

[rickysarraf]

That error is when your keyring may not have the file.

• What host system are you on ?
• What version of apt-offline are you using ?
• Have you tried with the latest from the git repository ?

The issue you mentioned is something that was fixed long back. 3787a2b

[semaka]

Do you know for what is used keyring? With or without keyring everything works.
By the way I found the problem. apt-offline works great and extract and copy the needed debs to cache without any problem.

With deep investigation, understanding that apt-get does not get the debs from cache, I found that, if apt-get has everything commented (as my case) in sources.list it does not go to cache.

So sources.list should have repositories there but no internet connection and when repositories are not found it goes to cache and install from there. (/var/cache/apt/archives)

Hope this will help other people having my problem too.
helped me the link:
https://itectec.com/ubuntu/ubuntu-install-a-package-moved-to-var-cache-apt-archives-manually/

[rickysarraf]

Please don't fight the system. There's a reason for everything in place.
https://wiki.debian.org/SecureApt

You can workaround all of it but that is NOT a solution.

[semaka]

thank you, I'll learn more from this.

[semaka]

By the way I found the problem.
apt-offline works great and extract and copy the needed debs to cache without any problem.

With deep investigation, understanding that apt-get does not get the debs from cache, I found that, if apt-get has everything commented (as my case) in sources.list it does not go to cache.

So sources.list should have repositories there but no internet connection and when repositories are not found it goes to cache and install from there. (/var/cache/apt/archives)

Hope this will help other people having my problem too.
helped me the link:
https://itectec.com/ubuntu/ubuntu-install-a-package-moved-to-var-cache-apt-archives-manually/

[rickysarraf]

This is not correct. There's more to it. apt-offline and apt are supposed to work together. The job of apt-offline is to just bridge the gap of network unavailability. Any other change is not needed.

[semaka]

yes they work together, but in my problem exposed here I found what could cause an anomaly for not working anymore. It is not normal what happens but I reproduced my problem each time and I saw the correction. Another bug observed by me, is that if sources.list was commented "#" all lines one time, and if apt-get is not working because of this, even if I change back the file with not comment lines the problem is not solved. It is needed a new OS install to work again.

[rickysarraf]

Please don't mark it as an answer. It will mislead other readers.

[semaka]

but that is the solution why not being as answer???