Bug 2053985
| Summary: | zathura-pdf-mupdf-0.3.8 is available | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
| Component: | zathura-pdf-mupdf | Assignee: | Ankur Sinha (FranciscoD) <sanjay.ankur> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | julen, mjg, psabata, sanjay.ankur | ||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | zathura-pdf-mupdf-0.3.8-3.fc35 zathura-pdf-mupdf-0.3.8-3.fc36 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-04-28 05:51:18 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Upstream Release Monitoring
2022-02-13 19:09:07 UTC
Created attachment 1860889 [details]
Update to 0.3.8 (#2053985)
the-new-hotness/release-monitoring.org's scratch build of zathura-pdf-mupdf-0.3.8-1.fc34.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=82780786 Heads-up: scratch build failed because of a missing tarball, which is fixed now. There are more problems, though, due to a changed meson build file upstream (catering to debian). I'm on it since this is directly related to the way we package mupdf on Fedora. First tests seem to work (reverting upstream's meson build change): F37 https://koji.fedoraproject.org/koji/taskinfo?taskID=82785325 F35 https://koji.fedoraproject.org/koji/taskinfo?taskID=82785070 Expect a PR tomorrow. So, to conclude: While I can get zathura-pdf-mupdf to build in Fedora I don't think it's worth it: git log --oneline 0.3.7..0.3.8 c4583da (tag: 0.3.8) Merge branch 'release/0.3.8' e6bbc27 Version 0.3.8 49a85ef Rework detection of mupdf bc495b6 Update installation instructions a95eb9d Merge branch 'mupdf-1.19' into 'develop' 3547a91 (mjg/mupdf-1.19, mupdf-1.19) link against tesseract/leptonica for mupdf 1.19.0 1e192df Merge tag '0.3.7' into develop So there are only two code changes: 3547a91 we carry in Fedora anyways, and it's upstreamed now 49a85ef breaks builds in Fedora, and we basically need to revert it So we would need to trade one patch (which is upstreamed) for another one which will never be upstreamed. None of them change any functionality. Upstream thinks their new mupdf detection is the right way to go (I don't think so). Once mupdf switches to shared builds (at some point in the future) things are different anyways. So I suggest to close as wontfix. (I pushed the necessary changes to mjg/zathura-pdf-mupdf nonetheless in case the maintainers decide differently, but no PR from me.) FEDORA-2022-a4676fa1df has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a4676fa1df FEDORA-2022-a4676fa1df has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-a4676fa1df` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a4676fa1df See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-90057185e6 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-90057185e6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-90057185e6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-8569eb0af6 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8569eb0af6 FEDORA-2022-253d8f36b2 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-253d8f36b2 FEDORA-2022-8569eb0af6 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-8569eb0af6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-8569eb0af6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-253d8f36b2 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-253d8f36b2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-253d8f36b2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-253d8f36b2 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-8569eb0af6 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |