i edited the new vim-core ebuild that uses the new eclass so it merges faster no need to compile vim when this doesnt even install that also im attaching an updated eclass file the comment at the top i think should be left so those that update it know the version format for the pre's of vim
Created attachment 5264 [details] vim-core-6.1-r3.ebuild updated vim-core ebuild
Created attachment 5265 [details] vim.eclass updated vim.eclass
committed the vim-core ebuild...
instead of making new bug... just so you know Ryan vim and vim-core are at patch level 213 and gvim is at 263 perhaps should unmask vim and vim-core's patch level? also vim patch level is now up to 6.1.288
This being the only seemingly relevant bug I could find for ViM, I'll post my error here. I'm trying to update my server (after exhaustively updating several test machines on my LAN, testing all packages, etc.) and ViM is being a stickler. My distfiles directory is exported via NFS to my LAN from this server. The vim files are in the distfiles directory, and those very files were used to install the latest available version on all workstations. This worked flawlessly. However, on the server I get the following upon emerge'ing vim-core; >>> Unpacking vim-6.1.tar.bz2 bzip2: (stdin) is not a bzip2 file. tar: Child returned status 2 tar: Error exit delayed from previous errors /usr/sbin/ebuild.sh: /var/tmp/portage/vim-core-6.1-r4/work/vim-4.2-speed_t.patch: No such file or directory !!! ERROR: app-editors/vim-core-6.1-r4 failed. !!! Function src_unpack, Line -5247, Exitcode 1 !!! (no error message) I've tried rm'ing and re-downloading the file, both with and without proxy to no effect. I've tried masking vim-6.1-r19, which resulted in using the -r15 ebuild - same problem. (I'm not sure how to handle masking of vim-core, or if it would have any effect)
stewart: what does emerge info state?
should be resolved in the newer ebuilds. make sure to rsync.
Created attachment 8014 [details] Output of `emerge info` Attached is the output of `emerge info`, follows is my attempt to update ViM after rsync'ing; zeus:~ # emerge vim -u Calculating dependencies ...done! >>> emerge (1 of 2) app-editors/vim-core-6.1-r4 to / >>> md5 ;-) vim-6.1.tar.bz2 >>> md5 ;-) vimpatch-1-300.tar.bz2 >>> Unpacking source... >>> Unpacking vim-6.1.tar.bz2 bzip2: (stdin) is not a bzip2 file. tar: Child returned status 2 tar: Error exit delayed from previous errors /usr/sbin/ebuild.sh: /var/tmp/portage/vim-core-6.1-r4/work/vim-4.2-speed_t.patch: No such file or directory
Quick follow-up; I've manually untarred both vim-6.1.tar.bz2 vimpatch-1-300.tar.bz2 on Zeus as both a regular user and root, without fail. I have updated Portage to the latest revision (of which I was only one behind), and re-sync'ed the entire /usr/portage tree (after removing it and rsync'ing anew) with the same results. tar and bzip2 are both at the latest revision available.
