Bug 12039 - openvpn-crl-updater is in Core update 128 missing
Summary: openvpn-crl-updater is in Core update 128 missing
Status: CLOSED NOTABUG
Alias: None
Product: IPFire
Classification: Unclassified
Component: openvpn (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - Major Usability
Assignee: Assigned to nobody - feel free to grab it and work on it
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-05 13:22 UTC by Erik Kapfer
Modified: 2019-04-20 17:37 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Kapfer 2019-04-05 13:22:10 UTC 
Hi all,
a fresh installed Core 128 do not delivers /etc/fcron.daily/openvpn-crl-updater anymore.

Report comes from the forum --> https://forum.ipfire.org/viewtopic.php?f=16&t=22571 .

Best,

Erik
Comment 1 Michael Tremer 2019-04-08 17:01:03 UTC 
> [root@ipfire ipfire-2.x]# git grep openvpn-crl-updater$
> config/rootfiles/common/openvpn:etc/fcron.daily/openvpn-crl-updater
> config/rootfiles/oldcore/120/filelists/files:etc/fcron.daily/openvpn-crl-updater
> lfs/openvpn:    chown root:root /etc/fcron.daily/openvpn-crl-updater
> lfs/openvpn:    chmod 750 /etc/fcron.daily/openvpn-crl-updater
> [root@ipfire ipfire-2.x]#

This is being shipped in the common root files with OpenVPN and was shipped in Core Update 120, too.
Comment 2 Michael Tremer 2019-04-18 10:27:50 UTC 
Any response?
Comment 3 Erik Kapfer 2019-04-19 07:35:56 UTC 
Hi Michael,
made a test now with a fresh installed Core 130 and the openvpn-crl-updater is present under /etc/fcron-daily . Not sure why this occurs by two indepandant installations. The users made a fast description --> https://forum.ipfire.org/viewtopic.php?f=16&t=22571&start=30 what have happens but i do not experienced it here and have also not seen any further users with this problem, also both problems has been solved in the forum now.

Best,

Erik
Comment 4 Michael Tremer 2019-04-20 17:37:46 UTC 
Okay, I will close this then as NOTABUG because it is not reproducible.

Could have been an early version of a core update that was installed that did not include the fix.