Hi, when ill try to update the repository has no xenial Release why???

 

Best regards,

 

Nelson

1 hour ago, Nelson R said:

why???

 

Our system only publish packages for supported distributions. Xenial is EOL from our maintaining perspective. We have to cut what is not important, but eats resources.

 

I consider that a xenial repository should be maintained since I have installed systems running Ubuntu 16 and I have problems for not being able to update package.

 

Best regards,

 

Nelson

6 hours ago, Nelson R said:

since I

Are you willing to pay for the cost?

Check personalized support here: https://github.com/armbian/build#support

10 hours ago, Nelson R said:

should be maintained

 

You also should support us before telling what we should and should not do. Perhaps just this way. Otherwise fork the project, leave your daily job and start maintaining it. Perhaps you will get help, perhaps not. Everyday you will bump into a person which expects you will work free of charge hours in their interest ...

@Igor, is there any xenial repository backup? I would like to mantain it for Armbian.

On 8/29/2021 at 7:56 PM, lvmc said:

@Igor, is there any xenial repository backup? I would like to mantain it for Armbian.

@lvmc as far as I know there is no backup of the armbian-part of xenial.

For your
/etc/apt/sources.list
you should use as a part of the url

http://ports.ubuntu.com/dists/xenial/

because only at this server there are armhf  and arm64 packages available.

 

Ckeck / add these xenial-source-directorys which does include newer files:

[DIR]	xenial-backports/	2021-08-30 18:14 	-
[DIR]	xenial-proposed/	2021-08-30 18:33 	-
[DIR]	xenial-security/	2021-08-30 18:13 	-
[DIR]	xenial-updates/	    2021-08-30 18:14 	-



[DIR]	xenial/	2016-04-21 07:43 	

 

@guidol, I was talking with @Igor these days and I think the main issue is how slow (and prone to errors) is the repository generator scripts for generating packages for all releases... it's time consuming and requires a lot of efforts from him. I'm taking a look at the scripts to see if I find a way to optimize it. Older releases must be support as `csc` I think.

 

And yes, I'm using exactly the repositories you suggested, thanks:
 

deb http://ports.ubuntu.com/ xenial main restricted universe multiverse
#deb-src http://ports.ubuntu.com/ xenial main restricted universe multiverse

deb http://ports.ubuntu.com/ xenial-security main restricted universe multiverse
#deb-src http://ports.ubuntu.com/ xenial-security main restricted universe multiverse

deb http://ports.ubuntu.com/ xenial-updates main restricted universe multiverse
#deb-src http://ports.ubuntu.com/ xenial-updates main restricted universe multiverse

deb http://ports.ubuntu.com/ xenial-backports main restricted universe multiverse
#deb-src http://ports.ubuntu.com/ xenial-backports main restricted universe multiverse

 

By the way now it's clearly that the affected packages are only the ones that are build by Armbian, not the packages that are provided by the official Ubuntu repositories.

I doubt that this is the same case, but I had the same error on an orangepi pc so for future reference I comment here.

I had upgraded to buster from strech but it seems that the command lsb_release did not work and probably armian.config could not choose the appropriate debian release. Then the list (/etc/apt/sources.list.d/armbian.list) contained no release info, and I was getting the same error. Just adding the release solved the issue.

 

root@orangepipc:~# cat /etc/apt/sources.list.d/armbian.list
#deb http://apt.armbian.com  main -utils
deb http://apt.armbian.com buster main buster-utils