1 |
On Monday, August 31, 2015 7:20:29 PM walt wrote: |
2 |
> On Mon, 31 Aug 2015 20:33:42 -0400 |
3 |
> Fernando Rodriguez <frodriguez.developer@×××××××.com> wrote: |
4 |
> |
5 |
> > On Tuesday, September 01, 2015 12:13:25 AM Alan McKinnon wrote: |
6 |
> > > On 31/08/2015 23:13, walt wrote: |
7 |
> > > > I ask this strange question because this (badly broken) machine |
8 |
> > > > once again flipped between 6.0 and 6.0-r1 after rsyncing this |
9 |
> > > > morning. |
10 |
> > > > |
11 |
> > > > First, it emerged 6.0, which turned out to be almost catastrophic |
12 |
> > > > because the qmerge phase of the emerge failed (although it claimed |
13 |
> > > > success afterwards) and deleted the entire /usr/share/terminfo |
14 |
> > > > subdirectory. That was fun, but I won't bore you with the |
15 |
> > > > details. (The ncurses-6.0 files in /lib64 are dated August 28, |
16 |
> > > > BTW.) |
17 |
> > > > |
18 |
> > > > Right now emerge tries to install ncurses-6.0-r1 but the 32-bit |
19 |
> > > > part of the build fails because emerge never ran make in the |
20 |
> > > > work/cross/progs directory, and so the 32-bit tools didn't get |
21 |
> > > > compiled. |
22 |
> > > > |
23 |
> > > > I hacked around this by running make in that directory manually, |
24 |
> > > > which allowed the ebuild install and ebuild package phases to |
25 |
> > > > succeed. |
26 |
> > > > |
27 |
> > > > Now I have an ncurses-6.0-r1 binary package available but I'm too |
28 |
> > > > scared to install it because I might need to kill myself |
29 |
> > > > afterwards :/ |
30 |
> > > > |
31 |
> > > > Any suggestions before I take the plunge? Is ncurses-6.0-r1 the |
32 |
> > > > right version as of today, Aug 31? |
33 |
> > > > |
34 |
> > > > Thanks. |
35 |
> > > > |
36 |
> > > > |
37 |
> > > > |
38 |
> > > |
39 |
> > > |
40 |
> > > |
41 |
> > > This machine was entirely unaffected by all the recent ncurses |
42 |
> > > issues: |
43 |
> > > |
44 |
> > > [I] sys-libs/ncurses |
45 |
> > > Available versions: |
46 |
> > > (0) 5.9-r3 (~)5.9-r4 5.9-r5(0/5) (~)6.0-r1(0/6) |
47 |
> > > (5) 5.9-r99(5/5) (~)5.9-r101(5/5) (~)6.0(5/6) |
48 |
> > > {ada +cxx debug doc gpm minimal profile static-libs test |
49 |
> > > threads tinfo trace unicode ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" |
50 |
> > > ABI_S390="32 64" ABI_X86="32 64 x32"} |
51 |
> > > Installed versions: 6.0-r1(12:52:29 30/08/2015)(cxx gpm |
52 |
> > > threads unicode -ada -debug -doc -minimal -profile -static-libs |
53 |
> > > -test -tinfo -trace ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" |
54 |
> > > ABI_S390="-32 -64" ABI_X86="32 64 -x32") |
55 |
> > > Homepage: https://www.gnu.org/software/ncurses/ |
56 |
> > > http://dickey.his.com/ncurses/ |
57 |
> > > Description: console display library |
58 |
> > > |
59 |
> > > So 6.0-r1 works completely relaible on at least one Gentoo machine |
60 |
> > > in this world :-) |
61 |
> > |
62 |
> > Hmm, I keyworded ncurses and this is what portage wants to do: |
63 |
> > |
64 |
> > [ebuild r U ~] sys-libs/ncurses-6.0-r1:0/6::gentoo |
65 |
> > [5.9-r5:0/5::fernan] USE="cxx doc gpm tinfo unicode -ada -debug |
66 |
> > -minimal -profile -static-libs {- test%} -threads% -trace" |
67 |
> > ABI_X86="32 (64) -x32" 3,059 KiB [ebuild U ~] |
68 |
> > sys-libs/ncurses-5.9-r101:5::gentoo [5.9-r99:5::gentoo] USE="gpm |
69 |
> > tinfo unicode (-ada%) (-cxx%*) (-static-libs%)" ABI_X86="32 (64) - |
70 |
> > x32" 0 KiB [ebuild rR ~] sys-devel/gdb-7.10::gentoo USE="client |
71 |
> > expat python server zlib -lzma -multitarget -nls {-test} -vanilla" |
72 |
> > PYTHON_SINGLE_TARGET="python2_7 -python3_3 -python3_4" |
73 |
> > PYTHON_TARGETS="python2_7 python3_4 -python3_3" 0 KiB [ebuild rR |
74 |
> > ] app-misc/screen-4.3.1::gentoo USE="pam -debug -multiuser - nethack |
75 |
> > -selinux" 0 KiB [ebuild rR ] app-emulation/wine-1.6.2::gentoo |
76 |
> > USE="X alsa cups custom- cflags fontconfig gecko jpeg lcms ldap mp3 |
77 |
> > ncurses openal opengl perl png prelink pulseaudio run-exes samba ssl |
78 |
> > threads truetype udisks v4l xcomposite xinerama xml -capi -dos |
79 |
> > -gphoto2 -gsm -gstreamer -mono -nls -odbc -opencl - osmesa -oss |
80 |
> > -realtime -scanner -selinux {-test}" ABI_X86="32 64 -x32" |
81 |
> > LINGUAS="-ar -bg -ca -cs -da -de -el -en -en_US -eo -es -fa -fi -fr |
82 |
> > -he -hi -hr -hu -it -ja -ko -lt -ml -nb_NO -nl -or -pa -pl -pt_BR |
83 |
> > -pt_PT -rm -ro -ru -sk - sl -sr_RS@cyrillic -sr_RS@latin -sv -te -th |
84 |
> > -tr -uk -wa -zh_CN -zh_TW" 0 KiB |
85 |
> > |
86 |
> > |
87 |
> > That looks dangerous to me because the first build will upgrade my |
88 |
> > 5.9 installation to 6.0 and the second will reinstall 5.9. |
89 |
> |
90 |
> That's exactly what happened to me last week and it was a disaster. |
91 |
> Don't allow that to happen. After hours of frustration I finally |
92 |
> got 6.0-r1 installed and everything Just Works again, but 6.0 was |
93 |
> another disaster. Do whatever you need to do to avoid 6.0. |
94 |
> |
95 |
> > So what happens in between when I have no 5.9 installed but |
96 |
> > everything is linked against it? Won't it need bash to build the |
97 |
> > second one? What if the 2nd build fails? Will stuff linked against |
98 |
> > 5.9 work with 6.0? |
99 |
> |
100 |
> No, but packages linked against 5.9 will continue to work if portage |
101 |
> doesn't delete the files from 5.9 (@preserved-rebuild, etc) |
102 |
|
103 |
Of course, stupid me isn't thinking right :) |
104 |
I'm paranoid of this package because it made my system unbootable at one point |
105 |
after removing the tinfo flag and libtinfo didn't get preserved but I think |
106 |
that was because it was a rebuild. I just installed the -r101 version first. |
107 |
|
108 |
> I suggest you quickpkg whatever ncurses you have now before you do |
109 |
> anything else. |
110 |
> |
111 |
> I also suggest you see what portage wants to do if you |
112 |
> |
113 |
> emerge -p =sys-libs/ncurses-6.0-r1 |
114 |
> |
115 |
> If the output from that looks reasonable then build 6.0-r1 as a binary |
116 |
> package *before* you install it so you have the binary packages for |
117 |
> both versions ready to go. |
118 |
> |
119 |
> I ran into other problems during the ncurses upgrade but I managed to |
120 |
> work through them, and you know more about this stuff than I do :) |
121 |
> |
122 |
> |
123 |
> |
124 |
|
125 |
-- |
126 |
Fernando Rodriguez |