Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok). Your package (caja) Fails To Install in Fedora 34: can't install caja: - nothing provides gamin needed by caja-1.24.0-6.fc34.x86_64 If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/ Thanks!
Note that this currently affects Fedora-MATE_Compiz-Live live spin: https://koji.fedoraproject.org/koji/taskinfo?taskID=61645659
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
Should be fixed with https://bodhi.fedoraproject.org/updates/FEDORA-2021-a51cfdbc56 I dropped gamin dependency for f34. https://src.fedoraproject.org/rpms/caja/c/b783ec305e97845816813b08c8d7ac37f049b8e1?branch=rawhide Next nightly build of Mate-Compiz spin should be run fine.
Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok). All subpackages of a package against which this bug was filled are now installable or removed from Fedora 34. Thanks for taking care of it!
Mate-compiz spin failed to build again. https://koji.fedoraproject.org/koji/taskinfo?taskID=61743325 pyanaconda.errors.NonInteractiveError: Non interactive installation failed: DNF error: Error in POSTIN scriptlet in rpm package xorg-x11-fonts-ISO8859-1-100dpi 09:54:53,049 DBG exception: Gtk cannot be initialized 09:54:53,049 DBG exception: In a non-main thread, sending a message with exception data 09:54:53,049 DBG simpleline: New signal ExceptionSignal enqueued with source ScreenScheduler 09:54:53,049 INF threading: Thread Done: AnaInstallThread (140307588970048) 09:54:53,495 DBG simpleline: Executing inner loop 09:54:53,495 DBG simpleline: New signal ExceptionSignal enqueued with source ScreenScheduler 09:54:53,496 ERR ui.tui: Looks like something is broken with package xorg-x11-fonts-ISO8859-1-100dpi package which is part of `legacy-fonts` comps group of `basic-desktop-environment` and `base-system`. What can we do to fix this? Still wondering that other spins doesn't have this problem. Can you help me, please?
The entire compose is still doomed: https://pagure.io/releng/failed-composes/issue/2249 I suggest to wait until it is resolved. If that doe snot help, ask on devel list maybe? Not sure.
(In reply to Wolfgang Ulbrich from comment #5) > Mate-compiz spin failed to build again. > > https://koji.fedoraproject.org/koji/taskinfo?taskID=61743325 > > pyanaconda.errors.NonInteractiveError: Non interactive installation failed: > DNF error: Error in POSTIN scriptlet in rpm package > xorg-x11-fonts-ISO8859-1-100dpi > > 09:54:53,049 DBG exception: Gtk cannot be initialized > 09:54:53,049 DBG exception: In a non-main thread, sending a message with > exception data > 09:54:53,049 DBG simpleline: New signal ExceptionSignal enqueued with source > ScreenScheduler > 09:54:53,049 INF threading: Thread Done: AnaInstallThread (140307588970048) > 09:54:53,495 DBG simpleline: Executing inner loop > 09:54:53,495 DBG simpleline: New signal ExceptionSignal enqueued with source > ScreenScheduler > 09:54:53,496 ERR ui.tui: > > Looks like something is broken with package xorg-x11-fonts-ISO8859-1-100dpi > package which is part of `legacy-fonts` comps group of > `basic-desktop-environment` and `base-system`. > > What can we do to fix this? > Still wondering that other spins doesn't have this problem. > Can you help me, please? This is: https://bugzilla.redhat.com/show_bug.cgi?id=1925922 Now not only MATE but also other spins are affected. Maybe we have to ask on @devel anyway.