# update self build rpms **URL:** \ **Category:** SLES Configure-Administer\ **Created:** [February 12, 2015, 11:58am UTC](https://forums.suse.com/t/update-self-build-rpms/26681 "2015-02-12T11:58:01Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![MoserHans](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@MoserHans](https://forums.suse.com/u/MoserHans)\ **Post date:** [February 12, 2015, 11:58am UTC](https://forums.suse.com/t/update-self-build-rpms/26681/1 "2015-02-12T11:58:01Z")
Hi, I build newer versions of openldap in the SuSE Build Service. 2.4.39 is installed on the SLES 11 SP 3 machine. (I used ansible for this, great tool, have a look at it, if you have not used any configuration management tool before!) ` # rpm -qa | grep openldap openldap2-2.4.39-0 openldap2-client-2.4.39-0 ` I build 2.4.40 and copied the files to my http repo. Unfortunatly my ansible script does not update. [CODE] tasks: - name: install LDAP RPMs zypper: name={{ item }} state=latest disable\_gpg\_check=yes with\_items: - libdb-4\_8 - openldap2-client - libldap-2\_4-2 - libldap-2\_4-2-32bit - openldap2 [/CODE] I checked with zypper on the machine: [CODE]# zypper up openldap2 Loading repository data… Reading installed packages… Resolving package dependencies… The following packages are going to be upgraded: libldap-2\_4-2 openldap2 openldap2-client The following packages are not supported by their vendor: libldap-2\_4-2 openldap2 openldap2-client 3 packages to upgrade. Overall download size: 1.5 MiB. After the operation, 1.6 MiB will be freed. Continue? [y/n/? shows all options] (y): n [/CODE] The new rpms are found. But zypper warns with “are not supported by their vendor”. I think this prevends ansible from automatically update the rpms. I have a vendors file for obs created before `# cat "/etc/zypp/vendors.d/obs" vendors = obs://build.opensuse.org ` [CODE]# zypper if openldap2 Loading repository data… Reading installed packages… Information for package openldap2: Repository: Netzdienste Repo Name: openldap2 Version: 2.4.40-0 Arch: x86\_64 Vendor: obs://build.opensuse.org/home:MoserHans Support Level: unknown Installed: Yes Status: out-of-date (version 2.4.39-0 installed) Installed Size: 3.1 MiB Summary: The OpenLDAP Server Description: The Lightweight Directory Access Protocol (LDAP) is used to access online directory services. It runs directly over TCP and can be used to access a stand-alone LDAP directory service or to access a directory service that has an X.500 back-end. :~ # rpm -qi openldap2 Name : openldap2 Relocations: (not relocatable) Version : 2.4.39 Vendor: obs://build.opensuse.org/home:MoserHans Release : 0 Build Date: Tue 10 Jun 2014 03:44:28 PM CEST Install Date: Mon 17 Nov 2014 03:27:19 PM CET Build Host: buildhost-sp3 Group : Productivity/Networking/LDAP/Clients Source RPM: openldap2-2.4.39-0.src.rpm Size : 4936865 License: OLDAP-2.8 Signature : (none) URL : [http://www.openldap.org](http://www.openldap.org) Summary : The OpenLDAP Server Description : The Lightweight Directory Access Protocol (LDAP) is used to access online directory services. It runs directly over TCP and can be used to access a stand-alone LDAP directory service or to access a directory service that has an X.500 back-end. Distribution: home:MoserHans:branches:network:ldap / SLE\_11\_SP3 [/CODE] What am I missing? ---
**Author:** ![smflood](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/smflood/32/10576_2.png) [@smflood](https://forums.suse.com/u/smflood)\ **Post date:** [February 12, 2015, 7:05pm UTC](https://forums.suse.com/t/update-self-build-rpms/26681/2 "2015-02-12T19:05:34Z")
On 12/02/2015 10:04, MoserHans wrote: [color=blue] > I build newer versions of openldap in the SuSE Build Service. > 2.4.39 is installed on the SLES 11 SP 3 machine.[/color] Given latest openldap2 package available from SUSE is 2.4.26-0.28.5 I’m guessing you installed your own version 2.4.39? [color=blue] > (I used ansible for this, great tool, have a look at it, if you have not > used any configuration management tool before!)[/color] I agree re Ansible. Which version are you using? I’ve been building various versions using the OBS with 1.8.1 the latest released. How did you install openldap2 version 2.4.39, via ansible or “manually” via zypper/YaST? [color=blue] > ## Code: > > ``` > # rpm -qa | grep openldap > > ``` > > openldap2-2.4.39-0 > openldap2-client-2.4.39-0 > > * * * > > I build 2.4.40 and copied the files to my http repo. > > Unfortunatly my ansible script does not update. > > ## Code: > > ``` > tasks: > > ``` > > - name: install LDAP RPMs > zypper: name={{ item }} state=latest disable\_gpg\_check=yes > with\_items: > - libdb-4\_8 > - openldap2-client > - libldap-2\_4-2 > - libldap-2\_4-2-32bit > - openldap2 > > * * * > > I checked with zypper on the machine: > > ## Code: > > ``` > # zypper up openldap2 > > ``` > > Loading repository data… > Reading installed packages… > Resolving package dependencies… > > The following packages are going to be upgraded: > libldap-2\_4-2 openldap2 openldap2-client > > The following packages are not supported by their vendor: > libldap-2\_4-2 openldap2 openldap2-client > > 3 packages to upgrade. > Overall download size: 1.5 MiB. After the operation, 1.6 MiB will be freed. > Continue? [y/n/? shows all options] (y): n > > * * * > > The new rpms are found. But zypper warns with “are not supported by > their vendor”. > I think this prevends ansible from automatically update the rpms. > > I have a vendors file for obs created before > > ## Code: > > ``` > # cat "/etc/zypp/vendors.d/obs" > > ``` > > vendors = obs://build.opensuse.org > > * * * > > ## Code: > > ``` > # zypper if openldap2 > > ``` > > Loading repository data… > Reading installed packages… > > Information for package openldap2: > > Repository: Netzdienste Repo > Name: openldap2 > Version: 2.4.40-0 > Arch: x86\_64 > Vendor: obs://build.opensuse.org/home:MoserHans > Support Level: unknown > Installed: Yes > Status: out-of-date (version 2.4.39-0 installed) > Installed Size: 3.1 MiB > Summary: The OpenLDAP Server > Description: > The Lightweight Directory Access Protocol (LDAP) is used to access > online directory services. It runs directly over TCP and can be used to > access a stand-alone LDAP directory service or to access a directory > service that has an X.500 back-end. > :~ # rpm -qi openldap2 > Name : openldap2 Relocations: (not relocatable) > Version : 2.4.39 Vendor: obs://build.opensuse.org/home:MoserHans > Release : 0 Build Date: Tue 10 Jun 2014 03:44:28 PM CEST > Install Date: Mon 17 Nov 2014 03:27:19 PM CET Build Host: buildhost-sp3 > Group : Productivity/Networking/LDAP/Clients Source RPM: openldap2-2.4.39-0.src.rpm > Size : 4936865 License: OLDAP-2.8 > Signature : (none) > URL : [http://www.openldap.org](http://www.openldap.org) > Summary : The OpenLDAP Server > Description : > The Lightweight Directory Access Protocol (LDAP) is used to access > online directory services. It runs directly over TCP and can be used to > access a stand-alone LDAP directory service or to access a directory > service that has an X.500 back-end. > Distribution: home:MoserHans:branches:network:ldap / SLE\_11\_SP3 > > * * * > > What am I missing?[/color] It’s possible Ansible is tripping up because of the “not supported” status but if you had previously installed 2.4.39 via Ansible that would make me think it’s something else. Checking the latest source for the zypper module it seems in the above scenario Ansible passes --non-interactive and --auto-agree-with-licenses (plus in your case --no-gpg-checks) parameters to zypper when updating already installed packages. None of those parameters have anything to do with the “not supported” status other than --non-interactive automatically agreeing to defaults responses - “not supported” is a warning. What does “zypper se -is openldap2” report? ## HTH. Simon SUSE Knowledge Partner * * * ## If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below. Thanks. ---
**Author:** ![MoserHans](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@MoserHans](https://forums.suse.com/u/MoserHans)\ **Post date:** [February 13, 2015, 12:41pm UTC](https://forums.suse.com/t/update-self-build-rpms/26681/3 "2015-02-13T12:41:34Z")
[QUOTE=smflood;26355]On 12/02/2015 10:04, MoserHans wrote: [color=blue] > I build newer versions of openldap in the SuSE Build Service. > 2.4.39 is installed on the SLES 11 SP 3 machine.[/color] > Given latest openldap2 package available from SUSE is 2.4.26-0.28.5 I’m > guessing you installed your own version 2.4.39? > [color=blue][/QUOTE] > Yes, I did. [QUOTE] How did you install openldap2 version 2.4.39, via ansible or “manually” via zypper/YaST? [color=blue][/QUOTE] via ansible. That’s why a created the vendor file, to allow the vendor change without any further questions. > [@](#): > > It’s possible Ansible is tripping up because of the “not supported” > status but if you had previously installed 2.4.39 via Ansible that would > make me think it’s something else. > > Checking the latest source for the zypper module it seems in the above > scenario Ansible passes --non-interactive and --auto-agree-with-licenses > (plus in your case --no-gpg-checks) parameters to zypper when updating > already installed packages. None of those parameters have anything to do > with the “not supported” status other than --non-interactive > automatically agreeing to defaults responses - “not supported” is a warning. I’m still an ansible 1.6.1 There no ansible 1.8.2 for SLES 11 SP 1 in the OBS at the moment, which I could update to. > [@](#): > > What does “zypper se -is openldap2” report? [CODE]# zypper se -is openldap2 Loading repository data… Reading installed packages… S | Name | Type | Version | Arch | Repository –±-----------------±--------±---------±-------±---------------- i | openldap2 | package | 2.4.39-0 | x86\_64 | myown Repo i | openldap2-client | package | 2.4.39-0 | x86\_64 | myown Repo [/CODE]