Default OS update log - Printable Version

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 - amp - 02-08-2020

(02-07-2020, 04:26 PM)ac8dg Wrote: In addition to using /usr/bin/mrfixit_update.sh ,

what are the recommended repositories to use for apt update ?

I have deb and deb-src for these
http://http.debian.net/debian stretch non-free contrib main
http://security.debian.org/debian stretch/updates non-free contrib main
http://http.debian.net/debian stretch/updates non-free contrib main

http.debian.net should be replaced with deb.debian.org (unless you don't want to download via Fastly).

You need the deb-src only for obtaining the source for the packages (for re-compiling, hacking, whatever), so feel free to comment them out for "regular" use.

RE: Default OS update log - rleasle - 02-08-2020

I'm pretty sure that second entry should be http://security.debian.org/ NOT http://security.debian.org/debian

RE: Default OS update log - wdt - 02-08-2020

I did an update today, it downloaded and installed all the 4.4.213 files,,,, BUT
when I type uname -a nothing has changed (after a shutdown)
Is there some trick?
uname -a
Linux Debian-Desktop 4.4.210 #1 SMP Tue Jan 14 22:28:43
OOps,, my screw-up, disregard (had card in sd slot, made boot confused)

RE: Default OS update log - amp - 02-09-2020

(02-08-2020, 12:10 PM)rleasle Wrote: I'm pretty sure that second entry should be http://security.debian.org/ NOT http://security.debian.org/debian

According to https://www.debian.org/security it should be:

Code:
deb http://security.debian.org/debian-security stretch/updates main contrib non-free

It currently also works without the "/debian-security" part though it might be disabled at some point (e.g. when stretch is not supported by the Debian Security Team anymore).

RE: Default OS update log - vfr400racer - 02-10-2020

On the "video hardware codec" thread I was discussing why my standard Debian installation is missing the h264_rkmpp codec. Downloading the latest default Debian image reveals, that the the ffmpeg executable differs from the one on my pbp. I've got mine in November and I am doing regularly "apt-get update", "apt-get upgrade". I assume, installing upstream packages breaks mrfixit2001's modifications.
Can this be true?
If so, is there a way to keep my system up to date without losing mrfilxit2001's modifications?
Regularly wiping the emmc with the newest image is no solution to me, as I've already done a lot of mods to the system.

RE: Default OS update log - Arwen - 02-10-2020

I don't know how others "lost" their modified FFMPEG, but mine is prevented from updating;

Code:
# apt-get upgrade

Reading package lists... Done

Building dependency tree       

Reading state information... Done

Calculating upgrade... Done

The following packages have been kept back:

 ffmpeg

The following packages will be upgraded:

...

I made no changes to the packages. Checking, FFMPEG still has "--enable-rkmpp".

RE: Default OS update log - vfr400racer - 02-10-2020

(02-10-2020, 11:14 AM)Arwen Wrote: I don't know how others "lost" their modified FFMPEG, but mine is prevented from updating;

Code:
# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: ffmpeg The following packages will be upgraded: ...

I made no changes to the packages. Checking, FFMPEG still has "--enable-rkmpp".

I know. It's aptitude!
Just tested it on my sd card image. apt-get shows ffmpeg as being held back. aptitude fetches the package and installs it.
aptitude also breaks ffmpeg. After the upgrade, neither the new nor the modified ffmpeg work:
ffmpeg.org: error while loading shared libraries: libavdevice.so.58: cannot open shared object file: No such file or directory

RE: Default OS update log - amp - 02-10-2020

(02-10-2020, 12:38 PM)vfr400racer Wrote:
(02-10-2020, 11:14 AM)Arwen Wrote: I don't know how others "lost" their modified FFMPEG, but mine is prevented from updating;

Code:
# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: ffmpeg The following packages will be upgraded: ...

I made no changes to the packages. Checking, FFMPEG still has "--enable-rkmpp".

I know. It's aptitude!
Just tested it on my sd card image. apt-get shows ffmpeg as being held back. aptitude fetches the package and installs it.
aptitude also breaks ffmpeg. After the upgrade, neither the new nor the modified ffmpeg work:
ffmpeg.org: error while loading shared libraries: libavdevice.so.58: cannot open shared object file: No such file or directory

It's probably because 'aptitude upgrade' does the equivalent of 'apt-get upgrade --with-new-pkgs'.

If you want to 'hold' a package use

Code:
echo 'package_name hold' > dpkg --set-selections

or configure a pin.

RE: Default OS update log - vfr400racer - 02-10-2020

(02-10-2020, 01:00 PM)amp Wrote:
(02-10-2020, 12:38 PM)vfr400racer Wrote:
(02-10-2020, 11:14 AM)Arwen Wrote: I don't know how others "lost" their modified FFMPEG, but mine is prevented from updating;

Code:
# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: ffmpeg The following packages will be upgraded: ...

I made no changes to the packages. Checking, FFMPEG still has "--enable-rkmpp".

I know. It's aptitude!
Just tested it on my sd card image. apt-get shows ffmpeg as being held back. aptitude fetches the package and installs it.
aptitude also breaks ffmpeg. After the upgrade, neither the new nor the modified ffmpeg work:
ffmpeg.org: error while loading shared libraries: libavdevice.so.58: cannot open shared object file: No such file or directory

It's probably because 'aptitude upgrade' does the equivalent of 'apt-get upgrade --with-new-pkgs'.

If you want to 'hold' a package use

Code:
echo 'package_name hold' > dpkg --set-selections

or configure a pin.

dpkg --get-selections showed ffmpeg on hold.
aptitude doesn't care about this.
I just double checked that.

RE: Default OS update log - sirspate - 02-13-2020

The latest update seems to have made the bluetooth stack more unstable. I have a pair of Taotronics TT-BH22, which are bluetooth noise-cancelling headphones, which is what I'm testing with.

Prior to the last update, things were a bit finicky, but could be worked around:
- If the PBP had never been put to sleep, then they could connect and work fine.
- If the PBP had ever been put to sleep, then they would connect over bluetooth, but after ~4 minutes the connection would time out and die. The bluetooth would stop working, so typically I'd switch to plugged in mode (i.e., use the audio jack) and keep going--or just reboot.

Since the latest update:
- It doesn't matter if the PBP has been put to sleep; the bluetooth stack times out after ~4 minutes. On top of that, the "Bluetooth Devices" applet stops responding. And after ~2 more minutes, the entire UI locks up, requiring a system reboot.

Anyone else seeing weird issues with bluetooth after the latest PBP update?