Adam Spiers
2014-04-29 18:26:45 UTC
Hi all,
I'm working on updating rubygem-vagrant, and I'm getting some spurious
warnings from rpmlint when building on 12.3:
[ 23s] rubygem-vagrant-doc.x86_64: W: wrong-file-end-of-line-encoding /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Environment/default_private_key_path-i.ri
[ 23s] rubygem-vagrant-doc.x86_64: W: wrong-file-end-of-line-encoding /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Errors/VagrantError/extra_data-i.ri
[ 23s] rubygem-vagrant-doc.x86_64: W: wrong-file-end-of-line-encoding /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/UI/Interface/opts-i.ri
[ 23s] rubygem-vagrant-doc.x86_64: W: wrong-file-end-of-line-encoding /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Environment/home_path-i.ri
[ 23s] This file has wrong end-of-line encoding, usually caused by creation or
[ 23s] modification on a non-Unix system. It could prevent it from being displayed
[ 23s] correctly in some circumstances.
[snipped]
[ 23s] rubygem-vagrant-doc.x86_64: W: unexpanded-macro /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Util/Downloader/download%21-i.ri %21
[ 23s] rubygem-vagrant-doc.x86_64: W: unexpanded-macro /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Registry/has_key%3f-i.ri %3f
[ 23s] This package contains a file whose path contains something that looks like an
[ 23s] unexpanded macro; this is often the sign of a misspelling. Please check your
[ 23s] specfile.
[ 23s]
[ 23s] 4 packages and 0 specfiles checked; 0 errors, 78 warnings.
I eventually tracked them down to a bug in rpmlint 1.4 (which got
propagated to rpmlint-mini) which was fixed before rpmlint 1.5:
http://sourceforge.net/p/rpmlint/code/ci/7ebdb2a
This explains why the warnings don't appear when building on 13.1
(which has rpmlint 1.5). I thought I had seen these explained
somewhere else before; maybe it was:
https://bugzilla.redhat.com/show_bug.cgi?id=850786
but unfortunately I get an error when I visit the upstream ticket:
http://rpmlint.zarb.org/cgi-bin/trac.cgi/ticket/569
Anyway, I couldn't find any openSUSE-related references to the issue,
so I thought it was worth posting about it here for reference, in case
other people google the issue in the future (unlikely since 12.3 is
old now, but you never know ...)
Would it be worth updating rpmlint on 12.3 to address these?
I'm working on updating rubygem-vagrant, and I'm getting some spurious
warnings from rpmlint when building on 12.3:
[ 23s] rubygem-vagrant-doc.x86_64: W: wrong-file-end-of-line-encoding /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Environment/default_private_key_path-i.ri
[ 23s] rubygem-vagrant-doc.x86_64: W: wrong-file-end-of-line-encoding /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Errors/VagrantError/extra_data-i.ri
[ 23s] rubygem-vagrant-doc.x86_64: W: wrong-file-end-of-line-encoding /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/UI/Interface/opts-i.ri
[ 23s] rubygem-vagrant-doc.x86_64: W: wrong-file-end-of-line-encoding /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Environment/home_path-i.ri
[ 23s] This file has wrong end-of-line encoding, usually caused by creation or
[ 23s] modification on a non-Unix system. It could prevent it from being displayed
[ 23s] correctly in some circumstances.
[snipped]
[ 23s] rubygem-vagrant-doc.x86_64: W: unexpanded-macro /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Util/Downloader/download%21-i.ri %21
[ 23s] rubygem-vagrant-doc.x86_64: W: unexpanded-macro /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Registry/has_key%3f-i.ri %3f
[ 23s] This package contains a file whose path contains something that looks like an
[ 23s] unexpanded macro; this is often the sign of a misspelling. Please check your
[ 23s] specfile.
[ 23s]
[ 23s] 4 packages and 0 specfiles checked; 0 errors, 78 warnings.
I eventually tracked them down to a bug in rpmlint 1.4 (which got
propagated to rpmlint-mini) which was fixed before rpmlint 1.5:
http://sourceforge.net/p/rpmlint/code/ci/7ebdb2a
This explains why the warnings don't appear when building on 13.1
(which has rpmlint 1.5). I thought I had seen these explained
somewhere else before; maybe it was:
https://bugzilla.redhat.com/show_bug.cgi?id=850786
but unfortunately I get an error when I visit the upstream ticket:
http://rpmlint.zarb.org/cgi-bin/trac.cgi/ticket/569
Anyway, I couldn't find any openSUSE-related references to the issue,
so I thought it was worth posting about it here for reference, in case
other people google the issue in the future (unlikely since 12.3 is
old now, but you never know ...)
Would it be worth updating rpmlint on 12.3 to address these?