Re: dnf conflict with cockpit upgrades

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> Am 17.01.2021 um 01:02 schrieb Samuel Sieb <samuel@xxxxxxxx>:
> 
> On 1/16/21 5:31 AM, Richard Shaw wrote:
>> So as far as I can remember I haven't done anything custom here but...
>>  Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
>>   - cannot install the best update candidate for package cockpit-dashboard-229-1.fc33.noarch
>>   - cannot install the best update candidate for package cockpit-bridge-229-1.fc33.x86_64
>>  Problem 2: problem with installed package cockpit-dashboard-229-1.fc33.noarch
>>   - package cockpit-bridge-235-1.fc33.x86_64 conflicts with cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
>>   - package cockpit-system-235-1.fc33.noarch requires cockpit-bridge >= 235-1.fc33, but none of the providers can be installed
>>   - cannot install the best update candidate for package cockpit-system-229-1.fc33.noarch
>> Is it me or a packaging problem?
> 
> I believe --skip-broken would have worked, but it is a packaging problem.
> 
> This is the changelog for cockpit 234-1.
> * Wed Dec 09 2020 Marius Vollmer <mvollmer@xxxxxxxxxx> - 234-1
> - machines: Allow editing VM's CPU mode and model
> - machines: Add support for cloning VMs
> - dashboard: So long
> 
> The dashboard has been removed for some reason.  But they forgot to fix the dependency of the -bridge package and didn't provide an obsoletes (which may or may not be intentional).
> I suggest filing a bug on cockpit if there isn't one already.


That is probably the most sensible thing to do.  

And it is exactly what I have also experienced on several occasions. I had to uninstall a package for the update, but was able to install it again afterwards. 

I must admit, I’m so busy at the moment, I just took it as it is. 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux