docs-qa July 2013

docs-qa@lists.fedoraproject.org

1 participants
97 discussions

[Bug 973950] New: Type in Chapter 1.2
by Red Hat Bugzilla 29 Jan '18

29 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=973950 Bug ID: 973950 Summary: Type in Chapter 1.2 Product: Fedora Documentation Version: devel Component: power-management-guide Severity: low Priority: unspecified Assignee: r.landmann(a)redhat.com Reporter: swierckx(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com, r.landmann(a)redhat.com Description of problem: In chapter 1.2 of the power management guide there is a type in the fedora version mentioned "The kernel used in releases of Fedora prior to Fedora 8 used a periodic timer for each CPU. This timer prevents the CPU from truly going idle ..." should probably be ""The kernel used in releases of Fedora prior to Fedora 18 used a periodic timer for each CPU. This timer prevents the CPU from truly going idle ..."" I deducted this from the sentence a little further where it is mentioned that only from Fedora 18 the idle CPU state is tickles -- You are receiving this mail because: You are the QA Contact for the bug.

2 3

[Bug 842190] New: Cpufreq governor
by Red Hat Bugzilla 29 Jan '18

29 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=842190 Bug ID: 842190 QA Contact: docs-qa(a)lists.fedoraproject.org Severity: unspecified Version: devel Priority: unspecified CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com Assignee: r.landmann(a)redhat.com Summary: Cpufreq governor Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: h479627(a)rtrtr.com Type: Bug Documentation: --- Hardware: Unspecified Mount Type: --- Status: NEW Component: power-management-guide Product: Fedora Documentation Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

2 4

[Bug 832179] New: Power management guide is wrong for frequency scaling in Fedora 17
by Red Hat Bugzilla 29 Jan '18

29 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=832179 Bug ID: 832179 QA Contact: docs-qa(a)lists.fedoraproject.org Severity: medium Version: devel Priority: unspecified CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com Assignee: r.landmann(a)redhat.com Summary: Power management guide is wrong for frequency scaling in Fedora 17 Regression: --- Story Points: --- Classification: Fedora OS: Linux Reporter: jnm11(a)cam.ac.uk Type: Bug Documentation: --- Hardware: All Mount Type: --- Status: NEW Component: power-management-guide Product: Fedora Documentation Description of problem: Power management guide is wrong https://docs.fedoraproject.org/en-US/Fedora/17/html/Power_Management_Guide/… Version-Release number of selected component (if applicable): Fedora 17 the location of the cpufreq directory is misspecified it is /lib/modules/3.4.0-1.fc17.x86_64/kernel/drivers/cpufreq There are no modules acpi-cpufreq or p4-clockmod available is acpi-cpufreq directly compiled in. the cpuspeed package is mentioned for the userspace governor but no package exists in fedora 17. I have been completely unable to figure out the following use case. My laptop overheats and powers off if the cpu load is high for too long. There should be a cpu governor or userspace daemon that reduces frequency when the temperature gets too high. -- You are receiving this mail because: You are the QA Contact for the bug.

2 8

[Bug 915751] New: Remove BuildArch: noarch from the meta package example
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

Product: Fedora Documentation https://bugzilla.redhat.com/show_bug.cgi?id=915751 Bug ID: 915751 Summary: Remove BuildArch: noarch from the meta package example Product: Fedora Documentation Version: devel Component: software-collections-guide Severity: high Priority: high Reporter: pkovar(a)redhat.com Remove BuildArch: noarch from the meta package example in: http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html… (Changed in scl-utils-20121110.) -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 769438] New: [PATCH] Fix syntax of code examples within rpm-guide-programming-python.xml
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [PATCH] Fix syntax of code examples within rpm-guide-programming-python.xml https://bugzilla.redhat.com/show_bug.cgi?id=769438 Summary: [PATCH] Fix syntax of code examples within rpm-guide-programming-python.xml Product: Fedora Documentation Version: devel Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: rpm-guide AssignedTo: bcotton+fedora(a)gmail.com ReportedBy: dmalcolm(a)redhat.com QAContact: docs-qa(a)lists.fedoraproject.org CC: oglesbyzm(a)gmail.com, pkovar(a)redhat.com Classification: Fedora Story Points: --- Type: --- Regression: --- Mount Type: --- Documentation: --- Created attachment 548940 --> https://bugzilla.redhat.com/attachment.cgi?id=548940 Patch to Rpm Guide to fix rpm-guide-programming-python.xml Unfortunately the examples of Python code within the RPM guide have been thoroughly broken since the initial conversion to DocBook, due to the way Python treats leading whitespace as significant. I'm attaching a patch which overhauls this page, so that the code examples are syntactically valid. See the notes in the patch -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

2 5

[Bug 985020] New: explain types of rpm packages (what are they for)
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=985020 Bug ID: 985020 Summary: explain types of rpm packages (what are they for) Product: Fedora Documentation Version: devel Component: packager-guide Severity: unspecified Priority: unspecified Assignee: pkovar(a)redhat.com Reporter: bvoperdf21(a)mt2014.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: pkovar(a)redhat.com Description of problem: First I'd like to thank for the awesome documentaions available. Also +1 for the export function (PDF,html-single,...). Looking at the packagers guide I missed some information. It would be nice if you also tell what kind of rpm packages are out there. What I found so far: .rpm .src.rpm .debugsource.... .debuginfo.... For example I still don't know if the debugsource is needed when using gdb for debugging or if the debuginfo package is enough. Version-Release number of selected component (if applicable):Edition 18.0.1 How reproducible: Steps to Reproduce: 1.go to http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Pac… 2.read everything Actual results: no description of the defferent types of rpm packages Expected results: find description of the defferent types of rpm packages and what they are used for/by. Additional info: would be nice to have this -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 959626] New: config_name mismatch in mock example
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

Product: Fedora Documentation https://bugzilla.redhat.com/show_bug.cgi?id=959626 Bug ID: 959626 Summary: config_name mismatch in mock example Product: Fedora Documentation Version: devel Component: packager-guide Severity: low Priority: unspecified Assignee: pkovar(a)redhat.com Reporter: axilleas(a)archlinux.gr QA Contact: docs-qa(a)lists.fedoraproject.org CC: fnadge(a)redhat.com Category: --- Description of problem: In section 2.4.3. Testing a Package with Mock, the last example uses the epel-6-x86_64 config whereas Fedora 18 is referenced above. According to the preamble, the example should read: mock -r fedora-18-x86_64 ~/rpmbuild/SRPMS/eject-2.1.5-0.1.fc18.src.rpm Link: https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Pa… -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 980931] New: The Virtualization Administration Guide Still Uses UNIX System V Commands
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=980931 Bug ID: 980931 Summary: The Virtualization Administration Guide Still Uses UNIX System V Commands Product: Fedora Documentation Version: devel Component: virtualization-administration-guide Keywords: Documentation Severity: medium Priority: unspecified Assignee: lnovich(a)redhat.com Reporter: jhradile(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: lnovich(a)redhat.com, me(a)petetravis.com Description of problem: The Virtualization Administration Guide for Fedora 18 [1] still uses UNIX System V commands “service” and “chkconfig”. Although these commands still work and will continue to work in the foreseeable future, users are strongly advised to learn and use the new command that is shipped with systemd and is part of the Fedora distribution since version 15. Version-Release number of selected component (if applicable): Fedora-Virtualization_Administration_Guide-18-en-US-1.0-1 How reproducible: Always. Steps to Reproduce: Read section 14.3, “Starting and stopping the daemon” [2], to learn how to configure the vhostmd service to start automatically at boot time. Actual results: /sbin/chkconfig vhostmd on Expected results: systemctl enable vhostmd.service Additional info: http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet ----- [1] http://docs.fedoraproject.org/en-US/Fedora/18/html-single/Virtualization_Ad… [2] http://docs.fedoraproject.org/en-US/Fedora/18/html-single/Virtualization_Ad… -- You are receiving this mail because: You are the QA Contact for the bug.

2 2

[Bug 982899] New: 7.3.1. Establishing a Wired (Ethernet) Connection
by Red Hat Bugzilla 11 Jul '17

11 Jul '17

https://bugzilla.redhat.com/show_bug.cgi?id=982899 Bug ID: 982899 Summary: 7.3.1. Establishing a Wired (Ethernet) Connection Product: Fedora Documentation Version: devel Component: system-administrator's-guide Severity: unspecified Priority: unspecified Assignee: jhradile(a)redhat.com Reporter: im_dracula(a)hotmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: jhradile(a)redhat.com Description of problem: In section 7.3.1: Default connection no longer called 'em1' No field for 'connection name' you can add new settings for the network under different profiles by selecting 'add profile...' you can remove/reset a profile by going to the 'options' button under the profile and selecting the 'reset' item on the left, and then choosing to either 'reset' or 'forget' -- You are receiving this mail because: You are the QA Contact for the bug.

2 6

[Bug 977042] New: GUI examples presume GNOME without stating it is GNOME
by Red Hat Bugzilla 15 Jul '16

15 Jul '16

https://bugzilla.redhat.com/show_bug.cgi?id=977042 Bug ID: 977042 Summary: GUI examples presume GNOME without stating it is GNOME Product: Fedora Documentation Version: devel Component: system-administrator's-guide Severity: unspecified Priority: unspecified Assignee: jhradile(a)redhat.com Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: jhradile(a)redhat.com The System Administrator's Guide references a number of GUI utilities, many of which are specific to GNOME. It isn't immediately obvious to the uninitiated that this is the case, causing non-GNOME users to find fault with the guide. I suggest an admonition in the preface along the lines of "Some of the graphical procedures and menu locations are specific to GNOME, but most command line instructions will be universally applicable" Comprehensively differentiating between GNOME procedures, procedures for other DEs, and universal procedures would probably be prohibitively time consuming. --Pete -- You are receiving this mail because: You are the QA Contact for the bug.

1 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

docs-qa July 2013