Skip to content

Elivepatch#5608

Closed
aliceinwire wants to merge 2 commits intogentoo:masterfrom
aliceinwire:elivepatch
Closed

Elivepatch#5608
aliceinwire wants to merge 2 commits intogentoo:masterfrom
aliceinwire:elivepatch

Conversation

@aliceinwire
Copy link
Member

initial version for elivepatch-server and elivepatch-client

@aliceinwire aliceinwire requested a review from gktrk September 4, 2017 03:48
@gentoo-repo-qa-bot gentoo-repo-qa-bot added new package The PR is adding a new package. self-maintained The PR changes only packages that are maintained by the submitter (i.e. no need to ask anybody else) assigned PR successfully assigned to the package maintainer(s). labels Sep 4, 2017
@gentoo-repo-qa-bot
Copy link
Collaborator

Pull Request assignment

Areas affected: ebuilds
Packages affected: sys-devel/elivepatch-client, sys-devel/elivepatch-server

sys-devel/elivepatch-client: @gentoo/proxy-maint (new package)
sys-devel/elivepatch-server: @gentoo/proxy-maint (new package)

@aliceinwire aliceinwire assigned gktrk and unassigned gktrk Sep 4, 2017
@aliceinwire aliceinwire requested review from dol-sen and gktrk and removed request for gktrk September 4, 2017 04:33
Copy link
Contributor

@gktrk gktrk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The server isn't installing any init or confd file?

Also,

/usr/lib64/python3.4/site-packages/resources
/usr/lib64/python3.4/site-packages/resources/AgentInfo.py
/usr/lib64/python3.4/site-packages/resources/__init__.py
/usr/lib64/python3.4/site-packages/resources/__pycache__
/usr/lib64/python3.4/site-packages/resources/__pycache__/AgentInfo.cpython-34.pyc
/usr/lib64/python3.4/site-packages/resources/__pycache__/AgentInfo.cpython-34.pyo
/usr/lib64/python3.4/site-packages/resources/__pycache__/__init__.cpython-34.pyc
/usr/lib64/python3.4/site-packages/resources/__pycache__/__init__.cpython-34.pyo
/usr/lib64/python3.4/site-packages/resources/__pycache__/dispatcher.cpython-34.pyc
/usr/lib64/python3.4/site-packages/resources/__pycache__/dispatcher.cpython-34.pyo
/usr/lib64/python3.4/site-packages/resources/__pycache__/livepatch.cpython-34.pyc
/usr/lib64/python3.4/site-packages/resources/__pycache__/livepatch.cpython-34.pyo
/usr/lib64/python3.4/site-packages/resources/dispatcher.py
/usr/lib64/python3.4/site-packages/resources/livepatch.py

We should install to our own namespace, not directly under resources. Same goes for elivepatch-client.

SLOT="0"
KEYWORDS="~amd64 ~x86"

RDEPEND="
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resources/dispatcher.py:11:import werkzeug

Copy link
Member Author

@aliceinwire aliceinwire Sep 4, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added werkzeug as dependency

inherit distutils-r1

DESCRIPTION="Live patch installer client working with elivepatch-server"
HOMEPAGE="https://wiki.gentoo.org/wiki/User:Aliceinwire/elivepatch"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update the HOMEPAGE to point to https://wiki.gentoo.org/wiki/Elivepatch

inherit distutils-r1

DESCRIPTION="Live patch building server with RESTFul Api for elivepatch-client"
HOMEPAGE="https://wiki.gentoo.org/wiki/User:Aliceinwire/elivepatch"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aliceinwire
Copy link
Member Author

aliceinwire commented Sep 4, 2017

I think the resources install location need to be fixed by setup.py and not by the ebuild

@aliceinwire
Copy link
Member Author

after latest changes to elivepatch-server
https://gist.github.com/aliceinwire/9c5163bfdc62dd995505bbdeb0b01b82

@aliceinwire aliceinwire removed the request for review from dol-sen September 4, 2017 16:52
@gktrk
Copy link
Contributor

gktrk commented Sep 4, 2017

Why is the category sys-devel? I don't think this belongs here. It's not used for a system-level development. sys-apps sounds like a better category to me.

dev-python/git-python[${PYTHON_USEDEP}]
dev-python/requests[${PYTHON_USEDEP}]"
DEPEND="${RDEPEND}
dev-python/setuptools[${PYTHON_USEDEP}]"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These entries should have a single level indent after DEPEND/RDEPEND

dev-python/flask[${PYTHON_USEDEP}]
dev-python/flask-restful[${PYTHON_USEDEP}]"
DEPEND="${RDEPEND}
dev-python/setuptools[${PYTHON_USEDEP}]"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These entries should have a single level indent after DEPEND/RDEPEND

Package-Manager: Portage-2.3.6, Repoman-2.3.1
@gktrk gktrk self-assigned this Sep 5, 2017
Package-Manager: Portage-2.3.6, Repoman-2.3.1
@gktrk
Copy link
Contributor

gktrk commented Sep 5, 2017

Merged in 4c4cea7...e6c6041. Congratulations!

@gktrk gktrk closed this Sep 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

assigned PR successfully assigned to the package maintainer(s). new package The PR is adding a new package. self-maintained The PR changes only packages that are maintained by the submitter (i.e. no need to ask anybody else)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants