Re: Toaster Interface

"Reyna, David" <[email protected]>
Newsgroups org.yoctoproject.lists.toaster
Message-ID <[email protected]>
Hi Pavan,

1) Did you clone Toaster from “master”, or a different clone tag?
2) I just cloned from “master”, and I see a trace error “django.core.management.base.CommandError: No fixture named 'custom' found.”

I fixed this a while ago and the fix should have already been pulled. I will follow up on that.

Here is the workaround from your “build” directory where you started Toaster:

  $ . toaster stop
  $ touch ../bitbake/lib/toaster/orm/fixtures/custom.xml
  $ rm ../toaster.sqlite
  $ . toaster start [webport=0.0.0.0:8000]

- David


From: pawanKumar [mailto:[email protected]]
Sent: Sunday, March 18, 2018 9:58 PM
To: Reyna, David
Cc: [email protected]
Subject: Re: [Toaster] Toaster Interface

Hi David,
Thanks for your tip.
I tried your tip but it didn't worked.
Can you please suggest any other, so I can try that.

Regards,
Pavan.

On Sat, Mar 17, 2018, 11:28 AM pawanKumar <[email protected]<mailto:[email protected]>> wrote:
Thanks for the tip!

On Sat, Mar 17, 2018, 12:28 AM Reyna, David <[email protected]<mailto:[email protected]>> wrote:
Hi Pavan,

There was a period when the OE Layer Index had the wrong links.

Try deleting your “…/poky/toaster.sqlite” file and restarting Toaster. That should get a clean dataset.

I will also do a fresh pull to see if something recently broke/changed in bitbake that affected Toaster (Sumo is undergoing a lot of changes right now).

- David

From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of pawanKumar
Sent: Friday, March 16, 2018 5:06 AM
To: [email protected]<mailto:[email protected]>
Subject: [Toaster] Toaster Interface

Hi,
Please clear my issue.
In yocto-toaster web interface compatible machines are zero for any release.
How to over come this.


Thanks,
Pavan.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.