[opensuse-packaging] Correctly splitting xinetd configuration file that has %config(noreplace).
Hi,
There are two VNC related packages: * xorg-x11-Xvnc, contains: - Xvnc binary (Xserver working as VNC server), since 12.3 based on tigervnc
* tightvnc, contains: - VNC client (tightvnc) - bunch of scripts to configure and start Xvnc comfortably - vnc_inetd_httpd (http server to deliver Java based VNC client) - /etc/xinetd.d/vnc file containing vnc and vnchttp services
tightvnc depends on xorg-x11-Xvnc and usually they are installed together.
The /etc/xinetd.d/vnc contains definition of vnc{1,2,3} services that start Xvnc from xorg-x11-Xvnc package and vnchttpd{1,2,3} services that start vnc_inetd_httpd from tightvnc package.
Now, to fix a bug that prevents Xvnc from working correctly in 12.3, we need to add additional option (-SecurityTypes None) to the xinetd configuration file. But it doesn't feel correct to add tigervnc specific option to file in tightvnc package. The best solution would be to split the xinetd configuration file into two and put each to appropriate package.
I have that prepared and I verified that YaST is still able to switch both vnc and vnchttp services on and off correctly.
Problem is that the /etc/xinetd.d/vnc is %config(noreplace) and if someone modified it, he will end up with two files - the original with all services and the new one with half of them. Xinetd refuses to start when it finds duplicate services.
Could you suggest some safe way to split the configuration file? Or is it better to keep it in one package?
Michal
On Thu, Apr 25, 2013 at 06:56:20PM +0200, Michal Srb wrote:
Hi,
There are two VNC related packages:
xorg-x11-Xvnc, contains:
- Xvnc binary (Xserver working as VNC server), since 12.3 based on tigervnc
tightvnc, contains:
- VNC client (tightvnc)
- bunch of scripts to configure and start Xvnc comfortably
- vnc_inetd_httpd (http server to deliver Java based VNC client)
- /etc/xinetd.d/vnc file containing vnc and vnchttp services
tightvnc depends on xorg-x11-Xvnc and usually they are installed together.
The /etc/xinetd.d/vnc contains definition of vnc{1,2,3} services that start Xvnc from xorg-x11-Xvnc package and vnchttpd{1,2,3} services that start vnc_inetd_httpd from tightvnc package.
Now, to fix a bug that prevents Xvnc from working correctly in 12.3, we need to add additional option (-SecurityTypes None) to the xinetd configuration file. But it doesn't feel correct to add tigervnc specific option to file in tightvnc package. The best solution would be to split the xinetd configuration file into two and put each to appropriate package.
I have that prepared and I verified that YaST is still able to switch both vnc and vnchttp services on and off correctly.
Problem is that the /etc/xinetd.d/vnc is %config(noreplace) and if someone modified it, he will end up with two files - the original with all services and the new one with half of them. Xinetd refuses to start when it finds duplicate services.
Could you suggest some safe way to split the configuration file? Or is it better to keep it in one package?
Hi,
what about to split the /etc/xinetd.d/vnc to two different files - let say Xvnc and vnchttpd. And to prevent the old vnc will be used, rename it to /etc/xinetd.d/vnc~, so file will be ignored by the xinetd.
Of course all modifications made in /etc/xinetd.d/vnc will be lost, but some kind of post update message is supported by libzypp and can be used in this case.
BTW: please involve ke once you will find a solution as the Release Notes shall mention that change.
Regards Michal Vyskocil
Michal
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
-
Michal Srb -
Michal Vyskocil