| 1 |
[NOTE: I did this a bit awkwardly by posting this message on the user |
| 2 |
list first. Probably it should be here] |
| 3 |
|
| 4 |
[aside: It may be of note that this `emerge world' comes after about |
| 5 |
2-3 mnths of neglect] |
| 6 |
|
| 7 |
I've hit something during an emege world while emerging emacs-vcs, |
| 8 |
that looks a lot like bug #299667: |
| 9 |
|
| 10 |
http://bugs.gentoo.org/show_bug.cgi?id=299667 |
| 11 |
|
| 12 |
I found the bug by googling the last bits from the build.log |
| 13 |
`bzr.eclass: can't update from |
| 14 |
bzr://bzr.savannah.gnu.org/emacs/trunk/' |
| 15 |
|
| 16 |
But the bug is reported fixed. This was sometime like Jan 2010. |
| 17 |
|
| 18 |
Reading the story of the bug I see its been due to renaming of stuff |
| 19 |
upstream. |
| 20 |
|
| 21 |
And a thead in emacs.devel list is cited: |
| 22 |
|
| 23 |
<http://thread.gmane.org/gmane.emacs.devel/119347/focus=119402> |
| 24 |
|
| 25 |
Again its quite old now so I wonder if there has been a recurrence of |
| 26 |
changes upstream or something else? |
| 27 |
|
| 28 |
Before posting a bug, I thought I'd ask here and see if it really is a |
| 29 |
bug or if others recently emerging emacs-vcs have had no trouble |
Archives