https://bugzilla.redhat.com/show_bug.cgi?id=1662306
Bug ID: 1662306
Summary: TigerVNC Configuration Page out of date
Product: Fedora Documentation
Version: devel
Hardware: x86_64
OS: Linux
Status: NEW
Component: system-administrator's-guide
Severity: medium
Assignee: pbokoc(a)redhat.com
Reporter: colin.henry(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Documentation does not reflect current file configuration
Version-Release number of selected component (if applicable):
Fedora 29
How reproducible:
Try and follow the instructions on the configuration page, it tells you to
change settings that aren't there. For instance, users are told to edit the
and change:
ExecStart=/sbin/runuser -l USER -c "/usr/bin/vncserver %i -geometry 1280x1024"
PIDFile=/home/USER/.vnc/%H%i.pid
Whereas the actual file contains:
ExecStart=/usr/bin/vncserver -autokill %i
PIDFile=/home/<USER>/.vnc/%H%i.pid
Steps to Reproduce:
1. Go to the documentation page:
https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide…
2. Install tigervnc-server
3. Look at the configuration file /lib/systemd/system/vncserver@.service
Actual results:
The files differ significantly, also following the instructions in the
configuration file fails to start vnc successfully, but I'll file a bug for
that separately.
Expected results:
Configuration documentation should match the files on the host
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1574954
--- Comment #1 from customercare(a)resellerdesktop.de ---
* bumb * Still no PDF download available.
--
You are receiving this mail because:
You are the QA Contact for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1657968
Bug ID: 1657968
Summary: systemd-rpm-macros doesn't exist
Product: Fedora Documentation
Version: devel
Status: NEW
Component: packager-guide
Assignee: pbokoc(a)redhat.com
Reporter: t0dd(a)protonmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pkovar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#_scri…
In this section you use the results of `rpm --eval %systemd_requires` and claim
it to be something that begins with `BuildRequires: systemd-rpm-macros`
I am an intermediate package builder and this section is confusing to me.
This is what I get on Fedora 28...
```
$ rpm --eval %{systemd_requires}
Requires(post): systemd
Requires(preun): systemd
Requires(postun): systemd
```
This section needs to be (a) updated, and (b) written a bit clearer. I think.
Anyway... it left me chasing my tail when I included that BuildRequires in my
specfile.
--
You are receiving this mail because:
You are the QA Contact for the bug.
The following is a list of bugs or attachments to bugs in which a user has been
waiting more than 7 days for a response from you. Please take
action on these requests as quickly as possible. (Note that some of these bugs
might already be closed, but a user is still waiting for your response.)
We'll remind you again in another 7 days if these requests are still
outstanding, or if there are any new requests where users have been waiting
more than 7 days for your response.
review
------
Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (1525 days old)
https://bugzilla.redhat.com/show_bug.cgi?id=1124344https://bugzilla.redhat.com/attachment.cgi?id=942713&action=edit
To see all your outstanding requests, visit:
https://bugzilla.redhat.com/request.cgi?action=queue&requestee=docs-qa%40li…