https://bugzilla.redhat.com/show_bug.cgi?id=1350454
Bug ID: 1350454
Summary: Error on Shasum Check for Mac OS
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: low
Assignee: cspicer(a)redhat.com
Reporter: wk4(a)tuta.io
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
External Bug ID: Red Hat Bugzilla 1282228
Description of problem:
Version-Release number of selected component (if applicable):
24
How reproducible:
100%
Steps to Reproduce:
1. open terminal
2. $ cd ~/Downloads/
3. shasum -a 256 -c *CHECKSUM
Actual results:
shasum: Fedora-Workstation-24-x86_64-CHECKSUM: no properly formatted SHA1
checksum lines found
Expected results:
shasum: Fedora-Workstation-netinst-x86_64-24-1.2.iso:
Fedora-Workstation-netinst-x86_64-24-1.2.iso: FAILED open or read
Fedora-Workstation-Live-x86_64-24-1.2.iso: OK
shasum: WARNING: 1 listed file could not be read
Additional info:
Tested on Mac OS X 10.11.5 (15F34)
Submitting a separate report as the bug (1282228) mentions both Mac OS and
Ubuntu. I do not have a fix for Ubuntu, only Mac OS.
How to fix:
I recommend replacing the step 3 in the guide with "$ grep '^SHA256' *-CHECKSUM
| awk -F '[()=]' '{ print $4 " " $2 }' | shasum -a 256 -c".
Credit (Fredy):
https://web.archive.org/web/20160627132229/https://ask.fedoraproject.org/en…
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1318103
Bug ID: 1318103
Summary: LiveUSB Creator as primary downloadable
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: cspicer(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
Description of problem:
Currently LiveUSB Creator is not mentioned at all in official documentation for
any platform.
https://docs.fedoraproject.org/en-US/Fedora/23/html/Installation_Guide/sect…
First, the two Windows platform recommendations in the documentation are odd
because they're neither created nor tested within Fedora.
Second, Live USB Creator is planned to be the primary/most prominent download
method for Fedora 24 for Fedora (maybe other Linux distros as well), Windows,
and possibly OS X if it arrives in time. So documentation should be updated to
reflect this.
Change description:
https://fedoraproject.org/wiki/Releases/24/ChangeSet#LiveUSBCreator_as_Prim…
Bug tracking:
https://bugzilla.redhat.com/show_bug.cgi?id=1310542
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1312621
Bug ID: 1312621
Summary: dhcpd instructions are unclear for PXE boot
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: cspicer(a)redhat.com
Reporter: danofsatx(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Section 10.2 of the Installation Guide gives the example setup for dhcpd to
enable a PXE boot / network installation. The example is unclear between
paragraphs 2 and 4 in that the text in paragraph 4 does not match up with the
text in paragraph 2, and there are no clear instructions as to where it goes in
the example file.
After trial and error and comparing with the F20 instructions, I was able to
get dhcpd started again. I suggest modifying paragraph 4 to include the whole
file as such:
option arch code 93 = unsigned integer 16;
subnet 192.168.1.0 netmask 255.255.255.0 {
option domain-name-servers 192.168.1.1;
option routers 192.168.1.1;
range 192.168.1.11 192.168.1.50;
authoritative;
default-lease-time 600;
max-lease-time 7200;
ddns-update-style none;
if option arch = 00:07 {
filename "uefi/shim.efi";
} else {
filename "pxelinux.0";
}
next-server 192.168.1.2;
}
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1309111
Bug ID: 1309111
Summary: Package environment ID required in kickstart
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: cspicer(a)redhat.com
Reporter: dgallowa(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
Documentation states a package environment's name can be specified in a
kickstart when the ID is required instead.
https://docs.fedoraproject.org/en-US/Fedora/22/html/Installation_Guide/sect…
@^Infrastructure Server <- does not work
@^infrastructure-server-environment <- works
Version-Release number of selected component (if applicable):
Fedora 22
How reproducible:
Every time
Steps to Reproduce:
1. Create kickstart specifying @^Infrastructure Server in %packages
2. Start install
Actual results:
You have specified that the group 'Infrastructure Server' should be installed.
This group does not exist. Would you like to ignore this group and continue
with installation?
Please respond 'yes' or 'no':
Expected results:
Group/Environment get installed
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1162045
Bug ID: 1162045
Summary: Power Mgmt Guide needs to Address Howto Suppress Sleep
State
Product: Fedora Documentation
Version: devel
Component: power-management-guide
Severity: low
Assignee: yruseva(a)redhat.com
Reporter: redzilla.coralnut(a)xoxy.net
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: ddomingo(a)redhat.com, yruseva(a)redhat.com,
zach(a)oglesby.co
Description of problem:
F20 Power Management Guide does not address the hooks into the sleep system
provided by systemd. Ever since p,m-utils was deprecated there have been no
Fedora/RHAT resources available that discuss how to utilize the hooks into the
sleep system to prevent entry into the sleep state.
Example: in the era of pm-utils (going back to what, F15?) one could write
scripts to suppress the transition to S3 if a desirable network connection were
established that should not be interrupted. All that was required was to place
the script in /etc/pm/sleep.d/ and have it issue a non-zero exit code if sleep
should be suppressed. When the goto sleep process prepared for sleep by
executing the script, the script could deliver a non-zero exit code and prevent
entry into the sleep state.
Now that pm-utils has been deprecated and replaced with systemd, Fedora now
ignores any/all scripts in /etc/pm/*. That isn't a problem. What *IS* a
problem, though, is that for the past 5 releases of Fedora, the Power
Management Guide has completely ignored the topic of how to use custom scripts
to prevent entry into the sleep state. As a result, our only options are to
look for help and examples in other distributions.
Version-Release number of selected component (if applicable):
F20, F21
How reproducible:
N/A. The documentation doesn't address the problem.
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=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=1253462
Bug ID: 1253462
Summary: Error in
http://docs.fedoraproject.org/en-US/Fedora_Draft_Docum
entation/0.1/html/RPM_Guide/ch16s03s05.html
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Severity: low
Assignee: bcotton+fedora(a)gmail.com
Reporter: nbasanes(a)cisco.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com,
zach(a)oglesby.co
Created attachment 1062752
--> https://bugzilla.redhat.com/attachment.cgi?id=1062752&action=edit
This attachment is a screenshot of a more readable result.
Description of problem:
The Python code section at
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM…
has an error in the following code:
# Dependencies
print "Provides:"
print h.dsFromHeader('providename')
print "Requires:"
print h.dsFromHeader('requirename')
if h.dsFromHeader('obsoletename'):
print "Obsoletes:"
print h.dsFromHeader('obsoletename')
if h.dsFromHeader('conflictname'):
print "Conflicts:"
print h.dsFromHeader('conflictname')
print h.dsFromHeader('conflictname') outputs <rpm.ds object at 0xb77584b8>.
h.dsFromHeader('conflictname'), without the "print" word, outputs it right.
Version-Release number of selected component (if applicable):
0.1
How reproducible:
Steps to Reproduce:
1. Copy the python code from the page to a file called rpminfo.py on a computer
that has the older version of Python, Python 2.
2. Run the Python code, by running the "cd" command until you get to the folder
that contains rpminfo.py.
3. Run rpminfo.py by entering the command python rpminfo.py.
Actual results:
Provides:
<rpm.ds object at 0xb77584b8>
Requires:
<rpm.ds object at 0xb77584b8>
Expected results:
Provides:
P config(httpd) = 2.2.15-39.el6.centos
Requires:
R libapr-1.so.0
Additional info:
The members of the object returned by dsFromHeader have integer indexes, since
the following code produces a more readable result:
# Dependencies
print "Provides:"
print h.dsFromHeader('providename')[0]
print "Requires:"
print h.dsFromHeader('requirename')[0]
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1163568
Bug ID: 1163568
Summary: POSIX capabilities "%caps" macro not mentioned
anyhwere
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Severity: medium
Assignee: bcotton+fedora(a)gmail.com
Reporter: matt(a)nightrealms.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com,
zach(a)oglesby.co
The RPM guide doesn't mention the "%caps" macro which can be used to set a
file's POSIX capabilities (see http://linux.die.net/man/7/capabilities) It
should go in chapter 9, section 5.4, at URL
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=1115469
Bug ID: 1115469
Summary: Link to full documentation is incorrect
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Assignee: bcotton+fedora(a)gmail.com
Reporter: msuchy(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:
This page:
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM…
links to
/usr/share/doc/rpm-devel-4.1/apidocs/html/group__python.html
Which does not exist on recent Fedoras.
RPM API is documented at:
/usr/share/doc/rpm-apidocs/index.html
And I did not find documentation for rpm-python itself.
--
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=1365347
Bug ID: 1365347
Summary: Please Publish edits made to virt-getting-started and
Release notes
Product: Fedora Documentation
Version: devel
Component: publishing-requests
Assignee: docs-publishers-members(a)fedoraproject.org
Reporter: grundblom(a)fedoraproject.org
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: docs-publishers-members(a)fedoraproject.org
Hello,
I have made corrections to the release notes, and I would like to request to
have them published to the website (docs.fedoraproject.org)
Also, I would like to request that the Virtualization Getting Started Guide
become available on the website (docs.fedoraproject.org)
The Virtualization Getting Started Guide has been migrated to:
https://pagure.io/virt-getting-started-guide
Let me know if you need more information or I have missed a step in this
process to get these published.
Thank you very much!
-Glen
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1276867
Bug ID: 1276867
Summary: Packaging:SourceURL#Git Tags is erroneous for GitHub
repository
Product: Fedora Documentation
Version: devel
Component: packager-guide
Severity: high
Assignee: pkovar(a)redhat.com
Reporter: francis.andre.kampbell(a)orange.fr
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pkovar(a)redhat.com
Hi
The documentation about specifying SourceURL at
https://fedoraproject.org/wiki/Packaging:SourceURL, chapter Git Tags is
erroneous
setup should be
%prep
%setup -qn %{name}-%{gittag0} [GitHub]
instead of
%prep
%setup -qn %{name}-%{version} [GitHub]
--
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.