The repository 'http://apt.armbian.com bionic Release' is not signed.

[Jerry Jyrer]

Errors shown when doing 

 

$ sudo apt update


...

Ign:1 https://armbian.tnahosting.net/apt bionic InRelease                                                                                        
Get:8 https://armbian.tnahosting.net/apt bionic Release [17.5 kB]                                                                                
Get:9 http://ports.ubuntu.com bionic-updates InRelease [88.7 kB]                                                                                 
Ign:10 https://armbian.tnahosting.net/apt bionic Release.gpg  

....

E: The repository 'http://apt.armbian.com bionic Release' is not signed.
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.

 

[Igor]

Most likely reason:

Edit: I tested manually on beta repository by changing nothing - and index is signed.

[IgorS]

Unfortunatelly i have same situation:

 

igor@ovpngw:~$ sudo apt update
[sudo] password for igor:              
Hit:1 http://ppa.launchpad.net/ultradvorka/ppa/ubuntu bionic InRelease
Hit:2 http://ports.ubuntu.com bionic InRelease                                                     
Hit:4 http://ports.ubuntu.com bionic-security InRelease                                            
Hit:5 http://ports.ubuntu.com bionic-updates InRelease
Hit:6 http://ports.ubuntu.com bionic-backports InRelease           
Ign:3 https://armbian.hosthatch.com/apt bionic InRelease                        
Get:7 https://armbian.systemonachip.net/apt bionic Release [17,5 kB]           
Ign:8 https://armbian.systemonachip.net/apt bionic Release.gpg         
Reading package lists... Done
E: The repository 'http://apt.armbian.com bionic Release' is no longer signed.
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.

Please, what can I do to fix this (if I can anything at all)?

[Igor]

1 hour ago, IgorS said:

Please, what can I do to fix this

Probably our repository has to be reindexed properly. Then it has to be distributed to the CDN. 24-48h is needed after its fixed.

 

But ... I am currently too busy to check and fix this problem and we have no backup for this particular task. If 3rd party tooling is the cause of this problem, then I might need several days just to dig in and fix. I have no knowledge of Aptly which we use for repository management. And TBH no interest to learn its internals. 

[IgorS]

Ok, than I need just wait. No problem, this is not such a big issue.

[Jerry Jyrer]

1 hour ago, IgorS said:

Ok, than I need just wait. No problem, this is not such a big issue.

 

here's what I did to get around the issue in the meantime: 

 

$ cat /etc/apt/sources.list.d/armbian.list
deb [trusted=yes] http://apt.armbian.com bionic main bionic-utils bionic-desktop

 

[IgorS]

Oh, that is good.  I have one machine which really need kernel update, because it was offline last six months. Thank you very much.

[Alex83]

Hey, I have the same issue and would love if the fix will be available soon.

 

Thank you very much in advance!

[Radovan Obal]

Same issue replicated.

[Igor]

I looked again, aptly is signing, but repository is unsigned. Just Bionic. Others are signed. No idea why ... Another workaround is upgrading to Focal.

Spoiler

root@nanopik1plus:/home/igorp # apt update
Hit:1 http://ports.ubuntu.com bionic InRelease
Get:2 http://ports.ubuntu.com bionic-security InRelease [88.7 kB]       
Get:3 https://imola.armbian.com/apt focal InRelease [18.3 kB]                       
Get:4 http://ports.ubuntu.com bionic-updates InRelease [88.7 kB]        
Hit:5 http://ports.ubuntu.com bionic-backports InRelease       
Get:6 https://imola.armbian.com/apt focal/main armhf Packages [909 kB]
Get:7 https://imola.armbian.com/apt focal/main arm64 Packages [1,084 kB]  
Get:8 https://imola.armbian.com/apt focal/focal-utils arm64 Packages [289 kB]        
Get:9 https://imola.armbian.com/apt focal/focal-utils armhf Packages [273 kB]       
Get:10 https://imola.armbian.com/apt focal/focal-desktop arm64 Packages [71.0 kB]   
Get:11 https://imola.armbian.com/apt focal/focal-desktop armhf Packages [24.9 kB]     
Fetched 2,846 kB in 2s (1,358 kB/s)                                              
Reading package lists... Done
Building dependency tree       
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.

 

 

[Jerry Jyrer]

The work around [trusted=yes] no longer works. As Igor said, Bionic one is not signed. 

 

If you must, 

 

$ sudo apt update -o Acquire::AllowInsecureRepositories=true -o Acquire::AllowDowngradeToInsecureRepositories=true

 

for the time being while it's being solved (hopefully, it is).

 

 

[nPHYN1T3]

"... Another workaround is upgrading" == A one line command becomes an all day project.

 

[trusted=yes] is working here...for now.

[Igor]

This problem should be resolved. CDN needs several hours ... so perhaps not right now.

[Jerry Jyrer]

23 minutes ago, Igor said:

This problem should be resolved. CDN needs several hours ... so perhaps not right now.

It's working for me now. Thanks Igor.

[favorit800]

To normal updating need reinstall key:

1. Download key 

wget https://armbian.hosthatch.com/apt/armbian.key

2. Install key 

apt-key add armbian.key

3. Upadte

apt update

 

[AnythingIsFine]

Hello,

 

I am still facing the

E: The repository 'http://apt.armbian.com bionic Release, is no longer signed.

 

 error message when attempting a

apt update

 

So far, I have tried:

 

1. Waiting

2. Re-adding the repository key as suggested by user "favorit800" in this thread.

3. Setting the repository as "trusted" as suggested by "Jerry Jyrer" in this thread.

 

None of the above have worked, I am running:
 

~$ cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=rock64
BOARD_NAME="Rock 64"
BOARDFAMILY=rockchip64
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=baaefaf69-dirty
DISTRIBUTION_CODENAME=bionic
DISTRIBUTION_STATUS=csc
VERSION=21.05.4
LINUXFAMILY=rockchip64
ARCH=arm64
IMAGE_TYPE=user-built
BOARD_TYPE=csc
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
BRANCH=current



~$ uname -a
Linux rock64 5.10.43-rockchip64 #21.05.4 SMP PREEMPT Wed Jun 16 08:02:12 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

 

Any ETA regarding the repository signing ?

 

Regards!

[Smiley Light]

I'm having the same problem on my orange pi and I've tried all the posted answers as well.

[Igor]

1 hour ago, AnythingIsFine said:

Waiting

 

It was fixed for a day or two but it broke again. This means quick fix doesn't work well, while serious and expensive time slot to tear down this complicated mechanism can't be allocated just like that. If you want that things works smoothly, you should not leave also costs of maintenance on our shoulders. We already blow too much on R&D and are crying for help, repository management tool authors as well, ...

 

1 hour ago, AnythingIsFine said:

None of the above have worked, I am running:

Even this is unrelated to the problem from the topic - your hardware (Rock64 due to quality issues) and software (Armbian Bionic is old LTS) and the way it was build (user-built / support is only for digitally signed releases) is not eligible for support we / armbian maintainers pay for you. We can't cover.

 

1 hour ago, AnythingIsFine said:

Any ETA regarding the repository signing ?

 

No ETA. It is urgent matter and will be fixed accordingly. With another quick fix, I am on vacations.

[Igor]

Another try. Hopefully it will last forever and after.

[TRS-80]

6 hours ago, Igor said:

I am on vacations

 

Good for you, you deserve it.

 

No wonder your tone is more calm than usual. 

[kfowler]

I have a large number of distributed orangepi (plus2e and zero) systems running Armbian stretch, and am building a few more. 

I do not want to attempt remote dist upgrades to buster, because if there are upgrade failures it may result in downtime, or worse - require a trip to the site.

I also want all my systems on roughly the same version to simplify support issues.

 

I also understand you do not want to support stretch into the future; but, could the "last" versions of your stretch packages still be available from your package server, even though they are no longer updated/maintained? This would allow me to set up new stretch systems to match the existing systems in the field.

 

I have also had to comment out the /etc/apt/sources.list.d/armbian.list content so that 'apt update' does not error out on all the deployed systems.

 

The day will come where I will devise some reliable procedure to upgrade all deployed systems to a current distribution/kernel; however, I do not currently have the resources to make that happen - something that I expect you guys at Armbian can appreciate.

 

Thank you,

Kevin

 

Edited August 5, 2021 by kfowler

[lanefu]

Most of this is a flaw in how we've managed apt repos to this point, but It does seem reasonable to keep old packages. 

 

Let me talk to @Igor

[lanefu]

Okay so unfortunately not a quick fix.    

We had some major repository issues a while back, and the tool we use to generate is broken.  See This thread for a little more context.

Are you familiar with ansible?   the `lineinfile` module could probably clean this up quickly if you have ssh access.

or the `copy` modules to just replace the armbian sources file

[Igor]

@lanefu I have added - lets see if it doesn't break anything  https://github.com/armbian/build/pull/3087

[Energokom]

On 8/5/2021 at 4:17 PM, lanefu said:

but It does seem reasonable to keep old packages. 

 

 

Archives for old packages are simply necessary. I have 3 pcs of OPI Zero, on the old kernel with OC armbian xenial (since I use TV OUT). And, if I have to add OPI ZERO, I won't be able to do it, so I won't get an update of armbian xenial packages. Thanks!

[Igor]

1 hour ago, Energokom said:

I won't get an update of ubuntu xenial packages.

 

Last change in legacy kernel is several years old -  if there are no changes to kernel sources for years, there is no point in building and updating packages with newer versions.

[Energokom]

17 hours ago, Igor said:

Last change in legacy kernel is several years old -  if there are no changes to kernel sources for years, there is no point in building and updating packages with newer versions.

How i download kernel headrs for old kernel - armbian xenial?

[Werner]

2 minutes ago, Energokom said:

xenial

Firmware packages do not depend on userspace. All flavors (e.g. Focal, Buster and so on) share the same kernel packages.

Search apt. If it is not there what you are looking for then the package is probably too old and has been removed.

[kfowler]

On 8/8/2021 at 12:42 PM, Igor said:

@lanefu I have added - lets see if it doesn't break anything  https://github.com/armbian/build/pull/3087

 

First of all, thank you - I no longer get errors on "apt update" when I have the /etc/apt/sources.list.d/armbian.list content un-commented for my stretch systems. Much appreciated.

 

One thing I expected to get with this was package updates related to armbian versions, such as:

linux-dtb-next-sunxi/now 5.83 armhf [installed,local]
linux-image-next-sunxi/now 5.83 armhf [installed,local]
linux-libc-dev/now 5.70 armhf [installed,local]
linux-stretch-root-next-orangepiplus2e/now 5.83 armhf [installed,local]
linux-u-boot-orangepiplus2e-next/now 5.83 armhf [installed,local]

To be clear(er), I initially install with the Armbian 5.83 image (the last one with the 4.19.x kernel, specifically 4.19.38-sunxi). Then I apt update/upgrade. This had brought my earlier systems up to Armbian 5.90 with kernel 4.19.62-sunxi. But even with the stretch support re-added to the repo server, that is no longer happening.

 

It is likely I am confused about where those linux packages were coming from, and perhaps I'm splitting hairs about dealing with two old kernel versions. But I'd thought it was worth asking about.

Thanks again for the timely response

Kevin

 

[Igor]

https://forum.armbian.com/topic/12210-armbian-1911y-release-notes/