walt <w41ter <at> gmail.com> writes:
> I avoided yesterday's downgrade from ncurses-6.0 to ncurses-5.9-r4 > because it was obviously(?) a mistake. I believe you. But here's what I just experienced:: I syncd a few hours ago. Now when I just went to upgrade I got this gyration of the latest ncurses debacle:: [ebuild U #] sys-libs/ncurses-5.9-r5:0/5::gentoo [5.9-r4:0/0::gentoo] [ebuild NS #] sys-libs/ncurses-5.9-r99:5::gentoo [5.9-r4:0::gentoo] OK so I masked off those to in package.mask. I decided to up grade a few packages, one at a time. Upgrading openssl got this response:: >>> Emerging (1 of 2) sys-libs/ncurses-6.0-r1::gentoo and it is not stable nor has it been unmasked. Something really funky/flunky be happening with ncurses (again). Now look:: [ebuild NS ~] sys-libs/ncurses-5.9-r101:5::gentoo [ebuild NS ~] sys-libs/ncurses-6.0:5/6::gentoo Surely I can mask off these updates and stay with :: sys-libs/ncurses- 5.9-r4 For a while, till things settle a bit? Weird. I mask off a version and a newer, later version appears. wtf? > Who last updated ncurses, and why? I believe you have 'hit the nail' dead center. Maybe a systemd requirement perhaps? I do not know. I know, systemd is running git now? James
