Your message dated Sun, 03 Sep 2023 11:19:05 +0000 with message-id <[email protected]> and subject line Bug#166533: fixed in cron 3.0pl1-175 has caused the Debian Bug report #166533, regarding cron: support different timezone in crontabs 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 [email protected] immediately.) -- 166533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=166533 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: cron Version: 3.0pl1-72 Severity: wishlist It should be possible to use different timezones in the crontab, allowing crontab times to be interpreted based on a timezone other than the system's default timezone. UTC is probably the most commonly desired timezone other than the local one, but cron might as well support every timezone if this feature is added. This feature is useful (required if you want to avoid nasty kludges) if you are trying to trigger an event based on an agreed-upon international time involving other timezones that do not treat daylight savings time the same as your timezone. For example, an open source project I am involved with agrees to do our distributed nightly run beginning just after 09:00 UTC. That's 02:00 PDT right now, but 02:00 PDT won't be 09:00 UTC next week. Possible ways to specify this: method 1: ------- start of cut text -------------- SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin TZ=UTC * * * * * root /usr/local/bin/some-cron-job ------- end ---------------------------- pros: obvious, easy, and simple cons: could conflict with current usage where TZ is set, but not used by cron method 2: ------- start of cut text -------------- SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin CRON_TZ=UTC * * * * * root /usr/local/bin/some-cron-job ------- end ---------------------------- pros: much safer than method 1 cons: not quite as obvious as method 1 I considered some sort of per-line format, but that would not be as compatible if used accidentally on an older cron version, and seems unnecessarily complicated to me. -- System Information Debian Release: 3.0 Kernel Version: Linux proton 2.4.19-ac4 #3 Sun Sep 15 01:57:14 PDT 2002 i686 unknown Versions of the packages cron depends on: ii debianutils 1.16 Miscellaneous utilities specific to Debian. ii libc6 2.2.5-11.2 GNU C Library: Shared libraries and Timezone ii libpam0g 0.72-35 Pluggable Authentication Modules library
--- End Message ---
--- Begin Message ---Source: cron Source-Version: 3.0pl1-175 Done: Georges Khaznadar <[email protected]> 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 [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar <[email protected]> (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 [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sun, 03 Sep 2023 12:30:35 +0200 Source: cron Architecture: source Version: 3.0pl1-175 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña <[email protected]> Changed-By: Georges Khaznadar <[email protected]> Closes: 166533 915289 1050702 Changes: cron (3.0pl1-175) unstable; urgency=medium . * removed the line SHELL=/usr/bin/sh from an example in crontab.5; this, Closes: #166533 * according to Message-ID: <[email protected]> sent to [email protected], this bug should be closed now ?? Closes: #915289 anyway. * uncommented EXTRA_OPTS="" in debian/cron.default; Closes: #1050702 Checksums-Sha1: 1aa3fd887e5b8cd147be96e54e9d4d95a249edde 2150 cron_3.0pl1-175.dsc 9b5cca204916c8bd0648a368da3163125747b3bb 118312 cron_3.0pl1-175.debian.tar.xz 0ae50570654e667e5e823a3a15c8dd108772d78d 7008 cron_3.0pl1-175_amd64.buildinfo Checksums-Sha256: 47d5c35e4cb7f7b3b148cb94d4dc0c48c17eebe78f6a9d081f6d716433ebcbc3 2150 cron_3.0pl1-175.dsc 49dc97179257d2a559f5bb4470d69417da141adf73eddd2ab9df9810faa4ac9f 118312 cron_3.0pl1-175.debian.tar.xz d55b62d182b23b1fcf3ea699e4f60127e881f53c411cbc24f8ddebb345770a5e 7008 cron_3.0pl1-175_amd64.buildinfo Files: f31a4249abcf181fc3e7f0788a86161b 2150 admin important cron_3.0pl1-175.dsc a6f5efd502faf7c354ef7a959e29cf31 118312 admin important cron_3.0pl1-175.debian.tar.xz 259153eddc9da67b7887c67ee0f99643 7008 admin important cron_3.0pl1-175_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmT0ZAsUHGdlb3JnZXNr QGRlYmlhbi5vcmcACgkQHCgWkHE2rjnjRA/7BI3JZhYQjTExgCSQgQw7qSCN6976 qFLF0iSLSAzNsydRjrvHuZZ4Swagwg5Mi3wQOtw6lwa0GjXLgqqsKAqPZpORb0UR +aPbeila0RPW4w4nPsdtwOsm4DFMbjMjlO5z9CMrqCTSooaPWyTlCy1vA2+dChCG 8Rpv6zf3RqpCie+2NhxIlJ2DJ9qaqcaEoSnhsvBOw1icPKHJs7vS8WuFkkGTf6LP Z4hA3uwkSes4O194Prtquf/91Uop7btEHB3r7LVaKoiwbjHaqUR3KRFL875zthSw PiCJeSDHeuSB9Ighfadc44IYCbfKSOxp0vXTa02o7yvIiOcySibE6KFN3ZlullY+ 10BC8zhfHCf/CRup8VIAnm9eBmacAb+M5VOhcMqcUq4BOlaQArryjEBNEX3/Cn8R kQBposCqfct6BCu5BKPY45jww+aHq3G8J+387p5wLSXY/Msk9ds0aD6JtZPVj+aA Z/JhJ2wc1WsQ4aEbP8WLOB6uaVDNcuufePt3dZCgWBC4IkA32/4LO5oRQkMo1pOk 4xO6zMZFA7aYoqAoozNoEDCgyjINnkWkuh/+/AwHWDkH5R1SIWnzl7A7gvEbxuEU lJA2DHEH542g1VEhKUQhUauJ7RSz2oUUdhiFcN+TDnnClc444GrfnT4M3vnayJgd gou9G12TeFLthzU= =Zy/H -----END PGP SIGNATURE-----
--- End Message ---
