docs-qa April 2014

docs-qa@lists.fedoraproject.org

1 participants
150 discussions

[Bug 1001371] New: Web Assets
by Red Hat Bugzilla 21 Oct '14

21 Oct '14

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.

1 4

[Bug 1088758] New: NetworkManager should be off when used with FreeIPA
by Red Hat Bugzilla 15 Oct '14

15 Oct '14

https://bugzilla.redhat.com/show_bug.cgi?id=1088758 Bug ID: 1088758 Summary: NetworkManager should be off when used with FreeIPA Product: Fedora Documentation Version: devel Component: freeipa-guide Assignee: dlackey(a)redhat.com Reporter: artur.szymczak(a)nadzieja.pl QA Contact: docs-qa(a)lists.fedoraproject.org CC: dlackey(a)redhat.com Description of problem: WHen you read FreeIPA Fedora Guide: https://docs.fedoraproject.org/en-US/Fedora/18/html/FreeIPA_Guide/installin… it says: [quote] The default networking service used by Fedora is NetworkManager, and due to the way this service works, it can cause problems with FreeIPA and the KDC. Consequently, it is highly recommended that you use the network service to manage the networking requirements in a FreeIPA environment and disable the NetworkManager service. [/quote] It is highly recommended to use NetworkManager instead of network service, because of systemd, and all related to it stuff. So I think it should be fied in doc, or in FreeIPA itself. Btw, it should be writed, why we should disable NetworkManager (some more details) if it is still accurate. 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.

1 2

[Bug 1008210] New: Transitive Trusts with Active Directory support for FreeIPA
by Red Hat Bugzilla 15 Oct '14

15 Oct '14

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.

1 4

[Bug 1015896] New: Documentation error in FreeIPA guide "Setting up a Kerberized NFS Server"
by Red Hat Bugzilla 15 Oct '14

15 Oct '14

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.

1 5

[Bug 1080575] New: Forgetting: condition="fedora"
by Red Hat Bugzilla 15 Oct '14

15 Oct '14

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.

1 2

[Bug 1001356] New: No Default Syslog
by Red Hat Bugzilla 15 Oct '14

15 Oct '14

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.

1 3

[Bug 986370] New: UEFI Secure Boot and Hibernate (Suspend to Disk)
by Red Hat Bugzilla 07 Oct '14

07 Oct '14

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.

1 4

[Bug 1089733] New: --useexisting not described for btrfs --subvol
by Red Hat Bugzilla 01 Sep '14

01 Sep '14

https://bugzilla.redhat.com/show_bug.cgi?id=1089733 Bug ID: 1089733 Summary: --useexisting not described for btrfs --subvol Product: Fedora Documentation Version: devel Component: install-guide Severity: high Assignee: pbokoc(a)redhat.com Reporter: gene(a)czarc.net QA Contact: docs-qa(a)lists.fedoraproject.org CC: pbokoc(a)redhat.com, zach(a)oglesby.co Description of problem: In order to reuse an existing subvol (but not the rootfs), --useexisting must be specified on the btrfs subvol command. This is not specified in the documentation. Version-Release number of selected component (if applicable): 20+ -- You are receiving this mail because: You are the QA Contact for the bug.

1 2

[Bug 1001049] New: Reinstallation method is not explained
by Red Hat Bugzilla 01 Sep '14

01 Sep '14

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.

1 1

[Bug 1012697] New: There are inconcistencies between Install Guide's 15.4 chapter (Kickstart options) and http://fedoraproject.org/wiki/Anaconda/Kickstart
by Red Hat Bugzilla 01 Sep '14

01 Sep '14

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.

1 1

← Newer
1
...
9
10
11
12
13
14
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

docs-qa April 2014