I have this machine. The BBAI-64 seems to be getting no more updates from a source…
I am slow to the game here. I got some site online where I can port to the BBB but there is some keyring involved that I know nothing about currently.
Anyway, w/out further ado, here:
Err:5 https://debian.beagleboard.org/arm64 bullseye InRelease
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 126.96.36.199 443]
Reading package lists... Done
E: Release file for http://deb.debian.org/debian/dists/bullseye/InRelease is not valid yet (invalid for another 131d 20h 48min 5s). Updates for this repository will not be applied.
E: Release file for http://security.debian.org/debian-security/dists/bullseye-security/InRelease is not valid yet (invalid for another 232d 9h 5min 55s). Updates for this repository will not be applied.
E: Release file for http://deb.debian.org/debian/dists/bullseye-updates/InRelease is not valid yet (invalid for another 232d 6h 54min 48s). Updates for this repository will not be applied.
E: Release file for http://repos.rcn-ee.com/debian-arm64/dists/bullseye/InRelease is not valid yet (invalid for another 232d 10h 53min 18s). Updates for this repository will not be applied.
Is this me or another issue that I cannot overcome myself?
P.S. If you have time, please send guidance. Currently, I will try to set up a git server that may cure some of my woes but…hmm. It most likely will not keep me system up to date. Is this of concern or are people too busy doing other things?
Scratch everything I was just saying. It seems the ole machine fixed itself in milliseconds.
Hello…the board, after a reboot, started to update/upgrade.
A git server will become your best friend.
Right. I have seen this so far in theory. Building the server is not quite that easy for whatever reason.
I listened to the manual in the book for Git. Hopefully, someone has attempted this before w/ a linode/akamai instance.
I will research some more again…
Follow the instructions on the SCM site regarding setting up a git server. Do it EXACTLY as they say, keep in mind they created it. It works perfectly out of the box.
Its only “hard” because so much click bait by those the don’t have a clue and only want to sell pay per view ads. Go to the source and get the facts.
This appears to be the current instruction set.
When you get that done, set up a LAMP stack.
You need something local for serving docs, testing out php, mysql (mariadb on arm) and for real life testing of a device attached to the internet in client server configuration.
The AI64 with the desktop disabled and NVMe attached is a very good platform for a local git / LAMP server.
Thank you. I have been struggling w/ the git-scm.com site so much w/ my server so far.
I know this is not BBB related perse but maybe I should try on my hard drive instead of in the cloud on a website? I think they mean for servers locally and not saying available for the general public.
I am currently working w/ git and gitlab to make this happen. If anyone is interested, I will update once completed.
That command may help. I just saw that one and I will work towards setting this up.
All of our stuff is on local machines.
Some of the hosting sites have the best content regarding setting stuff up for public access. Avoid information on monetized sites, they are all about click bait. The hosting companies want your business and will make sure the content is pretty close to being correct.