1 |
On 08/13/2016 10:22 AM, hw wrote: |
2 |
> james schrieb: |
3 |
>> On 08/12/2016 07:26 AM, hw wrote: |
4 |
>>> Michael Orlitzky schrieb: |
5 |
>>>> On 08/10/2016 06:54 AM, hw wrote: |
6 |
>>>>> |
7 |
>>>>> Hi, |
8 |
>>>>> |
9 |
>>>>> I´m trying to upgrade portage because I´m getting a message that it |
10 |
>>>>> needs to be able to work with EAPI 6 packages and can only do EAPI 5. |
11 |
>>>>> |
12 |
>>>>> I´m running into merge conflicts when trying to update portage, and |
13 |
>>>>> apparently one of the packages (dev-python/cryptography) I could try |
14 |
>>>>> to update first to be able to update portage requires a version of |
15 |
>>>>> portage that can handle EAPI 6 packages. |
16 |
>>>>> |
17 |
>>>> |
18 |
>>>> Try the other suggestions first -- but as a last resort -- you can |
19 |
>>>> always grab a new stage3 that should contain an updated version of |
20 |
>>>> portage and simply overwrite the portage files on your machine. A |
21 |
>>>> quickpkg from another Gentoo machine (or the liveCD?) would also work. |
22 |
>>>> |
23 |
>>>> |
24 |
>>> |
25 |
>>> I´m trying to update a production server here. If I overwrite the whole |
26 |
>>> system, who knows what might break. I can take it down for a few |
27 |
>>> hours in the evening unless I want to work over night, which is not |
28 |
>>> really an option. |
29 |
>>> |
30 |
>>> There must be a way to update a Gentoo installation without breaking it. |
31 |
>>> As wonderful as it otherwise is, updating Gentoo is always a nightmare |
32 |
>>> which |
33 |
>>> makes me very seriously consider not to use it anymore. Updating |
34 |
>>> needs to |
35 |
>>> be easy and flawless and not something you always run into weird issues |
36 |
>>> with. |
37 |
>> |
38 |
>> When I run gentoo as a critical server, I always have a second, |
39 |
>> redundant system pretty much identical, on stanby. I upgrade the |
40 |
>> stanby first and run it a few days, then the production system. It |
41 |
>> makes reliability extraordinarily high. But, the again, I do a version |
42 |
>> of the |
43 |
>> same thing with all critical systems, or I do not work on them. |
44 |
> |
45 |
> This isn´t really an option because the problem is with the updating |
46 |
> itself, not with something not working after the update has been |
47 |
> performed. |
48 |
|
49 |
If you have an identical, second system, then you can test whatever you |
50 |
want on trying to complete your upgrade. Get the second system up and |
51 |
running. Disconnect the ethernet on one and upgrade the other. If you |
52 |
fail, then just switch the ethernet cable. Sometimes you can just |
53 |
reassign the ethernet on one, so you can ssh into it and look around, |
54 |
while working on the other. (2) indentical systems allow you to work on |
55 |
one and keep the other stable, until the upgrade is finished. |
56 |
|
57 |
> |
58 |
>> Granted, |
59 |
>> as successful consultant, I have that luxury. |
60 |
> |
61 |
> It´s time consuming ... |
62 |
> |
63 |
>>> Did they recently make a new liveDVD? |
64 |
>> |
65 |
>> A few months ago. |
66 |
>> |
67 |
>> https://wiki.gentoo.org/wiki/Project:RelEng/LiveDVD/20160514 |
68 |
> |
69 |
> Cool, the old one was really getting old. |
70 |
> |
71 |
> |
72 |
>> Perhaps a better solution is to make a stage-4, of your current gentoo |
73 |
>> (production) system, verify that the stage-4 works by using it to |
74 |
>> install a similar system, test and deploy. And then hack or fix the |
75 |
>> production system, during the daytime, at your leisure? |
76 |
>> |
77 |
>> Stage-4 gentoo systems have been around a long time. Documentation |
78 |
>> varies and most have their own 'home spun' approach to stage-4 |
79 |
>> replicant systems, backups etc etc. |
80 |
> |
81 |
> It might be a way to try and see if upgrading from older states step by |
82 |
> step until the installation is current would work. But how do I do that? |
83 |
> |
84 |
|
85 |
In normal times, you could just make a stage 4. It's like a complete |
86 |
backup that installs. Like most other similar approaches, I always test |
87 |
them out to ensure they install and populate as needed. If you google, |
88 |
for gentoo : stage-4 you'll find lots of examples with slightly |
89 |
different steps. |
90 |
|
91 |
Here's an old one, translated:: |
92 |
|
93 |
http://translate.google.com/translate?prev=/language_tools&u=http%3A%2F%2Fgentoo-wiki.gentoo.ru%2Fwiki%2FStage4 |
94 |
|
95 |
There are better stage-4 guides, so just google for them:: |
96 |
|
97 |
|
98 |
http://www.tutorials.chymera.eu/blog/2014/05/18/mkstage4-stage4-tarballs-made-easy/ |
99 |
|
100 |
https://github.com/TheChymera/mkstage4/blob/master/README.md |
101 |
|
102 |
http://gentoo-en.vfose.ru/wiki/Custom_Stage4 |
103 |
|
104 |
http://gentoo-en.vfose.ru/wiki/Custom_Stage4#Installing_from_Stage4 |
105 |
|
106 |
|
107 |
Exercise some caution here. This is something that should be done and |
108 |
tested before you get in 'hot water'. Still, if you can duplicate what |
109 |
you have working (and test it) then you can experiment on the second |
110 |
indentical server, with out fear of corrupting the only one you have |
111 |
working. |
112 |
|
113 |
How you proceed is up to you. so be *careful*!!! |
114 |
|
115 |
> Considering how much time and effort it might take and that the update |
116 |
> problems aren´t going to go away, I have to wonder whether it´s better to |
117 |
> install Debian or Centos on another machine and to migrate the services. |
118 |
> Doing so would allow to make some improvements and to consolidate several |
119 |
> physical machines into one. |
120 |
|
121 |
Either way, you should back up your data /etc/ /var/lib/portage/world |
122 |
and any other info files you have or have modified, regardless of which |
123 |
OS you end up running on. Think about all the mods and installs and |
124 |
critical software you have customized on the system (iptables?). |
125 |
Back all of that up too. |
126 |
|
127 |
> |
128 |
> Either way, it sucks. |
129 |
|
130 |
System admin requires routine attention to systems, including backups |
131 |
and a total failure plan for critical systems, files, configs and other |
132 |
valuable information. Being in the fox-hole taking on water and low on |
133 |
ideas, hopefully will motivate you to have a more robust plan next time |
134 |
around. |
135 |
|
136 |
|
137 |
Good luck, |
138 |
hth, |
139 |
James |