Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1942237
Summary: | hakyll-init fails to create example site | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Martin B. <martin.bukatovic> |
Component: | ghc-hakyll | Assignee: | Jens Petersen <petersen> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 33 | CC: | petersen |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ghc-hakyll-4.13.4.0-5.fc34 ghc-hakyll-4.13.4.0-5.fc33 ghc-hakyll-4.13.4.0-5.fc32 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-03-30 00:16:04 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: |
Description
Martin B.
2021-03-23 22:36:08 UTC
The example is actually packaged though: ``` $ ls -l /usr/share/doc/ghc-hakyll-devel/example total 32 -rw-r--r--. 1 root root 724 Dec 19 2015 about.rst -rw-r--r--. 1 root root 129 Dec 19 2015 contact.markdown drwxr-xr-x. 2 root root 4096 Jan 9 17:57 css drwxr-xr-x. 2 root root 4096 Jan 9 17:57 images -rw-r--r--. 1 root root 352 Dec 19 2015 index.html drwxr-xr-x. 2 root root 4096 Jan 9 17:57 posts -rw-r--r--. 1 root root 2202 Feb 26 2020 site.hs drwxr-xr-x. 2 root root 4096 Jan 9 17:57 templates $ rpm -qf /usr/share/doc/ghc-hakyll-devel/example ghc-hakyll-devel-4.13.4.0-3.fc33.x86_64 ``` Looking at output of `strace hakyll-init .`, I see that hakyll-init looks for the example file in /usr/share/hakyll-4.13.4.0/example directory: ``` rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 stat("/usr/share/hakyll-4.13.4.0/example", 0x4200106a70) = -1 ENOENT (No such file or directory) getcwd("/home/martin/tvorba/hakyll-tutorial", 4096) = 36 ``` And indeed if I symlink the example directory there: ``` # ls -l /usr/share/hakyll-4.13.4.0/example lrwxrwxrwx. 1 root root 39 Mar 24 23:58 /usr/share/hakyll-4.13.4.0/example -> /usr/share/doc/ghc-hakyll-devel/example ``` hakyll-init starts to work: ``` $ hakyll-init . Creating ./templates/post-list.html Creating ./templates/post.html Creating ./templates/default.html Creating ./templates/archive.html Creating ./index.html Creating ./images/haskell-logo.png Creating ./site.hs Creating ./contact.markdown Creating ./css/default.css Creating ./about.rst Creating ./posts/2015-10-07-rosa-rosa-rosam.markdown Creating ./posts/2015-08-12-spqr.markdown Creating ./posts/2015-11-28-carpe-diem.markdown Creating ./posts/2015-12-07-tu-quoque.markdown Creating ./hakyll-tutorial.cabal ``` So this bug could be solved either by packaging the example into expected location, or patching hakyll to look for the example files in the %doc dir instead. The 1st option would be bit easier to do, the latter would requite bit tweaking, as hakyll-init searches for location of the example directory via cabal function getDataFileName. Thank you for reporting this. I don't actually use hakyll myself - so it is helpful feedback. FEDORA-2021-fb5b8cf6f2 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-fb5b8cf6f2 FEDORA-2021-dc750b96a0 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-dc750b96a0 FEDORA-2021-e76664b72d has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e76664b72d Thanks for the quick fix. FEDORA-2021-e76664b72d has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e76664b72d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e76664b72d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-dc750b96a0 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-dc750b96a0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-dc750b96a0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. (In reply to Martin B. from comment #7) > Thanks for the quick fix. Thank you for testing FEDORA-2021-fb5b8cf6f2 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-fb5b8cf6f2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-fb5b8cf6f2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-fb5b8cf6f2 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-dc750b96a0 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-e76664b72d has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. |