On 12/03/2012 01:12 PM, Gianluca Cecchi wrote:
Do i have to wait for  official packages for f18 or can I directly apply
patches ?

nightlies should have the patch afaiu.

My f18 sites no update and I installed two days ago...

Il giorno 03/dic/2012 11:59, "Eli Mesika" <emes...@redhat.com
<mailto:emes...@redhat.com>> ha scritto:



    ----- Original Message -----
     > From: "Gianluca Cecchi" <gianluca.cec...@gmail.com
    <mailto:gianluca.cec...@gmail.com>>
     > To: "Adrian Gibanel" <adrian.giba...@btactic.com
    <mailto:adrian.giba...@btactic.com>>
     > Cc: "users" <users@ovirt.org <mailto:users@ovirt.org>>
     > Sent: Monday, December 3, 2012 11:15:48 AM
     > Subject: Re: [Users] Testing ovirt all in one on F18 gives error
    on DB        creation
     >
     > On Sun, Dec 2, 2012 at 3:08 AM, Adrian Gibanel  wrote:
     > > Not sure if you can skip doing engine-cleanup as you ask.
     >
     > If engine-cleanup takes me to the starting point it is ok for me.
     > Or do I have to take any other manual step to clean up and start
     > again
     > after fixing the problem?
     >
     > I also found a post about problems with template0/template1 and this
     > change to avoid exensions totally...
     > but I don't know if it is applicable to my version
     > (ovirt-engine-setup-3.1.0-1.fc18.noarch as I wrote before):
     > http://gerrit.ovirt.org/#/c/8955/
     >
     > Hopefully this change is going to come to f18 too..?

    Hi
    This change was introduced especially for f18
    Patch was available from Nov 7 2012 and should resolve this problem.



     > _______________________________________________
     > Users mailing list
     > Users@ovirt.org <mailto:Users@ovirt.org>
     > http://lists.ovirt.org/mailman/listinfo/users
     >



_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users



_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to