You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yesterday I updated my fork of armbian/build to current main branch and updated the clone on my build server: Ubuntu "22.04.3 LTS (Jammy Jellyfish)" on a qemu virtual server. Then I created a branch for work on an image for a nanopi r2s plus which I have and for which eMMC and one network interface doesn't work with the nanopi r2s image - at least it didn't a few months ago, the last time I had time to work on it.
Today I made an image but after the image was made I checked my git status and found that there is an untracked file: lib/tools/common/__pycache__/. This is the only change. The directory contains one file: bash_declare_parser.cpython-310.pyc. It was last modified a few hours ago, so I don't know what command I ran created it, but it wasn't modified by the last image build.
I checked .gitignore in the project root and it has '/__pycache__/*', which doesn't match the folder in the sub-directory due to the leading slash.
So, maybe I am mistaken and lib/tools/common/__pycache__ should be committed to git, but it seems wrong to commit an __pycache__ directory to me. Or maybe I did something wrong that caused the directory to be created. This is entirely possible: I am not experienced with the build framework and I did have a couple of failed runs before I was able to build an image.
My thinking is that __pycache__/ or something similar should be added to .gitignore, to ignore __pycache__ in sub-directories, but I'm not certain as I am not very familiar with the build framework.
I tried to search for information bout __pycache__ related to the build framework. There are very few results and none that clarify this issue.
Which feature would you like to have?
Yesterday I updated my fork of armbian/build to current main branch and updated the clone on my build server: Ubuntu "22.04.3 LTS (Jammy Jellyfish)" on a qemu virtual server. Then I created a branch for work on an image for a nanopi r2s plus which I have and for which eMMC and one network interface doesn't work with the nanopi r2s image - at least it didn't a few months ago, the last time I had time to work on it.
Today I made an image but after the image was made I checked my git status and found that there is an untracked file: lib/tools/common/__pycache__/. This is the only change. The directory contains one file: bash_declare_parser.cpython-310.pyc. It was last modified a few hours ago, so I don't know what command I ran created it, but it wasn't modified by the last image build.
I checked .gitignore in the project root and it has '/__pycache__/*', which doesn't match the folder in the sub-directory due to the leading slash.
So, maybe I am mistaken and lib/tools/common/__pycache__ should be committed to git, but it seems wrong to commit an __pycache__ directory to me. Or maybe I did something wrong that caused the directory to be created. This is entirely possible: I am not experienced with the build framework and I did have a couple of failed runs before I was able to build an image.
My thinking is that __pycache__/ or something similar should be added to .gitignore, to ignore __pycache__ in sub-directories, but I'm not certain as I am not very familiar with the build framework.
I tried to search for information bout __pycache__ related to the build framework. There are very few results and none that clarify this issue.
Funding
The text was updated successfully, but these errors were encountered: