Bug 1598947 - Upgrade from F26 or F27 leaves texlive in inconsistent dnf state
Summary: Upgrade from F26 or F27 leaves texlive in inconsistent dnf state
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: texlive
Version: 28
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1598948 1598949 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-07 01:03 UTC by bob mckay
Modified: 2019-05-28 21:48 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 21:48:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Trace of running dnf update after upgrade to F28 (17.89 KB, text/plain)
2018-07-07 01:03 UTC, bob mckay
no flags Details

Description bob mckay 2018-07-07 01:03:03 UTC
Created attachment 1457110 [details]
Trace of running dnf update after upgrade to F28

Description of problem:
I upgraded two fedora installations, one with F26, the other F27, both to F28. In both cases, the upgrades appeared successful, but the installed texlive was left in an inconsistent dnf state (see trace) and now fails to update correctly.


Version-Release number of selected component (if applicable): 47


How reproducible: Occurred on two different machines, upgrading from two different fedora versions. I have no way to backtrack and repeat.


Steps to Reproduce:
1. Install texlive on fedora 26 or 27
2. Upgrade to fedora 28 using dnf
3. run dnf update

Actual results: see attached trae


Expected results: the texlive distribution updates correctly


Additional info:

Comment 1 Tom "spot" Callaway 2018-07-09 13:50:32 UTC
*** Bug 1598948 has been marked as a duplicate of this bug. ***

Comment 2 Tom "spot" Callaway 2018-07-09 13:51:42 UTC
This should be resolved with the latest texlive/texlive-base in updates-testing. Please try: dnf update --enablerepo=updates-testing

Comment 3 Tom "spot" Callaway 2018-07-09 20:12:27 UTC
*** Bug 1598949 has been marked as a duplicate of this bug. ***

Comment 4 bob mckay 2018-07-09 23:05:42 UTC
Thank you Tom. That seems to be working, though with 11252 updates to go, it will be a while before I can be certain 8^). Apologies for the triplicate bug, I'm not sure how it happened, but I was on a very high latency link at the time, it may be that I repeated actions that didn't appear to have worked.

Comment 5 bob mckay 2018-07-10 00:31:45 UTC
Yep, definitely fixed. Not sure if I should mark as closed. Thanks Tom.

Comment 6 Ben Cotton 2019-05-02 19:23:55 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Ben Cotton 2019-05-02 21:20:34 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2019-05-28 21:48:40 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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