| 1 |
Neil Bothwick wrote: |
| 2 |
> On Thu, 22 Oct 2015 09:53:57 +0000, Alan Mackenzie wrote: |
| 3 |
> |
| 4 |
>>> 1445464761: >>> unmerge success: sys-libs/glibc-2.20-r2 |
| 5 |
>>> 1445464768: === (1 of 13) Post-Build Cleaning |
| 6 |
>>> (sys-libs/glibc-2.21-r1::/var/cache/portage/tree/sys-libs/glibc/glibc-2.21-r1.ebuild) |
| 7 |
>>> 1445464768: ::: completed emerge (1 of 13) sys-libs/glibc-2.21-r1 |
| 8 |
>>> to / |
| 9 |
>> This is nothing to do with your problem, but it might be useful |
| 10 |
>> nonetheless. |
| 11 |
>> |
| 12 |
>> I finally got fed up with these "seconds since the epoch" time stamps a |
| 13 |
>> couple of days ago, and wrote a little filter to turn them into readable |
| 14 |
>> time stamps. Probably there is software around already which does this, |
| 15 |
>> but the effort to write the script was less than that to search for the |
| 16 |
>> existing software. |
| 17 |
> Either genlop or qlop (from portage-utils) will do this and much more. |
| 18 |
> You probably already have at least one of them installed. |
| 19 |
> |
| 20 |
> |
| 21 |
|
| 22 |
|
| 23 |
It can be done with the date command if you only need one done. Thing |
| 24 |
is, I already knew when this was done so the time stamps didn't matter |
| 25 |
to me. I went to the bottom of the file, the last emerges I did, then |
| 26 |
looked at the update section of the log. I didn't need timestamps to |
| 27 |
know where it was or anything. Go to bottom, scroll up a bit and look |
| 28 |
for the world update part. |
| 29 |
|
| 30 |
Of course, there is better ways of finding this info but I never can |
| 31 |
remember the command and it takes me a bit to figure out what options do |
| 32 |
what so I finally said "screw it" and work without it unless I just must |
| 33 |
have it. If I only need one, I use the date command. It works. ;-) |
| 34 |
|
| 35 |
I'm getting to old for this stuff. :/ |
| 36 |
|
| 37 |
Dale |
| 38 |
|
| 39 |
:-) :-) |
Archives