stale version during stabilize-packages.py (hardcoded?)

[gkernelci]

stale version during stabilize-packages.py (hardcoded?)

[mjeveritt]

Really?! What build is this?!

[kuzetsa]

Really?! What build is this?!

other_sources/1101

[mjeveritt]

Mmm, something is very strange there .. need to explore the python script, and what commands its generating to perform those merges, but looks like something is getting cached wrong (at best...) ...

[aliceinwire]

I don't think there is any hardcoded part, maybe the manifest file is broken?
I see is doing some ebuild package_name manifest

[kuzetsa]

the version / string isn't present in the sys-kernel/ck-sources manifest,
so if it's somewhere else I'd only be speculating (which: "manifest file" ?)

[mjeveritt]

I have significantly re-worked the stabilize_packages script, to use pythonic file writing rather than shell. It is functional on vmz-ci-test, as you can see.

@aliceinwire @kuzetsa Please review https://github.com/gentoo/Gentoo_kernelCI/compare/master...mjeveritt:overhaul-stabilize?expand=1 and I will tidy up commits and rebase, and file a Pull-Request after review.

[kuzetsa]

I've looked at the commits and I have no idea what the new python version does (it's been ported to fully native python code, I think? previously was using inline code which called shell commands)... dot dot dot

if it works better and passes sanity checks and is stable, etc. I'm not going to veto the change. 👍

[mjeveritt]

I -think- this should have been squashed, although I don't quite remember what the root cause was at this point in time .. assigning to self to revisit and Close if Fixed.

[aliceinwire]

there is still the problem ?
we can close this ?

[aliceinwire]

@mjeveritt still wating for your pull request

[aliceinwire]

closing as old and don't see such error anymore