Bug 12171 - After building an image, checking the packages there's nothing.
Summary: After building an image, checking the packages there's nothing.
Status: NEW
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 5.99
Assignee: David Reyna
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-10-03 21:06 UTC by Victor Manuel Rodriguez Garcia
Modified: 2025-06-11 09:02 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
logs and screenshots (237.88 KB, application/octet-stream)
2017-10-03 21:06 UTC, Victor Manuel Rodriguez Garcia
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Victor Manuel Rodriguez Garcia 2017-10-03 21:06:23 UTC
Created attachment 4047 [details]
logs and screenshots

STATUS: FAILED
BUILD: 2.4 M4: rc1-592c3449697ce39bf07864fafd7f0a61ca230561
ENVIRONMENT: Fedora 26
STEPS TO REPRODUCE: 1. Start with a default Yocto project (qemux86), start the Toaster, and build "bitbake core-image-minimal".
 
2. In Toaster, select the build, and select the "Packages" link in the left sidebar.

3. Theres a message: No packages were built. How did this happen? well, bitbabke reuses as much stuff as possible. if all of the packages needed were already built and available in your buid infrastructure, bitbake will not rebuild any of them. this might be slightly confusing, but it does make everything faster.

EXPECTED OUTCOME: View the package.
Comment 1 David Reyna 2017-10-03 21:27:00 UTC
Toaster is showing what bitbake did. It is not an 'error', but it is also not very helpful to the user.

If Toaster was used in the project's previous builds, then the package data for when it was built is present in the Toaster database. Users could today look back through the previous builds to find that data, but this is not user friendly.

I will consider this as an enhancement request in terms of usability, to make that known data available to the user if they want that historical data since it should still be relevant (if it is not relevant then the build/package changes and the package should have then re-built).

- David
Comment 2 Victor Manuel Rodriguez Garcia 2017-10-05 19:30:22 UTC
this was the first image that I created.
Comment 3 David Reyna 2017-10-06 07:08:02 UTC
The problem may be resolved with "12194" (specifically buildhistory missing). I see the problem in builds before the patch for #12194 but not after.

I will test some more, and then close as a duplicate if nothing else comes up.
Comment 4 Randy MacLeod 2023-10-24 14:24:47 UTC
Bulk move from 4.99 or 0.00 to 5.99