W: python-naming-policy-not-applied /usr/lib/python2.6/site-packages/xcbgen/__init__.pyo W: files-duplicate /usr/lib/python2.6/site-packages/xcbgen/state.pyo /usr/lib/python2.6/site-packages/xcbgen/state.pyc W: files-duplicate /usr/lib/python2.6/site-packages/xcbgen/expr.pyc /usr/lib/python2.6/site-packages/xcbgen/expr.pyo W: files-duplicate /usr/lib/python2.6/site-packages/xcbgen/matcher.pyc /usr/lib/python2.6/site-packages/xcbgen/matcher.pyo W: files-duplicate /usr/lib/python2.6/site-packages/xcbgen/__init__.pyo /usr/lib/python2.6/site-packages/xcbgen/__init__.pyc W: files-duplicate /usr/lib/python2.6/site-packages/xcbgen/error.pyc /usr/lib/python2.6/site-packages/xcbgen/error.pyo files-duplicate /usr/lib/python2.6/site-packages/xcbgen/xtypes.pyo /usr/lib/python2.6/site-packages/xcbgen/xtypes.pyc
On Thu, Jun 17, 2010 at 06:31:58 -0700, bugzilla-daemon@freedesktop.org wrote: > W: python-naming-policy-not-applied > /usr/lib/python2.6/site-packages/xcbgen/__init__.pyo > sounds like a packaging issue to me. also looks like an empty bug, what is the actual problem?
(In reply to comment #1) > On Thu, Jun 17, 2010 at 06:31:58 -0700, bugzilla-daemon@freedesktop.org wrote: > > > W: python-naming-policy-not-applied > > /usr/lib/python2.6/site-packages/xcbgen/__init__.pyo Oh sorry. I forgot to add: This package doesn't respect the naming policy for python packages. Its name should match the regular expression ^python(-|$). > > > sounds like a packaging issue to me. also looks like an empty bug, what > is the actual problem? RPMLINT detected that e.g. state.pyo and state.pyc are the "same" file. So it wants that one of them links to the other ... You can see the complete build process for protos here (please search for: "cd xcbproto"): https://build.opensuse.org/package/live_build_log?arch=i586&package=xorg-x11-proto-devel&project=home%3Ajobermayr&repository=openSUSE_Factory
This is an opensuse problem, not ours.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.