On Sat, Feb 11, 2012 at 10:25 PM, Carsten Munk <[email protected]>wrote:
> > I've sent review 314 for python for re-review by the testing system. > ok, if you are comfortable with the state of mini, i'll proceed with python2.7 but, WARNING: the mini spec file had 2 (nonstandard?, not in my current nemo n900 rpmrc) macros (not in fedora, either): py_ver py_libdir i fixed py_ver -> python_version. mini only 'worked' in meego/mer previously because py2.6 was unversioned, so the empty macro was ok (i guess). moving ahead, py is versioned. i didn't touch py_libdir. i think it is still broken? maybe it should be _python_path, but i should stop guessing about mini... > > > > > 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. > ok. my patch set 4 for py2.7 was incorrect (i think it is basically the same as patchset 3, which i know is broken), i broke my local git repo, & don't know how to fix - only how to break it more. to avoid confusion, i was hoping you could mark that changeid (Change I984779d5) as abandoned (i assume i cannot do that). then i can build a new local git repo from my local cobs repo (already done) & push a clean py2.7, with a new changeid, to gerrit. then, maybe py2.7 will succeed. i just didn't want to push this to gerrit without the obsolete changeid disappearing first - but i would like to do this in a couple of days before i'm offline for a couple of weeks. thanks > BR > Carsten Munk > > >
