11. feb. 2012 21.30 skrev letters.random13 <[email protected]>: > so, now that i think i've found where rpmlint-mini upstream pkg is from > (should come from) > (https://build.opensuse.org/package/files?package=rpmlint-mini&project=devel%3AopenSUSE%3AFactory%3Arpmlint) > > it seems they try to track rpmlint versions, which meego and thus mer > haven't been doing. > i'm pretty sure rpmlint-mini was broken for mer builds (on obs at least) > before i hacked it [MER#169]. i probably made it worse (but unfortunately, > that didn't show up in cobs builds). Yes, we had to wait for some OBS integration of the new cross compilation method - I haven't seen any breakage to rpmlint-mini in my builds.
> the opensuse mini changelog says it was fixed to support python2.7 at about > the same time of: > update to desktop-file-utils 0.17 > which is the current version of that file in mer (mini-1.1 apparently (spec > file), but hard to tell exactly) (mini-1.3 now has 0.19 at suse). something > else must be wrong on the mer side. > > it seems there is an rpmlint-tests pkg (possibly it is only for obs) at > https://build.opensuse.org/package/show?package=rpmlint-tests&project=openSUSE%3AFactory > that could eliminate problems with lint & lint-mini hacking like i did. > it has License: SUSE-Public-Domain I think you're actually on the right path, it's just that our testing system failed last time python was evaluated. So, rpmlint-mini is actually a method to embed some tools into /opt/testing , like python, rpmlint, desktop-file-utils, so we don't need to directly follow opensuse's. I've sent review 314 for python for re-review by the testing system. > > sorry for the endless dilution of mer progress that this is causing. Hey, don't worry about it - I'm just glad someone wants to dive into the nasty stuff other people never dares to touch :) I'm happy you're doing it. Since we have continuous integration, we're not getting held back due to this. BR Carsten Munk
