On 10/20/19 10:59 PM, Adam Williamson wrote:
On Sun, 2019-10-20 at 06:56 +0800, Ed Greshko wrote:
> On 10/18/19 2:31 PM, Ed Greshko wrote:
>> On 10/18/19 2:05 PM, Adam Williamson wrote:
>>> I might need more logs from your case to be sure of what's going on -
>>> if you could put the dnf logs and system journals up somewhere it'd
>>> help. Also, did you re-run the download phase after updating the
>>> system-upgrade plugin? You do need to do that...
>> Yes, I ran "dnf system-upgrade clean" as well as "dnf clean
packages" for good measure.
>>
>>> The change I put in last week fixes the case I diagnosed, but I mean
>>> it's still possible there's some other case where the transactions
come
>>> up different for sure. Will need data to figure it out though.
>> OK....
>>
>> journal is at
https://drive.google.com/open?id=1qCUyZcC5-QjE83uh9p5wC10tIai1PCO2
>> dnf log is at
https://drive.google.com/file/d/1K17NzRLf8e945kQ1gHKdlFqi2v87IpQb/view?us...
>>
> And for the record I have added to
https://bugzilla.redhat.com/show_bug.cgi?id=1758588
Sorry Ed, got sidelined by other stuff. But I need the dnf log from the
download transaction as well, to compare the two. Can you find that one
too? Thanks!
As you know, I did supply the requested logs in the BZ.
The issue I reported seems either not to have been considered or is irrelevant to 178588.
So, I think others may encounter the same issue. Should a new BZ be created? Or, will
there be an advisory to erase the offending packages and manually reinstall after the
upgrade
completes?
--
The key to getting good answers is to ask good questions.