On 15/05/2013, at 4:51 PM, Lorn Potter <lorn.pot...@jollamobile.com> wrote:
> > On 15/05/2013, at 4:29 PM, Marko Saukko <marko.sau...@gmail.com> > wrote: > >> On 05/15/2013 12:53 AM, Robin Burchell wrote: >>> Hi, >>> >>> Some recent changes have been made to sensorfw have been made, but there >>> are some problems -- one more serious than the other. I think we're >>> probably going to need another prerelease to fix issue #2 at least. >>> >>> 1) yaml and spec files are out of sync >> >> I think you looked the wrong files as I did sync them (or that was the >> intention at least ;)), but.. >> >> http://gitweb.merproject.org/gitweb?p=mer-core/sensorfw.git;a=commit;h=54b3668ba07d4ccaef6b3fd57af2ef841f82b0bd > > > I think this needs to be mapped to > https://github.com/lpotter/sensorfw > or that repo be pushed into nemo > > Having all these different methods/places for git/obs is really confusing. Hang on, this one: https://github.com/mer-packages/sensorfw > >> > >> >>> >>> it looks like the yaml and spec files have been hand-edited, the spec file >>> in the repository does not match the one in mer either, this has caused a >>> problem in mer that was probably not caught when developing locally (see 2) >>> >>> (this means that if someone doesn't check carefully and relies on the yaml >>> being up-to-date, they will be in for a very nasty surprise) >>> >>> 2) sensorfw-qt5-devel relies on qt5-devel, which does not exist >> >> .. I accidently added this qt5-devel dependency apparently. It was before >> qt-devel depedency which was also wrong. >> >> Regards, >> Marko >> >>> >>> qt5, unlike our qt4 packaging does not have a joint devel package -- you >>> need to pull in the explicit parts you need (NB: this is only broken in >>> mer, the spec file in the repository is ok -- although the yaml file is >>> broken) >>> >>> BR, >>> >>> Robin >>> >> > > > Lorn Potter Senior Software Engineer, QtSensors/QtSensorGestures
