Full featured apt package using stdeb - #1686
Conversation
|
Yes please squash, and remove |
|
The build process was documented in bionic job of the example sudo apt-get install -yq apt-file build-essential debhelper dh-python fakeroot libssl-dev python-all-dev \
python-msgpack python-qt4 python-setuptools python-stdeb
python setup.py sdist
python setup.py --command-packages=stdeb.command bdist_debUsing |
|
Yes I'm fixing it. |
So you OK with the old deb building procedure in the Dockerfile? Changes to |
|
Won't the |
|
|
I thought it was supposed to create the defaults if settingsversion isn't high enough, even if the api* options are already set. |
|
Without installing extra packages and running core tests it's just builds faster. |
|
It looks like an overkill to run |
Otherwise user should connect to container upon first run and manually enable API and set username and password. |
|
I think instead the bmconfigparser should set defaults when it's missing. Then you could create a minimal keys.dat and wouldn't have to run |
|
I also don't understand why these two things (Dockerfile and dpkg) are in one PR. |
I removed dpkg use from Dockerfile because it was a documentation for building deb. I can squash those changes with the removal of previous package files. Or I can drop last two commits and address docker cleanup in separate PR if you prefer. |
PeterSurda
left a comment
There was a problem hiding this comment.
Ok approved, just fix pylint.
|
I forgot the apparmor config here. |
As you suggested this PR is instead of #1675. Maybe squash more?