-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] profiles: remove obsolete package.accept_keywords entries #16
base: master
Are you sure you want to change the base?
[WIP] profiles: remove obsolete package.accept_keywords entries #16
Conversation
Thanks, been meaning to do that for some time ^-^
Unfortunately, as I'm travelling atm, I can't immediately check the impact of this.
Would you mind therefore getting a current copy of the gentoo-on-rpi3-64bit image, applying this PR, then doing a pretend emptytree @world emerge (with bdeps) to ensure nothing wants to be downgraded (or worse!) as a result?
If that works out OK, I'll merge it.
Best, sakaki
--
[email protected]
|
Will take me a while to get back to this, sorry, don't be surprised. |
…d for arm64 Most of entries in profiles/targets/rpi3/package.accept_keywords/* specify value "* ~*", which means "package is visible if it is in stable or testing status on any architecture". This means, once any affected package gets a new ebuild having *any* keyword, e.g. ~amd64, it becomes "visible" as a pending update for the system. This is not a bad trick per se, especially for a deliberate "bleeding edge" system, and especially in earlier times when arm64 didn't maintain a stable keyword. But this means potentially dealing with more cases of breakage, because Gentoo staff hasn't yet assured that the new version works on arm64 architecture. This commit turns such lines, for packages which are keyworded for arm64 (at least in unstable status, ~arm64), into lines with just the package name, which means "package is visible if it is in stable or testing status on *host* architecture". This means arm64 in this case. It might lead to some confusion for people who are trying to use the overlay for arm (32-bit) systems, but they don't seem to be the target audience anyway. I am open to changing this commit to list arm64 explicitly. The script used to produce the change: REPO=/usr/portage cat profiles/targets/rpi3/package.accept_keywords/* \ | grep -v -E '^$|^#|^=' \ | awk '{ print $1 }' \ | sort -u \ | while read CATPN; do if grep -q 'KEYWORDS=.*arm64' $REPO/$CATPN/*.ebuild &>/dev/null; then # Keyworded, stable or unstable # Replace '$CAT/$PN * ~*' which is 'accept stable or testing on any arch' # with '$CAT/$PN' which is 'accept testing on host arch' sed -i -e "s:^${CATPN}[ ]\+[*] [~][*]$:${CATPN}:" profiles/targets/rpi3/package.accept_keywords/* fi done
0e2f7f9
to
f648cf5
Compare
I reviewed what I was attempting to do here, and realized that my previous approach was too far from correctness. I have run
The only downgrade is media-gfx/gimp, and it is explanable - the package has "just recently" got keyworded arm64, but not in the latest ebuilds unfortunately. I am now re-running having added |
I see the same conflicts if i run the same command without my patch. So perhaps exactly that command is not indicative? |
30 Oct 2020: sadly, due legal obligations arising from a recent change in my 'real world' job, I must announce I am standing down as maintainer of this project with immediate effect. For the meantime, I will leave the repo up (for historical interest, and since the ebuilds etc. may be of use for others looking to take forward Gentoo on 64-bit RPi systems); however, there will be no further updates to the underlying binhost etc., nor will I be accepting / actioning further pull requests or bug reports from this point. Email requests for support will also have to be politely declined, so, please treat this as an effective EOL notice. |
The removed entries are now keyworded for both arm and arm64 in main
Gentoo tree.
Bash script: