Bug 8093 - Release change doesn't check machine compatibility
Summary: Release change doesn't check machine compatibility
Status: RESOLVED OBSOLETE
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: Future
Assignee: Elliot Smith
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-08-04 10:48 UTC by Michael Wood
Modified: 2016-04-22 15:55 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Wood 2015-08-04 10:48:44 UTC 
If you change the release of the project we currently don't check to see if the machine set is still valid.
Comment 1 Michael Halstead 2015-08-12 15:58:09 UTC 
Clearing 2.0 milestone
Comment 2 Elliot Smith 2015-09-16 07:18:25 UTC 
We could remove the capability to change the release for a project, so it's frozen when you create the project. If you want a project for other releases, make a new project. This would considerably simplify things.
Comment 3 Belen Barros Pena 2015-09-16 09:40:13 UTC 
How do we know if the machine is valid or not? Do you mean if it is still provided by one of the layers in the project after the release change?

About Elliot's suggestion of not being able to change the release, that is a bit draconian, particularly because we don't have an easy way to delete projects right now. What if I selected the wrong release by mistake? (which, by the way, just happened to me yesterday)

I rather keep the ability to change the project release, if at all possible.
Comment 4 Belen Barros Pena 2016-04-22 15:55:07 UTC 
We no longer allow users to change the project release, so this should now obsolete.