Hi everyone, we operate an own installation of the opensuse buildservice 2.0.4 and use it to build several php-related packages for various platforms including SLES 10 + 11. It happens only for SLES10, that automatic updates of our packages will fail. All packages coming from our repository are flagged as "locked" and zypper will not upgrade them. I also cannot find the lockfile in /etc/zypp/locks as suggested by http://en.opensuse.org/openSUSE:Libzypp_locksfile. When running "zypper install locked-package-name" it will complain about the locks. If one proceeds and selects "unlock" from the list of choices, then all packages will be installed, but each one will throw a dependency error during installation. I've read (German: http://www.linux-club.de/viewtopic.php?f=3&t=81259&sid=d48a82d276afac5e2c0ea0950dddd247), that any external package will be locked automatically in SLES10. Does this include external repositories (like ours) as well? The zypper version is very old on SLES10 and does not seem to support the lock-managing commands. sles10:~ # rpm -qa | grep zypp zypper-0.6.200-0.4.49 libzypp-2.100.3-0.4.23 libzypp-zmd-backend-7.1.1.0_2.16-0.4.46 I asked this on the opensuse-buildservice list, from where I was sent here. We already verified, that the packages are signed OK and that the GPG key is properly imported as well (rpm -qi). Now the question is: Is there a way our repository needs to be flagged, so that the packages will not get locked by SLES10? We rely on automatic upgrades of packages distributed from those repositories, so manual install is not a feasible solution. Is there a command in this old version of zypper to unlock the packages? With kind regards, Lars Volker -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org