Error when trying to change to testing version

Due to a failed SD card I am setting up the latest build of Openhabian on my Raspberry Pi 3+

Unfortunately when I try to change to the latest testing build I get the following error.

2020-05-13_14:57:26_BST [openHABian] Checking for root privileges... OK
2020-05-13_14:57:26_BST [openHABian] Updating Linux package information ... 2020-05-13_14:57:26_BST [openHABian] Loading configuration file '/etc/openhabian.conf'... OK
2020-05-13_14:57:26_BST [openHABian] openHABian configuration tool version: [master]v1.5-599(a2ee130)
2020-05-13_14:57:26_BST [openHABian] Checking for changes in origin... OK
2020-05-13_14:58:01_BST [openHABian] Updating Linux package information ... 2020-05-13_14:58:01_BST [openHABian] Installing or upgrading to latest openHAB milestone release (testing)...
$ apt-key add /tmp/openhab-key.asc

$ apt-get update
Hit:1 buster InRelease
Hit:2 buster InRelease
Ign:3 testing InRelease
Err:4 testing Release
  Unknown date format Bad header data [IP: 443]
Reading package lists... Done
E: The repository ' testing Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

$ apt-get -y --allow-downgrades install openhab2=
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '' for 'openhab2' was not found
FAILED (apt)

I have tried running this command based on other error reported but my result hasn’t changed.

wget -qO - '' | sudo apt-key add -

What am I missing?


Hi @gforce2010,

Sorry to say that you’re not missing anything. This is currently an intermittent bug with the service we use to host our testing repository. The problem comes and goes quite often so might be available later today. Please see this:

As you can see, the issue has been marked as resolved but affects the version that we are on (6.18.1). As soon as JFrog updates our Artifactory instance to the next version, the bug will be fixed. (@Kai I’m assuming we can’t check for updates ourselves here?)