Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=922305
Bug ID: 922305
Summary: I can't build this doc for f18(and f17)
Product: Fedora Documentation
Version: devel
Component: musicians-guide
Severity: unspecified
Priority: unspecified
Assignee: christopher.antila(a)adjectivenoun.ca
Reporter: elf(a)poyo.jp
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com
Description of problem:
I can't build this doc for f18.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. git clone ssh://git.fedorahosted.org/git/docs/musicians-guide.git
2. git checkout f18
3. publican build --embedtoc --publish --formats html-single --langs ja-JP
Actual results:
This step is to create a Fedora Draft Documentation.
$ find publish -type f -name \*.html
publish/ja-JP/Fedora_Draft_Documentation/0.1/html-single/Musicians_Guide/index.html
Expected results:
I want to create a Musicians Guide for f18.
Additional info:
I can not create a document also for f17.
Work results, for the f16 is created.
$ git checkout f17
$ publican build --embedtoc --publish --formats epub,html,html-single --langs
ja-JP
$ find publish -type f -name \*.html
publish/ja-JP/Fedora/16/html-single/Musicians_Guide/index.html
--
You are receiving this mail because:
You are the QA Contact for the bug.
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=920442
Bug ID: 920442
Summary: Typos in some new messages
Product: Fedora Documentation
Version: devel
Component: uefi-secure-boot-guide
Severity: medium
Priority: unspecified
Reporter: yurchor(a)ukr.net
Created attachment 708774
--> https://bugzilla.redhat.com/attachment.cgi?id=708774&action=edit
Patch to fix the typos
Description of problem: Some new files contain typos
Version-Release number of selected component (if applicable): git/master
How reproducible: always
Steps to Reproduce: Open files from the patch attached
Actual results:
funcionality
firmwre
Expected results:
functionality
firmware
Additional info:
thanks for fixing these typos
--
You are receiving this mail because:
You are the QA Contact for the bug.
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=912563
Bug ID: 912563
Summary: Instructions faulty and/or lackng regarding validation
of ISO's from a Windows 7 platform
Product: Fedora Documentation
Version: devel
Component: readme-burning-isos
Severity: medium
Priority: unspecified
Reporter: j.moorhouse(a)zoomtown.com
Created attachment 699286
--> https://bugzilla.redhat.com/attachment.cgi?id=699286&action=edit
Attachment 3 (the other 2 weren't allowed); 3 attempts at Command Prompt
Description of problem: First, you assume that the CHECKSUM file is readily
available; it isn't. It can be found by clicking the proper link from
https://fedoraproject.org/en/verify . In "Burning ISO Images to disc" 3.1 you
suggest 3 free tools to check the hashes in a Windows Graphical Environment;
none work. HashTab (att 1) doesn't cover the SHA256 algorithm, the web site for
the Marxio File Checksum Verifier couldn't be accessed, snd the DiviHasher (att
2) worked fine except that the length of the calculated hash exceeded the space
available. In 3.2 (att 3), we are trying the Command Line. The first attempt
does it just like the manual; it failed. The second assumed that by "Owner" in
the manual example you meant to substitute the actual name of the owner; it too
failed. The third attempt does the directory change in one operation and the
hash calculation in another, because that works; doing them both in the same
contiguous operation doesn't.
Incidentally, Windows no longer uses those cuddly little "My Whatever"
expressions.
Version-Release number of selected component (if applicable):
How reproducible: Very!! I spent over a week fighting this!
Steps to Reproduce:
1. Just follow the printed directions exactly
2.
3.
Actual results:
See attachments
Expected results:
Calculation of a valid checksum
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=879745
Bug ID: 879745
Summary: 18.5. Setting a FreeIPA Server as an Apache Virtual
Host causes systax errors
Product: Fedora Documentation
Version: devel
Component: freeipa-guide
Severity: unspecified
Priority: unspecified
Reporter: deanhunter(a)comcast.net
Description of problem:
Following the instructions in Section 18.5. Setting a FreeIPA Server as an
Apache Virtual Host of the FreeIPA Guide results in systax errors in the Apache
configuration.
Version-Release number of selected component (if applicable):
Fedora 17 FreeIPA Guide
freeipa-server.x86_64 2.2.1-2.fc17
How reproducible:
consistently
Steps to Reproduce:
1. Follow the instructions to modify ipa.conf
2. apachectl configtest
Actual results:
WSGISocketPrefix cannot occur within <VirtualHost> section
KrbConstrainedDelegationLock cannot occur within <VirtualHost> section
Expected results:
Syntax OK
Additional info:
I am trying to server user content from the Apache server installed with
FreeIPA. I thought if I configured the IPA server into a virtual host I could
create additional virtual hosts for user content without conflict.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=848546
Bug ID: 848546
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
Assignee: dlackey(a)redhat.com
Summary: ipa-install-server used instead of ipa-server-install
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: rmeggins(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: freeipa-guide
Product: Fedora Documentation
https://docs.fedoraproject.org/en-US/Fedora/17/html/FreeIPA_Guide/creating-…
"The FreeIPA setup process can be minimal, where the administrator only
supplies some required information, or it can be very specific, with
user-defined settings for many parts of the FreeIPA services. The configuration
is passed using arguments with the ipa-install-server script."
This should say ipa-server-install
--
You are receiving this mail because:
You are the QA Contact for the bug.