[winswitch] xpra-0.9.0 RPM installation

Utku Altunkaya utku at um-ic.com
Thu Apr 25 15:14:28 BST 2013

On 25/04/13 16:55, Antoine Martin wrote:
> On 04/25/2013 07:08 PM, Utku Altunkaya wrote:
>> When I tried to update XPRA on a CentOS 6.4 machine, I got the following
>> error:
>> Updating: xpra-0.9.0-25.el6.x86_64
>> Non-fatal POSTIN scriptlet failure in rpm package xpra-0.9.0-25.el6.x86_64
>> chcon: can't apply partial context to unlabeled file
>> `/usr/lib/python2.6/site-packages/xpra/x264/codec.so'
>> chcon: can't apply partial context to unlabeled file
>> `/usr/lib/python2.6/site-packages/xpra/vpx/codec.so'
>> warning: %post(xpra-0.9.0-25.el6.x86_64) scriptlet failed, exit status 1
>> Cleanup: xpra-0.8.8-1.el6.x86_64
> I'm pretty sure it isn't a problem.
>> SELinux is disabled on this machine, which is probably the reason for
>> this error. Although the message says "non-fatal", I'm worried that the
>> RPM post-installation script was interrupted and may have left some
>> configuration incomplete. 
> That's the only post-installation script there is, so even if it did
> stop (which I believe it did not), it would not be a problem.
>> Can you update the script to take into account
>> the case where SELinux is diasabled and files don't have any security
>> context assigned to them?
> I'm not sure how, or if it is even worth doing.
Thank you, I'm relieved. If this is the only task that the script
handles, then it wouldn't be worth the effort to go check for SELinux.
>> Another issue is that everytime I do an update the RPM overwrites my
>> custom site-wide configuration in /etc/xpra/xpra.conf. It should check
>> the existence of xpra.conf (which can be a regular file or, as is in my
>> case, a symbolic link) and leave it untouched, preferably saving the new
>> default configuration in a file such as xpra.conf.rpmorig.
> Isn't that rpm's responsability to manage how those are handled?
> Note: depending on how many users you do this for, you may simply want
> to keep your overrides in ~/.xpra/xpra.conf
As far as I could find, you need to mark config files in the RPM spec so
that they are not replaced during an update. The syntax is something like

%config(noreplace) /etc/xpra/xpra.conf

Utku Altunkaya

More information about the shifter-users mailing list