cron-4.2-6.12.2 4>$  Ap]!^p9|Kإ=wunZ3-=#J"|#kY k.l)7b{zYP a[Hfه)tfg`2>!az&WuXE򀃦L~l|QN|Wfd7aq^kx0hrynkXg̣G~ֺ?ھ[ p,Ԋ1S"Ǡ!DÝ]'S U6c964c158cc24f7b89842a5288f98f7310d63919412116df835a7eec0c5e573e3b9f0e9df696f95398daff3b9c56d244eb934dac؉]!^p9|9F)nc #0ҕ0 >dq[îJs eAl8[x %^YL4"*r! &) o26RAn6w M>d>p=?d   $tx /5;     ",HPd|(8 9x:#=<FDGXH`IhXlYt\]^bcde flu$v,zATX^Ccron4.26.12.2Auxiliary packageAuxiliary package, needed for proper update from vixie-cron 4.1 to cronie 1.4.4]"s390zp35SUSE Linux Enterprise 15SUSE LLC BSD-3-Clause and GPL-2.0 and MIThttps://www.suse.com/System/Daemonshttps://github.com/cronie-crond/cronielinuxs390x# Check if we are doing update from 4.1 vixie-cron. # The -h does report garbage on vixie cron. check_cron_mail_feature=`/usr/sbin/cron -h 2>&1 | /usr/bin/grep mail` if [ -e /usr/sbin/cron -a -z "${check_cron_mail_feature}" ]; then touch /var/run/update_from_old_cron for conf in /etc/pam.d/crond /etc/crontab /etc/cron.deny ; do cp "$conf" "$conf.rpmbk" done fi exit 0A큤]"]"c1426b3d7880dc50fcbcb2e0e7db375d4814c3eb3e9a8ed79b3d58efff2518edrootrootrootrootcronie-1.5.1-6.12.2.src.rpmcroncron(s390-64)    /bin/shcronierpmlib(CompressedFileNames)rpmlib(FileDigests)rpmlib(PayloadFilesHavePrefix)rpmlib(PayloadIsXz)1.5.1-6.12.23.0.4-14.6.0-14.0-15.2-14.14.1]*]d@\P\\6ZZ@Z Z@Y@XP@XӸWSWRU@U@U@UJ@UU@Up=T_W@kstreitova@suse.comkstreitova@suse.comkstreitova@suse.comkstreitova@suse.comkstreitova@suse.comrbrown@suse.comjsegitz@suse.comkstreitova@suse.comrbrown@suse.comkukuk@suse.dekstreitova@suse.comkstreitova@suse.comkstreitova@suse.comtchvatal@suse.comcrrodriguez@opensuse.orgcrrodriguez@opensuse.orgjmatejek@suse.comtchvatal@suse.comtchvatal@suse.comkstreitova@suse.comcrrodriguez@opensuse.orgledest@gmail.com- drop 'checkproc' line from the run-crons as the usage is bogus [bsc#1155929]- update cronie-nheader_lines.diff so it doesn't print the first 3 crontab lines (static comments) with the 'crontab -l' command [bsc#1155114]- remove cronie-nofork-nopid.patch that allowed running of multiple "cron -n" instances at once which is an unwanted behaviour [bsc#1133100]- update cronie-1.5.1-huge_crontab_DoS.patch to fix a regression that caused that only the first job from a crontab was being run [bsc#1130746]- add cronie-1.5.1-huge_crontab_DoS.patch to fix two security issues where users can cause DoS of the crond by loading huge crontab files. We now allow maximum 1000 environment variables and 1000 crontab entries. Also the comments and whitespace between the entries and variables are now limited to 32768 characters. [bnc#1128937] [CVE-2019-9704] and [bnc#1128935] [CVE-2019-9705]- Requires mail as it's really needed by cron-crons script, not smtp_daemon [bsc#1070565] [bsc#1064834]- Ensure that /etc/cron.{hourly,daily,weekly,monthly} have proper permissions and owner. This is racy but prevents some LPE vectors- Requires smtp_daemon (not just Recommends) as it's needed by run-crons script [bsc#1064834]- Replace references to /var/adm/fillup-templates with new %_fillupdir macro (boo#1069468)- Require group trusted if we use them- update to 1.5.1 * crontab: Use temporary file name that is ignored by crond. * crond: Inherit PATH from the crond environment if -P option is used. * crond: Remove hardcoded "system_u" SELinux user, use the SELinux user of the running crond. * anacron: Small cleanups and fixes. * crond: Fix longstanding race condition on repeated crontab modification. - refresh cronie-pam_config.diff - get rid of %{name} macros in the patch names - use %{ext_man} macro for anacron man pages - fedorahosted.org was retired on March 1st, 2017 * update Url and Source address- cleanup with spec-cleaner- remove the omc xml config that is useless nowdays- Add fix for bnc#983925 to run crons even when not on AC_POWER * Nowdays it does not make much sense to not run crons when on battery and actually it can even confuse people- cron.service: Use KillMode=process like upstream does.- revert last change, it is a bug in sssd.service, fixed in SR#313709- add support for MAILFROM, MAIL_CONFIG and different mailer binaries in run-crons (bnc#812367, bnc#366762)- Start cron after sssd.service bnc#926961- Redo the post/pre update approach to fix migration from SLE11. Should fix bnc#919028- update to 1.5.0 * crond: Job environment variables are set also when executing sendmail. * crond: Adding duplicate orphans on reload is now prevented. * crond: The regular crond shutdown is now logged. * crontab: PAM is not called in crontab command if the caller's uid is 0. * crond: PAM is not called from crond for system cron jobs (/etc/crontab, /etc/cron.d) which are run for uid 0. * crond: The existence of an user is checked at time when job is run and not when the crontab is parsed on database reload. - use spec-cleaner- cron.service: Start After=nss-user-lookup.target not after ypbind.service nscd.service -cron.service: Crons run at wall-time, order after time-sync.target- fix bashisms in pre scripts/bin/shs390zp35 15747077204.2-6.12.24.2-6.12.2croncron_to_cronie.README/usr/share/doc/packages//usr/share/doc/packages/cron/-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -gobs://build.suse.de/SUSE:Maintenance:13192/SUSE_SLE-15_Update/1e887df5ee46259ec01157dd0a93423e-cronie.SUSE_SLE-15_Updatecpioxz5s390x-suse-linuxdirectoryASCII textlT4b4utf-8e66f98d0d0661355b658a90004e774b4d8cd38cf9a051a91ae97eb7431f48327?07zXZ !t/c] crt:bLL -su8=ř}ػw]Z$/~HQHW8 dVqÙOQɭ_9VFG,G`j hrC3::֮R{ _o$ #51Imi}YqhA:}h'\y*ܫiolVq= &Zfb\ Nզʹ*ߥ} 3:1A]  YZ