Skip to content

sidn-unbound: add conflict with unbound#16

Open
BKPepe wants to merge 1 commit into
SIDN:masterfrom
BKPepe:unbound-conflicts
Open

sidn-unbound: add conflict with unbound#16
BKPepe wants to merge 1 commit into
SIDN:masterfrom
BKPepe:unbound-conflicts

Conversation

@BKPepe
Copy link
Copy Markdown

@BKPepe BKPepe commented Mar 4, 2022

Fixes:

Packages 'unbound' and 'sidn-unbound' do not conflict while providing same file: /usr/sbin/unbound
Packages 'unbound' and 'sidn-unbound' do not conflict while providing same file: /usr/sbin/unbound-checkconf
Packages 'unbound' and 'sidn-unbound' do not conflict while providing same file: /etc/unbound/named.cache
Packages 'unbound' and 'sidn-unbound' do not conflict while providing same file: /etc/init.d/unbound

Fixes:
Packages 'unbound-anchor' and 'sidn-unbound-anchor' do not conflict while providing same file: /usr/sbin/unbound-anchor
Packages 'unbound-control-setup' and 'sidn-unbound-control-setup' do not conflict while providing same file: /usr/sbin/unbound-control-setup
Packages 'sidn-unbound-control' and 'unbound' do not conflict while providing same file: /usr/sbin/unbound-control
Packages 'sidn-unbound-host' and 'unbound-host' do not conflict while providing same file: /usr/sbin/unbound-host
Packages 'unbound' and 'sidn-unbound' do not conflict while providing same file: /usr/sbin/unbound
Packages 'unbound' and 'sidn-unbound' do not conflict while providing same file: /usr/sbin/unbound-checkconf
Packages 'unbound' and 'sidn-unbound' do not conflict while providing same file: /etc/unbound/named.cache
Packages 'unbound' and 'sidn-unbound' do not conflict while providing same file: /etc/init.d/unbound
@BKPepe BKPepe force-pushed the unbound-conflicts branch from e52bda5 to b6f9915 Compare March 4, 2022 15:35
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

Successfully merging this pull request may close these issues.

1 participant