New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Man page scan results for rear #1892
Comments
@gdha We do not have any 'cron' file in the ReaR upstream source files. In particular my SUSE and openSUSE rear* RPM packages |
@jsmeix in our upstrean (#1892 (comment)) we do have a cron entry enabled. Which leads to the following question: do we still want this in upcoming releases? I know from end-users it generates ISO images without rear being properly configured, and therefore, it would perhaps be better we disable the cron entry altogether in rear. If we describe it in our documentation should be sufficient, no? |
What is the RHEL policy? Do they shop a cron job? If not then I would also move it to the docs or examples area so that the users have a more consistent RPM installation experience. This is especially important if users upgrade a distro RPM with our upstream RPM. In that scenario the perceived behavior should not change. |
@rmetrich What are your thoughts on this topic? |
@gdha The latter is already there in
I think we must not install such a 'cron' file into I think our current documentation is sufficient I think the current example RPM spec file Alternatively we may have several example RPM spec files |
This automatic cron is broken and leads to having broken ReaR ISOs at the end, in my opinion, we should remove this file and provide a systemd service + timer instead, which wouldn't be enabled by default. Example:
|
@rmetrich What I know what cannot work reliably is calling |
The cron entry doesn't catch errors and the admin will not notice that, unless he configures automatic email for example. |
@gdha Cf. What I did there to remove /etc/cron.d/rear/ related things is
|
@gdha Sure, drop ISO :) |
Removed the /etc/cron.d/rear/ related things in packaging/rpm/rear.spec see #1892
I removed the /etc/cron.d/rear/ related things via I noticed in packaging/rpm/rear.spec there is still
Does that also belong to the /etc/cron.d/rear/ related things |
@jsmeix Yes |
Removed "Requires: crontabs" in packaging/rpm/rear.spec see #1892
Removed "Requires: crontabs" via |
Now the one error part of this issue
is fixed. The remaining error part
is not yet fixed. I think we do not need and should not have a "man local.conf" man page I think we should close this issue as "fixed as far as reasonable". |
systemd related changes in the spec file differs from:
guess we better post-pone this to release 2.6? |
I created the new issue #2139
in ReaR 2.6 so that this issue which is actually about |
ReaR version ("/usr/sbin/rear -V"): any
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"): n/a
Description of the issue (ideally so that others can reproduce it):
https://bugzilla.redhat.com/show_bug.cgi?id=1612248
In order to improve usability of packages in Fedora, project Man Page Scan was created and its task is to provide consistency of man pages (and documentation in general). The results are now available for package maintainers to fix documentation issues.
If you need to re-run the check yourself, here is the simple process of man page check:
Download man-page-day from:
https://pagure.io/ManualPageScan/blob/master/f/man-page-day.sh
Run the script:
The text was updated successfully, but these errors were encountered: