https://bugs.contribs.org/show_bug.cgi?id=10862
--- Comment #9 from Chris Sansom-Ninnes <[email protected]> ---
Just installed smeserver-letsencrypt-0.5-13.noarch, did a post-upgrade and
reboot and, weirdly, I've still got the original letsencrypt file in my
cron.daily and template-begin in
/etc/e-smith/templates/etc/cron.daily/letsencrypt/
Here's the detail:
= ENVIRONMENT:
Tested on SME 9.2, up to date, with Fail2Ban contrib and
dehydrated-0.6.5-1.el6.noarch installed from smetest
= TESTING:
[root@irene ~]# rpm -qa smeserver-letsencrypt
smeserver-letsencrypt-0.5-12.noarch
[root@irene ~]# yum update smeserver-letsencrypt --enablerepo=smetest
...
[root@irene ~]# signal-event post-upgrade && signal-event reboot
...
[root@irene ~] rpm -qa smeserver-letsencrypt
smeserver-letsencrypt-0.5-13.noarch
[root@irene ~]# ls /etc/cron.daily
0logwatch conf-mod_ssl logrotate prelink SyncMacbook
BackupHome freshclam makewhatis.cron sa_update tmpwatch
cleanup_fail2ban letsencrypt mlocate.cron smeserver-yum
tmpwatch-formmagick
[root@irene ~]# cat /etc/cron.daily/letsencrypt
#!/bin/sh
/usr/bin/dehydrated -c 2>&1 | logger -t dehydrated
[root@irene ~]# ls /etc/e-smith/templates/etc/cron.daily/letsencrypt/
template-begin
[root@irene ~]# cat
/etc/e-smith/templates/etc/cron.daily/letsencrypt/template-begin
= CONCLUSION:
No change going from 0.5-12 to 0.5-13.
--
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
