PINE64
Default OS update log - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: General Discussion on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=112)
+--- Thread: Default OS update log (/showthread.php?tid=7830)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20


RE: Default OS update log - User 6582 - 11-03-2019

(11-03-2019, 07:32 PM)evilbunny Wrote:
(11-03-2019, 07:30 PM)rick1959 Wrote:
(11-03-2019, 01:58 PM)Der Geist der Maschine Wrote: # apt-get update && apt-get dist-upgrade

Unfortunately, those commands aren't working. 
I get this:
W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)

Any ideas? Thanks! :-)

use sudo in front of the commands above...
Thanks EV, but here's what I get when I put sudo in front:
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://cdn-fastly.deb.debian.org/debian stretch InRelease              
Hit:3 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease
Hit:4 http://cdn-fastly.deb.debian.org/debian stretch Release
Reading package lists... Done
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

Any other ideas? Thanks! :-)


RE: Default OS update log - evilbunny - 11-03-2019

(11-03-2019, 07:41 PM)rick1959 Wrote:
(11-03-2019, 07:32 PM)evilbunny Wrote:
(11-03-2019, 07:30 PM)rick1959 Wrote:
(11-03-2019, 01:58 PM)Der Geist der Maschine Wrote: # apt-get update && apt-get dist-upgrade

Unfortunately, those commands aren't working. 
I get this:
W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)

Any ideas? Thanks! :-)

use sudo in front of the commands above...
Thanks EV, but here's what I get when I put sudo in front:
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://cdn-fastly.deb.debian.org/debian stretch InRelease              
Hit:3 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease
Hit:4 http://cdn-fastly.deb.debian.org/debian stretch Release
Reading package lists... Done
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

Any other ideas? Thanks! :-)

&& starts a new command, so you need to add sudo between && and apt-get


RE: Default OS update log - User 6582 - 11-03-2019

(11-03-2019, 07:42 PM)evilbunny Wrote:
(11-03-2019, 07:41 PM)rick1959 Wrote:
(11-03-2019, 07:32 PM)evilbunny Wrote:
(11-03-2019, 07:30 PM)rick1959 Wrote:
(11-03-2019, 01:58 PM)Der Geist der Maschine Wrote: # apt-get update && apt-get dist-upgrade

Unfortunately, those commands aren't working. 
I get this:
W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)

Any ideas? Thanks! :-)

use sudo in front of the commands above...
Thanks EV, but here's what I get when I put sudo in front:
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://cdn-fastly.deb.debian.org/debian stretch InRelease              
Hit:3 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease
Hit:4 http://cdn-fastly.deb.debian.org/debian stretch Release
Reading package lists... Done
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

Any other ideas? Thanks! :-)

&& starts a new command, so you need to add sudo between && and apt-get
Perfect, Thank You!!!

The modified command : sudo apt-get update && sudo apt-get dist-upgrade
Works like a charm! :-)


RE: Default OS update log - Der Geist der Maschine - 11-03-2019

(11-03-2019, 07:48 PM)rick1959 Wrote:
(11-03-2019, 07:42 PM)evilbunny Wrote:
(11-03-2019, 07:41 PM)rick1959 Wrote:
(11-03-2019, 07:32 PM)evidddlbunny Wrote:
(11-03-2019, 07:30 PM)drick1959 Wrote: Unfortunately, those commands aren't working. 
I get this:
W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (1: Operation not permitted)
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (13: Permission denied)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (13: Permission denied)

Any ideas? Thanks! :-)

use sudo in front of the commands above...
Thanks EV, but here's what I get when I put sudo in front:
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://cdn-fastly.deb.debian.org/debian stretch InRelease              
Hit:3 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease
Hit:4 http://cdn-fastly.deb.debian.org/debian stretch Release
Reading package lists... Done
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

Any other ideas? Thanks! :-)

&& starts a new command, so you need to add sudo between && and apt-get
Perfect, Thank You!!!

The modified command : sudo apt-get update && sudo apt-get dist-upgrade
Works like a charm! :-)

In tutorials, you see quite often commands prefixed with either # or $. They are the typical login prompts, # for root and $ for non-root and they indicate what privileges are required to execute them.

How to become root is a matter of preference.

Hope that helps to avoid confusion in the future.


RE: Default OS update log - User 6582 - 11-03-2019

(11-03-2019, 09:16 PM)Der Geist der Maschine Wrote:
(11-03-2019, 07:48 PM)rick1959 Wrote:
(11-03-2019, 07:42 PM)evilbunny Wrote:
(11-03-2019, 07:41 PM)rick1959 Wrote:
(11-03-2019, 07:32 PM)evidddlbunny Wrote: use sudo in front of the commands above...
Thanks EV, but here's what I get when I put sudo in front:
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://cdn-fastly.deb.debian.org/debian stretch InRelease              
Hit:3 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease
Hit:4 http://cdn-fastly.deb.debian.org/debian stretch Release
Reading package lists... Done
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

Any other ideas? Thanks! :-)

&& starts a new command, so you need to add sudo between && and apt-get
Perfect, Thank You!!!

The modified command : sudo apt-get update && sudo apt-get dist-upgrade
Works like a charm! :-)

In tutorials, you see quite often commands prefixed with either # or $. They are the typical login prompts, # for root and $ for non-root and they indicate what privileges are required to execute them.

How to become root is a matter of preference.

Hope that helps to avoid confusion in the future.
Thank You!! :-)
I appreciate not being left to my own ignorance! :-)
Just be patient with me....I'll eventually get it :-)
Good Night!!

(11-03-2019, 09:16 PM)Der Geist der Maschine Wrote:
(11-03-2019, 07:48 PM)rick1959 Wrote:
(11-03-2019, 07:42 PM)evilbunny Wrote:
(11-03-2019, 07:41 PM)rick1959 Wrote:
(11-03-2019, 07:32 PM)evidddlbunny Wrote: use sudo in front of the commands above...
Thanks EV, but here's what I get when I put sudo in front:
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://cdn-fastly.deb.debian.org/debian stretch InRelease              
Hit:3 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease
Hit:4 http://cdn-fastly.deb.debian.org/debian stretch Release
Reading package lists... Done
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

Any other ideas? Thanks! :-)

&& starts a new command, so you need to add sudo between && and apt-get
Perfect, Thank You!!!

The modified command : sudo apt-get update && sudo apt-get dist-upgrade
Works like a charm! :-)

In tutorials, you see quite often commands prefixed with either # or $. They are the typical login prompts, # for root and $ for non-root and they indicate what privileges are required to execute them.

How to become root is a matter of preference.

Hope that helps to avoid confusion in the future.
P.S. How did I get to be a "Senior" member? By age, I guess. Can't be competency!! :-)


RE: Default OS update log - evilbunny - 11-03-2019

(11-03-2019, 09:20 PM)rick1959 Wrote: P.S. How did I get to be a "Senior" member? By age, I guess. Can't be competency!! :-)

I'm guessing but I'd put it down to the number of posts you have made.


RE: Default OS update log - amp - 11-04-2019

(11-03-2019, 01:58 PM)Der Geist der Maschine Wrote: That icon is mostly updating the kernel, uboot and device tree. You should update the actual Debian system from time to time via

# apt-get update && apt-get dist-upgrade

I would recomend:

# apt update && apt upgrade

instead. It's slightly shorter and nicer for interactive use. Besides, 'apt upgrade' should be sufficient for the same release.

'apt full-upgrade' or 'apt-get dist-upgrade' are only needed when upgrading to the next release or if you are running Debian's testing or unstable versions.

You might also want to run 'apt autoremove' (or 'apt --purge autoremove' if you understand the difference between 'remove' and 'purge') when suggested by apt.


RE: Default OS update log - User 6582 - 11-04-2019

(11-03-2019, 09:29 PM)evilbunny Wrote:
(11-03-2019, 09:20 PM)rick1959 Wrote: P.S. How did I get to be a "Senior" member? By age, I guess. Can't be competency!! :-)

I'm guessing but I'd put it down to the number of posts you have made.

Thanks EV!


RE: Default OS update log - zaius - 11-04-2019

(11-03-2019, 09:16 PM)Der Geist der Maschine Wrote: How to become root is a matter of preference.

This build also includes a root terminal.  I found that some commands worked with it, that did not work with sudo.


RE: Default OS update log - Der Geist der Maschine - 11-04-2019

Let me slightly rephrase what I wrote earlier about keeping the system up to date:


Let me clarify what you got. You did not get a full blown Debian, but Debian minus the installer minus uboot, kernel, initrd and other small things like extlinux.conf.

Instead of the installer, you got an .img file. That's a pitty, but not relevant for keeping the system up to date.

Instead of getting uboot, the kernel and initrd from Debian you got them from Mrfixit.


* You need to update what comes from Debian with Debian's own commands:

Code:
$ sudo  sh -c "apt-get update && apt-get dist-upgrade && apt-get autoremove --purge"

or what amp prefers

Code:
$ sudo  sh -c "apt update && apt upgrade && apt autoremove"

It would not surprise me if there are GUIs around this task.


* You need to update what comes from Mrfixit by clicking on his icon.


I suggested some time ago in this very same thread https://forum.pine64.org/showthread.php?tid=7830&pid=48815#pid48815 to provide deb packages for Mrfixit's changes so that they would be seamlessly installed as part of the apt-get commands, but that has not happened. Now, we need to update both parts separately.


Also, you got Debian 9 although the latest Debian version is 10. Debian 9 gets long term (security) support till 06/2022.