| 1 |
james schrieb: |
| 2 |
> On 08/12/2016 07:26 AM, hw wrote: |
| 3 |
>> Michael Orlitzky schrieb: |
| 4 |
>>> On 08/10/2016 06:54 AM, hw wrote: |
| 5 |
>>>> |
| 6 |
>>>> Hi, |
| 7 |
>>>> |
| 8 |
>>>> I´m trying to upgrade portage because I´m getting a message that it |
| 9 |
>>>> needs to be able to work with EAPI 6 packages and can only do EAPI 5. |
| 10 |
>>>> |
| 11 |
>>>> I´m running into merge conflicts when trying to update portage, and |
| 12 |
>>>> apparently one of the packages (dev-python/cryptography) I could try |
| 13 |
>>>> to update first to be able to update portage requires a version of |
| 14 |
>>>> portage that can handle EAPI 6 packages. |
| 15 |
>>>> |
| 16 |
>>> |
| 17 |
>>> Try the other suggestions first -- but as a last resort -- you can |
| 18 |
>>> always grab a new stage3 that should contain an updated version of |
| 19 |
>>> portage and simply overwrite the portage files on your machine. A |
| 20 |
>>> quickpkg from another Gentoo machine (or the liveCD?) would also work. |
| 21 |
>>> |
| 22 |
>>> |
| 23 |
>> |
| 24 |
>> I´m trying to update a production server here. If I overwrite the whole |
| 25 |
>> system, who knows what might break. I can take it down for a few |
| 26 |
>> hours in the evening unless I want to work over night, which is not |
| 27 |
>> really an option. |
| 28 |
>> |
| 29 |
>> There must be a way to update a Gentoo installation without breaking it. |
| 30 |
>> As wonderful as it otherwise is, updating Gentoo is always a nightmare |
| 31 |
>> which |
| 32 |
>> makes me very seriously consider not to use it anymore. Updating needs to |
| 33 |
>> be easy and flawless and not something you always run into weird issues |
| 34 |
>> with. |
| 35 |
> |
| 36 |
> When I run gentoo as a critical server, I always have a second, redundant system pretty much identical, on stanby. I upgrade the stanby first and run it a few days, then the production system. It makes reliability extraordinarily high. But, the again, I do a version of the |
| 37 |
> same thing with all critical systems, or I do not work on them. |
| 38 |
|
| 39 |
This isn´t really an option because the problem is with the updating |
| 40 |
itself, not with something not working after the update has been |
| 41 |
performed. |
| 42 |
|
| 43 |
> Granted, |
| 44 |
> as successful consultant, I have that luxury. |
| 45 |
|
| 46 |
It´s time consuming ... |
| 47 |
|
| 48 |
>> Did they recently make a new liveDVD? |
| 49 |
> |
| 50 |
> A few months ago. |
| 51 |
> |
| 52 |
> https://wiki.gentoo.org/wiki/Project:RelEng/LiveDVD/20160514 |
| 53 |
|
| 54 |
Cool, the old one was really getting old. |
| 55 |
|
| 56 |
|
| 57 |
> Perhaps a better solution is to make a stage-4, of your current gentoo |
| 58 |
> (production) system, verify that the stage-4 works by using it to install a similar system, test and deploy. And then hack or fix the production system, during the daytime, at your leisure? |
| 59 |
> |
| 60 |
> Stage-4 gentoo systems have been around a long time. Documentation varies and most have their own 'home spun' approach to stage-4 replicant systems, backups etc etc. |
| 61 |
|
| 62 |
It might be a way to try and see if upgrading from older states step by |
| 63 |
step until the installation is current would work. But how do I do that? |
| 64 |
|
| 65 |
Considering how much time and effort it might take and that the update |
| 66 |
problems aren´t going to go away, I have to wonder whether it´s better to |
| 67 |
install Debian or Centos on another machine and to migrate the services. |
| 68 |
Doing so would allow to make some improvements and to consolidate several |
| 69 |
physical machines into one. |
| 70 |
|
| 71 |
Either way, it sucks. |
Archives