Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

quattor-client: remove extra dependencies #65

Closed
jrha opened this issue May 11, 2015 · 4 comments
Closed

quattor-client: remove extra dependencies #65

jrha opened this issue May 11, 2015 · 4 comments
Assignees

Comments

@jrha
Copy link
Member

jrha commented May 11, 2015

As noted in quattor/release#90 we include extra packages on quattor clients.
In this repository this is handled by quattor/client/rpms.pan.

These are:

  • yum-priorities (xL5)
  • yum-plugin-priorities (! xL5)
  • yum-plugin-versionlock
  • perl-AppConfig
  • python-elementtree (xL5)

We should add these as dependencies of the things that need them and remove them from this template.

@jrha jrha added this to the 15.8 milestone May 11, 2015
@jouvin jouvin modified the milestones: 15.6, 15.8 May 14, 2015
@jouvin jouvin self-assigned this May 14, 2015
@jrha jrha modified the milestones: 15.10, 15.8 Aug 21, 2015
@jrha jrha modified the milestones: 16.2, 15.12 Dec 7, 2015
@jrha jrha removed this from the 16.2 milestone Feb 12, 2016
@jouvin
Copy link
Contributor

jouvin commented Jun 4, 2016

For me this isssue has been fixed a while ago (May 18, 2015) by @stdweird. #114 is a minor cleanup to use pkg_repl and handle properly the version locking used anywhere else in the Quattor client (e.g. configuration modules).
I suggest closing this issue, except if I missed something. @jrha any comment?

@jrha
Copy link
Member Author

jrha commented Jun 6, 2016

Are the dependencies now expressed correctly by the RPMs?

@jouvin
Copy link
Contributor

jouvin commented Mar 27, 2017

@jrha I just had a quick check on a SL6 machine with 16.12 and yes, the dependencies are correctly expressed in the RPMs. And as I said the mentioned template has been cleaned up a while ago. I really think this issue can be closed.

@jrha
Copy link
Member Author

jrha commented Mar 27, 2017

Great, thanks!

@jrha jrha closed this as completed Mar 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants