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

Package conflict on Debian #71

Closed
uu1101 opened this issue Jun 16, 2013 · 5 comments
Closed

Package conflict on Debian #71

uu1101 opened this issue Jun 16, 2013 · 5 comments

Comments

@uu1101
Copy link

uu1101 commented Jun 16, 2013

Nginx has been recently split in Debian into nginx-common, nginx-full, etc. These packages include some useful modules such as AuthPAM, which I make use of.

Commit a97e038 made Debian fetch from upstream APT repository. Unfortunately, upstream packages conflict with current Debian stable:

Preparing to replace nginx 1.2.1-2.2 (using .../nginx_1.4.1-1~wheezy_amd64.deb) ...
Unpacking replacement nginx ...
dpkg: error processing /var/cache/apt/archives/nginx_1.4.1-1~wheezy_amd64.deb (--unpack):
 trying to overwrite '/etc/init.d/nginx', which is also in package nginx-common 1.2.1-2.2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/nginx_1.4.1-1~wheezy_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Although the problem can be readily solved by Apt pinning, I think it would be convenient to be able to opt-out of using upstream packages (or, better yet, opt-in to using them) and use Debian's instead.

@hingstarne
Copy link

Hi,
i did a pull request that maybe helps you out with this issue.
Have a look at PR #89

@deric
Copy link
Contributor

deric commented Oct 8, 2013

Now it could be solved by specifying manage_repo

class { 'nginx': 
    manage_repo => false
}

or you can override the nginx package name (nginx-light from your distribution repository would be installed)

class { 'nginx': 
    manage_repo    => false,
    package_name   => 'nginx-light'
}

It should work when #152 is closed.

@3flex
Copy link
Contributor

3flex commented Nov 22, 2013

@uu1101, as deric mentioned above you can now specify the package name:

class { 'nginx':
  manage_repo  => false,
  package_name => 'nginx-light'
}

You can set manage_repo and package_name when declaring the nginx class, the nginx::package class or the nginx::package::debian class depending on how you're using it.

Could you close this if the current module meets your requirements? This code's in v0.0.6.

@3flex
Copy link
Contributor

3flex commented Nov 22, 2013

@jfryman while you're checking into issues, this can be closed. There are a couple of others that can be closed too, I'll ping you on those as well.

@jfryman jfryman closed this as completed Nov 22, 2013
@uu1101
Copy link
Author

uu1101 commented Nov 27, 2013

Thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants