Created attachment 660794 [details] ftp upload config file Description of problem: Anaconda since F18 is missing this option. To add it back python-meh need to provide a libreport configuration to enable ftp/scp Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 660795 [details] libreport config file
Created attachment 660797 [details] libreport anaconda config files Please see the README in the zip file for the details.
After discussion with vpodzime we decided to create libreport-anaconda subpackage instead of pushing these files to anaconda or python-meh. The only changes required on anaconda and python-meh side are: 1. add Requires: libreport-anaconda 2. add {"type", "anaconda"} to problem data when creating crash report, so libreport will recognize it as an Anaconda problem and will handle it accordingly
(In reply to comment #3) > After discussion with vpodzime we decided to create libreport-anaconda > subpackage instead of pushing these files to anaconda or python-meh. The > only changes required on anaconda and python-meh side are: > > 1. add Requires: libreport-anaconda > 2. add {"type", "anaconda"} to problem data when creating crash report, so > libreport will recognize it as an Anaconda problem and will handle it > accordingly Doesn't work, see bug #902828.
(In reply to comment #4) > (In reply to comment #3) > > After discussion with vpodzime we decided to create libreport-anaconda > > subpackage instead of pushing these files to anaconda or python-meh. The > > only changes required on anaconda and python-meh side are: > > > > 1. add Requires: libreport-anaconda > > 2. add {"type", "anaconda"} to problem data when creating crash report, so > > libreport will recognize it as an Anaconda problem and will handle it > > accordingly > Doesn't work, see bug #902828. Patch tested with the fix for bug #902828 posted to anaconda-patches for a review.
Pushed to master.
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: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.