On Mon, Nov 30, 2009 at 12:25:05PM +0100, Christian Rüb wrote:
> Hi,
> 
> I just set up a new environment and for my own package I am preparing ATM I 
> get gitr0 (it was gitr10 before) now.
> Is this related to this variable?
> How do I get AUTOREV working again?
> 
> from bb file:
> PV       = "0.0.1-gitr${AUTOREV}"
> 
> Thanks for helping me out here.
> 
> Cheers,
>  Christian

Hi,

find your key (somthing like url+recipe name) with

sqlite3 tmp/cache/om-gta02/bb_persist_data.sqlite3
select * from BB_URI_LOCALCOUNT where key LIKE '%your_recipe_name%_count';

update BB_URI_LOCALCOUNT set value=10 where key = 'your_key_count';

PS: never remove cache dir again..

Cheers
> 
> > If you have an SHR development environment installed, you will have
> > noticed the numerous git errors that plague each build (and most of the
> > time will abort the operation).
> > 
> > There is a solution to that, but of course there's also an disavantage.
> > The solution is to disable (or remove) BB_GIT_CLONE_FOR_SRCREV in your
> > local.conf. The SHR makefile will not set that variable on new setups
> > anymore now, but it will remain in existing installations.
> > 
> > Parsing will work much faster and it won't need to download all git
> > repositories of this world..., the downside is that you will have
> > different revision numbers (lower ones) than the buildhost, so you won't
> > be able to mix and match package upgrades  from your local build and the
> > buildhost.
> > 
> > spaetz
> > 
> > PS. JaMa has also written a lengthy mail to openembedded-devel a few
> > hours ago who want to learn about the specifics)
> > 
> > 
> _______________________________________________
> Shr-devel mailing list
> Shr-devel@lists.shr-project.org
> http://lists.shr-project.org/mailman/listinfo/shr-devel

-- 
uin:136542059                jid:martin.ja...@gmail.com
Jansa Martin                 sip:jama...@voip.wengo.fr 
JaMa                         
_______________________________________________
Shr-devel mailing list
Shr-devel@lists.shr-project.org
http://lists.shr-project.org/mailman/listinfo/shr-devel

Reply via email to