forum.opsi.org

Dear opsi developers,

I just tried to upgrade my opsi server (CentOS 6) for the 6 new packages released at version 4.0.3 from 4.0.2. I issued

Code: Alles auswählen

yum update opsiconfd opsipxeconfd ...etc...

All worked OK except for opsipxeconfd. Yum reported that it failed to remove the 4.0.2 package due to an error in the %preun script and, as a result, the system believed that it had both 4.0.3 and 4.0.2 version opsipxeconfd installed!

I downloaded the opsipxeconfd source rpm to find out what is wrong in the spec file and found this

Code: Alles auswählen

%preun
%stop_on_removal opsipxeconfd

The stop_on_removal is a Suse macro and will not work on RHEL/CentOS, hence the error.
I checked the opsiconfd spec file for comparison and found the same macro, but in a conditional test

Code: Alles auswählen

%preun
%if 0%{?suse_version}
	%stop_on_removal opsiconfd
%else...

Please fix this error in the opsipxeconfd spec file in the next package update.

For anyone else caught by this, get rid of the old version by running

Code: Alles auswählen

rpm -e --noscripts opsipxeconfd-<old version>

Then reinstall the current version to make sure all is OK

Code: Alles auswählen

yum reinstall opsipxeconfd

Regards,

Stephen Jones

Thanks for your bug report.

We will check this issue and hopefully fix it in tne next release,

Regards,
Bardo Wolf

Verfasst: **08 Apr 2014, 21:41**

This still happens I guess:

yum list installed | grep opsi

Code: Alles auswählen

duplicity.x86_64                     0.6.08b-10.3                      @opsi4
librsync.x86_64                      0.9.7-176.3                       @opsi4
opsi-atftp.x86_64                    0.7.dfsg-10.2                     @opsi4
opsi-configed.noarch                 4.0.4.1.2-4.2                     @opsi4
opsi-depotserver.noarch              4.0.4.4-1.2                       @opsi4
opsi-linux-bootimage.noarch          20140118-1.2                      @opsi4
opsi-utils.noarch                    4.0.4.1-2.2                       @opsi4
opsiconfd.noarch                     4.0.4.3-1.2                       @opsi4
opsipxeconfd.noarch                  4.0.3.1-1.1                       @opsi4
opsipxeconfd.noarch                  4.0.4.1-2.1                       @opsi4
opsipxeconfd.noarch                  4.0.4.1-2.2                       @opsi4
python-GnuPG-Interface.x86_64        0.3.2-4.4                         @opsi4
python-Twisted.x86_64                12.0.0-8.2                        @opsi4
python-crypto.x86_64                 2.1.0-5.2                         @opsi4
python-ldaptor.x86_64                0.0.43-3.6                        @opsi4
python-mysql.x86_64                  1.2.2-92.2                        @opsi4
python-opsi.noarch                   4.0.4.5-2.2                       @opsi4
python-pam.x86_64                    0.5.0-76.2                        @opsi4
python-pexpect.x86_64                2.3-31.2                          @opsi4
python-pyparsing.noarch              2.0.1-42.2                        @opsi4
python-serial.noarch                 2.4-11.2                          @opsi4
python-simplejson.x86_64             2.0.9-11.2                        @opsi4
python-zopeinterface.x86_64          3.3.0-114.2                       @opsi4

And I also got a 'failed' on removing opsipxeconfd from yum with the most recent update.

Verfasst: **21 Apr 2014, 17:11**

This bug is still here. I just found the same problem upgrading to 4.0.4 version. I checked the spec file in the src rpm and it has not been fixed. Please rectify this problem.

Stephen Jones

Verfasst: **30 Apr 2014, 14:37**

Hello,

just adapted the spec file to match the process in the opsiconfd. Should be fixed in the next release.

With kind regards

Niko

forum.opsi.org

Error on remove/upgrade opsipxeconfd rpm

Error on remove/upgrade opsipxeconfd rpm

Re: Error on remove/upgrade opsipxeconfd rpm

Re: Error on remove/upgrade opsipxeconfd rpm

Re: Error on remove/upgrade opsipxeconfd rpm

Re: Error on remove/upgrade opsipxeconfd rpm