Bug 1154321
| Summary: | Fedora Packaging Rules violation: No source for chrome/content/rulesets.json | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan Kratochvil <jan.kratochvil> |
| Component: | mozilla-https-everywhere | Assignee: | Russell Golden <niveusluna> |
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 38 | CC: | jan, jan.kratochvil, niveusluna |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-19 12:15:21 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 739323 | ||
|
Description
Jan Kratochvil
2014-10-18 19:31:32 UTC
Ah. Before the sqlite changeover, they had been XML. I never switched from just grabbing the XPI and extracting it. Completely forgot that SQL databases were technically binary. Should a new release be pushed out ASAP for this, or can it wait until the next upstream release? I intend to fix it right now in SCM and Rawhide either way. I forgot about this. Fixing this bug will make it unable to build on EL6. The build requires Python 2.7. I don't know the needed python to patch the build scripts. (In reply to Russell Golden from comment #1) > Should a new release be pushed out ASAP for this, or can it wait until the > next upstream release? I find a next upstream release fine, it is great there is at least a response to this Bug. Thanks. (In reply to Russell Golden from comment #2) > I forgot about this. Fixing this bug will make it unable to build on EL6. > The build requires Python 2.7. Maybe to package that .sqlite file into .src.rpm and use it only for EL6 build? But this may be more a question for fedora-devel if there are some established practices for such cases. > I find a next upstream release fine, it is great there is at least a > response to this Bug. Thanks. You... expected... no response? O.o > Maybe to package that .sqlite file into .src.rpm and use it only for EL6 > build? But this may be more a question for fedora-devel if there are some > established practices for such cases. I'd better ask, yeah. This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22 Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. It is now in "chrome/content/rulesets.json" so it is more editable but still that is apparently a compilation output file. This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'. At the moment, we are using signed upstream tarballs to take advantage of Firefox's signature validation. Building from upstream git source is a major undertaking due to many build dependencies. I've already tried once, but the number of new required JS packages quickly grew into tens of packages, so I gave up. Help is welcome. I did rebuild it fine some time ago. I will try to package a build script. Why Status->POST? Geez. The build deps got even worse when I wasn't paying attention, didn't they? As long as you're going to build it from source, you might disable the cacert.org rules. I asked for a build flag to be added for that a long time ago, but since compiling for EPEL was such a pain, I never used it. I think I'll take back up building for EPEL now that I have a Fedora system installed FINALLY. I may have to resort to decompressing the tarball, though. The difficulty building it once EFF changed the build reqs is what made me give up and decompress in the first place. I *still* don't know python. <_< This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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. mozilla-https-everywhere-2018.1.29-2.fc29 https-everywhere-2018.1.29-eff/rules/default.rulesets This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'. This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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. mozilla-https-everywhere-2019.6.27-3.fc31 This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32. This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 '32'. 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 32 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. mozilla-https-everywhere-2020.8.13-2.fc35 This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35. This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. mozilla-https-everywhere-2022.5.11-1.fc38 This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38. |