Bug 1384777 - dnf stucks after cleanup phase
Summary: dnf stucks after cleanup phase
Keywords:
Status: CLOSED DUPLICATE of bug 1384586
Alias: None
Product: Fedora
Classification: Fedora
Component: texlive
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-14 06:49 UTC by Pavel Grunt
Modified: 2016-10-15 12:07 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-14 13:57:33 UTC
Type: Bug


Attachments (Terms of Use)
screenshot (119.55 KB, image/png)
2016-10-14 06:49 UTC, Pavel Grunt
no flags Details

Description Pavel Grunt 2016-10-14 06:49:26 UTC
Created attachment 1210371 [details]
screenshot

Description of problem:
dnf does nothing after finishing the last package in the cleanup phase

Version-Release number of selected component (if applicable):
dnf-2.0.0_0.rc1.1-8g61f489d.fc26.noarch

How reproducible:
100%

Steps to Reproduce:
1. sudo dnf update --refresh

Actual results:
dnf does nothing after finishing the last package in the cleanup phase

Expected results:
dnf finishes successfully

Additional info:
I am using dnf & friend from copr rpmsoftwaremanagement/dnf-nightly

Comment 1 Igor Gnatenko 2016-10-14 07:17:00 UTC
I bet money that you have texlive* packages.

Comment 2 Igor Gnatenko 2016-10-14 07:17:28 UTC
Basically it does updmap in endless loop.

Comment 3 Pavel Grunt 2016-10-14 07:31:36 UTC
(In reply to Igor Gnatenko from comment #1)
> I bet money that you have texlive* packages.

It was a good bet

Comment 4 Tomas Mraz 2016-10-14 10:09:49 UTC
It is also breaking rawhide builds which BR texlive.

Comment 5 Jerry James 2016-10-14 13:49:20 UTC
See bug 1384586, where I gave a fix for this.

Comment 6 Igor Gnatenko 2016-10-14 13:57:33 UTC

*** This bug has been marked as a duplicate of bug 1384586 ***


Note You need to log in before you can comment on or make changes to this bug.