python2.7 upgrade may be proceding ok except for an rpmlint-mini build failure.
is this _core_ pkg totally undocumented? the url in the spec file just points to rpmlint; i don't understand what 'mini' implies. i guess i could manually (and repeatedly) hack the magical file: Source100: rpmlint-deps.txt to _add_ missing (but not _remove_ obsoleted?) python2.7 dependencies that are complained about during rpmlint-mini package build, until the build succeeds. this must surely be non-backward compatible w/ current py2.6. rpmlint-deps.txt currently has 226 module names (.pyo or .so), one per line, not in alphabetical order... but i can't imagine that is the actual procedure to update this package... it certainly does not seem to be as simple as, e.g., find /usr/lib/python2.7 -name '*.so' find /usr/lib/python2.7 -name '*.pyo' the rpmlint-mini changelog shows there might be some useful info: * Sat Jan 09 2010 Anas Nashif <[email protected]> - 1.1 - Fixed python dependencies i'm assuming i cannot diff / look at that change from the current mer rpmlint-mini.git (initial import dated 2011-10-04)? likewise, on crumbling(!) build.pub.meego.com obs i cannot find any remaining project / pkg that might contain the meego era rpmlint-mini on which i could do an osc diff, etc.? let me know if some / all of this info should just be placed in a generic rpmlint-mini bug for archival / placeholder purposes prior to the hacking in support of py2.7. thanks for any info
