1 |
On Tuesday, September 01, 2015 12:13:25 AM Alan McKinnon wrote: |
2 |
> On 31/08/2015 23:13, walt wrote: |
3 |
> > I ask this strange question because this (badly broken) machine once |
4 |
> > again flipped between 6.0 and 6.0-r1 after rsyncing this morning. |
5 |
> > |
6 |
> > First, it emerged 6.0, which turned out to be almost catastrophic |
7 |
> > because the qmerge phase of the emerge failed (although it claimed |
8 |
> > success afterwards) and deleted the entire /usr/share/terminfo |
9 |
> > subdirectory. That was fun, but I won't bore you with the details. |
10 |
> > (The ncurses-6.0 files in /lib64 are dated August 28, BTW.) |
11 |
> > |
12 |
> > Right now emerge tries to install ncurses-6.0-r1 but the 32-bit part of |
13 |
> > the build fails because emerge never ran make in the work/cross/progs |
14 |
> > directory, and so the 32-bit tools didn't get compiled. |
15 |
> > |
16 |
> > I hacked around this by running make in that directory manually, which |
17 |
> > allowed the ebuild install and ebuild package phases to succeed. |
18 |
> > |
19 |
> > Now I have an ncurses-6.0-r1 binary package available but I'm too scared |
20 |
> > to install it because I might need to kill myself afterwards :/ |
21 |
> > |
22 |
> > Any suggestions before I take the plunge? Is ncurses-6.0-r1 the right |
23 |
> > version as of today, Aug 31? |
24 |
> > |
25 |
> > Thanks. |
26 |
> > |
27 |
> > |
28 |
> > |
29 |
> |
30 |
> |
31 |
> |
32 |
> This machine was entirely unaffected by all the recent ncurses issues: |
33 |
> |
34 |
> [I] sys-libs/ncurses |
35 |
> Available versions: |
36 |
> (0) 5.9-r3 (~)5.9-r4 5.9-r5(0/5) (~)6.0-r1(0/6) |
37 |
> (5) 5.9-r99(5/5) (~)5.9-r101(5/5) (~)6.0(5/6) |
38 |
> {ada +cxx debug doc gpm minimal profile static-libs test threads |
39 |
> tinfo trace unicode ABI_MIPS="n32 n64 o32" ABI_PPC="32 64" ABI_S390="32 |
40 |
> 64" ABI_X86="32 64 x32"} |
41 |
> Installed versions: 6.0-r1(12:52:29 30/08/2015)(cxx gpm threads |
42 |
> unicode -ada -debug -doc -minimal -profile -static-libs -test -tinfo |
43 |
> -trace ABI_MIPS="-n32 -n64 -o32" ABI_PPC="-32 -64" ABI_S390="-32 -64" |
44 |
> ABI_X86="32 64 -x32") |
45 |
> Homepage: https://www.gnu.org/software/ncurses/ |
46 |
> http://dickey.his.com/ncurses/ |
47 |
> Description: console display library |
48 |
> |
49 |
> So 6.0-r1 works completely relaible on at least one Gentoo machine in |
50 |
> this world :-) |
51 |
|
52 |
Hmm, I keyworded ncurses and this is what portage wants to do: |
53 |
|
54 |
[ebuild r U ~] sys-libs/ncurses-6.0-r1:0/6::gentoo [5.9-r5:0/5::fernan] |
55 |
USE="cxx doc gpm tinfo unicode -ada -debug -minimal -profile -static-libs {- |
56 |
test%} -threads% -trace" ABI_X86="32 (64) -x32" 3,059 KiB |
57 |
[ebuild U ~] sys-libs/ncurses-5.9-r101:5::gentoo [5.9-r99:5::gentoo] |
58 |
USE="gpm tinfo unicode (-ada%) (-cxx%*) (-static-libs%)" ABI_X86="32 (64) - |
59 |
x32" 0 KiB |
60 |
[ebuild rR ~] sys-devel/gdb-7.10::gentoo USE="client expat python server |
61 |
zlib -lzma -multitarget -nls {-test} -vanilla" PYTHON_SINGLE_TARGET="python2_7 |
62 |
-python3_3 -python3_4" PYTHON_TARGETS="python2_7 python3_4 -python3_3" 0 KiB |
63 |
[ebuild rR ] app-misc/screen-4.3.1::gentoo USE="pam -debug -multiuser - |
64 |
nethack -selinux" 0 KiB |
65 |
[ebuild rR ] app-emulation/wine-1.6.2::gentoo USE="X alsa cups custom- |
66 |
cflags fontconfig gecko jpeg lcms ldap mp3 ncurses openal opengl perl png |
67 |
prelink pulseaudio run-exes samba ssl threads truetype udisks v4l xcomposite |
68 |
xinerama xml -capi -dos -gphoto2 -gsm -gstreamer -mono -nls -odbc -opencl - |
69 |
osmesa -oss -realtime -scanner -selinux {-test}" ABI_X86="32 64 -x32" |
70 |
LINGUAS="-ar -bg -ca -cs -da -de -el -en -en_US -eo -es -fa -fi -fr -he -hi -hr |
71 |
-hu -it -ja -ko -lt -ml -nb_NO -nl -or -pa -pl -pt_BR -pt_PT -rm -ro -ru -sk - |
72 |
sl -sr_RS@cyrillic -sr_RS@latin -sv -te -th -tr -uk -wa -zh_CN -zh_TW" 0 KiB |
73 |
|
74 |
|
75 |
That looks dangerous to me because the first build will upgrade my 5.9 |
76 |
installation to 6.0 and the second will reinstall 5.9. |
77 |
|
78 |
So what happens in between when I have no 5.9 installed but everything is |
79 |
linked against it? Won't it need bash to build the second one? What if the 2nd |
80 |
build fails? Will stuff linked against 5.9 work with 6.0? |
81 |
|
82 |
-- |
83 |
Fernando Rodriguez |