Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1748870 - containers-mounts.conf.5.gz from install of containers-common-1:0.1.40-0.2.dev.gitee9e9df.fc31.x86_64 conflicts with file from package podman-2:1.5.1-3.fc30.x86_64
Summary: containers-mounts.conf.5.gz from install of containers-common-1:0.1.40-0.2.de...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: podman
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Lokesh Mandvekar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F31BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2019-09-04 10:50 UTC by Zbigniew Jędrzejewski-Szmek
Modified: 2019-09-05 11:35 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-05 11:35:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Zbigniew Jędrzejewski-Szmek 2019-09-04 10:50:39 UTC 
During upgrade to F31:

Error: Transaction check error:
  file /usr/share/man/man5/containers-mounts.conf.5.gz from install of containers-common-1:0.1.40-0.2.dev.gitee9e9df.fc31.x86_64 conflicts with file from package podman-2:1.5.1-3.fc30.x86_64
Comment 1 Fedora Blocker Bugs Application 2019-09-04 10:51:02 UTC 
Proposed as a Blocker for 31-beta by Fedora user zbyszek using the blocker tracking app because:

 Breaks upgrade path.
Comment 2 Daniel Walsh 2019-09-04 18:37:45 UTC 
It looks like if podman was updated in same transaction, this would not have happened.


rpm -qlp podman-1.5.1-2.17.dev.gitce64c14.fc31.x86_64.rpm | grep man5
Comment 3 Adam Williamson 2019-09-04 23:38:40 UTC 
Yeah...podman-1.5.1-2.17.dev.gitce64c14.fc31 is tagged f31 stable, so the question may be 'why isn't your upgrade including the newer podman?' The answer may well be that it has some kinda dependency issue with something *else*. Can you look into the upgrade dnf output/logs and see if you can see a reason, Zbigniew?
Comment 4 Zbigniew Jędrzejewski-Szmek 2019-09-05 11:35:35 UTC 
That's a good question. Previously I removed podman to make the upgrade, and now 'dnf install podman' proposes podman-1.5.1-2.17.dev.gitce64c14.fc31.x86_64 without any issue. Unfortunately I didn't save the dnf output from
before. Let's close this.
Note You need to log in before you can comment on or make changes to this bug.