| 1 |
On Wednesday, July 22, 2015 02:30:18 PM Dale wrote: |
| 2 |
> Neil Bothwick wrote: |
| 3 |
> > On Wed, 22 Jul 2015 12:56:41 -0500, Dale wrote: |
| 4 |
> >> So, after fighting to get it to build, they remove it and it wants to go |
| 5 |
> >> back to the old version I had that worked. ROFLMBO |
| 6 |
> > |
| 7 |
> > And today's lesson is: If an ebuild fails, re-sync and try again (or |
| 8 |
> > search Bugzilla which may well tell you to re-sync and try again). |
| 9 |
> |
| 10 |
> Well, I'm pretty sure I had re-synced at least a couple times. I |
| 11 |
> usually update about twice a week. I posted about this problem on the |
| 12 |
> 16th and had been seeing it for at least a few days before that. It |
| 13 |
> doesn't seem that a re-sync would really have solved the problem. This |
| 14 |
> is my sync history: |
| 15 |
> |
| 16 |
> Sat Jul 11 12:45:14 2015 >>> gentoo |
| 17 |
> Sun Jul 12 18:27:27 2015 >>> gentoo |
| 18 |
> Mon Jul 13 19:30:28 2015 >>> gentoo |
| 19 |
> Sun Jul 19 20:29:01 2015 >>> gentoo |
| 20 |
> Wed Jul 22 12:43:43 2015 >>> gentoo |
| 21 |
> |
| 22 |
> Since I synced three days in a row, I suspect the problem started on the |
| 23 |
> 11th. I posted a thread on the 16th here. Before I posted about it, I |
| 24 |
> had already re-synced a couple times. It was the removal of the old and |
| 25 |
> broken ebuilds that fixed it but there was a decent lag before it was |
| 26 |
> done. Well over a week it seems. |
| 27 |
> |
| 28 |
> While it is possible to sync and catch the tree at a bad time, this |
| 29 |
> doesn't seem to be the case here. It seems there was just a lag between |
| 30 |
> some updates and removals of broken ebuilds. |
| 31 |
> |
| 32 |
> Dale |
| 33 |
> |
| 34 |
> :-) :-) |
| 35 |
|
| 36 |
In this case, it was "resolved" on the 20th. (That's when I synched). |
| 37 |
|
| 38 |
-- |
| 39 |
Joost |
Archives