@spockfish here is the feedback d35d5557d5db6afe
done multiple restarts config changes commits etc still no update. all others have updated no issues.
its a wifi connection but I am now trying to reboot on a wired connection to see if that changes anything.
edit - nope still the same
might need a command line update which is?
It reports that it can’t update, but not why …
So can you run a:
pacman -Syu
And before you hit enter show me what it says?
Thanks
didn’t go so well
[root@DigiAMPBlack ~]# pacman -Syu
:: Synchronizing package databases…
ropieee-beta 16.1 KiB 101K/s 00:00 [######################] 100%
error: failed retrieving file ‘core.db’ from repos-v1.ropieee.io : error setting certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
error: failed to update core (download library error)
error: failed retrieving file ‘extra.db’ from repos-v1.ropieee.io : error setting certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
error: failed to update extra (download library error)
error: failed retrieving file ‘community.db’ from repos-v1.ropieee.io : error setting certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
error: failed to update community (download library error)
error: failed retrieving file ‘alarm.db’ from repos-v1.ropieee.io : error setting certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
error: failed to update alarm (download library error)
error: failed to synchronize all databases
[root@DigiAMPBlack ~]#
ouch…
Ok. This requires some tinkering. Here we go:
step 1: change the url in /etc/pacman.d/ropieee
to
Server=http://repo-beta.ropieee.org/
Save the file and exit.
step 2: run the following command:
pacman -Syu
step 3: run the following command (only if the previous went ok!):
/opt/RoPieee/sbin/configure
It already was the repo so that’s not going to change anything
I hate vi … is there anything else installed on ropieee? nano or pico didnt work
[root@DigiAMPBlack ~]# /opt/RoPieee/sbin/configure
(1/23) configure [00-ropieee_aaa_base]
*** configuring RoPieee base
(2/23) configure [01-ropieee_upgrade_to_xl]
(3/23) configure [05-ropieee_timezone]
*** setting up timezone: Asia/Singapore
(4/23) configure [06-ropieee_hostname]
(5/23) configure [15-ropieee_config_txt]
(6/23) configure [16-ropieee_cmdline_txt]
(7/23) configure [17-ropieee_repositories]
*** setting up RoPieee base repository for channel: beta
*** setting up RoPieee contrib repository for channel: beta
*** setting up ArchLinux mirror repository
(8/23) configure [18-ropieee_audio]
*** setting up audio for: iqaudio-dacplus,unmute_amp
*** enabling USB audio
(9/23) configure [20-ropieee_touchscreen]
(10/23) configure [29-ropieee_network_static_macaddr]
(11/23) configure [30-ropieee_network_wired]
*** setting up wired network
(12/23) configure [31-ropieee_network_wireless]
*** setting up wireless network
trying WiFi driver 8723bu...
trying WiFi driver 88x2bu...
trying WiFi driver 8192eu...
trying WiFi driver rt2800usb... BINGO!
*** wireless interface found: wlan0
*** wireless: WPA supplicant
*** psk: 96339886bc
(13/23) configure [32-ropieee_network_services]
*** restart network daemon
*** restart resolve daemon
*** restart Avahi daemon
(14/23) configure [40-ropieee_ssh]
*** setting up SSH
(15/23) configure [41-ropieee_webpage]
*** setting up RoPieee's webpage
(16/23) configure [50-ropieee_extensions]
(17/23) configure [75-ropieee_remote_control]
(18/23) configure [90-hqplayer_config]
*** configuring HQPlayer NAA
*** disabling output
(19/23) configure [90-librespot_config]
*** configuring Librespot
*** output set to auto, trying to decide...
(20/23) configure [90-shairport_config]
*** configuring Shairport-Sync
*** setting output to HAT
(21/23) configure [90-squeezelite_config]
*** configuring Squeezelite
*** disabling output
(22/23) configure [90-upmpdcli_config]
*** configuring upmpdcli
*** disabling output
(23/23) configure [95-ropieee_update_version_info]
[root@DigiAMPBlack ~]# pacman -Syu
:: Synchronizing package databases...
ropieee-beta 17.0 KiB 106K/s 00:00 [####################################] 100%
error: failed retrieving file 'core.db' from repos-v1.ropieee.io : error setting certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
error: failed to update core (download library error)
error: failed retrieving file 'extra.db' from repos-v1.ropieee.io : error setting certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
error: failed to update extra (download library error)
error: failed retrieving file 'community.db' from repos-v1.ropieee.io : error setting certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
error: failed to update community (download library error)
error: failed retrieving file 'alarm.db' from repos-v1.ropieee.io : error setting certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
error: failed to update alarm (download library error)
error: failed to synchronize all databases
[root@DigiAMPBlack ~]#Awwww… sh…
Please change the file /etc/pacman.d/archlinux and change the server line to:
Server=http://repo-mirror-arch.ropieee.org/201808_00/$repo
Now run again
pacman -Syu
Better I think…seems to be going OK…I still wish there was something more user friendly than vi 
But while its showing in info tab as 2555 and in the footer its showing up in the device list still as 2553 
[root@DigiAMPBlack ~]# vi /etc/pacman.d/archlinux
[root@DigiAMPBlack ~]# cat /etc/pacman.d/archlinux
# RoPieee mirror repo
Server=http://repo-mirror-arch.ropieee.org/201808_00/$repo
[root@DigiAMPBlack ~]# pacman -Syu
:: Synchronizing package databases...
ropieee-beta is up to date
core is up to date
extra is up to date
community is up to date
alarm is up to date
:: Starting full system upgrade...
warning: ca-certificates: local (20180821-1) is newer than core (20170307-1)
warning: dhcpcd: local (7.0.7-1) is newer than core (7.0.5b-1)
warning: e2fsprogs: local (1.44.4-1) is newer than core (1.44.3-1)
warning: ethtool: local (1:4.18-1) is newer than extra (1:4.17-1)
warning: expat: local (2.2.6-1) is newer than core (2.2.5-1)
warning: filesystem: local (2018.8-1) is newer than core (2018.1-2)
warning: firmware-raspberrypi: local (6-1) is newer than alarm (4-1)
warning: fontconfig: local (1:2.13.1-1) is newer than extra (2.13.0+10+g58f5285-1)
warning: gdbm: local (1.17-1) is newer than core (1.16-1)
warning: glib2: local (2.56.2-1) is newer than core (2.56.1-1)
warning: graphite: local (1:1.3.12-1) is newer than extra (1:1.3.11-1)
warning: harfbuzz: local (1.8.8-1) is newer than extra (1.8.7-1)
warning: iproute2: local (4.18.0-1) is newer than core (4.17.0-1)
warning: keyutils: local (1.5.11-1) is newer than core (1.5.10-2)
warning: libglvnd: local (1.1.0-1) is newer than extra (1.0.0-1)
warning: libpcap: local (1.9.0-1) is newer than core (1.8.1-2)
warning: libuv: local (1.23.0-1) is newer than extra (1.22.0-1)
warning: libx11: local (1.6.6-1) is newer than extra (1.6.5-1)
warning: llvm-libs: local (6.0.1-4) is newer than extra (6.0.1-2)
warning: mkinitcpio-busybox: local (1.29.2-1) is newer than core (1.28.4-1)
warning: node-gyp: local (3.8.0-1) is newer than community (3.7.0-1)
warning: nodejs: local (10.9.0-1) is newer than community (10.8.0-2)
warning: npm: local (6.4.1-1) is newer than community (6.3.0-1)
warning: nss-mdns: local (0.14.1-1) is newer than extra (0.10-7)
warning: openssh: local (7.8p1-1) is newer than core (7.7p1-2)
warning: raspberrypi-bootloader: local (20191211-1) is newer than alarm (20180810-1)
warning: raspberrypi-firmware: local (20191211-1) is newer than alarm (20180730-1)
warning: rng-tools: local (6.3.1-3) is newer than community (6.3.1-1)
warning: semver: local (5.5.1-1) is newer than community (5.5.0-1)
warning: shadow: local (4.6-1) is newer than core (4.5-4)
warning: tzdata: local (2018e-2) is newer than core (2018e-1)
warning: wayland: local (1.16.0-1) is newer than extra (1.15.0-1)
resolving dependencies...
looking for conflicting packages...
Packages (6) ca-certificates-utils-20181109-3 libffi-3.3-3 libp11-kit-0.23.20-5 p11-kit-0.23.20-5
ropieee-2:20200717-1 ropieee-version-2:555-1
Total Download Size: 0.54 MiB
Total Installed Size: 3.22 MiB
Net Upgrade Size: -0.23 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
libffi-3.3-3-armv7h 32.9 KiB 205K/s 00:00 [####################################] 100%
libp11-kit-0.23.20-5-armv7h 329.2 KiB 672K/s 00:00 [####################################] 100%
p11-kit-0.23.20-5-armv7h 125.7 KiB 12.3M/s 00:00 [####################################] 100%
ca-certificates-utils-20181109-3-any 7.9 KiB 0.00B/s 00:00 [####################################] 100%
ropieee-version-2:555-1-any 4.3 KiB 0.00B/s 00:00 [####################################] 100%
ropieee-2:20200717-1-any 48.8 KiB 4.76M/s 00:00 [####################################] 100%
(6/6) checking keys in keyring [####################################] 100%
(6/6) checking package integrity [####################################] 100%
(6/6) loading package files [####################################] 100%
(6/6) checking for file conflicts [####################################] 100%
:: Processing package changes...
(1/6) upgrading libffi [####################################] 100%
(2/6) installing libp11-kit [####################################] 100%
(3/6) upgrading p11-kit [####################################] 100%
(4/6) upgrading ca-certificates-utils [####################################] 100%
(5/6) upgrading ropieee-version [####################################] 100%
pre_upgrade()
(6/6) upgrading ropieee [####################################] 100%
post_ugprade()
:: Running post-transaction hooks...
(1/4) Creating system user accounts...
(2/4) Running RoPieee hook...
(3/4) Arming ConditionNeedsUpdate...
(4/4) Rebuilding certificate stores...
[root@DigiAMPBlack ~]# Connection to 192.168.0.147 closed by remote host.
Connection to 192.168.0.147 closed.
micro-00CF6E:~ wizardofoz$You need to run
/opt/RoPieee/bin/configure
and then reboot
Ok I’ll try that in the morning
Will it still be ok if it’s been rebooted etc since then.
you can guess… I can’t read the file.
This is happening all the time when you try to send me feedback…
Ok this didn’t work
root@LoungeLCD ~]# /opt/RoPieee/bin/configure
-bash: /opt/RoPieee/bin/configure: No such file or directory
[root@LoungeLCD ~]# pacman -Syu
:: Synchronizing package databases…
ropieee-beta is up to date
core is up to date
extra is up to date
community is up to date
alarm is up to date
:: Starting full system upgrade…
warning: firmware-raspberrypi: local (6-1) is newer than alarm (4-1)
warning: raspberrypi-bootloader: local (20191211-1) is newer than alarm (20180810-1)
warning: raspberrypi-bootloader-x: local (20191211-1) is newer than alarm (20180810-1)
warning: raspberrypi-firmware: local (20191211-1) is newer than alarm (20180730-1)
there is nothing to do
[root@LoungeLCD ~]# /opt/RoPieee/bin/configure
-bash: /opt/RoPieee/bin/configure: No such file or directory
[root@LoungeLCD ~]#
Oh djeez. I’m tired. Sorry. It’s sbin in stead of bin
/opt/RoPieee/sbin/configure
330am here so I will try it tmro as the pi is powered down now
I’ll reflash the sd card I think on that other one.
Seems my other display pi’s are screen crashed too but GUI is fine
See if this says much affbdd8fe027c033
That has been fixed. If you reboot it will update and fix the screens.
Seems to be good now after the early AM reboot for the bedroom unit…thanks Harry.
That did the trick I think too but now all my other units show as 2555 in the devices tab version except the one I had the issue with which is now 2562 but all the others show footers of 2562 … so still maybe a bug or 3 floating about
@wizardofoz Can you send me logs from one of the other units?
Yes, thanks!
You’re unit actually did update properly, but did not ran configure and hence the version info is not updated.
Harmless, and will be resolved with the next release.
