Your message dated Tue, 26 Mar 2024 18:49:39 +0000 with message-id <e1rpbrf-002e2o...@fasolo.debian.org> and subject line Bug#1065356: fixed in cron 3.0pl1-189 has caused the Debian Bug report #1065356, regarding Issues in man pages of cron to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1065356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: cron Version: 3.0pl1-186 Severity: minor Tags: patch X-Debbugs-CC: mario.blaetterm...@gmail.com Dear Debian cron maintainer, the manpage-l10n project maintains a large number of translations of man pages both from a large variety of sources (including cron) as well for a large variety of target languages. During their work translators notice different possible issues in the original (english) man pages. Sometimes this is a straightforward typo, sometimes a hard to read sentence, sometimes this is a convention not held up and sometimes we simply do not understand the original. We use several distributions as sources and update regularly (at least every 2 month). This means we are fairly recent (some distributions like archlinux also update frequently) but might miss the latest upstream version once in a while, so the error might be already fixed. We apologize and ask you to close the issue immediately if this should be the case, but given the huge volume of projects and the very limited number of volunteers we are not able to double check each and every issue. Secondly we translators see the manpages in the neutral po format, i.e. converted and harmonized, but not the original source (be it man, groff, xml or other). So we cannot provide a true patch (where possible), but only an approximation which you need to convert into your source format. Finally the issues I'm reporting have accumulated over time and are not always discovered by me, so sometimes my description of the problem my be a bit limited - do not hesitate to ask so we can clarify them. I'm now reporting the errors for your project. If future reports should use another channel, please let me know. (Btw., do you have a working e-mail address of upstream?) Man page: cron.8 Issue: B<-L loglevel> → B<-L> I<loglevel> "B<-L loglevel>" -- Man page: crontab.1 Issue 1: I<-h> → B<-h> Issue 2: I<crontab> → B<crontab> "If the I<-h> option is given, I<crontab> shows a help message and quits " "immediately." -- Man page: crontab.1 Issue 1: I<-h> → B<-h> Issue 2: I<crontab> → B<crontab> "If the I<-n> option is given, it means \"dry run\": I<crontab> examines " "\"your\" crontab for its syntax, and outputs a success message if this " "syntax is correct, but nothing is written to any crontab." -- Man page: crontab.1 Issue: if, they exist, → , if they exist, "The files I</etc/cron.allow> and I</etc/cron.deny> if, they exist, must be " "either world-readable, or readable by group ``crontab''. If they are not, " "then cron will deny access to all users until the permissions are fixed." -- Man page: crontab.1 Issue: crontab(5), cron(8), spc(1) → B<crontab>(5), B<cron>(8), B<spc>(1) "crontab(5), cron(8), spc(1)" -- Man page: crontab.5 Issue: I<su> → B<su> "A I<crontab> file contains instructions to the I<cron>(8) daemon of the " "general form: ``run this command at this time on this date''. Each user has " "their own crontab, and commands in any given crontab will be executed as the " "user who owns the crontab. Uucp and News will usually have their own " "crontabs, eliminating the need for explicitly running I<su>(1) as part of a " "cron command." -- Man page: crontab.5 Issue: LOGNAME → I<LOGNAME> "Several environment variables are set up automatically by the I<cron>(8) " "daemon. SHELL is set to /usr/bin/sh, and LOGNAME and HOME are set from the /" "etc/passwd line of the crontab's owner. HOME and SHELL may be overridden by " "settings in the crontab; LOGNAME may not." -- Man page: crontab.5 Issue: I<ncal> or I<calendar> For → B<ncal>(1) or B<calendar>(1). For "If the program itself cannot do the checks then a wrapper script would be " "required. Useful tools that could be used for date analysis are I<ncal> or " "I<calendar> For example, to run a program the last Saturday of every month " "you could use the following wrapper code:" -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Source: cron Source-Version: 3.0pl1-189 Done: Georges Khaznadar <georg...@debian.org> We believe that the bug you reported is fixed in the latest version of cron, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1065...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar <georg...@debian.org> (supplier of updated cron package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Tue, 26 Mar 2024 19:08:34 +0100 Source: cron Architecture: source Version: 3.0pl1-189 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar <georg...@debian.org> Changed-By: Georges Khaznadar <georg...@debian.org> Closes: 1065356 Changes: cron (3.0pl1-189) unstable; urgency=medium . * rewritten the man pages in docbook XML format, so their typography and layout can be mastered at a higher level: hacking groff sources can be prone to error (Closes: #1065356) Checksums-Sha1: 348132cd112bb1392fe81155a5747fe80b855849 2083 cron_3.0pl1-189.dsc 72d1a20a6afe91c4e4f0e193e18d82b785b5661f 136948 cron_3.0pl1-189.debian.tar.xz a51f5228f37d309befd167f8b818dd0af4eac21e 7268 cron_3.0pl1-189_amd64.buildinfo Checksums-Sha256: a4761d768a30352308916f6084576a95d2294c8a759bb168d52442128c205e72 2083 cron_3.0pl1-189.dsc 8f9caee1c25c5e941a9bd37c66f225618d56e9957885d7b7ce24b6497ee0d3e7 136948 cron_3.0pl1-189.debian.tar.xz 372e6c69368100756866531fab8cb707c50185bccf24c52b753ee0c55c5e25ee 7268 cron_3.0pl1-189_amd64.buildinfo Files: df040f5b98b037057d93b1a3afaa1eac 2083 admin important cron_3.0pl1-189.dsc aaaf57eb1d3966497e4b8cc7f16d17f8 136948 admin important cron_3.0pl1-189.debian.tar.xz 53a0a60f78a28e218664be8cca8bfd09 7268 admin important cron_3.0pl1-189_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmYDEBMACgkQHCgWkHE2 rjnlgA/+N+9m0dGCaO70DSSbSz3u1l8a9Fl5LHk0rKDCeHU5RKJGG5NdDWecDAMD 6eN9wFPswE9jZwgtj9jsRjOUu0iR+2wxYEIqzD47QQ0qhhmIqCeP1CPtDc+h/B8j LYyxgpXruhEJ04geo7XHBMHa4dmmaEXRGkAO6OJxhF9fvsNNqtNtFu3JL7/7iS1I bospZu5ry+QuO85NvFBpvnEHjXGIRJdDALLJ3bP3EplUzBSiGCxBHDd3pnaayYnS QaKXY3FXI53ZW+XgbS6LKR7GOof+gD86iiiyd7be7UI11E6kgS+08UOhXBto8TPl Mfo22jScr33lc0orwKuQFppPYVXW/gEJgC31qOmS2bLlevsJGEFnuAibfgNU9T+H A1j6JgPRyPR+UGlP3BIaevFXWUrjsmlE4QF+nVRlib4lMRYwB+mIGCc8beg54U8z VjHFsngW4jE5uiFnHHuq/3QZ5dotrqu7NHAF5jNtgYo1uIUrHt3DtCGG5MdtgcNw tanNXtSDWxtuldBCRUU1/mi8OibanqaUfMXT1VEO0x9OUbCkAn29ezKMbr1YkwWY IRtTL+/v5n4K9a7Bb5BiOZwcYuzRBKoOCnXai6xS5B7i8CxCEboxtwbGgeGwQoM1 Qy6GOHVDamTbX2UvBX+RkMFZeDSB2iVAK5L3YtRp1j8stB7MRas= =isq9 -----END PGP SIGNATURE-----
Description: PGP signature
--- End Message ---
