| 1 |
Thanks, yes I am aware of the caveats - but they dont really apply when |
| 2 |
rescuing something as severely broken as this system was - I upgraded 3 |
| 3 |
machines without a problem, and this one died on reboot - badly :( |
| 4 |
|
| 5 |
BillK |
| 6 |
|
| 7 |
|
| 8 |
On Thu, 2009-11-19 at 23:44 -0600, Dale wrote: |
| 9 |
> Bill Kenworthy wrote: |
| 10 |
> > Some time back I saw someone mention a way to get emerge to install an |
| 11 |
> > ebuild with a bad digest - man emerge shows nothing so can someone give |
| 12 |
> > me a hint. It was much easier than going down the ebuild path. |
| 13 |
> > |
| 14 |
> |
| 15 |
> I think it is --digest. I don't see it in the man page so you may have |
| 16 |
> to do that with the ebuild command and the manifest option. See man |
| 17 |
> page to make sure. |
| 18 |
> |
| 19 |
> I will also add, you should not do this unless it passed the first test |
| 20 |
> and you had to edit the file for some reason. It could be corrupt or |
| 21 |
> altered in some unknown way otherwise. |
| 22 |
> |
| 23 |
> > Also, I am in the process of rescuing a system from the |
| 24 |
> > e2fs/util-linux/device-mapper snafu and find that now I have it booted |
| 25 |
> > re-emerging util-linux wont overwrite the files I manually installed to |
| 26 |
> > replace the missing ones - necessitating manually rm'ing some 50 or so |
| 27 |
> > files - is there a way to force emerge to ignore file collisions and |
| 28 |
> > just overwrite them in this circumstance? |
| 29 |
> > |
| 30 |
> > BillK |
| 31 |
> > |
| 32 |
> > |
| 33 |
> |
| 34 |
> I think you are looking for this option with emerge: |
| 35 |
> |
| 36 |
> --noconfmem |
| 37 |
> Causes portage to disregard merge records indicating |
| 38 |
> that a config file inside of a CONFIG_PRO- |
| 39 |
> TECT directory has been merged already. Portage will |
| 40 |
> normally merge those files only once to |
| 41 |
> prevent the user from dealing with the same config |
| 42 |
> multiple times. This flag will cause the file |
| 43 |
> to always be merged. |
| 44 |
> |
| 45 |
> Keep in mind that it will replace whatever it emerges which may include |
| 46 |
> dependencies. I have never used that option before so be forewarned if |
| 47 |
> it does. |
| 48 |
> |
| 49 |
> Hope that helps. |
| 50 |
> |
| 51 |
> Dale |
| 52 |
> |
| 53 |
> :-) :-) |
| 54 |
> |
| 55 |
-- |
| 56 |
William Kenworthy <billk@×××××××××.au> |
| 57 |
Home in Perth! |
Archives