rvalle Posted January 30 Share Posted January 30 Hi, I have been recently working on a couple of extensions: lvm and cloud-init I forked off "v23.11.2" tag when creating my branches, since they are extensions, and wont alter the framework much. Today I noticed that OdroidUX4 is not building, but it was building last week. A patch seems to be failing. I guess it is a kernel/driver patch. Then my question is: is it possible that, on the same tag (v23.11.2), builds break? I am starting to think that the tag is only for the build process/patch set, but excludes, for example a reference to kernel code. I suppose then the situation is that a kernel update has "broken" a patch, would that be the case? If so, is it possible to also checkout a particular working kernel for the sake of a stable dev environment? How do you normally do? R. 0 Quote Link to comment Share on other sites More sharing options...
rvalle Posted January 30 Author Share Posted January 30 I can see the checkout is here: ``` [🐳|🌱] git: Fetch from remote completed, rev-parsing... [ 'kernel:6.1' 'odroidxu4-6.1.y' 'FETCH_HEAD' ] [🐳|🌿] Using Kernel git revision [ 5737e0cc255c905e3c35a0186ee528ba7f056ae8 at 'Mon Jan 29 21:34:07 UTC 2024' ] ``` I can see there was an update yesterday at hardkernel repo, that is used here. I guess something broke. 0 Quote Link to comment Share on other sites More sharing options...
rvalle Posted January 31 Author Share Posted January 31 is there anyway to point the checkout to a particular revision? 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted January 31 Share Posted January 31 1 hour ago, rvalle said: is there anyway to point the checkout to a particular revision? We pin major releases this way (branch v23.11) https://github.com/armbian/build/commit/d69350a88447ee64bbb50b443f86858a7f6f4075 while main (or some tag) is not. For mainline based, check this: https://github.com/armbian/build/blob/main/config/sources/mainline-kernel.conf.sh 23 hours ago, rvalle said: How do you normally do? Main branch is updated and fixed daily in case upstream messes up. Just keep rebasing. 0 Quote Link to comment Share on other sites More sharing options...
rvalle Posted January 31 Author Share Posted January 31 @Igor it is a bit confusing. OdroidXU4 is now building on main. I guess a fix was posted. However, I am not sure if it is building on v23.11. Should a kernel update break the v23.11 tag? Perhaps it is an issue at my environment. 0 Quote Link to comment Share on other sites More sharing options...
rvalle Posted January 31 Author Share Posted January 31 (edited) Yes, managed to build OdroidXU4 on the main tag but not on v23.11.2, I need to investigate why is this. I even deleted the local armbian build docker container, just in case. Edited January 31 by rvalle 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted January 31 Share Posted January 31 43 minutes ago, rvalle said: OdroidXU4 is now building on main. I guess a fix was posted. Yes. https://github.com/armbian/build/commit/833e1c20c63ea3da7f1323429828e94eaa9b52c7 44 minutes ago, rvalle said: However, I am not sure if it is building on v23.11. We forgot to pin it to the commit / version. Its still branch: https://github.com/armbian/build/blob/v23.11/config/sources/families/odroidxu4.conf#L24 0 Quote Link to comment Share on other sites More sharing options...
rvalle Posted January 31 Author Share Posted January 31 thanks! that explains everything. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.