peterm6881 has joined #Speedsaver
<Speedsaver`> master @ buildroot-speedsaver-lichee: peterbmckinley pushed 1 commit (https://github.com/Speedsaver/buildroot-speedsaver-lichee/compare/a8188d78971c...350acabb7f66):
<Speedsaver`> master @ buildroot-speedsaver-lichee: peterbmckinley 350aca: board/speedsaver: bump kernel to 5.19.7 (https://github.com/Speedsaver/buildroot-speedsaver-lichee/commit/350acabb7f66625ac0e856864228ef4a2060dfcd)
peterm6881 has quit [Remote host closed the connection]
peterm6881 has joined #Speedsaver
<peterm6881> hey Xogium
<peterm6881> are you there?
<Xogium> peterm6881: sure, what's up ?
<peterm6881> ive updated the lichee repo, but when I try to test the OPi0 build something weird happens
<peterm6881> i think its what caused our problem before
<peterm6881> hang on a sec
<peterm6881> cd Speedsaver
<peterm6881> peter@peter-powermatemlxxx:~/Speedsaver$ git add configs/speedsaver_defconfig
<peterm6881> On branch master
<peterm6881> peter@peter-powermatemlxxx:~/Speedsaver$ git commit -m "board/speedsaver: bump kernel to 5.19.7"
<peterm6881> Your branch is up-to-date with 'origin/master'.
<peterm6881> nothing to commit, working tree clean
<peterm6881> with Lichee, i got something entirely different
<Xogium> did you save your defconfig from the correct buildroot tree though ?
<Xogium> did you actually do a orange pi build and modified that menuconfig ?
<peterm6881> sorry brain is fried, it was a bad idea to ask you anything about it
<Xogium> lol
<Xogium> no worries
<Xogium> think of them as 2 separate projects
<peterm6881> ill just start all over from scratch with a fresh OPi0 directory
<Xogium> you have to run the menuconfig in the correct place for both of them
<peterm6881> yeah I do, everything is completely separate, but somethings not right with the OPi0 guies, I need to go through it again step by step
<peterm6881> guide
<Speedsaver`> buildroot-speedsaver-lichee: peterbmckinley tagged * 8d2806 (Release 2022-09-05) as 2022-09-05 (https://github.com/Speedsaver/buildroot-speedsaver-lichee/commit/8d2806901158)
<Speedsaver`> 2022-09-05 @ buildroot-speedsaver-lichee: peterbmckinley 8d2806: Release 2022-09-05 (https://github.com/Speedsaver/buildroot-speedsaver-lichee/commit/8d2806901158b90c961459b264b34e10c3738872)
<Speedsaver`> buildroot-speedsaver-lichee: peterbmckinley tagged 2022-08-19-dontuse * 046a9e (Release 2022-08-19) as 2022-08-19 (https://github.com/Speedsaver/buildroot-speedsaver-lichee/compare/2022-08-19)
<Speedsaver`> buildroot-speedsaver-lichee: peterbmckinley tagged 2022-09-05 (https://github.com/Speedsaver/buildroot-speedsaver-lichee/releases/tag/2022-09-05)
<Speedsaver`> buildroot-speedsaver-lichee: peterbmckinley tagged 2022-08-19 (https://github.com/Speedsaver/buildroot-speedsaver-lichee/releases/tag/2022-08-19)
<Speedsaver`> master @ buildroot-speedsaver-lichee: peterbmckinley pushed 1 commit (https://github.com/Speedsaver/buildroot-speedsaver-lichee/compare/350acabb7f66...8d2806901158):
<Speedsaver`> master @ buildroot-speedsaver-lichee: peterbmckinley 8d2806: Release 2022-09-05 (https://github.com/Speedsaver/buildroot-speedsaver-lichee/commit/8d2806901158b90c961459b264b34e10c3738872)
<peterm6881> does that all look ok for lichee at least?
<Xogium> hmmm I'm not sure why we get 2 2022-08-19 release
<peterm6881> yup, no clue
<Xogium> one with the dontuse tag and one without it that you seemed to have tagged
<peterm6881> this is literally the steps I take:
<peterm6881> To update kernel locally:
<peterm6881> cd buildroot-2022.02.5-lichee/output/speedsaver
<peterm6881> OPEN A PURE CONSOLE (Ctrl+Alt F2 and log in as Peter)
<peterm6881> make menuconfig
<peterm6881> edit kernel version to current Stable version from kernel.org
<peterm6881> make update-defconfig
<peterm6881> cd
<peterm6881> cd buildroot-speedsaver-lichee
<peterm6881> git add configs/speedsaver_defconfig
<peterm6881> git commit -m "board/speedsaver: bump kernel to 5.19.7"
<peterm6881> TEST KERNEL AT THIS POINT
<peterm6881> git push
<peterm6881> git release -c yyyy-mm-dd
<peterm6881> git status
<Xogium> right that seems good
<peterm6881> so if its doing weird shit, I dont know why
<Xogium> yeah I must admit me neither
<Xogium> my guess is you somehow still have the 2022-08-19 old tag and git will push it
<peterm6881> im not very good at this
<Xogium> well, at least you're doing your best ;)
<Xogium> other people would have been like fuck this and stopped their entire project just because they didn't want to learn git
<peterm6881> i have no clue what a tag is
<Xogium> its a release
<Xogium> its like git says, this commit has this specific tag here
<Xogium> makes it easier for checking out older releases
<Speedsaver`> master @ Speedsaver: peterbmckinley pushed 1 commit (https://github.com/Speedsaver/Speedsaver/compare/a6aad6e3fb37...b5366d660937):
<Speedsaver`> master @ Speedsaver: peterbmckinley b5366d: board/speedsaver: bump kernel to 5.19.7 (https://github.com/Speedsaver/Speedsaver/commit/b5366d660937c276bc9b6575cd99115d9709ed1b)
<Speedsaver`> master @ Speedsaver: peterbmckinley pushed 4 commits (https://github.com/Speedsaver/Speedsaver/compare/b5366d660937...7c10b6b11e41):
<Speedsaver`> master @ Speedsaver: peterbmckinley 2336ac: Release 2022-09-05 (https://github.com/Speedsaver/Speedsaver/commit/2336acbbf5339cd64b0de461fabdaf316b5be3df)
<Speedsaver`> master @ Speedsaver: peterbmckinley 46d42e: Release 2022-09-05 (https://github.com/Speedsaver/Speedsaver/commit/46d42ecb3f05941764303986402c9fda73ed4edd)
<Speedsaver`> master @ Speedsaver: peterbmckinley 7cb2af: Release 2022-09-05 (https://github.com/Speedsaver/Speedsaver/commit/7cb2af9780dafc969a594a53b4203666b5181f27)
<Speedsaver`> master @ Speedsaver: peterbmckinley 7c10b6: Release 2022-09-05 (https://github.com/Speedsaver/Speedsaver/commit/7c10b6b11e41e4f498c18e304e0624bc3a6acac2)
<peterm6881> dont ask
<peterm6881> :)
<peterm6881> ok I think we're good now
<peterm6881> almost
<peterm6881> for OPi0, I ended up with sdcard-2022-09-05-3-g7c10b6b.img
<peterm6881> sigh
<Speedsaver`> Speedsaver: peterbmckinley tagged * 0d577a (Release 2022-09-06) as 2022-09-06 (https://github.com/Speedsaver/Speedsaver/compare/66ab3c929c73^...0d577a792c15)
<Speedsaver`> 2022-09-06 @ Speedsaver: peterbmckinley 66ab3c: Release 2022-09-05 (https://github.com/Speedsaver/Speedsaver/commit/66ab3c929c73ba824af4076ebf223f65ca7ed262)
<Speedsaver`> 2022-09-06 @ Speedsaver: peterbmckinley 0d577a: Release 2022-09-06 (https://github.com/Speedsaver/Speedsaver/commit/0d577a792c158295342bc98c927da46f48681c4f)
<Speedsaver`> Speedsaver: peterbmckinley tagged 2022-09-06 (https://github.com/Speedsaver/Speedsaver/releases/tag/2022-09-06)
<Speedsaver`> Speedsaver: peterbmckinley tagged 2022-09-05 (https://github.com/Speedsaver/Speedsaver/releases/tag/2022-09-05)
<Speedsaver`> Speedsaver: peterbmckinley tagged * 2336ac (Release 2022-09-05) as 2022-09-05 (https://github.com/Speedsaver/Speedsaver/compare/2022-09-05)
<Speedsaver`> master @ Speedsaver: peterbmckinley pushed 2 commits (https://github.com/Speedsaver/Speedsaver/compare/7c10b6b11e41...0d577a792c15):
<Speedsaver`> master @ Speedsaver: peterbmckinley 66ab3c: Release 2022-09-05 (https://github.com/Speedsaver/Speedsaver/commit/66ab3c929c73ba824af4076ebf223f65ca7ed262)
<Speedsaver`> master @ Speedsaver: peterbmckinley 0d577a: Release 2022-09-06 (https://github.com/Speedsaver/Speedsaver/commit/0d577a792c158295342bc98c927da46f48681c4f)
<peterm6881> the tag thing is a bit of a shambles, but we are where we are, just gonna have to live with it forever
<peterm6881> since i'm simply following the same set of instructions
<Xogium> yeah its like weird... I don't have this here. I'm sure its something obvious but since I can't actually investigate because no ssh, well
<Xogium> if its too difficult and releases always end up a mess, maybe its better to just endlessly push commits to the master branch
<peterm6881> I might try no idea what that means and i dont wanna know
<Xogium> its not a whole lot better if you have a release that points to multiple commits after all
<peterm6881> ive had enough for tomight, I should be asleep
<Xogium> basically just do the git commit / git push stiff without git release
<Xogium> so menuconfig, update-defconfig, add config file, git commit, git push
<Xogium> no more releases
<Xogium> *stuff
<peterm6881> cant have that, the release is splashed all over the fucking screen every time you boot
<Xogium> well its not much better if the relseas are all confused from one push to another
<Xogium> releases
<Xogium> I don't even understand why your git pushes releases it has already pushed
<peterm6881> i'll try ok im gonna delete the gits and pull them again
<peterm6881> they defintely both look ok to you?
<Xogium> well they are a bit of a mess like I said, you got the dontuse and 2022-08-19 both
<Xogium> for lichee
<Xogium> so er
<peterm6881> can you tidy all that shit up?
<peterm6881> im obviously not going to touch it
<Xogium> I can but you'll have to restart from scratch, I reckon
<peterm6881> yeah lets do that
<Xogium> otherwise your repo will keep repushint stuff the next time you release something
<Xogium> alright, gonna get some sleep for now and tidy it up tomorrow morning
<peterm6881> it needs to be right if im going to keep it up to date. Its hard enough to build shit and test it then commit and rebuild it again to make it a release (just to make it look pretty on the screen) without it being broke as well
<peterm6881> thanks Xogium
<Xogium> yeah I don't understand why it pushes multiple times the same things
<peterm6881> is the OPi0 repo healthy?
<Xogium> I wonder, would an asciicast of me doing this be good to show you how it goes on my end ?
<peterm6881> its ok, I think we'll be good if I just redo everything at my end after GH is fully spring cleaned and all the trash taken out
<peterm6881> is there any junk in the OPi0 Speedsaver repo?
<Xogium> its a bit weird because your release changelog for 06 contains all the same messages several times, release for 05
<peterm6881> ignore that, I was having trouble editing the file, that was definitely my fault
<Xogium> the 6 last commits in your repo only modify the changelog
<Xogium> I think you attempted several git release commands and that creates tons of these
<peterm6881> I think the information I have is correct, its just that my git is a bit... fucked
<peterm6881> so if you can make it right on GH, and get rid of any rubbish, I think we'll be goot going forward
<peterm6881> ffs...
<peterm6881> good
<peterm6881> night Xogium
<peterm6881> as long as we end up with a release, because sadly that gets splashed all over the display
<peterm6881> so it cant be gobbledegook
<Xogium> well its not that, if you know how to interpret it correctly
<Xogium> it tells you exactly on which commit you are
<peterm6881> i give up
<peterm6881> send me a message on Messenger when you're happy with the 2 GH repos
<peterm6881> then I'll redo everything from scratch, and HOPEFULLY we'll be good to go when Buildroot make a new LTS
<peterm6881> I think I have the process ok, its just that something is broke on my machine
<peterm6881> just make sure the last thing you do is make it a release, otherwise we're no further forward
<peterm6881> thanks Xogium , over and out
peterm6881 has quit [Quit: Leaving]