Google Code since 25 January belongs to history.
There are already reports that software fails to build due to this shutdown (eg https://go-review.googlesource.com/#/c/18952)
So what about OE?
Here is what we have in meta OpenPLi.
I guess every new build (without old sources folder) will miserably fail until those get fixed.
There are already reports that software fails to build due to this shutdown (eg https://go-review.googlesource.com/#/c/18952)
So what about OE?
find meta-* openembedded-core/ -type f -name "*.bb" -o -name "*.inc" | xargs egrep "code.google.com|googlecode.com" | awk -F: '{ print $1 }' | sort | uniq | wc -l 46Yep we have 46 projects that still referring google code.
Here is what we have in meta OpenPLi.
find meta-* openembedded-core/ -type f -name "*.bb" -o -name "*.inc" | xargs egrep "code.google.com|googlecode.com" | awk -F: '{ print $1 }' | sort | uniq | grep openpli meta-openpli/recipes-connectivity/rtorrent/libtorrent_0.13.2.bb meta-openpli/recipes-connectivity/rtorrent/rtorrent_0.9.2.bb meta-openpli/recipes-devtools/python/python-gdata_2.0.18.bb meta-openpli/recipes-devtools/python/python-mutagen_1.18.bbPython GData can safely go (old google API is history too).
I guess every new build (without old sources folder) will miserably fail until those get fixed.