3

working with procedure procedure to update Ubuntu 18.04 offline machine, the sudo apt-offline install /path_to_downloaded_package_folder do not apply any updates/upgrades. The beginning of the massage I get is :

sudo apt-offline install ./updates_path/
No changelog available
(Y) Yes. Proceed with installation
(N) No, Abort.
(C) Display changelog
(?) Display this help message.
What would you like to do next:  (y, N, ?)y
Proceeding with installation
ERROR: Path for keyring is invalid: /etc/apt/trusted.gpg
gpgv: Signature made Mon 06 Jan 2020 08:17:27 AM MST
gpgv:                using RSA key 3B4FE6ACC0B21F32
gpgv: Good signature from "Ubuntu Archive Automatic Signing Key (2012) <[email protected]>"
gpgv: Signature made Mon 06 Jan 2020 08:18:52 AM MST
gpgv:                using RSA key 3B4FE6ACC0B21F32
gpgv: Good signature from "Ubuntu Archive Automatic Signing Key (2012) <[email protected]>"
gpgv: Signature made Mon 06 Jan 2020 08:18:25 AM MST
gpgv:                using RSA key 3B4FE6ACC0B21F32
gpgv: Good signature from "Ubuntu Archive Automatic Signing Key (2012) <[email protected]>"
gpgv: Signature made Thu 26 Apr 2018 05:38:40 PM MDT
gpgv:                using RSA key 3B4FE6ACC0B21F32
gpgv: Good signature from "Ubuntu Archive Automatic Signing Key (2012) <[email protected]>"
security.ubuntu.com_ubuntu_dists_bionic-security_InRelease synced.
security.ubuntu.com_ubuntu_dists_bionic-security_Release synced.
security.ubuntu.com_ubuntu_dists_bionic-security_Release.gpg synced.

What am I doing wrong?

user1889297
  • 161
  • 4

1 Answers1

5

The apt-offline package no longer functions correctly based upon bugs reported in Debian and Ubuntu such as Debian Bug #871656 and Ubuntu Bug #1848755. Although you followed a posted procedure from a well-known site, Debian pulled the package from testing upstream since it doesn't meet their standards. Currently the development of apt is breaking all offline installation solutions per Debian Bug #934657 which has not been updated since August 2019.

The package author is waiting on changes in apt itself before the tool can get some re-writes accomplished to be able to function again. This situation cannot be fixed presently. You didn't do anything wrong, though.