> On 10/7/19 10:51 AM, Alan wrote:
>> On Sat, 2019-10-05 at 13:37 +0000, Rodger Etz wrote:
>>> Thanks, Chris! I did so, but reboot did not create a debugdata dir.
>>> Therefore I have uploaded the dnf logs.
>>>
>>>  From what I have seen so far, it still seems the best option to
>>> modify system-upgrade so it safes the transaction before reboot and
>>> reboot reruns it ... or something similar.
>>>
>>> Trying to figure out what obscure dependency constellation this is
>>> causing, will be painful and most likely fail, because we do not have
>>> enough information and the state of dependencies changes so quickly,
>>> the issue might not occur after the next update of those packages.
>>> And even if we find this particular one, it might be there are others
>>> as well.
>>
>> This is what I get if I don't use the --allowdelete option. The "does
>> not belong to a distupgrade repository" is the part that concerns me.
>
> I assume you mean --allowerasing?  Why don't you want to use that?

Yes. (My sinus headache is not helping.) Because it causes the upgrade to
fail after the reboot.

> The libgit2 module problem is a known issue that is currently being
> hotly discussed.  The "does not belong to a distupgrade repository"
> message is bit confusing.  Usually what it seems to mean is that some
> package that is getting upgraded was a dependency for something that
> isn't.  The original version which is still required is not available in
> any of the repos being used for the upgrade.  It would be a lot more
> helpful if dnf would provide some more useful information, like which
> package is getting upgraded to cause the problem.  Maybe that info is
> further up in the list of packages getting upgraded?
>
>> Error:
>>   Problem 1: package gnome-shell-extension-fedmsg-0.1.9-19.fc29.noarch
>> requires fedmsg-notify, but none of the providers can be installed
>>    - fedmsg-notify-0.5.9-1.fc29.noarch does not belong to a distupgrade
>> repository
>
> I don't know what's happening here.  Neither one is getting upgraded
> because they are both retired.  Maybe it's a python 2 thing.
>
>>   Problem 2: package plasma-discover-snap-5.15.5-1.fc30.x86_64 requires
>> plasma-discover = 5.15.5-1.fc30, but none of the providers can be
>> installed
>>    - plasma-discover-5.15.5-1.fc30.x86_64 does not belong to a
>> distupgrade repository
>
> Not sure here either, although there appears to have been a build
> problem.  A build of an older version was done after a newer one, so
> something could be confused.
>
>>   Problem 3: problem with installed package kf5-ktexteditor-5.59.0-
>> 1.fc30.x86_64
>>    - package kf5-ktexteditor-5.61.0-1.fc31.x86_64 requires
>> libgit2.so.28()(64bit), but none of the providers can be installed
>>    - kf5-ktexteditor-5.59.0-1.fc30.x86_64 does not belong to a
>> distupgrade repository
>>    - package libgit2-0.28.2-2.module_f31+5411+fa1856a4.x86_64 is
>> excluded
>>    - package libgit2-0.28.3-1.fc31.x86_64 is excluded
>
> This is the libgit2 issue.  It can't upgrade libgit2, so it can't
> upgrade kf5-ktexteditor.  It's telling you that the old version is not
> available in F31.
>
>>   Problem 4: problem with installed package qt5-qtwebengine-freeworld-
>> 5.12.4-2.fc30.x86_64
>>    - package qt5-qtwebengine-freeworld-5.12.4-3.fc31.x86_64 requires
>> qt5-qtbase(x86-64) = 5.12.4, but none of the providers can be installed
>
> qt5-qtbase was updated in Fedora, but qt5-qtwebengine-freeworld which
> depends on it is in rpmfusion.  I see there is a new build today, so
> this issue should be fixed soon.
>
>>    - qt5-qtwebengine-freeworld-5.12.4-2.fc30.x86_64 does not belong to
>> a
>> distupgrade repository
>>    - qt5-qtbase-5.12.4-4.fc30.x86_64 does not belong to a distupgrade
>> repository
>
> Just telling you that the packages are no longer available.
>
>>   Problem 5: problem with installed package scribus-generator-2.8.1-
>> 1.fc30.noarch
>>    - package scribus-generator-2.8.1-2.fc31.noarch requires tkinter,
>> but
>> none of the providers can be installed
>
> "tkinter" used to be provided by the python2-tkinter package, but the
> provide has been dropped.  scribus-generator needs to change the depend
> to python2-tkinter now, although it should really move to python3
> instead.
>
>>    - scribus-generator-2.8.1-1.fc30.noarch does not belong to a
>> distupgrade repository
>>    - python2-tkinter-2.7.16-2.fc30.x86_64 does not belong to a
>> distupgrade repository
>
> Again, the old packages are no longer available.
>
>>   Problem 6: package kf5-ktexteditor-devel-5.61.0-1.fc31.x86_64
>> requires
>> kf5-ktexteditor(x86-64) = 5.61.0-1.fc31, but none of the providers can
>> be installed
>>    - problem with installed package kf5-ktexteditor-devel-5.59.0-
>> 1.fc30.x86_64
>>    - package kf5-ktexteditor-5.61.0-1.fc31.x86_64 requires
>> libgit2.so.28()(64bit), but none of the providers can be installed
>>    - kf5-ktexteditor-devel-5.59.0-1.fc30.x86_64 does not belong to a
>> distupgrade repository
>>    - package libgit2-0.28.2-2.module_f31+5411+fa1856a4.x86_64 is
>> excluded
>>    - package libgit2-0.28.3-1.fc31.x86_64 is excluded
>
> libgit2 again.

If you use --allowerasing, the upgrade transaction works, but since that
flag does not get passed to the upgrade after the reboot, the process
fails because it tries to upgrade those packages and they were never
downloaded.

This is going to confuse an unknown number of people.

Q: Why do programmers confuse Halloween and Christmas?
A: Because OCT 31 == DEC 25.
_______________________________________________
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Reply via email to