Your commit broke the encoding of these documents: http://www.gentoo.org/cgi-bin/viewcvs.cgi/app-admin/skey/ChangeLog?r1=1.36&r2=1.37 http://www.gentoo.org/cgi-bin/viewcvs.cgi/sys-fs/cryptsetup/ChangeLog?r1=1.30&r2=1.31 http://www.gentoo.org/cgi-bin/viewcvs.cgi/sys-fs/e2fsprogs/ChangeLog?r1=1.79&r2=1.80 If you want i can fix it.
I've fixed it in the tree. If you need help with your system, someone to test,..., don't hesitate and ask. Thanks.
Again: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sci-geosciences/gpsd/ChangeLog?r1=1.14&r2=1.15
fixed changelog of sci-geosciences/gpsd
Tom, your commits are constantly breaking the encoding of the ChangeLog, if you need help to fix this problem please ask. I think it's unacceptable to deface other contributor's names.
No idea why is this still open.
(In reply to comment #5) > No idea why is this still open. It is not fixed: http://sources.gentoo.org/viewcvs.py/gentoo-x86/mail-client/mozilla-thunderbird/ChangeLog?r1=1.153&r2=1.154 http://sources.gentoo.org/viewcvs.py/gentoo-x86/x11-plugins/enigmail/ChangeLog?r1=1.42&r2=1.43 Tom, i know it only happens sometimes. Maybe it helps you to find the reason for it.
(In reply to comment #6) > It is not fixed: So make repoman detect those garbled logs?
A new one: http://sources.gentoo.org/viewcvs.py/gentoo-x86/www-client/mozilla-firefox/ChangeLog?r1=1.232&r2=1.233 Tom Gall, you don't care, do you? (In reply to comment #7) > So make repoman detect those garbled logs? Have an idea how to do it?
http://sources.gentoo.org/viewcvs.py/gentoo-x86/www-client/mozilla-firefox/ChangeLog?r1=1.237&r2=1.238 http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-portage/ufed/ChangeLog?r1=1.54&r2=1.55
CCing portage folks, repoman really should check for this... @tgall - could you damn post some response on this bug finally?
(In reply to comment #10) > CCing portage folks, repoman really should check for this... Sure, let us know how.
tgall - are you breaking this on purpose or WTH? Could you kindly respond here finally?! This is getting absurd... <snip> 21:29:28 <+CIA-1> tgall * gentoo-x86/dev-ruby/fusefs/ (ChangeLog fusefs-0.6.0.ebuild): 21:29:28 <+CIA-1> added ~ppc64 21:29:28 <+CIA-1> (Portage version: 2.1.2-r9) 21:35:10 <+CIA-1> tove * gentoo-x86/dev-ruby/fusefs/ChangeLog: 21:35:10 <+CIA-1> fixed broken encoding in ChangeLog </snip>
http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/facets/ChangeLog?r1=1.12&r2=1.13 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/facets/ChangeLog?r1=1.12&r2=1.13 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/dpklib/ChangeLog?r1=1.5&r2=1.6 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/devel-logger/ChangeLog?r1=1.10&r2=1.11 etc. etc. etc.
http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/sqlite-ruby/ChangeLog?r1=1.29&r2=1.30 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/misen/ChangeLog?r1=1.4&r2=1.5 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/ncurses-ruby/ChangeLog?r1=1.21&r2=1.22 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/nora/ChangeLog?r1=1.8&r2=1.9 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/ruby-fcgi/ChangeLog?r1=1.18&r2=1.19 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/ruby-xslt/ChangeLog?r1=1.7&r2=1.8 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/narray/ChangeLog?r1=1.27&r2=1.28 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/needle/ChangeLog?r1=1.14&r2=1.15 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/mysql-ruby/ChangeLog?r1=1.32&r2=1.33 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/nano-methods/ChangeLog?r1=1.3&r2=1.4 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/og/ChangeLog?r1=1.10&r2=1.11 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/libxml/ChangeLog?r1=1.10&r2=1.11 http://sources.gentoo.org/viewcvs.py/gentoo-x86/dev-ruby/nimage/ChangeLog?r1=1.2&r2=1.3
then as now, the system I'm using is a ppc64 box, vim 7.0.174. There's really nothing magical about the system at all. I'm not breaking anything on purpose. > vim foo-whatever.ebuild usual vim commands here ending with :w, :x > repoman scan > repoman commit Has anything thought about putting together a test data file with DB data in it and testing it with vim on ppc64? pop into #gentoo-ppc64 if you'd like to check out that route. adding ppc64@gentoo.org on the CC as should be the case for all ppc64 related bugs.
Are you using "echangelog" for your ChangeLog entries? If not, why not? That might solve the issue for you, as echangelog is UTF8-aware.
No never have. Shouldn't matter. vim *SHOULD* be utf-8 aware. Did a UTF8 bug get missed in vim?
Vim is only utf-8 aware if you tell it to be. Vim's documentation goes into this in great depth.
given that bit of info, shouldn't http://devmanual.gentoo.org/appendices/editor-configuration/vim/index.html be updated to include the gory details like has been done for emacs at : http://devmanual.gentoo.org/appendices/editor-configuration/emacs/index.html ? Have a deeper link into the vim documentation Ciaran? Thanks
Probably, if anyone's maintaining the devmanual these days. Having said that, you're supposed to use echangelog, not vim.
Tom, good point here to use echangelog. echangelog seems to use nano but for what it is worth, if the variable EDITOR is set to /usr/bin/vim then echangelog will invoke vim. And we're back to Tom's problem. Tom do you know what to fix now?
I was thinking more like: echangelog "This is my ChangeLog message. There are many like it, but this one is mine." ;]
I just hit this myself. When editing a Changelog, vim shows: fileencoding=utf-8 Any changes I make will cause the UTF-8 encoding to be broken. However, if I manually set "fileencoding=latin1" then it doesn't break. This doesn't seem to be inline with vim's documentation and I find it to be confusing.
fileencoding in vim contains what the file is *now*, not what it was when it was opened. If vim can't figure out the file encoding on its own, you need to open a file using the ++enc option.
Getting back to the original bug (as I'm back from a business trip and plenty of real life crap) so are you saying Ciaran that perhaps vim's ability to detect the encoding of the file might be buggy or the files are mislabeled? Guess I'd like to understand a bit more how vim does this encoding detection magic.
Vim's detection isn't buggy. It's just that it's impossible to determine encoding automatically in many situations because most documents are valid in most encodings. Like I said, Vim's documentation explains all.
adding the vim team onto the cc. The little bit about GLEP31 and gentoo-syntax changes to utf-8 being the default seems to be the interesting bit of trivia. In review: 1) vim and ppc64 and amd64 seems to have issues when the ebuild/changelog have utf8 data in them. 2) Comment 23 from Paul seems to suggest that fileencoding=latin1 avoid the problem. (And I've confirmed on ppc64) I'm going to rebuild vim on my box with the ignore-glep31 USE flag and see if that has any effect. Given that this is affecting two gentoo architectures, seems like the ownership of this bug probably need to fall into the hands of those that implemented glep31 or the vim team.
rebuilding gentoo-synxtax with ignore-glep31 fixes this bug.
This has nothing to do with architecture, and using latin1 will lead to broken display and broken files. This is user error and nothing more.
How do we get this fixed? In order for me to not break the ChangeLog, I have to do a set fileencoding=latin1. I have read through the documentation and I can not find how I have vim misconfigured that doing the above causes it to work correctly.
You need to make sure that fileencoding is set to utf-8 *before* you open up the ChangeLog file. The easiest way to do this is using one of the ++enc options, which are described at length in the documentation.
Uh. Seriously, a developer unable to set up $EDITOR properly is not a bug; closing this, as in "read the fine manual". :P
Ignore me...
Nothing to see here...just fixing the resolution (if invalid could be called a fix...its definitely not a "remind" though :) )
