Red Hat Bugzilla – Bug 723666
libreport-python-2.0.5 FILE conflicts with report-gtk-0.23
Last modified: 2015-01-09 19:06:16 EST
Description of problem:
libreport-python-2.0.5 has a FILE conflict with report-gtk-0.23, but no actual conflict ... so dep. checking fails.
Using this to split off the report/libreport portion of https://bugzilla.redhat.com/show_bug.cgi?id=728657 : file conflicts on the F16 Alpha RC1 DVD. This is an Alpha blocker per criterion "There must be no file conflicts (cases where the files in some packages conflict but the packages have explicit Conflicts: tags are acceptable) or unresolved package dependencies during a media-based (DVD) install". Conflicts:
Robatino confirmed this is fixed in RC2 (https://fedoraproject.org/wiki/Test_Results:Fedora_16_Alpha_RC2_Install#DVD). I've also re-run the conflicts  and deps  tests against i686 and x86_64 DVD media, and confirmed the problem is resolved.
0 file conflicts found.
0 package conflicts found.
http://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life please make sure that the propper procedure is foolowed to eol report so we completely drop it out.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
Pretty sure this one's dead now.