This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. [bug automatically created by: add-tracking-bugs]
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1134676,1134677 # Description of your update notes=Security fix for CVE-2014-0485 # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi update submission link instead: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=1134676,1134677
Here is the upstream commit to fix this: https://bitbucket.org/nikratio/s3ql/commits/091ac263809b4e8 I don't have a tested patch for it though, any chance we can get this updated?
Can an update be pushed for this package?
We still need a fix for this, any updates?
This package is going to be marked as unresponsive maintainer and abandoned if there is no update provided in the ticket.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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.
This is fixed in version 1.19. Newer versions are already available.
The packager is unresponsive.
IIRC the newer versions of s3ql have dependencies which are not packaged for Fedora yet. Personally I would prefer if someone more committed to this Software would take over maintenance.
Could you just patch the current version to at least fix this security issue?
Can help find a new maintainer if you are unable to continue? Or at take care of this patch to provide more time to find a replacement maintainer?
s3ql-2.13-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/s3ql-2.13-1.fc21
s3ql-2.13-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/s3ql-2.13-1.fc22
Package s3ql-2.13-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing s3ql-2.13-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-10869/s3ql-2.13-1.fc22 then log in and leave karma (feedback).
s3ql-2.13-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
s3ql-2.13-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.