https://bugzilla.redhat.com/show_bug.cgi?id=1021605
Bug ID: 1021605
Summary: No Default Syslog
Product: Fedora Documentation
Version: devel
Component: install-guide
Keywords: Tracking
Assignee: pbokoc(a)redhat.com
Reporter: pbokoc(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: brentrbrian(a)gmail.com, johannbg(a)gmail.com,
jreznik(a)redhat.com, kvolny(a)redhat.com,
mattdm(a)redhat.com, pbokoc(a)redhat.com,
yjcoshc(a)gmail.com, zach(a)oglesby.co, zbyszek(a)in.waw.pl
Depends On: 967521, 998573
Blocks: 1001355, 1001356
+++ This bug was initially created as a clone of Bug #998573 +++
This is a tracking bug for Change: No Default Syslog
For more details, see: http://fedoraproject.org//wiki/Changes/NoDefaultSyslog
No longer install a traditional syslog service by default. (Specifically,
remove rsyslog from the @core or @standard groups in comps.)
--- Additional comment from Zbigniew Jędrzejewski-Szmek on 2013-10-08 15:22:54
EDT ---
http://cgit.freedesktop.org/systemd/systemd/commit/?id=2b8f6883a17b
--- Additional comment from Jaroslav Reznik on 2013-10-11 04:44:57 EDT ---
This message is a reminder that Fedora 20 Accepted Changes 100%
Completed Deadline is on 2013-10-15 [1].
All Accepted Changes has to be code complete and ready to be
validated in the Beta release (optionally by Fedora QA). Required
bug state at this point is ON_QA.
As for several System Wide Changes, Beta Change Deadline is a
point of contingency plan, all incomplete Changes will be
reported to FESCo for 2013-10-16 meeting. In case of any
questions, don't hesitate to ask Wrangler (jreznik).
[1] https://fedoraproject.org/wiki/Releases/20/Schedule
--- Additional comment from Matthew Miller on 2013-10-15 14:38:53 EDT ---
The basic change to implement this went in, although quite a few packages still
bring in rsyslogd as a dependency. I think this feature is fine as it is, and
we'll detangle that as part of making separate, targeted Fedora products.
--- Additional comment from Jaroslav Reznik on 2013-10-16 06:56:42 EDT ---
Ok, thanks, moving to ON_QA.
--- Additional comment from Karel Volný on 2013-10-21 08:27:14 EDT ---
just FTR, journal brings bug #967521 - how could we switch to this nonsense if
that one is still unresolved?
well, in fact, how could we even have this activated by default, maybe I'm just
out of luck googling, but I see no approval for journal to be used?
--- Additional comment from Jóhann B. Guðmundsson on 2013-10-21 08:59:21 EDT
---
Just an FYI This feature is not as simple as no default syslog. We need to fix
the entire syslog ( journal/rsyslog/syslog-ng ) implementation in the
distribution, come up with virtual provide ( to sub package or not to sub
package rsyslog/syslog-ng ) as well as fix roughly 600 packages. Now the
proposal on how to do so has been stuck with FPC for 2 years now and until that
has been done and fixed this feature can never be considered 100% complete...
--- Additional comment from Matthew Miller on 2013-10-21 09:10:10 EDT ---
(In reply to Jóhann B. Guðmundsson from comment #6)
> Just an FYI This feature is not as simple as no default syslog. We need to
> fix the entire syslog ( journal/rsyslog/syslog-ng ) implementation in the
> distribution, come up with virtual provide ( to sub package or not to sub
> package rsyslog/syslog-ng ) as well as fix roughly 600 packages. Now the
> proposal on how to do so has been stuck with FPC for 2 years now and until
> that has been done and fixed this feature can never be considered 100%
> complete...
I agree that that's the target, and also that it will continue to be
slow-moving. This feature was intentionally meant to slice off and accomplish a
small portion of that.
--- Additional comment from Brent R Brian on 2013-10-21 09:42:27 EDT ---
My comments are not intended to be a remedy, fix, enoursement of a fix/remedy
or anything other than a "data point".
If you guys need a "lab rat", let me know.
B
--- Additional comment from Jóhann B. Guðmundsson on 2013-10-21 11:10:22 EDT
---
(In reply to Matthew Miller from comment #7)
> (In reply to Jóhann B. Guðmundsson from comment #6)
> > Just an FYI This feature is not as simple as no default syslog. We need to
> > fix the entire syslog ( journal/rsyslog/syslog-ng ) implementation in the
> > distribution, come up with virtual provide ( to sub package or not to sub
> > package rsyslog/syslog-ng ) as well as fix roughly 600 packages. Now the
> > proposal on how to do so has been stuck with FPC for 2 years now and until
> > that has been done and fixed this feature can never be considered 100%
> > complete...
>
> I agree that that's the target, and also that it will continue to be
> slow-moving. This feature was intentionally meant to slice off and
> accomplish a small portion of that.
That is one of the core problem people really as in that feature and related
work are just implemented up to the point it serves the feature requester need
( and is labelled as 100% feature completed ) as opposed to the actual work
required to implement properly into the distribution.
What we need to do is to keep distribute wide changes as these in a separated
branch and switch all the components at the same time when the feature actually
is 100% feature complete
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=967521
[Bug 967521] /var/log/journal breaks system startup
https://bugzilla.redhat.com/show_bug.cgi?id=998573
[Bug 998573] No Default Syslog
https://bugzilla.redhat.com/show_bug.cgi?id=1001355
[Bug 1001355] No Default Syslog
https://bugzilla.redhat.com/show_bug.cgi?id=1001356
[Bug 1001356] No Default Syslog
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008207
Bug ID: 1008207
Summary: FreeIPA OTP UI
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nathaniel(a)natemccallum.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, tbabej(a)redhat.com,
zach(a)oglesby.co
Depends On: 998526
+++ This bug was initially created as a clone of Bug #998526 +++
This is a tracking bug for Change: FreeIPA OTP UI
For more details, see: http://fedoraproject.org//wiki/Changes/IPAv3OTPUI
FreeIPA will gain a user interface for managing users' OTP tokens.
--- Additional comment from Tomas Babej on 2013-08-28 10:24:59 EDT ---
This feature is self-contained and not in a testable state yet. It is planned
for FreeIPA 3.4 Beta release which is aligned with the F20 schedule.
------------------------------------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001200.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008206
Bug ID: 1008206
Summary: FreeIPA OTP UI
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nathaniel(a)natemccallum.com,
relnotes(a)fedoraproject.org, tbabej(a)redhat.com,
wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 998526
+++ This bug was initially created as a clone of Bug #998526 +++
This is a tracking bug for Change: FreeIPA OTP UI
For more details, see: http://fedoraproject.org//wiki/Changes/IPAv3OTPUI
FreeIPA will gain a user interface for managing users' OTP tokens.
--- Additional comment from Tomas Babej on 2013-08-28 10:24:59 EDT ---
This feature is self-contained and not in a testable state yet. It is planned
for FreeIPA 3.4 Beta release which is aligned with the F20 schedule.
----------------------------------------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001200.h…
Please document this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008191
Bug ID: 1008191
Summary: Apache OpenOffice
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, stickster(a)gmail.com,
zach(a)oglesby.co
Depends On: 998511
+++ This bug was initially created as a clone of Bug #998511 +++
This is a tracking bug for Change: Apache OpenOffice
For more details, see: http://fedoraproject.org//wiki/Changes/ApacheOpenOffice
Add Apache OpenOffice, the free productivity suite, to Fedora.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008190
Bug ID: 1008190
Summary: Apache OpenOffice
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 998511
+++ This bug was initially created as a clone of Bug #998511 +++
This is a tracking bug for Change: Apache OpenOffice
For more details, see: http://fedoraproject.org//wiki/Changes/ApacheOpenOffice
Add Apache OpenOffice, the free productivity suite, to Fedora.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1021570
Bug ID: 1021570
Summary: OS Installer Support for LVM Thin Provisioning
Product: Fedora Documentation
Version: devel
Component: install-guide
Keywords: Tracking
Assignee: pbokoc(a)redhat.com
Reporter: pbokoc(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dlehman(a)redhat.com, jreznik(a)redhat.com,
pbokoc(a)redhat.com, zach(a)oglesby.co
Depends On: 998527
Blocks: 998532, 1008211, 1008212
+++ This bug was initially created as a clone of Bug #998527 +++
This is a tracking bug for Change: OS Installer Support for LVM Thin
Provisioning
For more details, see:
http://fedoraproject.org//wiki/Changes/InstallerLVMThinProvisioningSupport
LVM has introduced thin provisioning technology, which provides greatly
improved snapshot functionality in addition to thin provisioning capability.
This change will make it possible to configure thin provisioning during OS
installation.
--- Additional comment from David Lehman on 2013-08-27 11:28:33 EDT ---
The only missing piece is a way to select a usage profile in anaconda. You
specify metadata size and chunk size via kickstart. The bug to add profiles to
lvm2 for common thinp usage patterns is bug 958464.
--- Additional comment from Jaroslav Reznik on 2013-10-11 04:45:46 EDT ---
This message is a reminder that Fedora 20 Accepted Changes 100%
Completed Deadline is on 2013-10-15 [1].
All Accepted Changes has to be code complete and ready to be
validated in the Beta release (optionally by Fedora QA). Required
bug state at this point is ON_QA.
As for several System Wide Changes, Beta Change Deadline is a
point of contingency plan, all incomplete Changes will be
reported to FESCo for 2013-10-16 meeting. In case of any
questions, don't hesitate to ask Wrangler (jreznik).
[1] https://fedoraproject.org/wiki/Releases/20/Schedule
--- Additional comment from Jaroslav Reznik on 2013-10-21 10:13:43 EDT ---
I see 958464 in POST state but probably without profiles. Is it acceptable to
consider this Change completed without it or not? FESCo asked me to finish
review of Changes this week. Thanks.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=998527
[Bug 998527] OS Installer Support for LVM Thin Provisioning
https://bugzilla.redhat.com/show_bug.cgi?id=998532
[Bug 998532] Snapshot and Rollback Tool
https://bugzilla.redhat.com/show_bug.cgi?id=1008211
[Bug 1008211] OS Installer Support for LVM Thin Provisioning
https://bugzilla.redhat.com/show_bug.cgi?id=1008212
[Bug 1008212] OS Installer Support for LVM Thin Provisioning
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008211
Bug ID: 1008211
Summary: OS Installer Support for LVM Thin Provisioning
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dlehman(a)redhat.com, jreznik(a)redhat.com,
relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Depends On: 998527
Blocks: 998532
+++ This bug was initially created as a clone of Bug #998527 +++
This is a tracking bug for Change: OS Installer Support for LVM Thin
Provisioning
For more details, see:
http://fedoraproject.org//wiki/Changes/InstallerLVMThinProvisioningSupport
LVM has introduced thin provisioning technology, which provides greatly
improved snapshot functionality in addition to thin provisioning capability.
This change will make it possible to configure thin provisioning during OS
installation.
--- Additional comment from David Lehman on 2013-08-27 11:28:33 EDT ---
The only missing piece is a way to select a usage profile in anaconda. You
specify metadata size and chunk size via kickstart. The bug to add profiles to
lvm2 for common thinp usage patterns is bug 958464.
--------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/185803.html
Please document this Change in the Release Notes
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008212
Bug ID: 1008212
Summary: OS Installer Support for LVM Thin Provisioning
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dlehman(a)redhat.com, jreznik(a)redhat.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998527
Blocks: 998532
+++ This bug was initially created as a clone of Bug #998527 +++
This is a tracking bug for Change: OS Installer Support for LVM Thin
Provisioning
For more details, see:
http://fedoraproject.org//wiki/Changes/InstallerLVMThinProvisioningSupport
LVM has introduced thin provisioning technology, which provides greatly
improved snapshot functionality in addition to thin provisioning capability.
This change will make it possible to configure thin provisioning during OS
installation.
--- Additional comment from David Lehman on 2013-08-27 11:28:33 EDT ---
The only missing piece is a way to select a usage profile in anaconda. You
specify metadata size and chunk size via kickstart. The bug to add profiles to
lvm2 for common thinp usage patterns is bug 958464.
--------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/185803.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1080006
Bug ID: 1080006
Summary: Incorrect command for multi-core power saving
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Assignee: yruseva(a)redhat.com
Reporter: fedorabugs(a)aylett.co.uk
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, yruseva(a)redhat.com,
zach(a)oglesby.co
Description of problem:
In section 4.2
[https://docs.fedoraproject.org/en-US/Fedora/20/html/Power_Management_Guide/…],
there's a list of commands that can be executed to save some power. The
command listed for "enable multi-core power-saving (part of the
laptop-battery-powersave profile)" is a duplicate of the previous command and
is therefore incorrect.
Version-Release number of selected component (if applicable):
1.1-0
The command is given as:
echo Y > /sys/module/snd_ac97_codec/parameters/power_save
Which is the command for enabling audio codec power saving, not for enabling
multi-core power saving.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1036886
Bug ID: 1036886
Summary: Incorrect command to start tuned at boot in Power
Management Guide
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Assignee: yruseva(a)redhat.com
Reporter: stevenhrosenberg(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, yruseva(a)redhat.com,
zach(a)oglesby.co
Description of problem:
On this page --
http://docs.fedoraproject.org/en-US/Fedora/19/html/Power_Management_Guide/s…
-- the command to start the tuned utility at boot has two words transposed:
Specifically right here --
http://docs.fedoraproject.org/en-US/Fedora/19/html/Power_Management_Guide/s…:
How it reads:
To enable tuned to start every time the machine boots, type the following
command:
systemctl tuned enable
But it should be:
To enable tuned to start every time the machine boots, type the following
command:
systemctl enable tuned
As you can see, the last two words of the command need to be transposed.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008872
Bug ID: 1008872
Summary: CPUfreq documentation for F19 lacks information on the
new intel_pstate driver and its governors
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Assignee: yruseva(a)redhat.com
Reporter: mail2benny(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, yruseva(a)redhat.com,
zach(a)oglesby.co
https://docs.fedoraproject.org/en-US/Fedora/19/html/Power_Management_Guide/…
only documents governors for the acpi-cpufreq driver but not for the new
intel_pstate driver.
--
You are receiving this mail because:
You are the QA Contact for the bug.
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.
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.
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.
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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1025475
Bug ID: 1025475
Summary: typo in yum update for kexi-mysql
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Assignee: bcotton+fedora(a)gmail.com
Reporter: admin(a)velusuniverse.co.uk
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com,
zach(a)oglesby.co
Description of problem:
calligra-kexi-driver-mysql summary says mysqwl driver for kexi but shouldnt it
say mysql driver for kexi ??
Version-Release number of selected component (if applicable):
How reproducible:
use the yum extender andd look up calligra-kexi-driver-mysql
Steps to Reproduce:
1.
2.
3.
Actual results:
ummary says mysqwl driver for kexi
Expected results:
mysql driver for kexi
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1017792
Bug ID: 1017792
Summary: %verify doesn't know symlink, maj min
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Assignee: bcotton+fedora(a)gmail.com
Reporter: jskarvad(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com,
zach(a)oglesby.co
Description of problem:
In the "Verifying the %files section" chapter of the RPM guide [1], there is
written "symlink", but it seems RPM uses "link" instead.
Also I had trouble with the "maj" and "min", I guess there is "rdev" used
instead.
Version-Release number of selected component (if applicable):
0.1
How reproducible:
Always
Steps to Reproduce:
1. See the "Verifying the %files section" chapter
Actual results:
There are symlink, maj and min
Expected results:
The link and probably rdev
Additional info:
[1]
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM…
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1003962
Bug ID: 1003962
Summary: RPM scriptlet -p option not documented
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Assignee: bcotton+fedora(a)gmail.com
Reporter: daniel.neuberger(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com,
zach(a)oglesby.co
The fedora RPM guide does not document the -p option that can be passed to the
RPM scriptlets. It should probably be located here
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM…,
but I looked through the entire guide and couldn't find it.
The only only place I could find it documented is here
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets, but what it says is
wrong. It says:
"The basic syntax is similar to the %build, %install, and other sections of the
rpm spec file. The scripts support a special flag, -p which allows the
scriptlet to invoke a single program directly rather than having to spawn a
shell to invoke the programs. (ie: %post -p /sbin/ldconfig)"
A more accurate description is:
"The basic syntax is similar to the %build, %install, and other sections of the
rpm spec file.
The scripts support a special flag, -p which specifies the interPreter that
should be used to run the script (the default is /bin/sh). Sometimes the -p
option is used with no body in order to run a single command directly rather
than having to spawn a shell to invoke the programs (i.e. %post -p
/sbin/ldconfig). Note that this form requires that there be nothing but white
space (not even comments) until the next section begins."
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1057882
Bug ID: 1057882
Summary: Fedora - Installation Quick Start Guide - An update of
the Czech translation ready
Product: Fedora Documentation
Version: devel
Component: publishing-requests
Assignee: docs-publishers-members(a)fedoraproject.org
Reporter: josef.hruska(a)upcmail.cz
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs-publishers-members(a)fedoraproject.org
Description of problem:
Please publish an updated Czech version of the F20 Installation Quick Start
Guide
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Mostly grammar errors found in current version.
Expected results:
An updated Czech translation published - missing translation(s) added,
translation revision and precision.
Additional info:
If the bug BZ#1056196 is a serious obstacle, publish this update once the bug
is resolved.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1050903
Bug ID: 1050903
Summary: Fedora - burning ISO images to disc - Updated Czech
translation
Product: Fedora Documentation
Version: devel
Component: publishing-requests
Assignee: docs-publishers-members(a)fedoraproject.org
Reporter: josef.hruska(a)upcmail.cz
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs-publishers-members(a)fedoraproject.org
Description of problem:
Please publish an update of the Czech translation of Burning ISO images to disc
guide
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Translation update - missing translation, revision and precision.
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1008227
Bug ID: 1008227
Summary: SSD cache
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: agk(a)redhat.com, i.gnatenko.brain(a)gmail.com,
jeremy(a)goop.org, jreznik(a)redhat.com, kzak(a)redhat.com,
nobody(a)fedoraproject.org, rdieter(a)math.unl.edu,
rolf(a)rolffokkens.nl, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998543, 999690, 1000817, 1001120, 1003208, 1000078,
1003207
+++ This bug was initially created as a clone of Bug #998543 +++
This is a tracking bug for Change: SSD cache
For more details, see: http://fedoraproject.org//wiki/Changes/SSD_cache
Using recent kernel (3.9 and later) features for (fast) SSD caching of (slow)
ordinary hard disks.
--- Additional comment from Rolf Fokkens on 2013-08-21 13:35:33 EDT ---
I'll build a bcache-tools RPM and a dm-cache-utils rpm (actually bcache-tools
is already available here: bcache-tools-20130820-0.1.fc19.src.rpm).
I'll follow the procedure as described here:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
--- Additional comment from Rolf Fokkens on 2013-08-24 11:51:34 EDT ---
Tried to create a dmcache-utils package as well (Bug 1000078) but it doesn't
look really useful. So I'll focus on bcache-tools first. For that I still need
a sponsor.
--- Additional comment from Rolf Fokkens on 2013-08-27 06:52:40 EDT ---
I closed Bug 1000078 since good userland support requires LVM2 to support
dm-cache. Which will happen 'in the future', but F20 doesn't look feasible to
me.
--- Additional comment from Rolf Fokkens on 2013-08-31 16:21:30 EDT ---
Create Bug 1003207 (bcache support for dracut) which is not blocking for F20,
but probably will be blocking for F21.
--- Additional comment from Rolf Fokkens on 2013-08-31 16:25:06 EDT ---
Create Bug 1003208 (bcache support for anaconda) which is not blocking for F20,
but probably will be blocking for F21.
--- Additional comment from Rolf Fokkens on 2013-09-09 04:18:18 EDT ---
Test day planned: https://fedorahosted.org/fedora-qa/ticket/415
--------------------------------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/185336.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1058066
Bug ID: 1058066
Summary: new virt-xml functionality coming from upstream
libvirt should be documented
Product: Fedora Documentation
Version: devel
Component: virtualization-deployment-and-administrative-guide
Assignee: lnovich(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com
There is a new tool called `virt-xml` that will end up in Fedora soon[1]. It
looks very useful, and should be documented.
[1] https://www.redhat.com/archives/libvir-list/2014-January/msg01226.html
--
You are receiving this mail because:
You are the QA Contact for the bug.
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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1001344
Bug ID: 1001344
Summary: Allow kdump on secureboot machines
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, stickster(a)gmail.com,
vgoyal(a)redhat.com, zach(a)oglesby.co
Depends On: 998565
+++ This bug was initially created as a clone of Bug #998565 +++
This is a tracking bug for Change: Allow kdump on secureboot machines
For more details, see:
http://fedoraproject.org//wiki/Changes/Kdump_with_secureboot
Currently kexec/kdump is disabled on machines with secureboot enabled. This
feature aims to enable kexec/kdump on such machines.
--- Additional comment from Vivek Goyal on 2013-08-22 10:43:53 EDT ---
I think first thing is to include a new package ima-evm-tools in F20. I am not
sure how to do it.
--- Additional comment from Jaroslav Reznik on 2013-08-26 10:28:07 EDT ---
(In reply to Vivek Goyal from comment #1)
> I think first thing is to include a new package ima-evm-tools in F20. I am
> not sure how to do it.
Vivek, create Package Review -
http://fedoraproject.org/wiki/Package_Review_Process for ima-evm-tools and
block this bug on the created review bug. After review, add it to comps.
Thank you.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001179.h…
Please assess existing documentation for the impact of this Change
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001343
Bug ID: 1001343
Summary: Allow kdump on secureboot machines
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
vgoyal(a)redhat.com, wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 998565
+++ This bug was initially created as a clone of Bug #998565 +++
This is a tracking bug for Change: Allow kdump on secureboot machines
For more details, see:
http://fedoraproject.org//wiki/Changes/Kdump_with_secureboot
Currently kexec/kdump is disabled on machines with secureboot enabled. This
feature aims to enable kexec/kdump on such machines.
--- Additional comment from Vivek Goyal on 2013-08-22 10:43:53 EDT ---
I think first thing is to include a new package ima-evm-tools in F20. I am not
sure how to do it.
--- Additional comment from Jaroslav Reznik on 2013-08-26 10:28:07 EDT ---
(In reply to Vivek Goyal from comment #1)
> I think first thing is to include a new package ima-evm-tools in F20. I am
> not sure how to do it.
Vivek, create Package Review -
http://fedoraproject.org/wiki/Package_Review_Process for ima-evm-tools and
block this bug on the created review bug. After review, add it to comps.
Thank you.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001179.h…
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=997219
Bug ID: 997219
Summary: No "Write to Disk" option for ISO images in Fedora 19
Product: Fedora Documentation
Version: devel
Component: readme-burning-isos
Assignee: oglesbyzm(a)gmail.com
Reporter: sirjake(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, stickster(a)gmail.com
Description of problem:
Guide says that you can right click on a ISO image and choose "Write to disc."
This is not true, at least with Fedora 19.
Version-Release number of selected component (if applicable):
19
How reproducible:
Always, at least in 32 bit.
Steps to Reproduce:
1.
http://docs.fedoraproject.org/en-US/Fedora/19/html/Burning_ISO_images_to_di…
2. Insert a DVD.
3. Attempt to follow the directions above. No "Write to disk" option exists.
Actual results:
No obvious way to burn ISO images in Fedora Linux 19.
Expected results:
Directions to burn ISO disk in Fedora Linux 19
Additional info:
I had a new-to-me computer that I assumed would not support 64 bit, but after
installing 32 bit found out that 64 was supported by my processor. I downloaded
64 ( Fedora-Live-Desktop-x86_64-19-1.iso ), and wanted to burn a disk of it,
but the option was not available and the directions online did not help. I had
to go back to Windows on a different machine to burn it.
Note: I do have a DVD burner on this machine. The same thing occurs with CD's
in the burner.
--
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=948823
Bug ID: 948823
Summary: Need a search solution for docs.fedoraproject.org
Product: Fedora Documentation
Version: devel
Component: project-tracking
Severity: unspecified
Priority: unspecified
Assignee: nobody(a)fedoraproject.org
Reporter: sparks(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, sparks(a)redhat.com,
stickster(a)gmail.com
Category: ---
Description of problem: Due to the removal of Google search feature (see bug
616876) we no longer have a search solution for docs.fp.o.
We need to investigate an alternate solution and bring the search feature back.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1002573
Bug ID: 1002573
Summary: Enable SELinux Labeled NFS Support
Product: Fedora Documentation
Version: devel
Component: security-guide
Keywords: Tracking
Assignee: sparks(a)redhat.com
Reporter: sparks(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, me(a)petetravis.com,
nobody(a)fedoraproject.org, pkennedy(a)redhat.com,
security-guide-list(a)redhat.com, sparks(a)redhat.com,
steved(a)redhat.com, stickster(a)gmail.com,
zach(a)oglesby.co
Depends On: 984718, 998566, 1001346
+++ This bug was initially created as a clone of Bug #1001346 +++
+++ This bug was initially created as a clone of Bug #998566 +++
This is a tracking bug for Change: Enable SELinux Labeled NFS Support
For more details, see: http://fedoraproject.org//wiki/Changes/LabeledNFS
The Linux Kernel has grown support for passing SELinux labels between a client
and server using NFS.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001216.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982914
Bug ID: 982914
Summary: 7.4.1. Configuring 802.1x Security
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.4.1 under 'Procedure 7.8. For a wired connection...', '
Procedure 7.9. For a wireless connection...':
The 'Network Connections' dialogue can be accessed via:
activities --> applications --> sundry --> network connections, or via
nm-connection-editor
This is not specified at all in this section.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982911
Bug ID: 982911
Summary: 7.3.3. Establishing a Mobile Broadband 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:
Under section 7.3.3, in 'Procedure 7.3. Adding a New Mobile Broadband
Connection', 'Procedure 7.4. Editing an Existing Mobile Broadband Connection':
network connection editor can also be found at:
activities --> applications --> sundry --> network connections
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982910
Bug ID: 982910
Summary: 7.3.5. Establishing a DSL 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.5 under 'Procedure 7.6. Adding a New DSL Connection', 'Procedure
7.7. Editing an Existing DSL Connection':
These procedures could also specify that the network connections editor can be
accessed from:
activities --> applications --> Sundry --> Network Connections
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1003065
Bug ID: 1003065
Summary: images missing from document
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: low
Assignee: jhradile(a)redhat.com
Reporter: mordred(a)warpmail.net
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Description of problem:
in document:
http://docs.fedoraproject.org/en-US/Fedora/18/html-single/System_Administra…
missing following 5 images under:
http://docs.fedoraproject.org/en-US/Fedora/18/html-single/System_Administra…
images/authconfig-ui.png
images/authconfig-local.png
images/authconfig_LDAP.png
images/authconfig_nis.png
images/authconfig_winbind.png
Version-Release number of selected component (if applicable): n/a
How reproducible: n/a
Steps to Reproduce: n/a
Actual results:
Expected results: n/a
Additional info: n/a
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=987307
Bug ID: 987307
Summary: Section 11.1.2.4 Figure 11.2 requires updating
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: jhradile(a)redhat.com
Reporter: im_dracula(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhradile(a)redhat.com
Created attachment 777222
--> https://bugzilla.redhat.com/attachment.cgi?id=777222&action=edit
layout of ldap/kerberos options in authentication dialog
Description of problem:
Figure 11.2 in section 11.1.2.4 no longer looks like this as there is a third
'password options tab' on this dialog
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=987301
Bug ID: 987301
Summary: Section 11.1.1 Figure 11.1 missing
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
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:
Section 11.1.1 has a missing screenshot (Figure 11.1)
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=983366
Bug ID: 983366
Summary: Cover Page says "Fedora 17" in 'header' logo
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:
Header logo on cover page of System Administrators guide says "Fedora 17" above
first line of text
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982894
Bug ID: 982894
Summary: 7.2.4. User and System Connections
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:
the network settings dialogue does not have tabs, instead, the identity section
of the dialogue is concerned with setting the connection to be available to all
users (or not)
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982510
Bug ID: 982510
Summary: 4.3. Using the User Manager Tool
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 4.3, the location of the user manager tool has changed in Gnome
3.8.3:
Activities --> Applications --> Sundry --> Users and Groups
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982504
Bug ID: 982504
Summary: 4.2. Using the User Accounts Tool
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:
section 4.2 Using the User Accounts Tool
related to bug 982500
location of the settings dialog is:
activities --> applications --> utilities --> settings
Further:
The 'User Accounts' tool is called 'Users' in Gnome 3.8.3
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982444
Bug ID: 982444
Summary: 1.1 - region and language
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:
Sys admin guide information regarding region and language doesn't specify which
desktop environment is assumed to find the region and language. Also to find
region and language in KDE, you click on the applications launcher, go to
applications --> settings --> system settings, but it's also set as a favourite
by default in F19 so can be found under favourites. Also in KDE, under system
settings, the 'region and language' settings are under 'locale',
'country/region and language'.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982500
Bug ID: 982500
Summary: 2.1 Using the Date and Time Configuration Tool
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:
Gnome settings menu location has changed in 3.8.3:
Activities --> Applications --> Utilities --> Settings
This is not reflected in section 2.1
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1018500
Bug ID: 1018500
Summary: There's no section in the documentation for NFS, after
Fedora 14
Product: Fedora Documentation
Version: devel
Component: storage-administration-guide
Assignee: ddomingo(a)redhat.com
Reporter: david.jones74(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, zach(a)oglesby.co
Description of problem:
There's no section in the documentation for current Fedora versions, about how
to configure NFS. There's SAMBA and FTP, but no NFS.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Search or browse documentation.
2.
3.
Actual results:
Can find scattered information about configuring NFS, but no consolidated
section.
Expected results:
Section for configuring NFS clients and servers.
Additional info:
There are many changes in NFS configuration since Fedora 14. There's a
different init system with different service names, There's also a new firewall
manager. I'm just guess at a lot of the details, and it's pretty frustrating.
Why does SAMBA have a large detailed section, and NFS has nothing? This is
Linux, right? Is the Fedora Project moving to SAMBA as the preferred file
sharing method?
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=990252
Bug ID: 990252
Summary: incomplete index for Virtualization Administration
Guide
Product: Fedora Documentation
Version: devel
Component: virtualization-administration-guide
Assignee: lnovich(a)redhat.com
Reporter: stephent98(a)hotmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com
Description of problem:
The index for the Virtualization Administration Guide has only three entries.
Specifically, I was trying to find information on host memory requirements.
Version-Release number of selected component (if applicable):
http://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administr…
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1068889
Bug ID: 1068889
Summary: Remove references to version numbers in package
documentation directories
Product: Fedora Documentation
Version: devel
Component: virtualization-deployment-and-administrative-guide
Assignee: lnovich(a)redhat.com
Reporter: sclark(a)fedoraproject.org
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com
Created attachment 866496
--> https://bugzilla.redhat.com/attachment.cgi?id=866496&action=edit
The attached archive contains patches to implement this change
Following instructions in
https://fedoraproject.org/wiki/Changes/UnversionedDocdirs remove the version
number from the directory name for all references to any package documentation
directory in /usr/share/doc , leaving just the package's name.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008149
Bug ID: 1008149
Summary: Contraficting info about the need of shared storage
for storing guest images to be migrated
Product: Fedora Documentation
Version: devel
Component: virtualization-getting-started-guide
Assignee: dayleparker(a)redhat.com
Reporter: jrodrigosm(a)yahoo.es
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dayleparker(a)redhat.com, docs(a)lists.fedoraproject.org
Hi,
In the Fedora 19 "Virtualization Getting Started Guide", section 2.2 ("What is
migration?"), URL
http://docs.fedoraproject.org/en-US/Fedora/19/html/Virtualization_Getting_S…
In the paragraph right before the 2.2.1 title, it is stated that "In Fedora 19,
shared storage is not necessary for storing guest images to be migrated. With
live storage migration [...]".
But in the last paragraph of the page, right before the note, it is stated that
"Shared, networked storage must be used for storing guest images to be
migrated. Without shared storage, migration is not possible."
These two statements seem contradictory to me. I just started learning about
virtualization, so I am unable to propose an alternative. But I do think some
clarification is needed.
Thanks,
Rodrigo
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982906
Bug ID: 982906
Summary: 7.3.2. Establishing a Wireless 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:
Section 7.3.2 under the heading:
'Saving Your New (or Modified) Connection and Making Further Configurations'
it states:
"You can further configure an existing connection by selecting it in the
Network Connections window and clicking Edit to return to the Editing dialog."
This could be clarified by stating that network connections can be found under:
activities --> applications --> sundry --> network connections
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=979158
Bug ID: 979158
Summary: Windows Virtio Drivers version 1-59 blue screens
windows when you hot add virtio drives
Product: Fedora Documentation
Version: devel
Component: virtualization-deployment-guide
Severity: high
Priority: unspecified
Assignee: lbailey(a)redhat.com
Reporter: robert.rupert(a)servicemesh.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lbailey(a)redhat.com
Description of problem:
Windows Blue Screens in KVM when using the latest virtio driver 1-59. When hot
adding scsi drive
Version-Release number of selected component (if applicable):
How reproducible:
fresh install with virtio scsi driver 1-59,=. Then hot add virtio scsi driver
in windows 7, 2008r2 and 2012
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
using the previose version 1-52 works fine
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=999762
Bug ID: 999762
Summary: Java FAQ
Product: Fedora Documentation
Version: devel
Component: release-notes
Severity: low
Assignee: relnotes(a)fedoraproject.org
Reporter: pcsnow(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Description of problem: Parts of Java FAQ may need some updates.
https://fedoraproject.org/wiki/Java/FAQ?rd=JavaFAQ
Version-Release number of selected component (if applicable):19
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
1. JPackage does not seem updated since 2009
2. Intelllij complains that non-sun version has performance problems during
install and recommends against use of OpenJDK.
3. It might be helpful to provide some assistance in docs to allow easy
integration of Oracle Java using system-switch-java.
The FAQ does not mention switch-java as an option.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001342
Bug ID: 1001342
Summary: Fedora 20 Boost 1.54 Uplift
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
pmachata(a)redhat.com, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 991875, 991877, 991878, 991879, 991882, 991883,
991919, 998564
+++ This bug was initially created as a clone of Bug #998564 +++
This is a tracking bug for Change: Fedora 20 Boost 1.54 Uplift
For more details, see: http://fedoraproject.org//wiki/Changes/F20Boost154
This change brings Boost 1.54.0 to Fedora 20.
--- Additional comment from Petr Machata on 2013-08-19 11:30:25 EDT ---
Current state: Boost has been rebased, most clients were rebuilt about two
weeks back. There are 7 broken boost dependencies as of now (fawkes, hugin,
iwhd, mrpt, pcl, python-tag, sumwars).
--- Additional comment from Jaroslav Reznik on 2013-08-20 08:57:28 EDT ---
(In reply to Petr Machata from comment #1)
> Current state: Boost has been rebased, most clients were rebuilt about two
> weeks back. There are 7 broken boost dependencies as of now (fawkes, hugin,
> iwhd, mrpt, pcl, python-tag, sumwars).
Could you please set blocks/depends on for broken boost deps (if bug exists?).
Thanks.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001169.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001341
Bug ID: 1001341
Summary: Fedora 20 Boost 1.54 Uplift
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, pmachata(a)redhat.com,
relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Depends On: 991875, 991877, 991878, 991879, 991882, 991883,
991919, 998564
+++ This bug was initially created as a clone of Bug #998564 +++
This is a tracking bug for Change: Fedora 20 Boost 1.54 Uplift
For more details, see: http://fedoraproject.org//wiki/Changes/F20Boost154
This change brings Boost 1.54.0 to Fedora 20.
--- Additional comment from Petr Machata on 2013-08-19 11:30:25 EDT ---
Current state: Boost has been rebased, most clients were rebuilt about two
weeks back. There are 7 broken boost dependencies as of now (fawkes, hugin,
iwhd, mrpt, pcl, python-tag, sumwars).
--- Additional comment from Jaroslav Reznik on 2013-08-20 08:57:28 EDT ---
(In reply to Petr Machata from comment #1)
> Current state: Boost has been rebased, most clients were rebuilt about two
> weeks back. There are 7 broken boost dependencies as of now (fawkes, hugin,
> iwhd, mrpt, pcl, python-tag, sumwars).
Could you please set blocks/depends on for broken boost deps (if bug exists?).
Thanks.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001169.h…
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001346
Bug ID: 1001346
Summary: Enable SELinux Labeled NFS Support
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, steved(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 984718, 998566
+++ This bug was initially created as a clone of Bug #998566 +++
This is a tracking bug for Change: Enable SELinux Labeled NFS Support
For more details, see: http://fedoraproject.org//wiki/Changes/LabeledNFS
The Linux Kernel has grown support for passing SELinux labels between a client
and server using NFS.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001216.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001345
Bug ID: 1001345
Summary: Enable SELinux Labeled NFS Support
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
steved(a)redhat.com, wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 984718, 998566
+++ This bug was initially created as a clone of Bug #998566 +++
This is a tracking bug for Change: Enable SELinux Labeled NFS Support
For more details, see: http://fedoraproject.org//wiki/Changes/LabeledNFS
The Linux Kernel has grown support for passing SELinux labels between a client
and server using NFS.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001216.h…
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008221
Bug ID: 1008221
Summary: Ryu Network Operating System
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, stickster(a)gmail.com,
ymht.fedora(a)gmail.com, zach(a)oglesby.co
Depends On: 998540
+++ This bug was initially created as a clone of Bug #998540 +++
This is a tracking bug for Change: Ryu Network Operating System
For more details, see: http://fedoraproject.org//wiki/Changes/Ryu
Ryu Network Operating System http://osrg.github.com/ryu/
------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/184930.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008220
Bug ID: 1008220
Summary: Ryu Network Operating System
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
wb8rcr(a)arrl.net, ymht.fedora(a)gmail.com,
zach(a)oglesby.co
Depends On: 998540
+++ This bug was initially created as a clone of Bug #998540 +++
This is a tracking bug for Change: Ryu Network Operating System
For more details, see: http://fedoraproject.org//wiki/Changes/Ryu
Ryu Network Operating System http://osrg.github.com/ryu/
-----------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/184930.html
Please document this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=846864
Bug ID: 846864
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: docs(a)lists.fedoraproject.org
Assignee: laine(a)redhat.com
Summary: Need a list of toolsets and when they are appropriate
in the virt Getting Started guide
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: laine(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: virtualization-getting-started-guide
Product: Fedora Documentation
The Getting Started Guide needs an overview of all the different toolsets, and
when each would be appropriate. In particular I'm talking about the following:
1) gnome-boxes
2) virt-manager
3) virsh, virt-install
4) ovirt
5) Should we point some people to OpenStack?
I will write up a first draft of this, and hand it to a qualified docs person
to edit and correctly place in the guide.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=846184
Bug ID: 846184
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: low
Version: devel
Priority: unspecified
CC: oglesbyzm(a)gmail.com
Assignee: mprpic(a)redhat.com
Summary: New Russian translation for Fedora Resource Management
Guide
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: brezhnev(a)redhat.com
Type: Bug
Documentation: ---
Hardware: All
Mount Type: ---
Status: NEW
Component: resource-management-guide
Product: Fedora Documentation
Created attachment 602635
--> https://bugzilla.redhat.com/attachment.cgi?id=602635&action=edit
Russian translation of Fedora 17 Resource Management Guide
The patch providing Russian translation of the guide is attached.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=829952
Bug ID: 829952
QA Contact: docs-qa(a)lists.fedoraproject.org
Severity: unspecified
Version: devel
Priority: unspecified
CC: oglesbyzm(a)gmail.com
Assignee: mprpic(a)redhat.com
Summary: Outdated information about cgconfig service in
Resource Management Guide for Fedora 17
Regression: ---
Story Points: ---
Classification: Fedora
OS: Unspecified
Reporter: brezhnev(a)redhat.com
Type: Bug
Documentation: ---
Hardware: Unspecified
Mount Type: ---
Status: NEW
Component: resource-management-guide
Product: Fedora Documentation
Description of problem:
The Resource Management Guide for Fedora 17 contains outdated information about
cgconfig service in section 2.1 "The cgconfig Service"
The guide states that the cgconfig service is not started by default in Fedora
17. It is not true. In addition, the guide contains phrase "When you start the
service with chkconfig" that is wrong for any release. For Fedora 17 is should
be "When you start the service with the <command>systemctl start</command>
command".
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1018053
Bug ID: 1018053
Summary: New nmcli features should be documented
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: swadeley(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
nmcli in Fedora 20 can now add, delete, edit, activate, and deactivate
connections, probably including bridge and Bond devices. This functionality
should be represented in the SysadminGuide.
http://fedoraproject.org/wiki/Networking/CLI is a start.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001349
Bug ID: 1001349
Summary: NetworkManager Bridging Support
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, psimerda(a)redhat.com,
relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Depends On: 998568
+++ This bug was initially created as a clone of Bug #998568 +++
This is a tracking bug for Change: NetworkManager Bridging Support
For more details, see:
http://fedoraproject.org//wiki/Changes/NetworkManagerBridging
NetworkManager should be able to configure bridge interfaces with commonly used
options and recognize their existing configuration on startup without
disrupting their operation.
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/186536.html
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001352
Bug ID: 1001352
Summary: NetworkManager Bridging Support
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
psimerda(a)redhat.com, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998568
Blocks: 1001349
+++ This bug was initially created as a clone of Bug #998568 +++
This is a tracking bug for Change: NetworkManager Bridging Support
For more details, see:
http://fedoraproject.org//wiki/Changes/NetworkManagerBridging
NetworkManager should be able to configure bridge interfaces with commonly used
options and recognize their existing configuration on startup without
disrupting their operation.
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/186536.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1005479
Bug ID: 1005479
Summary: Need references for YUM
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: low
Assignee: pbokoc(a)redhat.com
Reporter: lsatenstein(a)yahoo.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
I noted the following
Within
http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/s1-pk…
In the Note
Only one desktop environment can be selected at install time. To install
additional environments once Fedora is installed, use the *Software*
tool or the yum groupinstall| command.
I do not recall a previous mention of yum in this guide. We who are
familiar with Fedora know yum as the command line system software tool
that accompanies Fedora. Perhaps we need to elaborate with a footnote,
about yum and where to visit to fetch the yum documentation.
Version-Release number of selected component (if applicable):
Refer to the link.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1060216
Bug ID: 1060216
Summary: RELNOTES - Summarize the release note
suggestion/content
Product: Fedora Documentation
Version: devel
Component: release-notes
Assignee: relnotes(a)fedoraproject.org
Reporter: limburgher(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Blocks: 168083 (fc5-relnotes-traqr)
gpodder is being upgraded from 2.20.3 to 3.5.2. There is a configuration and
date storage change between these versions. After upgrading the RPM, any user
on the system who uses gpodder, prior to opening it, should run
/usr/bin/gpodder-migrate2tres, which will migrate the user's data and
configuration to the new format, including all subscribed feeds and downloaded
podcasts.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=168083
[Bug 168083] FC5 release notes tracker bug
--
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=928623
Bug ID: 928623
Summary: Need to explain HOW to try different desktop
environments in live image
Product: Fedora Documentation
Version: devel
Component: readme-live-image
Severity: unspecified
Priority: unspecified
Assignee: docs(a)lists.fedoraproject.org
Reporter: mike(a)thosehallidays.org
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: nathan(a)afternoondust.co.uk, oglesbyzm(a)gmail.com
Description of problem:
Chapter 6 says "You can use the live image to try different desktop
environments such as GNOME, KDE, Xfce, or others" but does not explain HOW to
do that (or provide a contextual reference).
Version-Release number of selected component (if applicable):
Fedora 18
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1050197
Bug ID: 1050197
Summary: Deployment Guide misspells yum's --disableplugin
option
Product: Fedora Documentation
Version: devel
Component: deployment-guide
Assignee: jhradile(a)redhat.com
Reporter: scottt.tw(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dhensley(a)redhat.com, jhradile(a)redhat.com,
zach(a)oglesby.co
http://docs.fedoraproject.org/en-US/Fedora/15/html/Deployment_Guide/sec-Yum…
The "Enabling, Configuring and Disabling Yum Plugins" section of the Deployment
Guide incorrectly mentions a "--disableplugins" yum option. The correct option
name is "--disableplugin", i.e. without the extra "s" at the end.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982908
Bug ID: 982908
Summary: 7.3.4. Establishing a VPN 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:
Under section 7.3.4, in 'Procedure 7.5. Adding a New VPN Connection':
3. There is no VPN menu entry, There is also no interface option if you select
the plus sign, however if you click the plus sign and select VPN, and then set
the type of VPN, you can begin configuring the connection.
4. There is no create button
5. After clicking the plus button you are asked to choose the protocol type
6. The 'add network connection' dialogue comes up with the identity section
selected on the left side of the dialogue
1,2,3. The dialogue is different to what is shown in 'Figure 7.5. Editing the
newly-created VPN connection 1.' Also the menu items do not correspond with the
instructions in 1,2,3.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982819
Bug ID: 982819
Summary: 3.3.2. Installing chrony
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:
Section 3.3.2 states the default install location for 'chrony' (guessing
chronyc here) is listed as /usr/local/sbin, actual install location for chronyc
is /usr/bin
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982821
Bug ID: 982821
Summary: 3.4.1.1. Configuring chrony to Connect and Disconnect
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:
Location of chronyc is incorrect in the examples. Actual location is
/usr/bin/chronyc
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982818
Bug ID: 982818
Summary: 3.3.1. Checking if chrony is Installed
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:
Section 3.3.1 states the install location of chronyd is /usr/local/sbin. It is
actually installed at /usr/sbin/chronyd
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982485
Bug ID: 982485
Summary: 3.3.7 Manually Adjusting the System Clock
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:
Section 3.3.7 - Manualy adjusting system clock
1) Manually spelt wrong in title
2) when typing the commands listed, I get the following:
$ chrony
chrony version 1.28-pre1
Copyright (C) 1997-2003, 2007, 2009-2012 Richard P. Curnow and others
chrony comes with ABSOLUTELY NO WARRANTY. This is free software, and
you are welcome to redistribute it under certain conditions. See the
GNU General Public License version 2 for details.
chronyc> password
password: (tried root password)
501 Not authorised --- Reply not authenticated
chronyc> makestep
501 Not authorised
After consulting the help file (e.g. chronyc> help) it states:
password [<new-password>] : Set command authentication password
So it seems the password option sets the command auth password, but then it
should have set the password so this is confusing.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=977045
Bug ID: 977045
Summary: Guide should document chronyd, not ntpd
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
As of F16, Fedora uses `chrony` (chronyd.service) as the default time
daemon[1]. Chrony monitors and offsets local clock skew, making it superior
for machines without a constant connection to an ntp server. It also
effectively changes the system clock for even very large time changes, where
ntpd would require manual adjustment. The System administrator's guide should
be updated to reflect this.
The following sections, and references to them, should be updated:
2.2.3, “Configuring the Network Time Protocol”
D.1.14. /etc/sysconfig/ntpd
--Pete
[1]
https://git.fedorahosted.org/cgit/docs/release-notes.git/plain/en-US/System…
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008217
Bug ID: 1008217
Summary: Adding NetworkManager Connections via CLI
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
psimerda(a)redhat.com, sparks(a)redhat.com,
stickster(a)gmail.com, thaller(a)redhat.com,
zach(a)oglesby.co
Depends On: 998530
+++ This bug was initially created as a clone of Bug #998530 +++
This is a tracking bug for Change: Adding NetworkManager Connections via CLI
For more details, see:
http://fedoraproject.org//wiki/Changes/NetworkManagerCLIAddConnection
Support for adding new NetworkManager connections using the nmcli commandline
tool.
--- Additional comment from Thomas Haller on 2013-08-28 04:08:50 EDT ---
I did some minor rephrasing on the Changes page. It should be ok as it is now.
---------------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/186525.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001348
Bug ID: 1001348
Summary: NetworkManager Bonding Support
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dcbw(a)redhat.com, jreznik(a)redhat.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998567
+++ This bug was initially created as a clone of Bug #998567 +++
This is a tracking bug for Change: NetworkManager Bonding Support
For more details, see:
http://fedoraproject.org//wiki/Changes/NetworkManagerBonding
NetworkManager should be able to configure bond master interfaces with commonly
used options and recognize their existing configuration on startup without
disrupting their operation.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001214.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001354
Bug ID: 1001354
Summary: No Default Sendmail
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, mattdm(a)redhat.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998571
+++ This bug was initially created as a clone of Bug #998571 +++
This is a tracking bug for Change: No Default Sendmail
For more details, see: http://fedoraproject.org//wiki/Changes/NoDefaultSendmail
No longer install an MTA by default. (Specifically let's remove sendmail from
@core and @standard comps groups.)
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/186536.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001365
Bug ID: 1001365
Summary: Unversioned Docdirs
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, stickster(a)gmail.com,
ville.skytta(a)iki.fi, zach(a)oglesby.co
Depends On: 993551 (F20UnversionedDocDirs), 998579
+++ This bug was initially created as a clone of Bug #998579 +++
This is a tracking bug for Change: Unversioned Docdirs
For more details, see:
http://fedoraproject.org//wiki/Changes/UnversionedDocdirs
Install package specific documentation to an unversioned subdir in
/usr/share/doc.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001195.h…
and https://lists.fedoraproject.org/pipermail/devel/2013-July/186623.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008215
Bug ID: 1008215
Summary: KDE Plasma Workspaces 4.11
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dvratil(a)redhat.com, jgrulich(a)redhat.com,
jreznik(a)redhat.com, kevin.kofler(a)chello.at,
ltinkl(a)redhat.com, mbriza(a)redhat.com,
nobody(a)fedoraproject.org, rdieter(a)math.unl.edu,
sparks(a)redhat.com, stickster(a)gmail.com,
than(a)redhat.com, zach(a)oglesby.co
Depends On: 998528 (kde-4.11), 995167 (lokalize), 995226
(kde-dev-utils), 996067 (kcron), 996068 (ksystemlog),
996069 (kuser), 1005133
+++ This bug was initially created as a clone of Bug #998528 +++
This is a tracking bug for Change: KDE Plasma Workspaces 4.11
For more details, see: http://fedoraproject.org//wiki/Changes/KDE411
Rebase to version 4.11 of: the KDE Plasma Workspaces including the Plasma
Desktop and Netbook workspaces, the KDE Applications and the KDE Platform.
--- Additional comment from Lukáš Tinkl on 2013-08-26 08:54:02 EDT ---
KDE Plasma Workspaces 4.11 is in its final and fully testable state.
--- Additional comment from Jaroslav Reznik on 2013-08-27 11:11:30 EDT ---
KDE team agreed to move to MODIFIED.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001178.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008202
Bug ID: 1008202
Summary: Apache Hadoop 2.x
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, matt(a)redhat.com,
mattias.ellert(a)fysast.uu.se, nobody(a)fedoraproject.org,
sparks(a)redhat.com, stickster(a)gmail.com,
zach(a)oglesby.co
Depends On: 998521, 1003034, 1005724, 985087
+++ This bug was initially created as a clone of Bug #998521 +++
This is a tracking bug for Change: Apache Hadoop 2.x
For more details, see: http://fedoraproject.org//wiki/Changes/Hadoop
Provide native Apache Hadoop packages.
----------------------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/185026.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001336
Bug ID: 1001336
Summary: Application Installer
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
rhughes(a)redhat.com, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998562
+++ This bug was initially created as a clone of Bug #998562 +++
This is a tracking bug for Change: Application Installer
For more details, see: http://fedoraproject.org//wiki/Changes/AppInstaller
We will replace the existing gnome-packagekit frontends (gpk-update-viewer and
gpk-application) by a new application.
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/186166.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001368
Bug ID: 1001368
Summary: Visible Cloud
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, mattdm(a)redhat.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998582
+++ This bug was initially created as a clone of Bug #998582 +++
This is a tracking bug for Change: Visible Cloud
For more details, see: http://fedoraproject.org//wiki/Changes/VisibleCloud
With Fedora 19's First Class Cloud Images feature, we have Amazon EC2 and
downloadable cloud images (in qcow2 and raw.xz format) produced and released
together with the traditional desktop installer and and livecd images. Now,
let's go to the next level and present the cloud images as equal options.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001187.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008195
Bug ID: 1008195
Summary: Enlightenment
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, metherid(a)gmail.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 954132 (Enlightenment-Tracker), 998517
+++ This bug was initially created as a clone of Bug #998517 +++
This is a tracking bug for Change: Enlightenment
For more details, see: http://fedoraproject.org//wiki/Changes/Enlightenment
Enlightenment 0.17 a new stable release has been released after 12 years or so
of development. As many desktops are being landed on Fedora, Integrating
Enlightenment in Fedora can not only enlarge the number of available desktops
in Fedora, but also improve user experiences and give users another choice of
Desktop Environment.
---------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001210.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001362
Bug ID: 1001362
Summary: Ruby on Rails 4.0
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, jstribny(a)redhat.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, vondruch(a)redhat.com,
zach(a)oglesby.co
Depends On: 998578
+++ This bug was initially created as a clone of Bug #998578 +++
This is a tracking bug for Change: Ruby on Rails 4.0
For more details, see: http://fedoraproject.org//wiki/Changes/Ruby_on_Rails_4.0
Ruby on Rails 4.0 is the latest version of well know web framework written in
Ruby.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001189.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008185
Bug ID: 1008185
Summary: ACPICA Tools Update
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ahs3(a)redhat.com, jreznik(a)redhat.com,
okrh(a)johnfreed.com, relnotes(a)fedoraproject.org,
wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 998504
+++ This bug was initially created as a clone of Bug #998504 +++
This is a tracking bug for Change: ACPICA Tools Update
For more details, see: http://fedoraproject.org//wiki/Changes/AcpicaTools
For developers working with the ACPI subsystem, there are tools available from
the reference implementation at http://www.acpica.org. These tools have been
restructured over time and the current Fedora packages as a result contain
either outdated versions or do not make available a complete set of tools. We
propose an acpica-tools package that replaces both the existing iasl package
and the the existing pmtools package in order to make all current tools
available, and make it more straightforward in the future to keep them
up-to-date.
--- Additional comment from Al Stone on 2013-08-28 18:08:23 EDT ---
Package has been uploaded into git and builds done for all architectures for
f20.
--- Additional comment from John Freed on 2013-09-09 04:02:26 EDT ---
acpica-tools obsoletes pmtools, but it appears it should also obsolete iasl:
Transaction check error:
file /usr/bin/iasl from install of acpica-tools-20130823-2.fc19.x86_64
conflicts with file from package iasl-20120913-7.fc19.x86_64
file /usr/share/man/man1/iasl.1.gz from install of
acpica-tools-20130823-2.fc19.x86_64 conflicts with file from package
iasl-20120913-7.fc19.x86_64
Erasing iasl and installing acpica-tools works.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008186
Bug ID: 1008186
Summary: ACPICA Tools Update
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ahs3(a)redhat.com, jreznik(a)redhat.com,
nobody(a)fedoraproject.org, okrh(a)johnfreed.com,
sparks(a)redhat.com, stickster(a)gmail.com,
zach(a)oglesby.co
Depends On: 998504
Blocks: 1008185
+++ This bug was initially created as a clone of Bug #998504 +++
This is a tracking bug for Change: ACPICA Tools Update
For more details, see: http://fedoraproject.org//wiki/Changes/AcpicaTools
For developers working with the ACPI subsystem, there are tools available from
the reference implementation at http://www.acpica.org. These tools have been
restructured over time and the current Fedora packages as a result contain
either outdated versions or do not make available a complete set of tools. We
propose an acpica-tools package that replaces both the existing iasl package
and the the existing pmtools package in order to make all current tools
available, and make it more straightforward in the future to keep them
up-to-date.
--- Additional comment from Al Stone on 2013-08-28 18:08:23 EDT ---
Package has been uploaded into git and builds done for all architectures for
f20.
--- Additional comment from John Freed on 2013-09-09 04:02:26 EDT ---
acpica-tools obsoletes pmtools, but it appears it should also obsolete iasl:
Transaction check error:
file /usr/bin/iasl from install of acpica-tools-20130823-2.fc19.x86_64
conflicts with file from package iasl-20120913-7.fc19.x86_64
file /usr/share/man/man1/iasl.1.gz from install of
acpica-tools-20130823-2.fc19.x86_64 conflicts with file from package
iasl-20120913-7.fc19.x86_64
Erasing iasl and installing acpica-tools works.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001339
Bug ID: 1001339
Summary: Migrate to Bluez 5
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bnocera(a)redhat.com, jreznik(a)redhat.com,
kalevlember(a)gmail.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, stickster(a)gmail.com,
zach(a)oglesby.co
Depends On: 998563
+++ This bug was initially created as a clone of Bug #998563 +++
This is a tracking bug for Change: Migrate to Bluez 5
For more details, see: http://fedoraproject.org//wiki/Changes/Bluez5
BlueZ is the Linux Bluetooth stack for managing wireless Bluetooth devices. In
Fedora 20, we are going to switch from BlueZ version 4 to version 5.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-August/001227…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001377
Bug ID: 1001377
Summary: Perl 5.18
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jplesnik(a)redhat.com, jreznik(a)redhat.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998584
+++ This bug was initially created as a clone of Bug #998584 +++
This is a tracking bug for Change: Perl 5.18
For more details, see: http://fedoraproject.org//wiki/Changes/perl5.18
A new perl 5.18 version brings a lot of changes done over a year of
development. See 5.18.0 perldelta for more details.
--- Additional comment from Jitka Plesnikova on 2013-08-23 04:40:10 EDT ---
Perl has been updated and the most of packages was rebuilt.
All packages, which was not built, are listed on the feature page.
--- Additional comment from Jaroslav Reznik on 2013-08-26 10:25:18 EDT ---
(In reply to Jitka Plesnikova from comment #1)
> Perl has been updated and the most of packages was rebuilt.
> All packages, which was not built, are listed on the feature page.
Thank you, I'm changing bug state to MODIFIED now to reflect current Change
state.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-June/001158.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008231
Bug ID: 1008231
Summary: SSSD CIFS plugin
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jhrozek(a)redhat.com, jreznik(a)redhat.com,
nobody(a)fedoraproject.org, sbose(a)redhat.com,
sparks(a)redhat.com, stickster(a)gmail.com,
zach(a)oglesby.co
Depends On: 998544
+++ This bug was initially created as a clone of Bug #998544 +++
This is a tracking bug for Change: SSSD CIFS plugin
For more details, see: http://fedoraproject.org//wiki/Changes/SSSD_CIFS_plugin
During the F20 development cycle, the SSSD will provide an ID-mapping
plugin for cifs-utils so that Windows SIDs can be mapped onto POSIX IDs
and/or names without requiring Winbind and using the same code as the SSSD uses
for identity information.
--- Additional comment from Sumit Bose on 2013-08-28 11:40:40 EDT ---
The public interfaces for SID related queries are available and testable. The
plugin for the cifs-utils is planned for the next SSSD release which is aligned
with the Fedora 20 beta schedule.
----------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/185376.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008200
Bug ID: 1008200
Summary: GNOME 3.10
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, mclasen(a)redhat.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998518
+++ This bug was initially created as a clone of Bug #998518 +++
This is a tracking bug for Change: GNOME 3.10
For more details, see: http://fedoraproject.org//wiki/Changes/Gnome3.10
Update GNOME to the latest upstream release
--- Additional comment from Matthias Clasen on 2013-08-23 10:44:03 EDT ---
3.9.90 is in f20
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001192.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008219
Bug ID: 1008219
Summary: Plasma-nm
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jgrulich(a)redhat.com, jreznik(a)redhat.com,
ltinkl(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, stickster(a)gmail.com,
zach(a)oglesby.co
Depends On: 998531
+++ This bug was initially created as a clone of Bug #998531 +++
This is a tracking bug for Change: Plasma-nm
For more details, see: http://fedoraproject.org//wiki/Changes/Plasma-nm
Replace current network applet in KDE with a new one and bring the latest news
in NetworkManager to KDE.
--- Additional comment from Lukáš Tinkl on 2013-08-20 08:27:16 EDT ---
This change is currently fully working and in testable state, using:
$ yum install kde-plasma-nm
------------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/185649.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008193
Bug ID: 1008193
Summary: Developer Assistant GUI
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bkabrda(a)redhat.com, jreznik(a)redhat.com,
nobody(a)fedoraproject.org, phracek(a)redhat.com,
sparks(a)redhat.com, stickster(a)gmail.com,
zach(a)oglesby.co
Depends On: 998501
+++ This bug was initially created as a clone of Bug #998501 +++
This is a tracking bug for Change: Developer Assistant GUI
For more details, see:
http://fedoraproject.org//wiki/Changes/DeveloperAssistantGUI
The feature aims to provide GUI for devassistant package.
--- Additional comment from Petr Hracek on 2013-08-23 03:53:55 EDT ---
Main Developer Assistant GUI is finished and testable.
Problem with aborting project creation was already solved.
GUI for creation of user assistants depends on some devassistant-lint engine
which is not implemented yet (will be in future).
devassistant-lint program should check whether yaml assistant is correct and
runnable by devassistant engine.
Developer Assistant Creator GUI can be used only for beginners which do not
want to use any command line or IDE editor for YAML files.
Field "Fixed in Version" will be filled during next week when will be a new
release
--- Additional comment from Bohuslav "Slavek" Kabrda on 2013-08-28 07:57:30 EDT
---
Testable in devassistant-0.6.1-2.fc20 by invoking "da-gui".
---------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001190.h…
Please assess existing documentation for the impact of this change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001359
Bug ID: 1001359
Summary: python-setuptools update to 0.7.x and greater
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: a.badger(a)gmail.com, jreznik(a)redhat.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, toshio(a)fedoraproject.org,
zach(a)oglesby.co
Depends On: 998574
+++ This bug was initially created as a clone of Bug #998574 +++
This is a tracking bug for Change: python-setuptools update to 0.7.x and
greater
For more details, see:
http://fedoraproject.org//wiki/Changes/Python_setuptools_0.7
Update to a new upstream release of python-setuptools that is not completely
compatible with previous releases. The python-setuptools "major" version may
be higher than 0.7.x as there's some other structural changes happening that
should not affect API.
--- Additional comment from Toshio Ernie Kuratomi on 2013-08-26 12:51:51 EDT
---
Currently, no rawhide packages are known to be incompatible with the updated
setuptools. Moving to MODIFIED.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-June/001159.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1076963
Bug ID: 1076963
Summary: 9.14.5 Recommended Partition Scheme, outdated info
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: bugzilla(a)colorremedies.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Existing documentation with the problem is here:
http://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Guide/s2-di…
Here's a minimal list of problems and proposed changes for this page.
1. 9.14.5.1 recommends a layout the installer doesn't use by default. To fix
it:
a. Change "partitions" to "mount points", to be consistent with newui
terminology, and to apply to either partitions or LVs since the default is
swap, root, home on LV, and only boot is on a partition.
2. The first NOTE, under "A /boot/ partition (500 MB)":
Let's just remove this. We haven't dealt with cylinders on drives for over 5
years, but rather Logical Block Addresses. I'm not sure what problem this is
trying to solve, other than 2.2+TB drives in which case they need to be GPT and
hope the BIOS doesn't puke. If it does, a separate /boot isn't going to fix it.
Seems like very antiquated advice.
3. A root partition (3.0 GB - 5.0 GB)
Change to 3 GB to 20 GB to be consistent with the body text "full desktop
installation, a minimum of 20GB for the root partition is recommended". Please
also drop the insignificant digit
4. Side bar "Root and /root"
Both sentences are confusing, suggested rewrite:
The / mount point is the top of the Linux Filesystem Hierarchy, and is referred
to as the root file system, or root.The /root directory, sometimes pronounced
"slash-root", is the home directory for the root user.
*I consulted the v2.3 FHS to come up with this.
5. A home partition (at least 100 MB)
100MB is useless for gnome which is our default installation. Its indexer
consumes 3GB for just one person. So if present, it needs to be a lot bigger
than this or it should just be in /.
6. "To store user data separately from system data, create a dedicated
partition within a volume group for the /home directory. This will enable you
to upgrade or reinstall Fedora without erasing user data files."
This is really confusing because it conflates partitions and Logical Volumes in
one sentence. Rewrite as follows:
"To store user data separately from system data, create a mount point for
/home. This will enable you to reinstall Fedora without erasing user data."
7. "If you create many partitions instead of one large / partition, upgrades
become easier."
This should be removed as it's based on partitioning mythology/religion, not
fact. We even say separate /usr is proscribed. Fewer volumes to assemble is
less complex which is easier, but so long as we can upgrade what we permit
users to create, the "ease" of upgrading should be the same and if not then
it's a bug. I'd just strike this whole sentence.
8. 9.14.5.1.1 Advice on partitions.
"Each kernel installed on your system requires approximately 220 MB on the
/boot partition."
Untrue. On /boot, kernel 3.14 takes up 18.1MB total. That includes config*,
initramfs*, System.map*, and vmlinuz*. Debug kernel with a generic non-host
initramfs is 45MB. Even fully installed (to both /boot and /lib) is 141MB. This
should be changed to "approximately 25MB" which leaves a bit of headroom for
growing kernel sizes.
9. Find all instances of "partition" and make sure we mean partition (i.e.
related to an entry in the MBR or GPT) and not either "mount point" or
"volume". Partition is not a good generic term for applying to Logical Volumes
and Btrfs subvolumes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1029712
Bug ID: 1029712
Summary: Suggestions for documentation improvement.
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: low
Assignee: pbokoc(a)redhat.com
Reporter: r.landmann(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lsatenstein(a)yahoo.com, me(a)petetravis.com,
mmcallis(a)redhat.com, pbokoc(a)redhat.com,
r.landmann(a)redhat.com, zach(a)oglesby.co
Depends On: 994794
Thanks Leslie:
Cloning to separate the Document Conventions suggestions from the Install Guide
suggestions.
+++ This bug was initially created as a clone of Bug #994794 +++
Improvement recommendation for Install Guide.
http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/Insta…
Under
1.1. Typographic Conventions
The indented paragraph reads
To see the contents of the file my_next_bestselling_novel in your current
working directory, enter the cat my_next_bestselling_novel command at the shell
prompt and press Enter to execute the command.
I would replace the word "see" with view.
To view the contents of the...
See for me, would be the result of issuing the ls command. See the file, view
the contents.
As an aside, for French translation, "to see" translates to "regarder"
whereas view tranlates to "voir". A similar difference is with Spanish
Please correct for Fedora 20.
======
Further on the same page...
Warnings should not be ignored. Ignoring warnings will most likely cause data
loss.
My comment.
Warnings do not cause data loss. Warnings advise of a situation that if not
attended to, will most likely cause data loss.
=======
Follow page with Introduction
Introduction
This guide covers installation of Fedora, a Linux distribution built on free
and open source software.
Please change ... built on ... to built with.
My reasoning... You may be on topic, or build on a foundation, but Fedora is
built with free and open source software
=======
Another question. Would you say, "Install Fedora on a computer," or would you
say "Install Fedora onto a computer"?
My preference is to drop the "on a computer". That would shorten the sentence
and accommodate some future hardware device.
=======
2.1.1. How Do I Download Installation Files?
To follow a Web-based guide to downloading, visit
http://get.fedoraproject.org/. For guidance on which architecture to download,
refer to Section 2.1.2, “Which Architecture Is My Computer?”.
Would the meaning be more clear if the title started with the word "Of" as in
"Of which Architecture Is My Computer?"
(sections 2.1.2 and 2.1.3)
--- Additional comment from Pete Travis on 2013-08-08 20:59:31 EDT ---
The "Typographic Conventions" content is defined by publican, the publishing
tool used to create the guide.
--- Additional comment from Leslie Satenstein on 2013-08-15 15:36:18 EDT ---
In the installation guide, I noted that chapter two and following that
"the discussion is about downloading the various versions of Fedora
(netinstall, dvd, etc)."
Then aas a follow up, there is a long discussion about which version of Fedora
is the one to select from a list of options based on architecture and the like.
Should not the latter documentation section precede the downloading
information? As the comments in the guide were "for new users of Linux and
experienced ones", the guide may (in my opinion) be presenting information that
the individual should know about before downloading or acquiring any version.
Most users of technical manuals do a two pass read.
The first read is to get an appreciation of the product and guide, and the
second pass is to follow the recipe. By following the recipe, it should be
a) step one, determine your version and suitability of hardware
b) step two determine the version of Fedora you want to install (32bit/64bit)
etc.
c) Download/acquire
....
and so forth.
The guide is almost in the step by step recipe sequence,
If you go forward, would the improvements be present before Fedora 20,so the
new sequence could be ready for a reviewer and his comments? And if you keep
the sequence, I presume the update draft would also be ready for the reviewers
and their comments.
--- Additional comment from Leslie Satenstein on 2013-08-15 15:37:32 EDT ---
In the installation guide, I noted that chapter two and following that
"the discussion is about downloading the various versions of Fedora
(netinstall, dvd, etc)."
Then aas a follow up, there is a long discussion about which version of Fedora
is the one to select from a list of options based on architecture and the like.
Should not the latter documentation section precede the downloading
information? As the comments in the guide were "for new users of Linux and
experienced ones", the guide may (in my opinion) be presenting information that
the individual should know about before downloading or acquiring any version.
Most users of technical manuals do a two pass read.
The first read is to get an appreciation of the product and guide, and the
second pass is to follow the recipe. By following the recipe, it should be
a) step one, determine your version and suitability of hardware
b) step two determine the version of Fedora you want to install (32bit/64bit)
etc.
c) Download/acquire
....
and so forth.
The guide is almost in the step by step recipe sequence,
If you go forward, would the improvements be present before Fedora 20,so the
new sequence could be ready for a reviewer and his comments? And if you keep
the sequence, I presume the update draft would also be ready for the reviewers
and their comments.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=994794
[Bug 994794] Suggestions for documentation improvement.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1045205
Bug ID: 1045205
Summary: post-f19 askmethod behavior should be documented
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: medium
Assignee: pbokoc(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: awilliam(a)redhat.com, g.kaviyarasu(a)hotmail.com,
jonathan(a)jonmasters.org, kanarip(a)kanarip.com,
maurizio.antillon(a)gmail.com, pbokoc(a)redhat.com,
rtguille(a)gmail.com, sbueno(a)redhat.com, zach(a)oglesby.co
Depends On: 889887
+++ This bug was initially created as a clone of Bug #889887 +++
Description of problem:
If one boots the netinstall to install over nfs (or anything that is not
closest mirror) one needs to wait for closest mirror to be ready. In my case it
is about 20 minutes, but that will be different for other people.
The issue is that anaconda has already selected (correctly) closest mirror for
the netinstall iso, but it is cannot be interrupted. I wanted to install from
nfs source over wi-fi but i must wait my SLOW(TM) internet connection prior to
selecting nfs as an INSTALLATION SOURCE.
If anaconda has access to the internet, everything has to wait for closest
mirror to be ready.
Please, consider adding a small timeout that allows one to enter INSTALLATION
DESTINATION to override the closes mirror.
Version-Release number of selected component (if applicable):
F18-TC2
How reproducible:
always
Steps to Reproduce:
1. boot anaconda netinstall
2. wait for closest mirror to be ready
3. select your nfs installation source and install.
Actual results:
long wait for an installation source to be setup which will not be used.
Expected results:
some time to enter INSTALLATION SOURCE and be able to select nfs (or other)
without waiting for closest mirror.
Additional info:
--- Additional comment from Chris Lumens on 2013-01-22 15:30:11 EST ---
I do somewhat agree, given that we've got this shiny installation source UI
that we then don't really let you use. On the other hand, our threading/spoke
stuff doesn't really work in this direction. Threads can wait on other things
to be completed but there's not really any way to stop a thread when you enter
a spoke. So, I think implementation of this would be very difficult.
Would you settle for a check for the old "askmethod" command line parameter and
not immediately fire up the mirror checking stuff if that parameter exists?
--- Additional comment from Reartes Guillermo on 2013-01-23 16:46:11 EST ---
> Would you settle for a check for the old "askmethod" command line parameter
> and not immediately fire up the mirror checking stuff if that parameter exists?
I have no objection for such proposal.
The current workaround (Fedora Release NetInstall ISO) is:
1. Start Anaconda and reach the MAIN HUB
2. Enter NETWORK CONFGURATION and 'disable' the Network
3. Wait for INSTALLATION SOURCE to be back in 'Nothing Selected'
4. Enter NETWORK CONFGURATION and 'enable' the Network
5. Enter INSTALLATION SOURCE and now select NFS or other.
In my test (KVM Guest) it works, but i don't know if this workaround
do work with all network cards at them moment. (It should but there
could be bugs).
Since this workaround is somewhat simple, maybe it should be documented
as the default way of aborting the automatic selection of closest mirror
by Anaconda for NetInstall Images. In that case, nothing new is needed.
Cheers.
--- Additional comment from Adam Williamson on 2013-05-11 02:33:13 EDT ---
Tested with F19 Beta TC3. The askmethod behaviour described in c#1 has been
added. It works, though it's somewhat ugly: it leaves the Installation Source
spoke in an 'error' condition. But it works.
--- Additional comment from Adam Williamson on 2013-05-13 12:38:48 EDT ---
Note, Reartes took the testing further than me, and found that if you actually
try to complete an install with the new parameter, it fails:
https://bugzilla.redhat.com/show_bug.cgi?id=962098 .
--- Additional comment from Reartes Guillermo on 2013-06-01 17:05:55 EDT ---
There parameter 'askmethod', it is still not usable due to the issue in comment
#3.
Re-Tested with F19b RC4 (19.30-1)
--- Additional comment from Adam Williamson on 2013-06-02 13:54:58 EDT ---
How do you mean 'not usable'? It does what it's meant to do: lets you go into
the spoke immediately. I wouldn't call that 'not usable'.
========================================
Also refer to
https://fedoraproject.org/wiki/Anaconda_Boot_Options?rd=Anaconda/Options
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=889887
[Bug 889887] please add a small timeout in netinstall images for
INSTALLATION SOURCE that permits one to override the 'closest mirror'
selection (and the long wait it might imply)
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1065771
Bug ID: 1065771
Summary: Remove references to version numbers in package
documentation directories
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: swadeley(a)redhat.com
Reporter: sclark(a)fedoraproject.org
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Created attachment 863833
--> https://bugzilla.redhat.com/attachment.cgi?id=863833&action=edit
The attached archive contains patches to implement this change
Following instructions in
https://fedoraproject.org/wiki/Changes/UnversionedDocdirs remove the version
number from the directory name for all references to any package documentation
directory in /usr/share/doc , leaving just the package's name.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1079540
Bug ID: 1079540
Summary: Document SELinux sandboxing
Product: Fedora Documentation
Version: devel
Component: security-guide
Assignee: sparks(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pkennedy(a)redhat.com, security-guide-list(a)redhat.com,
sparks(a)redhat.com, zach(a)oglesby.co
What is SELinux sandboxing and why should I care? How do I do it?
These questions and more should be covered in the Security Guide
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008204
Bug ID: 1008204
Summary: DNSSEC support for FreeIPA
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
pspacek(a)redhat.com, sparks(a)redhat.com,
stickster(a)gmail.com, tbabej(a)redhat.com,
zach(a)oglesby.co
Depends On: 998522
+++ This bug was initially created as a clone of Bug #998522 +++
This is a tracking bug for Change: DNSSEC support for FreeIPA
For more details, see: http://fedoraproject.org//wiki/Changes/IPAv3DNSSEC
FreeIPA with integrated DNS server will support serving of DNSSEC secured
zones.
--- Additional comment from Tomas Babej on 2013-08-28 10:22:11 EDT ---
This feature is self-contained and not in a testable state yet. It is planned
for FreeIPA 3.4 Beta release which is aligned with the F20 schedule.
--- Additional comment from Petr Spacek on 2013-09-02 07:18:58 EDT ---
It is possible that we will not be able to complete the feature in time for
Fedora 20 beta.
From:
http://fedoraproject.org//wiki/Changes/IPAv3DNSSEC#Contingency_Plan
Contingency mechanism: Do not expose new feature in FreeIPA's user interface
(i.e. revert patches for user interface)
--- Additional comment from Jaroslav Reznik on 2013-09-04 08:28:20 EDT ---
Ok, in case you won't be able to finish it by Beta Change Deadline (currently
planned for 2013-10-08), let me know and put the bug to the NEW state, version
to rawhide.
Thanks for update!
-----------------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001193.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008203
Bug ID: 1008203
Summary: DNSSEC support for FreeIPA
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, pspacek(a)redhat.com,
relnotes(a)fedoraproject.org, tbabej(a)redhat.com,
wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 998522
+++ This bug was initially created as a clone of Bug #998522 +++
This is a tracking bug for Change: DNSSEC support for FreeIPA
For more details, see: http://fedoraproject.org//wiki/Changes/IPAv3DNSSEC
FreeIPA with integrated DNS server will support serving of DNSSEC secured
zones.
--- Additional comment from Tomas Babej on 2013-08-28 10:22:11 EDT ---
This feature is self-contained and not in a testable state yet. It is planned
for FreeIPA 3.4 Beta release which is aligned with the F20 schedule.
--- Additional comment from Petr Spacek on 2013-09-02 07:18:58 EDT ---
It is possible that we will not be able to complete the feature in time for
Fedora 20 beta.
From:
http://fedoraproject.org//wiki/Changes/IPAv3DNSSEC#Contingency_Plan
Contingency mechanism: Do not expose new feature in FreeIPA's user interface
(i.e. revert patches for user interface)
--- Additional comment from Jaroslav Reznik on 2013-09-04 08:28:20 EDT ---
Ok, in case you won't be able to finish it by Beta Change Deadline (currently
planned for 2013-10-08), let me know and put the bug to the NEW state, version
to rawhide.
Thanks for update!
-----------------------------------------------------------------
Discussion available at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001193.h…
Please document this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008575
Bug ID: 1008575
Summary: Install Guide Tweaking
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: low
Assignee: pbokoc(a)redhat.com
Reporter: lsatenstein(a)yahoo.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Please consider corrections for Fedora 20 install guide. The following is my
feedback for F19 Install guide.
Description of problem:
Improvement recommendation for Install Guide.
http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/Insta…
Under
1.1. Typographic Conventions
The indented paragraph reads
To see the contents of the file my_next_bestselling_novel in your current
working directory, enter the cat my_next_bestselling_novel command at the shell
prompt and press Enter to execute the command.
I would replace the word "see" with view.
To view the contents of the...
For me, "see" would be the result of issuing the ls command. See the file, view
the contents.
As an aside, for French translation, "to see" translates to "regarder"
whereas view translates to "voir". Il voit le contenu.
Please correct for Fedora 20.
======
Further on the same page...
Warnings should not be ignored. Ignoring warnings will most likely cause data
loss.
My comment.
Warnings do not cause data loss. Warnings advise of a situation that if not
attended to, will most likely cause data loss.
=======
Follow page with Introduction
Introduction
This guide covers installation of Fedora, a Linux distribution built on free
and open source software.
Please change ... built on ... to built with.
My reasoning... You may be on topic, or build on a foundation, but Fedora is
built with free and open source software
=======
Another question. Would you say, "Install Fedora on a computer," or would you
say "Install Fedora onto a computer"? If the latter is more correct, this
fragment is found within the Audience section.
=======
2.1.1. How Do I Download Installation Files?
To follow a Web-based guide to downloading, visit
http://get.fedoraproject.org/. For guidance on which architecture to download,
refer to Section 2.1.2, “Which Architecture Is My Computer?”.
Would the meaning be more clear if the title started with the word "Of" as in
"Of which Architecture Is My Computer?"
(sections 2.1.2 and 2.1.3)
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1069985
Bug ID: 1069985
Summary: Release notes should contain changes to kickstart
options
Product: Fedora Documentation
Version: devel
Component: release-notes
Assignee: relnotes(a)fedoraproject.org
Reporter: edgar.hoch(a)ims.uni-stuttgart.de
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Description of problem:
Release notes for Fedora 20 contains nothing about the changes to kickstart
options.
It would be helpful if changes to kickstart options will be noticed in future
release notes too. Now I know that I have to check the wiki diffs of the
Anaconda/Kickstart wiki page to see the changes, but other administrators may
check only the release notes.
An example is the "--addsupport=" option to the "lang" kickstart option which
was added to Fedora 20 (I assume... - I have no information about the time of
the change), together with "%packages ... -instLangs=..." still not
implemented.
Please see also at https://bugzilla.redhat.com/show_bug.cgi?id=1051816#c11
Version-Release number of selected component (if applicable):
Fedora 20 release notes.
How reproducible:
Always.
Another note:
This request is to improve the next release notes.
But I want to note that there should a place (web page, wiki page, etc.) too
where additional (late) informations can be added to release notes of already
released Fedora versions. Is such a place available?
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1060328
Bug ID: 1060328
Summary: Fedora 20 Release Notes imply that rsyslog is no
longer installed
Product: Fedora Documentation
Version: devel
Component: release-notes
Assignee: relnotes(a)fedoraproject.org
Reporter: toby(a)ovod-everett.org
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Description of problem:
The Fedora 20 Release Notes imply that rsyslog is no longer installed (section
2.8.1) during normal installs. It appears, according to
http://fedoraproject.org/wiki/Talk:Changes/NoDefaultSyslog, that it got moved
from @core to @standard. However, I suspect that a lot of users will do
installs that include @standard, and as a result they will get rsyslog
installed and perhaps be confused as to why they got it when the Release Notes
imply it is no longer included. I can confirm that the
repodata/ac802acf81ab55a0eca1fe5d1222bd15b8fab45d302dfdf4e626716d374b6a64-Fedora-20-comps.xml
file on the x86_64 install DVD contains rsyslog in the @standard package group.
Also, https://fedoraproject.org/wiki/Talk:Changes/NoDefaultSendmail implies
that sendmail got moved from @core to @standard, whereas it appears to me that
it actually got removed from both of them (at least I can't find it anywhere in
the comps.xml file).
Version-Release number of selected component (if applicable): Fedora 20 x86_64
DVD.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1063068
Bug ID: 1063068
Summary: Wrong distribution mentioned ;)
Product: Fedora Documentation
Version: devel
Component: virtualization-deployment-and-administrative-guide
Severity: medium
Assignee: lnovich(a)redhat.com
Reporter: hetz(a)hetz.biz
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: lnovich(a)redhat.com
Description of problem:
the page regarding the compatibility mentioning wrong Linux distributin
Here is the page: http://hetz.me/y30lk
As you can see, it mentions "Fedora 6". IMHO it should be Red Hat Enterprise
Linux 6 - as Fedora 6 is dead long time ago ;)
Also, Where can I see the latest version of the doc? or is it always the same
URL as right now?
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001374
Bug ID: 1001374
Summary: Web Assets
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org,
sparks(a)redhat.com, stickster(a)gmail.com,
tchollingsworth(a)gmail.com, zach(a)oglesby.co
Depends On: 997677 (F20WebAssets), 998583
+++ This bug was initially created as a clone of Bug #998583 +++
This is a tracking bug for Change: Web Assets
For more details, see: http://fedoraproject.org//wiki/Changes/Web_Assets
Traditionally, Fedora has been pushing bits from its various servers to
people's browsers in an ad-hoc fashion, and issues surrounding JavaScript have
been swept under the rug. This change proposal provides a simple framework for
shipping static web content and a way forward to treat JavaScript more closely
to other code in the distribution.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001197.h…
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001371
Bug ID: 1001371
Summary: Web Assets
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
tchollingsworth(a)gmail.com, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Depends On: 997677 (F20WebAssets), 998583
+++ This bug was initially created as a clone of Bug #998583 +++
This is a tracking bug for Change: Web Assets
For more details, see: http://fedoraproject.org//wiki/Changes/Web_Assets
Traditionally, Fedora has been pushing bits from its various servers to
people's browsers in an ad-hoc fashion, and issues surrounding JavaScript have
been swept under the rug. This change proposal provides a simple framework for
shipping static web content and a way forward to treat JavaScript more closely
to other code in the distribution.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001197.h…
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1008210
Bug ID: 1008210
Summary: Transitive Trusts with Active Directory support for
FreeIPA
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: abokovoy(a)redhat.com, jreznik(a)redhat.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998502
+++ This bug was initially created as a clone of Bug #998502 +++
This is a tracking bug for Change: Transitive Trusts with Active Directory
support for FreeIPA
For more details, see:
http://fedoraproject.org//wiki/Changes/IPAv3TransitiveTrusts
FreeIPA will support transitive trusts with Active Directory
--- Additional comment from Alexander Bokovoy on 2013-08-26 23:20:18 EDT ---
I'm on vacation and will only be able to work fully on the feature starting
September.
-----------------------------------------------
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/185634.html
Please assess existing documentation for the impact of this Change.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1015896
Bug ID: 1015896
Summary: Documentation error in FreeIPA guide "Setting up a
Kerberized NFS Server"
Product: Fedora Documentation
Version: devel
Component: freeipa-guide
Assignee: dlackey(a)redhat.com
Reporter: bschneiders(a)woti.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dlackey(a)redhat.com
Description of problem:
A command example is missing from the text of the guide. This example still
exists in the coresponding RHEL documentation.
Version-Release number of selected component (if applicable):
http://docs.fedoraproject.org/en-US/Fedora/18/html/FreeIPA_Guide/kerb-nfs.h…
Actual results:
If ipa-getkeytab command is run on the NFS server, then save the keys directly
to the host keytab. For example:
For a Fedora machine, that's all you need to do.
Expected results:
If ipa-getkeytab command is run on the NFS server, then save the keys directly
to the host keytab. For example:
[jsmith@server ~]$ ipa-getkeytab -s server.example.com -p
nfs/nfs-server.example.com -k /etc/krb5.keytab
For a Fedora machine, that's all you need to do.
Additional info:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux…
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1080575
Bug ID: 1080575
Summary: Forgetting: condition="fedora"
Product: Fedora Documentation
Version: devel
Component: freeipa-guide
Assignee: dlackey(a)redhat.com
Reporter: Geodebay(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: dlackey(a)redhat.com
Description of problem:
In automount.xml, line 467/468
<screen condition="redhat">[jsmith@server ~]$ ipa-getkeytab -k /etc/krb5.keytab
-p host/nfs-client-server.example.com(a)EXAMPLE.COM</screen>
the screen for "fedora" is forgotten.
When you "publican" on fedora the automount.po file, the example dont appear.
Version-Release number of selected component (if applicable):
present
How reproducible:
always
Steps to Reproduce:
1.
2.
3.
Actual results:
" Si la commande ipa-getkeytab est exécutée sur le client NFS, enregistrer
alors les clés directement dans le tableau de clés de l'hôte. Par exemple :
Pour une machine sous Fedora, c'est tout ce qu'il est nécessaire de faire."
Expected results:
" Si la commande ipa-getkeytab est exécutée sur le client NFS, enregistrer
alors les clés directement dans le tableau de clés de l'hôte. Par exemple :
[jsmith@server ~]$ ipa-getkeytab -k /etc/krb5.keytab -p
host/nfs-client-server.example.com(a)EXAMPLE.COM
Pour une machine sous Fedora, c'est tout ce qu'il est nécessaire de faire."
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001356
Bug ID: 1001356
Summary: No Default Syslog
Product: Fedora Documentation
Version: devel
Component: docs-requests
Keywords: Tracking
Assignee: nobody(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, mattdm(a)redhat.com,
nobody(a)fedoraproject.org, sparks(a)redhat.com,
stickster(a)gmail.com, zach(a)oglesby.co
Depends On: 998573
+++ This bug was initially created as a clone of Bug #998573 +++
This is a tracking bug for Change: No Default Syslog
For more details, see: http://fedoraproject.org//wiki/Changes/NoDefaultSyslog
No longer install a traditional syslog service by default. (Specifically,
remove rsyslog from the @core or @standard groups in comps.)
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/185329.html
Please assess existing documentation for the impact of this Change.
In particular, review for coverage of `journalctl` and journald features.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=986370
Bug ID: 986370
Summary: UEFI Secure Boot and Hibernate (Suspend to Disk)
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: justin.mitchell.bennett(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, pbokoc(a)redhat.com
Description of problem:
With OEMs shipping preloads of Windows 8 on new purchase computers, UEFI tends
to be enabled by default. Though Fedora can work with a secure boot UEFI bios,
certain features have been disable (See Fedora 18 UEFI Secure Boot Edition
18.4).
As hibernation (suspend to disk) functionality has been disabled on an UEFI
Secure Boot system, users need to be aware, prior to installation of Fedora (as
sole OS on the system), whether to enable or disable this functionality.
Those using Fedora on a laptop/netbook, shouldn't discover *after* completing
installation, that hibernation has been disabled. It becomes a huge pain, to
google how to disable the /boot/efi partition, and grub2, if even possible.
If not documented or referenced in the install-guide, CommonBugs should make
note of this issue.
Version-Release number of selected component (if applicable):
Fedora 18, Fedora 19
How reproducible:
Install Fedora on a system with a Secure Boot, UEFI, enabled bios.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1001049
Bug ID: 1001049
Summary: Reinstallation method is not explained
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: wifienclair(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
In paragraph 18.1 Determining Whether to Upgrade or Re-Install, it is written:
"This recommended reinstallation method helps to ensure the best system
stability possible."
But I didn't find a reinstallation method in the document.
I suggest to replace this sentence by something like:
"The reinstallation method is recommended to ensure the best system stability
possible."
and to add a paragraph or a chapter on how to reinstall.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1012697
Bug ID: 1012697
Summary: There are inconcistencies between Install Guide's 15.4
chapter (Kickstart options) and
http://fedoraproject.org/wiki/Anaconda/Kickstart
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: q2dg(a)yahoo.es
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
It seems Wiki is more updated, because at least in "upgrade" option shows a
note like this: "Note that from F18 onward, upgrades are no longer supported in
anaconda and should be done with FedUp, the Fedora update tool.", whereas in
Install Guide this note doesn't exist. And there are more differences between
these two places, so I'm confused about which of these is the right place to
have the right reference.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001367
Bug ID: 1001367
Summary: Visible Cloud
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, mattdm(a)redhat.com,
relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Depends On: 998582
+++ This bug was initially created as a clone of Bug #998582 +++
This is a tracking bug for Change: Visible Cloud
For more details, see: http://fedoraproject.org//wiki/Changes/VisibleCloud
With Fedora 19's First Class Cloud Images feature, we have Amazon EC2 and
downloadable cloud images (in qcow2 and raw.xz format) produced and released
together with the traditional desktop installer and and livecd images. Now,
let's go to the next level and present the cloud images as equal options.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001187.h…
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1021602
Bug ID: 1021602
Summary: Visible Cloud
Product: Fedora Documentation
Version: devel
Component: install-guide
Keywords: Tracking
Assignee: pbokoc(a)redhat.com
Reporter: pbokoc(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, mattdm(a)redhat.com,
pbokoc(a)redhat.com, zach(a)oglesby.co
Depends On: 998582
Blocks: 1001367, 1001368
+++ This bug was initially created as a clone of Bug #998582 +++
This is a tracking bug for Change: Visible Cloud
For more details, see: http://fedoraproject.org//wiki/Changes/VisibleCloud
With Fedora 19's First Class Cloud Images feature, we have Amazon EC2 and
downloadable cloud images (in qcow2 and raw.xz format) produced and released
together with the traditional desktop installer and and livecd images. Now,
let's go to the next level and present the cloud images as equal options.
--- Additional comment from Jaroslav Reznik on 2013-10-11 04:45:00 EDT ---
This message is a reminder that Fedora 20 Accepted Changes 100%
Completed Deadline is on 2013-10-15 [1].
All Accepted Changes has to be code complete and ready to be
validated in the Beta release (optionally by Fedora QA). Required
bug state at this point is ON_QA.
As for several System Wide Changes, Beta Change Deadline is a
point of contingency plan, all incomplete Changes will be
reported to FESCo for 2013-10-16 meeting. In case of any
questions, don't hesitate to ask Wrangler (jreznik).
[1] https://fedoraproject.org/wiki/Releases/20/Schedule
--- Additional comment from Matthew Miller on 2013-10-15 14:41:27 EDT ---
Here's the current status:
A) New web site design will put cloud on equal footing as described. Will
continue to work with web team on this.
B) Yes, we have basic cloud image release criteria.
C) The updated koji isn't in place for image generation with the new method, so
we will just use the old one. Not a problem but we may need to kludge things
differently in the kickstart file.
--- Additional comment from Jaroslav Reznik on 2013-10-16 06:58:37 EDT ---
Ok, thanks, setting the Change to ON_QA.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=998582
[Bug 998582] Visible Cloud
https://bugzilla.redhat.com/show_bug.cgi?id=1001367
[Bug 1001367] Visible Cloud
https://bugzilla.redhat.com/show_bug.cgi?id=1001368
[Bug 1001368] Visible Cloud
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001335
Bug ID: 1001335
Summary: Application Installer
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
rhughes(a)redhat.com, wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 998562
+++ This bug was initially created as a clone of Bug #998562 +++
This is a tracking bug for Change: Application Installer
For more details, see: http://fedoraproject.org//wiki/Changes/AppInstaller
We will replace the existing gnome-packagekit frontends (gpk-update-viewer and
gpk-application) by a new application.
Discussion at
https://lists.fedoraproject.org/pipermail/devel/2013-July/186166.html
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1021600
Bug ID: 1021600
Summary: Application Installer
Product: Fedora Documentation
Version: devel
Component: install-guide
Keywords: Tracking
Assignee: pbokoc(a)redhat.com
Reporter: pbokoc(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, mclasen(a)redhat.com,
pbokoc(a)redhat.com, rhughes(a)redhat.com, zach(a)oglesby.co
Depends On: 998562, 1002288
Blocks: 1001335, 1001336
+++ This bug was initially created as a clone of Bug #998562 +++
This is a tracking bug for Change: Application Installer
For more details, see: http://fedoraproject.org//wiki/Changes/AppInstaller
We will replace the existing gnome-packagekit frontends (gpk-update-viewer and
gpk-application) by a new application.
--- Additional comment from Jaroslav Reznik on 2013-08-27 11:26:43 EDT ---
Application Installer is tracked/still under discussion by FESCo.
--- Additional comment from Jaroslav Reznik on 2013-08-28 14:43:51 EDT ---
Current status from Change Page: The hawkey backend is available in PackageKit
git master. gnome-software is available in git.gnome.org. Neither is in f20
yet. We are aiming for a first gnome-software release by end of August, and
will package it asap, then.
--- Additional comment from Matthias Clasen on 2013-09-02 13:52:34 EDT ---
gnome-software has been built for f20 today
--- Additional comment from Jaroslav Reznik on 2013-10-11 04:46:26 EDT ---
This message is a reminder that Fedora 20 Accepted Changes 100%
Completed Deadline is on 2013-10-15 [1].
All Accepted Changes has to be code complete and ready to be
validated in the Beta release (optionally by Fedora QA). Required
bug state at this point is ON_QA.
As for several System Wide Changes, Beta Change Deadline is a
point of contingency plan, all incomplete Changes will be
reported to FESCo for 2013-10-16 meeting. In case of any
questions, don't hesitate to ask Wrangler (jreznik).
[1] https://fedoraproject.org/wiki/Releases/20/Schedule
--- Additional comment from Jaroslav Reznik on 2013-10-21 09:06:29 EDT ---
Change is completed, moving to ON_QA as agreed with the owner.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=998562
[Bug 998562] Application Installer
https://bugzilla.redhat.com/show_bug.cgi?id=1001335
[Bug 1001335] Application Installer
https://bugzilla.redhat.com/show_bug.cgi?id=1001336
[Bug 1001336] Application Installer
https://bugzilla.redhat.com/show_bug.cgi?id=1002288
[Bug 1002288] Review Request: gnome-software - A software center for GNOME
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1036625
Bug ID: 1036625
Summary: Link to docs.redhat.com should properly link to
access.redhat.com
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: low
Assignee: pbokoc(a)redhat.com
Reporter: rpjday(a)crashcourse.ca
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
In Section 3, Acknowledgements, link to "docs.redhat.com" (correctly) redirects
to access.redhat.com, but links should really link directly to the correct
page, I think. Not sure if this has already been logged, it's possible there
are other links with the same property.
rday
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1001364
Bug ID: 1001364
Summary: Unversioned Docdirs
Product: Fedora Documentation
Version: devel
Component: release-notes
Keywords: Tracking
Assignee: relnotes(a)fedoraproject.org
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: jreznik(a)redhat.com, relnotes(a)fedoraproject.org,
ville.skytta(a)iki.fi, wb8rcr(a)arrl.net, zach(a)oglesby.co
Depends On: 993551 (F20UnversionedDocDirs), 998579
+++ This bug was initially created as a clone of Bug #998579 +++
This is a tracking bug for Change: Unversioned Docdirs
For more details, see:
http://fedoraproject.org//wiki/Changes/UnversionedDocdirs
Install package specific documentation to an unversioned subdir in
/usr/share/doc.
Discussion at
https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001195.h…
and https://lists.fedoraproject.org/pipermail/devel/2013-July/186623.html
Please create entries for this Change in the Release Notes.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1021603
Bug ID: 1021603
Summary: Unversioned Docdirs
Product: Fedora Documentation
Version: devel
Component: install-guide
Keywords: Tracking
Assignee: pbokoc(a)redhat.com
Reporter: pbokoc(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: adam(a)spicenitz.org, jreznik(a)redhat.com,
pbokoc(a)redhat.com, ville.skytta(a)iki.fi,
zach(a)oglesby.co
Depends On: 993551 (F20UnversionedDocDirs), 998579
Blocks: 1001364, 1001365
+++ This bug was initially created as a clone of Bug #998579 +++
This is a tracking bug for Change: Unversioned Docdirs
For more details, see:
http://fedoraproject.org//wiki/Changes/UnversionedDocdirs
Install package specific documentation to an unversioned subdir in
/usr/share/doc.
--- Additional comment from Adam Goode on 2013-09-25 22:50:18 EDT ---
This should be fixed in rawhide.
--- Additional comment from Jaroslav Reznik on 2013-10-11 04:46:54 EDT ---
This message is a reminder that Fedora 20 Accepted Changes 100%
Completed Deadline is on 2013-10-15 [1].
All Accepted Changes has to be code complete and ready to be
validated in the Beta release (optionally by Fedora QA). Required
bug state at this point is ON_QA.
As for several System Wide Changes, Beta Change Deadline is a
point of contingency plan, all incomplete Changes will be
reported to FESCo for 2013-10-16 meeting. In case of any
questions, don't hesitate to ask Wrangler (jreznik).
[1] https://fedoraproject.org/wiki/Releases/20/Schedule
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=993551
[Bug 993551] F20 Unversioned doc dirs tracker bug
https://bugzilla.redhat.com/show_bug.cgi?id=998579
[Bug 998579] Unversioned Docdirs
https://bugzilla.redhat.com/show_bug.cgi?id=1001364
[Bug 1001364] Unversioned Docdirs
https://bugzilla.redhat.com/show_bug.cgi?id=1001365
[Bug 1001365] Unversioned Docdirs
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1021203
Bug ID: 1021203
Summary: PDF version of Installation Guide misformatted
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: ruslan.khafizov(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
PDF version of Installation Guide looks unusual.
Margins are huge and take 2/3 of page width.
Font is quite small and barely readable.
Version-Release number of selected component (if applicable):
19
How reproducible:
Download document from
http://docs.fedoraproject.org/en-US/Fedora/19/pdf/Installation_Guide/Fedora…
Steps to Reproduce:
1. Go to
http://docs.fedoraproject.org/en-US/Fedora/19/pdf/Installation_Guide/Fedora…
2. See.
Actual results:
pdf document which is hard to read
Expected results:
pdf document which can be read and printed.
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=991093
Bug ID: 991093
Summary: Innacurate information about deleting data in 12.
Storage and partitioning
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: pbokoc(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, pbokoc(a)redhat.com
Below is a copypaste of two e-mails from docs(a)lists.fedoraproject.org
explaining the issue.
================================================================================
Mail 1 from Adam Williamson:
Someone on the forums kindly pointed out an inaccuracy in the
Installation Guide:
https://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Quick_Star…
"All data will be erased during installation from the disks you select
at this stage. Do not select disks that contain data you want to
preserve."
This is not correct. It would be correct to say that no data can
*possibly* be deleted from any disks you *don't* select at this stage,
but it is not true that all data will be removed from disks you *do*
select. Suggesting that this is the case prevents people from following
lots of common install paths.
What actually happens to the data on the selected disks depends on the
user's choices at Installation Options and 'custom partitioning' or
Reclaim Space. If you go to custom partitioning, basically, you're in
complete control of what happens; you can do all sorts of stuff from
there, but no data/partitions will be lost unless you explicitly choose
for that to happen.
If the disk has sufficient unpartitioned space and you just pick the
easiest 'install into empty space' path, no existing data will be
disturbed, though any existing bootloader in the MBR will be overwritten
(this is normal and has always been the case).
If you go through Reclaim Space, you get the choice of what existing
partitions to delete or resize.
=====================================================================
Mail 2 from Chris Murphy:
Yeah, the user actually needs to go to some extreme lengths to erase all data
on the selected disk. In Custom, it's deleted one partition at a time, with an
optional shortcut that popsup offering to delete all related partitions (which
still may not be all data on disk). Further, a summary pops up and shows what
will be deleted in red text.
In Guided, user either must set each partition to be deleted, or click on the
disk (make model number) and set it to delete which then shows all partitions
being set to delete as well.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1036643
Bug ID: 1036643
Summary: Example 3.1 appears to mix references to 32- and
64-bit install DVD isos
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: low
Assignee: pbokoc(a)redhat.com
Reporter: rpjday(a)crashcourse.ca
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
In Example 3.1 in the current install guide, the mount command refers to a
64-bit version of the ISO, but the final call to "livecd-iso-to-disk" refers to
a 32-bit version of the ISO. Is this deliberate? It seems potentially
confusing.
rday
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982656
Bug ID: 982656
Summary: A couple of suggestions for 9.17. Installation
Complete
Product: Fedora Documentation
Version: devel
Component: install-guide
Keywords: Documentation
Severity: unspecified
Priority: unspecified
Assignee: pbokoc(a)redhat.com
Reporter: pkovar(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, pbokoc(a)redhat.com
Hey Petr,
Just a couple of suggestions for section 9.17. Installation Complete
"Now that you have configured the remaining settings, your Fedora installation
is now complete!" --> "Now that you have configured the remaining settings,
your Fedora installation is complete."
"9.17.1. Initial Setup in GNOME" --> GNOME Initial Setup
"haven't" --> "have not"
"The Initial Setup application is only available for GNOME."
This might need some rewording since we now have two initial setup apps in
Fedora (http://fedoraproject.org/wiki/Features/NewFirstboot,
https://fedoraproject.org/wiki/Features/InitialExperience) that do almost the
same thing, but target different DEs.
"create an user account" --> "create a user account"
"After you are finished configuring" --> "After you have finished configuring"
"On the first login, the Gnome Help application will automatically open"
The application is called Yelp, not Gnome Help. However, you probably just want
to mention that "GNOME Help will automatically open...".
"Figure 9.40. Language selection in Gnome Initial Setup" --> "Language
selection in GNOME Initial Setup"
--
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=904083
Bug ID: 904083
Summary: Storage Administration Guide is obsolete or not?
Product: Fedora Documentation
Version: devel
Component: storage-administration-guide
Severity: medium
Priority: unspecified
Reporter: q2dg(a)yahoo.es
I've seen in http://docs.fedoraproject.org that last version of "Storage
Administration Guide" is for Fedora 14. It's more than two years ago!!
I don't know if this fact is due to this guide doesn't need any update or if
it's due to a lack of love from editors.
I want to notify this in Bugzilla to remember this situation, but I'm not sure
it is really a bug...
Could you tell me the reason of this abandonment?
Thanks!!
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1010674
Bug ID: 1010674
Summary: kdeaccessibility
Product: Fedora Documentation
Version: devel
Component: accessibility-guide
Assignee: gerard(a)ryan.lt
Reporter: cickumqt(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: gerard(a)ryan.lt, sparks(a)redhat.com, zach(a)oglesby.co
Hi,
In transifex:
"In Fedora, <application>KMouseTool</application> is packaged in the
<package>kdeaccessibility</package> package. This package also contains
kmagnifier, kmouth, and ktts, all of which are discussed in other areas of this
guide. To install <package>kdeaccessibility</package> you can either select
<menuchoice><guilabel>System > Administration > Add/Remove
Software</guilabel></menuchoice> and then type in
<package>kdeaccessibility</package> in the screen that pops up, or in a
terminal window type su -c "yum install kdeaccessibility"."
I just searched and found kmousetool has been packaged as standalone package
from f20, should we revise the doc?
Thanks.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=995128
Bug ID: 995128
Summary: Add a UEFI not compatible arch (i686)
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: pbokoc(a)redhat.com
Reporter: kraymond(a)shaiton.org
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: oglesbyzm(a)gmail.com, pbokoc(a)redhat.com
Please add that the i686 releases are not UEFI compatible on the following
section:
http://docs.fedoraproject.org/en-US/Fedora/19/html/Installation_Guide/ch-ne…
This is the one we use to choose the arch, that's where it should fit, more
than in table 3.1 (Boot and installation media) or Chap 7 (Booting the
Installer).
Related to BZ#994854
Thanks,
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1050178
Bug ID: 1050178
Summary: Fedora - Documentation website - Updated Czech
translation
Product: Fedora Documentation
Version: devel
Component: publishing-requests
Assignee: docs-publishers-members(a)fedoraproject.org
Reporter: josef.hruska(a)upcmail.cz
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs-publishers-members(a)fedoraproject.org
Description of problem:
Please publish an updated Czech translation of the Fedora Documentation Website
(docsite-publican).
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Published version shows some typos and untranslated strings.
Expected results:
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1043292
Bug ID: 1043292
Summary: simple typos
Product: Fedora Documentation
Version: devel
Component: readme-burning-isos
Assignee: zach(a)oglesby.co
Reporter: josef.hruska(a)upcmail.cz
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: stickster(a)gmail.com, zach(a)oglesby.co
Description of problem:
Few typos found in some of the guide chapters/files:
Version-Release number of selected component (if applicable):
20
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
1. File: Making_USB_Media
Line 281 (last para): Use this method for the distribution image, the
minimal boot media image, or on systems with a UNIX operating system (including
Mac OX X).
Incorrect name of the Apple operating system.
2. File: Making_Minimal_Boot_Media
Line 27 (5th para, 3rd item/indent of the list Use minimal boot media): to
use a kickstart file during installation (refer to <xref
linkend="s2-kickstart2-boot-media"/>
The ending round bracket/parenthesis is missing.
3. File: Procedure_dd_Image_to_USB
Line 22 (3rd para, preceding the output of dmesg command): ...The output
will identify the <systemitem>device node</systemitem> of the drive, in this
case <literal>/dev/sdc</literal>:
The actual output however contains sdd (inconsistency).
Expected results:
1. Should be Mac OS X
2. The ending round bracket/parenthesis should be added
3. The device name should be changed to /dev/sdd
Additional info:
Just noticed, while doing the translation.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=982517
Bug ID: 982517
Summary: 4.4.1. Adding a New User
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 4.4.1 at item number 6 explaining the user creation process, it is
inferred that the contents of /etc/skel are as follows:
.
..
.bash_logout
.bash_profile
.bashrc
.gnome2
.mozilla
They are in fact:
.
..
.bash_logout
.bash_profile
.bashrc
.mozilla
.zshrc
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1023496
Bug ID: 1023496
Summary: 4.2.1.6.1. Host-to-Host Connection - no IPsec tab
found
Product: Fedora Documentation
Version: devel
Component: security-guide
Assignee: sparks(a)redhat.com
Reporter: bobgus(a)rcn.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pkennedy(a)redhat.com, security-guide-list(a)redhat.com,
sparks(a)redhat.com, zach(a)oglesby.co
Created attachment 816182
--> https://bugzilla.redhat.com/attachment.cgi?id=816182&action=edit
When I type system-config-network, this is what I see
Description of problem:
In section 4.2.1.6.1. Host-to-Host Connection
The first few steps don't seem to work:
1) In a command shell, type system-config-network to start the Network
Administration Tool.
2) On the IPsec tab, click New to start the IPsec configuration wizard.
I don't see any IPsec tab.
Version-Release number of selected component (if applicable):
[root@hoho6 user1]# uname -a
Linux hoho6.chidig.com 3.11.6-200.fc19.x86_64 #1 SMP Fri Oct 18 22:34:18 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
[root@hoho6 user1]#
I did a yum update a few minutes ago.
How reproducible:
every time
Steps to Reproduce:
1. open a terminal session, log in as root
2. type 'system-config-network'
3. look for IPsec tab.
Actual results:
Could not find IPsec tab
Expected results:
Found IPsec tab
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=891931
Bug ID: 891931
Summary: Chapter 3
Product: Fedora Documentation
Version: devel
Component: uefi-secure-boot-guide
Severity: unspecified
Priority: unspecified
Reporter: jwboyer(a)redhat.com
Description of problem:
I wrote this a couple of weeks ago:
http://jwboyer.livejournal.com/46149.html
It details building a custom kernel. Feel free to use anything you'd like from
there. However, it doesn't cover:
- generating your own key/certs
- signing shim or grub2 (trivially derived from the existing kernel example)
- third party module signing
Peter is working on a tool to make generating certs that UEFI likes easier for
people. I was waiting for that tool to be available before really covering
those aspects, as that is what we want users to use.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1071943
Bug ID: 1071943
Summary: Manual does not compile in f20
Product: Fedora Documentation
Version: devel
Component: defensive-coding-guide
Assignee: fweimer(a)redhat.com
Reporter: nmavrogi(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: fweimer(a)redhat.com, sparks(a)redhat.com
Description of problem: Does not compile
How reproducible:
In f20, after installing publican" and the "publican-fedora" packages, try
"make build-manual".
Output:
...
Can't open file 'tmp/en-US/xml_tmp/Web_Applications.xml'
not well-formed (invalid token) at line 46, column 43, byte 2693:
Won't be escaped (DON'T DO THIS!)
<h:outputText value="#{param.name}" escape=false>
==========================================^
</code>
at /usr/lib64/perl5/vendor_perl/XML/Parser.pm line 187.
at /usr/share/perl5/vendor_perl/Publican/Builder/DocBook4.pm line 484.
make: *** [build-manual] Error 255
using escape="false" instead fixes the issue, but different errors show up. I'm
not familiar with docbook to provide a fix.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1035500
Bug ID: 1035500
Summary: F19 security guide - iptables intallation command is
wrong
Product: Fedora Documentation
Version: devel
Component: security-guide
Assignee: sparks(a)redhat.com
Reporter: maxime.carron(a)fedoraproject.org
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pkennedy(a)redhat.com, security-guide-list(a)redhat.com,
sparks(a)redhat.com, zach(a)oglesby.co
Description of problem:
The command to install iptables-services is wrong in fedora 19 documentation
Version-Release number of selected component (if applicable):
Current version (fedora 19), security guide, chapter "3.8.9.1. Using the
iptables service"
link :
http://docs.fedoraproject.org/en-US/Fedora/19/html/Security_Guide/sec-Disab…
Actual results:
quote :
Then install the iptables-service package by entering the following command as
root:
~]# iptables-service
Expected results:
The command should be :
yum install iptables-services
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=995595
Bug ID: 995595
Summary: Allocators.xml
Product: Fedora Documentation
Version: devel
Component: defensive-coding-guide
Assignee: fweimer(a)redhat.com
Reporter: Geodebay(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: fweimer(a)redhat.com, sparks(a)redhat.com
Description of problem:
In Allocators.xml, line 135 to 138, you write:
" .... For instance,
to allocate an array of <literal>n</literal> elements of type
<literal>T</literal>, check that the requested size is not
greater than <literal>n / sizeof(T)</literal>."
It is not rather?
" .... For instance,
to allocate an array of <literal>n</literal> elements of type
<literal>T</literal>, check that the requested size is not
smaller than <literal>n * sizeof(T)</literal>."
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1030257
Bug ID: 1030257
Summary: Typo Fedora Amateur Radio Guide
Product: Fedora Documentation
Version: devel
Component: amateur-radio-guide
Assignee: wb8rcr(a)arrl.net
Reporter: ikhyar.com(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: sparks(a)redhat.com, wb8rcr(a)arrl.net, zach(a)oglesby.co
Description of problem:
in transifex contain space typos in words "e dge" to "edge"
Version-Release number of selected component (if applicable): transifex
How reproducible: -
Steps to Reproduce: -
1.
2.
3.
Actual results: e dge
Expected results: edge
Additional info:
Thanks for correcting these typos.
https://fedora.transifex.com/projects/p/fedora-amateur-radio-guide/
--
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=892673
Bug ID: 892673
Summary: UEFI Secure Boot Guide: suggestions for edits
Product: Fedora Documentation
Version: devel
Component: uefi-secure-boot-guide
Severity: unspecified
Priority: unspecified
Reporter: fweimer(a)redhat.com
Replace: "With the planned release of Windows 8, Microsoft has decided that all
hardware that is marked "Windows 8 client ready" should"
With: "Microsoft requires that client devices carrying the Windows 8 logo must"
Replace: "This means that Fedora as it stands booted on such hardware will
refuse to boot until the user disables secure boot in the firmware."
With: "The UEFI boot loader on Fedora installation media and on the installed
system are signed with the Microsoft key, to enable booting and installation on
such systems."
Remove the following paragraph, ending in "This plan has been approved by the
Fedora Engineering Steering Committee as of 23-Jul-2012."
After: "any operations from userland which cause userland-defined DMA"
Insert: "disable support for hibernate/suspend-to-disk, and other features
which would allow executing arbitrary code in kernel mode (even for the root
user)."
--
You are receiving this mail because:
You are the QA Contact for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: value of security measures; no metric, no scope description
https://bugzilla.redhat.com/show_bug.cgi?id=782916
Summary: value of security measures; no metric, no scope
description
Product: Fedora Documentation
Version: devel
Platform: Unspecified
OS/Version: All
Status: NEW
Severity: unspecified
Priority: unspecified
Component: security-guide
AssignedTo: eric(a)christensenplace.us
ReportedBy: budden(a)nps.navy.mil
QAContact: docs-qa(a)lists.fedoraproject.org
CC: pkennedy(a)redhat.com, eric(a)christensenplace.us,
security-guide-list(a)redhat.com, oglesbyzm(a)gmail.com
Classification: Fedora
Story Points: ---
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Description of problem:
The juncture between computer security and network security is inadequate --
too many seams which leaves too many man-in-middle attack opportunities.
The most egregious omission in this (otherwise pretty good) document is
treatment of SCOPE. This probably belongs in the vicinity of 1.3.
Analysis first. Map each of the security solutions you have in the guide onto
the ISO Reference Model:
Layer 1/2 security measures (like WiFi security) protect frames. The scope of
the security is limited to a single segment. No security beyond the router and
no security within end systems.
Layer 3 security protected datagrams (VPNs do this, IPSec ....). The scope is
an enclave tunneled through an internetwork. The protection cannot extend
beyond the VPN boxes, so data is wholly unprotected within end systems (and LAN
if the VPN box is associated with the last router).
Layer 4/5 security includes SSL (aka TLS). You have a how-to for securing an
http server (good) but no admonitions regarding scope -- the security extends
from the TCP socket in one end system to the TCP socket at the other end of the
connection -- again no security inside the OS comes from SSL.
All of the above security measures protect infrastructure. But they do not
protect the data.
Layer 6/7 security measures protect the data. Here the scope _can be_ truly
end to end. S/MIME is a good example (so is ssh and XML sign/crypt) where the
data passes over the internet and through the OS in protected form. Only in a
fairly small space is the data unprotected. In Evolution, for example, only
the parts of the UA that deal with composing, reading, ... mail are places
where the authenticity and confidentiality of the data is possible. Most of
the rest of the UA (including all the filing system deals with data that has
been protected exactly the way it's been sent over the network. In the case of
Evolution (UAs differ in implementation) secured data is stored in the file
system exactly the way it was transmitted.
Recommendations:
1) include a mapping similar to above so users have an idea what the scope of
this or that security measure is.
2) emphasize those security measures that apply to applications (layer 6/7) as
Fedora distribution evolves and matures. (What got me here this morning is the
continuing frustration getting Evolution to properly play ball with DoD CAC
cards ... works, but doesn't 'just work').
Version-Release number of selected component (if applicable):
Security Guide 16.3 (doesn't have a date)
How reproducible:
The above analysis doesn't invent anything; it only organizes and sorts.
Anyone can reproduce it.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1005452
Bug ID: 1005452
Summary: Outdated information
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Severity: medium
Assignee: bcotton+fedora(a)gmail.com
Reporter: cickumqt(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com,
zach(a)oglesby.co
Quoted from
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM…:
The RPM bindings for Python are documented along with the C programming API. On
a Red Hat Linux system, look in the file
/usr/share/doc/rpm-devel-4.1/apidocs/html/group__python.html to see the start
of the Python-specific documentation.
Note that much of this online documentation covers the C functions that provide
the Python bindings, not the Python API itself. But, if you examine the online
information on objects listed as classes, such as rpmts, you can find the
Python-specific documentation.
Furthermore, if you look into the .c files that make up the Python bindings,
you can find PyMethodDef structure tables. These tables provide useful glimpses
into the Python API.
To learn more about programming in Python, install the python-docs package. The
python-docs package has a large set of online documentation for Python,
including the official Python Tutorial. With Red Hat Linux, start at
/usr/share/doc/python-docs-2.2.1/html/tut/tut.html.
Cross Reference
Other tutorials are available at http://diveintopython.org for the Dive Into
Python tutorial for experienced programmers, and at
http://py.vaults.ca/parnassus/apyllo.py/935043691.636055170 for the Vaults of
Parnassus listing of tutorials.
I think we need to update some words like RPM4.1,
/usr/share/doc/python-docs-2.2.1 (F20 docdir changes) and Red Hat Linux ....
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1047428
Bug ID: 1047428
Summary: ABRT section has deprecated service commands
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Assignee: swadeley(a)redhat.com
Reporter: me(a)petetravis.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Created attachment 843622
--> https://bugzilla.redhat.com/attachment.cgi?id=843622&action=edit
This patch corrects the reported issue.
The ABRT section has commands that use the deprecated service and chkconfig
utilities instead of systemctl. The section should be updated to reflect the
migration to systemd.
I have attached a patch to correct this, please review and apply. Feedback
would be welcome.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1080005
Bug ID: 1080005
Summary: Revision history shows version 1.1-0 released in the
future
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Assignee: yruseva(a)redhat.com
Reporter: fedorabugs(a)aylett.co.uk
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, yruseva(a)redhat.com,
zach(a)oglesby.co
Description of problem:
https://docs.fedoraproject.org/en-US/Fedora/20/html/Power_Management_Guide/…
gives the release date of 1.1-0 as 17 December 2014, which is in the future.
Version-Release number of selected component (if applicable):
1.1-0
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=977063
Bug ID: 977063
Summary: New NetworkManager features should be documented
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
NetworkManager now offers hotspot functionality, allowing users to easily share
a non-wireless connection over a wireless interface.
As of F19, NetworkManager allows the creation and usage of both bridge and bond
virtual devices.
These features should be documented in the System Administrator's guide.
--Pete
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1071699
Bug ID: 1071699
Summary: partition type crossref to partition type strings
Product: Fedora Documentation
Version: devel
Component: system-administrator's-reference-guide
Severity: medium
Assignee: swadeley(a)redhat.com
Reporter: bugz.to.anomalyst(a)xoxy.net
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
External Bug ID: Red Hat Bugzilla 1066196
Description of problem:
need a man page to 'officially' document partition types and their text string
translations.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
May I suggest a centralized file /etc/fstype which would document the GPT
fstypes and maybe a brief overview their history (date created & date modified)
and official text translations.
Its very difficult find this information with a search engine
the closest thing I have found is "sgdisk --list-types"
see also <https://bugzilla.redhat.com/show_bug.cgi?id=1066194>
--
You are receiving this mail because:
You are the QA Contact for the bug.