First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 190621
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: GNU Emacs Team <emacs@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Graham Murray <gmurray@webwayone.co.uk>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 190621 depends on: Show dependency tree
Bug 190621 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2007-08-29 10:04 0000 
There seems to be a mismatch between the version in the ebuild and that in the
cvs HEAD

* Copying emacs from /usr/portage/distfiles/cvs-src ...
 * CVS module emacs is now in
/var/tmp/portage/app-editors/emacs-cvs-23.0.51-r1/work


 * Emacs CVS branch: HEAD
 * Emacs version number: 23.0.50
 * 
 * ERROR: app-editors/emacs-cvs-23.0.51-r1 failed.
 * Call stack:
 *   ebuild.sh, line 1654:   Called dyn_unpack
 *   ebuild.sh, line 768:   Called qa_call 'src_unpack'
 *   ebuild.sh, line 44:   Called src_unpack
 *   emacs-cvs-23.0.51-r1.ebuild, line 76:   Called die
 * 
 * Upstream version number changed to 23.0.50

------- Comment #1 From Ulrich Müller 2007-08-29 12:39:13 0000 ------- 
Yes, upstream has merged the multi-tty branch to the CVS trunk today and played
some games with the version number in the CVS trunk.

From CVS log of lisp/version.el:
   revision 2.55, 2007-07-26 05:26:37 +0000: version 22.1.50
   revision 2.56, 2007-08-29 05:28:02 +0000: version 23.0.51 (multi-tty merge)
   revision 2.57, 2007-08-29 08:07:06 +0000: version 22.1.50
   revision 2.58, 2007-08-29 08:14:32 +0000: version 23.0.50

I had already fixed it in our CVS three minutes before your bug report. ;-)
Please re-sync and try again.
First Last Prev Next    No search results available      Search page      Enter new bug