| 1 |
On 02/04/2018 12:21:13 AM, Bill Kenworthy wrote: |
| 2 |
> On 04/02/18 01:34, Helmut Jarausch wrote: |
| 3 |
> > On 02/03/2018 04:11:33 PM, Marc Joliet wrote: |
| 4 |
> >> Am Samstag, 3. Februar 2018, 10:50:53 CET schrieb Helmut Jarausch: |
| 5 |
> >> > On 02/03/2018 06:54:06 AM, Dale wrote: |
| 6 |
> >> > > While on this topic, I have a question about glibc. I have it |
| 7 |
> set in |
| 8 |
> >> > > make.conf to save the binary packages. Generally I use it |
| 9 |
> when I |
| 10 |
> >> need |
| 11 |
> >> > > to go back shortly after a upgrade, usually Firefox or |
| 12 |
> something. |
| 13 |
> >> > > However, this package is different since going back a version |
| 14 |
> isn't a |
| 15 |
> >> > > good idea. My question tho, what if one does go back a |
| 16 |
> version using |
| 17 |
> >> > > those saved binary packages? Has anyone ever did it and it |
| 18 |
> work or |
| 19 |
> >> > > did |
| 20 |
> |
| 21 |
> 1. do another backup |
| 22 |
> 2. take your last good binary package and unpack it in the root |
| 23 |
> directory - it is an "image" of that package as it sits in the file |
| 24 |
> system. |
| 25 |
> 3. rebuild that version of glibc by overiding emerge - comment out |
| 26 |
> "die |
| 27 |
> "aborting to save your system" in |
| 28 |
> /usr/portage/eclass/toolchain-glibc.eclass |
| 29 |
> |
| 30 |
> I have done this a couple of times with gcc (when manual deletes have |
| 31 |
> gone rogue) but it should work with glibc as you have not recompiled |
| 32 |
> any |
| 33 |
> new packages. |
| 34 |
> |
| 35 |
|
| 36 |
Many thanks Bil, |
| 37 |
Helmut |
Archives