Bug 9453

Summary: Does not save the re-editing of the "Git revision" field on an imported layer
Product: [Build System, Metadata & Runtime] Toaster Reporter: Libertad <libertad.gonzalez.de.la.cruz>
Component: toasterAssignee: Toaster default assignee <toaster>
Status: RESOLVED DUPLICATE QA Contact: Libertad <libertad.gonzalez.de.la.cruz>
Severity: normal    
Priority: Undecided CC: belen.barros.pena, jessica.zhang, stanciux.mihail
Version: 2.1   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
Just a screenshot of layer detail page none

Description Libertad 2016-04-12 21:28:18 UTC
Created attachment 3121 [details]
Just a screenshot of layer detail page

PROBLEM DESCRIPTION

After importing a layer, I tried to edit the "Git Revision" field then save it but it wont save the new value.


STEPS TO REPRODUCE

1. Start toaster
2. Create a new project as local
3. Import a layer with the following information:
       
       Layer name
              test-meta-intel
       Repository URL
              git://git.yoctoproject.org/meta-intel 
       Repository subdirectory
              Local 
       Git revision
              HEAD 
       Layer dependencies
             openembedded-core

4. After the layer is listed in the layer section  click on the layer test-meta-intel and edit the "Git revision" field to "master" then save. 
 you can see attachment of what the layer detail page looks like in Layer_edit_page.png

5. Go back on the project main page and again enter enter the layer detail page by clicking on the test-meta-intel layer, you will see that it still holds the value of HEAD. 


EXPECTED RESULT
1. I expected that the git revision field can be changed to master and saved as it lead to believe. 

REPRODUCE RATE: always only when  editing imported layers
Comment 1 Libertad 2016-04-15 17:41:53 UTC
This is a duplicate of 8959

*** This bug has been marked as a duplicate of bug 8959 ***
Comment 2 Libertad 2016-04-15 17:43:18 UTC
made mistake is a duplicate of 8952

*** This bug has been marked as a duplicate of bug 8952 ***