bbhtt opened a new issue, #1988:
URL: https://github.com/apache/buildstream/issues/1988

   Create an image with Python 3.13 to get cache key:
   
   ```sh
   distrobox create --pull -i debian:sid --name debian-sid
   distrobox enter debian-sid
   sudo apt install python3.13-venv python3-pip lzip git bubblewrap
   python3 -m venv .venv && source .venv/bin/activate
   pip install dulwich requests buildstream
   git clone [email protected]:freedesktop-sdk/freedesktop-sdk.git
   git checkout 9544ef08d442518af349be4188f808a271c08168
   
   bst show -f "%{full-key}" --deps none components/glib.bst
   f3bc575e05a5df618f57874c4c8b54b82519bf2cd3cffb0f41def6f0a1c08fa7
   ```
   
   Now do the same with a Python 3.12 based image:
   
   
   ```sh
   distrobox create --pull -i debian:trixie --name debian-trixie
   distrobox enter debian-trixie
   sudo apt install python3-venv python3-pip lzip git bubblewrap
   python3 -m venv .venv && source .venv/bin/activate
   pip install dulwich==0.22.7 requests==2.32.3 buildstream==2.4.0
   git clone [email protected]:freedesktop-sdk/freedesktop-sdk.git
   git checkout 9544ef08d442518af349be4188f808a271c08168
   
   bst show -f "%{full-key}" --deps none components/glib.bst
   ad991b447c32c8755bcf7f530299eefd810a2d04ab8d619e9345d98ff5989919
   ```
   
   
   Primary investigation reveals that `get_unique_key` elements are changing 
order between Python versions for example the below (but there are others too):
   
   ```
   Elementsource uniq key: [{'key': {'ref': 
'3.5.2-0-g08dacae618775831243f6bbab47d9be590d511f2', 'bugfix': 1}, 'name': 
'git_repo'}]
   Elementsource cache key: 
7aa86099aeb23ad95c064a361420d6677a22acefd1a314da4041128d19b7d8f7
   ```
   
   
[python3.13.txt](https://github.com/user-attachments/files/18546851/python3.13.txt)
   
[python3.12.txt](https://github.com/user-attachments/files/18546852/python3.12.txt)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to