lanefu

The critical difference is the user has to opt-in to upgrading releases. the default behavior would not be people's shit by a routine `apt update`

I have slightly different approach to going's solution, but this would be compatible with it

Every quarter some one apt updates and breaks something after a release.... This can be prevented. We need to produce a repository per release for our debs just like Debian ubuntu etc aka lane@blipsqueak:~/GIT/lj-tools$ cat /etc/apt/sources.list.d/armbian.list deb http://apt.armbian.com focal main focal-utils focal-desktop becomes lane@blipsqueak:~/GIT/lj-tools$ cat /etc/apt/sources.list.d/armbian.list deb http://apt.armbian.com/chiru focal main focal-utils focal-desktop

yeah unfortunately the kernel and armbian packages have effectively been a rolling release, but I hope we can switch them to be bound to a release in the future. one of the issues is we depend on aptly and it..needs help

I'll give better answer later but yeah there's an option you can set in network manager.conf that lets you set resolver=files

Is anybody able to tell if after the update the UUID for the rootfs no longer matches between boot.scr, /etc/fstab and the init image?

I believe the -minimal images do not include armbianmonitor or armbian-confg and would probably satisfy that desire.

nope.. but there is more conversation about Raxda Zero on our discord server. A few people have some samples there.

Good to see you on the forum as well!

At August 6, 2021, 18:04 GMT -04:00 Our VPS provider had a massive data center outage impacting multiple carriers and power. We were offline for approximately 4.5 hours... our apt redirect service was moved to a temporary location around 3 hours into the outage. It's since moved back. FYI: https://status.armbian.com provides site status info. Prior to this our awesome VPS provider had given us 100% uptime for 13 months

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

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

okay that was mostly blank files and an incomplete contents on the pastebin. ... can you just do apt clean and apt update and see if that fixes it

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. can you also share your other error messages.... and show me /etc/apt/sources.list.d/* try an apt clean before apt update also.

Great fixes @MichaIng code is deployed. Thank you so much!

Lol i got a lot of feedback about https being an undesirable default. Major reason being those on small connections heavilly rely on caching proxies to make life better. And yes persisting protocol based on request would be ideal. How are you at python? https://github.com/armbian/dl-router/issues/2

yeah sorry about the trouble.. I/we had some bad defaults with that, and I had changed them on the direct server, and I think your older install at the apt setup that way.

Change https://apt.armbian.com to http and see if that helps

Short answer: No. This cannot explained with just a few sentences. Man we really need to write the definitive sermon on this and add it to faq / documentation. I think there might be an issue open for it somewhere

spice-vdagent in linux the VM. not sure what's going on there.. can't really help.

You need to install UTM rather than trying to run it from the disk image... UTM is a hypervisor.

I donr have the why but downgrading the uboot package to an older one from our deb archive does seem to solve.

make `userpatches/lib.config` try put the following in NO_APT_CACHER=yes APT_PROXY_ADDR=PROXYHOST:PROXYPORT you may also want to your standard proxy environment variables to it export ex: export HTTP_PROXY=

So Armbian bare-metal on M1 is really contrary to our mission... but I do hope the community can run with the work I've started with the virtual-qemu image... because virtual armbian on M1 is fun and practice.

the WIP file is for building with the armbian build tools... I have some crappy tips in there for qemu. okay so here's a really quick n dirty download UTM for Mac Download zip and extract. this UTM config https://armbian.lane-fu.com/virtual-qemu/Armbian UTM.zip there will be a .utm file and a u-boot.bin file download one of the virtual-emu images from our nightlies or try whatever is here https://armbian.lane-fu.com/virtual-qemu/. don't forget to extra xz file find utm and right click and choose show package contents(edited) [8:15 PM] then you'll expand and put this u-boot.bin in this subfolder open the UTM file then clone it to a new virtual machine edit the new virtual machine goto the drives tab click that little trash can to delete the previous image click import drive to load the new image that you downloaded and make sure you set the interface to virtio because it will default to IDE you'll need to fiddle around with display settings possibly.. the high dpi flag etc. I think I've added to default on the newer images. make sure spice-vdagent is installed. .. this is all I can help with for now. You're on your own from here Please turn this into some better documentation if you can. ideally someone needs to figure out a process around this and document it