| 1 |
On Saturday 02 December 2006 19:22, Richard Fish wrote: |
| 2 |
> On 12/2/06, Helmut Jarausch <jarausch@××××××××××××××××.de> wrote: |
| 3 |
> > The next step which I'm afraid of is upgrading |
| 4 |
> > to glibc-2.5 |
| 5 |
> > |
| 6 |
> > Having destroyed (the system) of my machine some years |
| 7 |
> > ago by upgrading glibc (on Suse), I know that this |
| 8 |
> > is not a trivial step. |
| 9 |
> |
| 10 |
> Actually the glibc-2.4 to 2.5 upgrade is pretty trivial, *if* you |
| 11 |
> already have nptl/nptlonly USE flags set. If you are using a i386 |
| 12 |
> CHOST (vs i686 or x86_64), then you end up having to change CHOST |
| 13 |
> before you can upgrade since glibc-2.5 is nptlonly, and that is not |
| 14 |
> trivial unfortunately. See the current thread on this list. |
| 15 |
> |
| 16 |
> > So, the question: |
| 17 |
> > |
| 18 |
> > Is there a general source of information about |
| 19 |
> > warnings, actions to be taking, etc to be followed |
| 20 |
> > when upgrading certains critical packages. |
| 21 |
> |
| 22 |
> Generally speaking, if you set in make.conf: |
| 23 |
> |
| 24 |
> PORTAGE_ELOG_CLASSES="warn error log" |
| 25 |
> PORTAGE_ELOG_SYSTEM="save" |
| 26 |
> |
| 27 |
> then any ebuilds that want to warn you or give you actions to take |
| 28 |
> will create files in /var/log/portage/elog/ for you to read. You can |
| 29 |
> just delete these once you've taken whatever action is required. |
| 30 |
> |
| 31 |
> More complicated upgrades (like the switch to modular-X, or gcc |
| 32 |
> upgrades) usually have some kind of guide created before they reach |
| 33 |
> stable. But at this point, there isn't any single-page reference for |
| 34 |
> these guides...probably something we should have. |
| 35 |
|
| 36 |
Also, the GWN gives a heads up on substantial system component upgrades and |
| 37 |
links to upgrade guides, which is fine as long as you are not running ~ARCH |
| 38 |
and bleeding edge version packages. |
| 39 |
|
| 40 |
-- |
| 41 |
Regards, |
| 42 |
Mick |
Archives