# zypper cannot find all packages **URL:** \ **Category:** SLES Configure-Administer\ **Created:** [November 10, 2016, 3:43pm UTC](https://forums.suse.com/t/zypper-cannot-find-all-packages/28941 "2016-11-10T15:43:51Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![DJViking](https://avatars.discourse-cdn.com/v4/letter/d/ecccb3/32.png) [@DJViking](https://forums.suse.com/u/DJViking)\ **Post date:** [November 10, 2016, 3:43pm UTC](https://forums.suse.com/t/zypper-cannot-find-all-packages/28941/1 "2016-11-10T15:43:51Z")
using zypper it cannot find all packages in my repository I have tried to delete /etc/zypp, and recreate the repositories again. Still same problem persist. machine1:~ # zypper install --force gcc49 Loading repository data… Reading installed packages… Package gcc49-4.9.2-2companyBuild.x86\_64 not found in repositories, cannot reinstall. However if I enter into YaST =\> Software Management, I am able to find the package under this repository, and able to forcefully reinstall it. How come zypper cannot find the package? Using SUSE Linux Enterprise Server 11. Not sure where to look for discrepancies on the system. I have tried to clean with zypper clean -all and rpmdb --rebuilddb. I tried these commands on one server and it worked there, but only there. Other servers still have the problem with zypper cannot find the package. This works fine on SLES 11 SP3, but fails on SLES 11. I know SP3 has zypper 1.6.326, while SLES 11 has version 1.0.13. The repository is comprized of two symlinks /repo/sles11/dir1 =\> /dir1 /repo/sles11/dir2 =\> /dir2 It finds the packages from dir2, but not dir1. The access is the same on each symlink and underlying directories. The repodata/filelist.xml.gz contains all the packages from both these directories. Still zypper cannot find all, but YaST does. Is there any manual procedures I can try to clean out everything (short of doing a reinstall) ? ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [November 11, 2016, 1:16am UTC](https://forums.suse.com/t/zypper-cannot-find-all-packages/28941/2 "2016-11-11T01:16:04Z")
Hi 😉 If you use zypper to search for gcc, sure your using the correct name for the package? Have you run zypper --clean What it the output from zypper lr -d ---
**Author:** ![DJViking](https://avatars.discourse-cdn.com/v4/letter/d/ecccb3/32.png) [@DJViking](https://forums.suse.com/u/DJViking)\ **Post date:** [November 11, 2016, 8:57am UTC](https://forums.suse.com/t/zypper-cannot-find-all-packages/28941/3 "2016-11-11T08:57:02Z")
[QUOTE=malcolmlewis;35209]Hi 😉 If you use zypper to search for gcc, sure your using the correct name for the package? Have you run zypper --clean What it the output from zypper lr -d[/QUOTE] I am using the correct name for the package. Zypper cannot find the package when I try to forcefully update it. ```auto machine1:~ # zypper install --force gcc49 Loading repository data... Reading installed packages... Package gcc49-4.9.2-2comp.x86_64 not found in repositories, cannot reinstall. Resolving package dependencies... ``` On packages that are installed from that repository ```auto machine1:~ # zypper info gcc49 Loading repository data... Reading installed packages... Information for package gcc49: Repository: @System Name: gcc49 Version: 4.9.2-2comp ``` It should not say @System on Repository. I have run zypper clean --all several times ```auto jmachine1:~ # zypper lr -d # | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service --+--------------+--------------+---------+---------+----------+--------+--------------------------------------------------------------------------+-------- 1 | VMware | VMware | Yes | No | 99 | rpm-md | http://download.opensuse.org/repositories/Virtualization:/VMware/SLE_11/ | 2 | comp-jpss | comp-jpss | Yes | No | 99 | rpm-md | http://repo.company.com/repo/FeatureA/sles11.0/ | 3 | comp-sles | comp-sles | Yes | No | 99 | rpm-md | ftp://username@suse.company.com/sle11.0/STABLE/x86_64/ | 4 | staging-f1 | staging-f1 | Yes | No | 99 | rpm-md | http://repo.company.com/stagingrepo/FeatureA/sles11.0/ | ``` ---
**Author:** ![DJViking](https://avatars.discourse-cdn.com/v4/letter/d/ecccb3/32.png) [@DJViking](https://forums.suse.com/u/DJViking)\ **Post date:** [November 11, 2016, 10:55am UTC](https://forums.suse.com/t/zypper-cannot-find-all-packages/28941/4 "2016-11-11T10:55:22Z")
Zypper search list this package under the right repository. But not zypper info. [CODE]machine2:~ # zypper se -s gcc49 Loading repository data… Reading installed packages… S | Name | Type | Version | Arch | Repository –±--------------------±--------±------------±-------±----------- i | gcc49 | package | 4.9.2-2comp | x86\_64 | F1-sle110 v | gcc49 | package | 4.9.2-2comp | i586 | F1-sle110 | gcc49-32bit | package | 4.9.2-2comp | x86\_64 | F1-sle110 i | gcc49-c++ | package | 4.9.2-2comp | x86\_64 | F1-sle110 v | gcc49-c++ | package | 4.9.2-2comp | i586 | F1-sle110 i | gcc49-fortran | package | 4.9.2-2comp | x86\_64 | F1-sle110 v | gcc49-fortran | package | 4.9.2-2comp | i586 | F1-sle110 | gcc49-fortran-32bit | package | 4.9.2-2comp | x86\_64 | F1-sle110 | gcc49-info | package | 4.9.2-2comp | x86\_64 | F1-sle110 | gcc49-info | package | 4.9.2-2comp | i586 | F1-sle110 | gcc49-locale | package | 4.9.2-2comp | x86\_64 | F1-sle110 | gcc49-locale | package | 4.9.2-2comp | i586 | F1-sle110 machine2~ # zypper info gcc49 Loading repository data… Reading installed packages… Information for package gcc49: Repository: @System Name: gcc49 Version: 4.9.2-2comp Arch: x86\_64 Vendor: Installed: Yes Status: up-to-date Installed Size: 141.3 M Summary: The GNU C Compiler and Support Files Description: Core package for the GNU Compiler Collection, including the C language frontend. Language frontends other than C are split to different sub-packages, namely gcc-ada, gcc-c++, gcc-fortran, gcc-java, gcc-objc and gcc-obj-c++.[/CODE] I removed the gcc49 package, then zypper info list it under the right repository. ```auto machine2:~ # zypper info gcc49 Loading repository data... Reading installed packages... Information for package gcc49: Repository: F1-sle110 Name: gcc49 Version: 4.9.2-2comp ``` After regular install without force this time, the Repository is back on @System with zypper info. ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [November 11, 2016, 6:42pm UTC](https://forums.suse.com/t/zypper-cannot-find-all-packages/28941/5 "2016-11-11T18:42:12Z")
> [@](#): > > On Fri 11 Nov 2016 09:04:01 AM CST, DJViking wrote: > > After regular install without force this time, the Repository is back on > @System with zypper info. Hi Try; ```auto zypper in -f gcc49 --from F1-sle110 ``` Wonder if it’s related to the vendor change… – Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) openSUSE Leap 42.1|GNOME 3.16.2|4.1.34-33-default 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:** ![DJViking](https://avatars.discourse-cdn.com/v4/letter/d/ecccb3/32.png) [@DJViking](https://forums.suse.com/u/DJViking)\ **Post date:** [November 14, 2016, 9:14am UTC](https://forums.suse.com/t/zypper-cannot-find-all-packages/28941/6 "2016-11-14T09:14:55Z")
[QUOTE=malcolmlewis;35242]Hi Try; ```auto zypper in -f gcc49 --from F1-sle110 ``` Wonder if it’s related to the vendor change… [/QUOTE] ```auto machine2:~ # zypper install --from F1-sle110 --force gcc49 Loading repository data... Reading installed packages... Package gcc49-4.9.2-2comp.x86_64 not found in repositories, cannot reinstall. Resolving package dependencies... Nothing to do. machine2:~ # zypper install --repo F1-sle110 --force gcc49 Loading repository data... Reading installed packages... Package gcc49-4.9.2-2comp.x86_64 not found in repositories, cannot reinstall. Resolving package dependencies... Nothing to do. ``` We have also some inhouse built packages which have the same problem, if they have already been installed. It is the --force that causes problem. I am able to remove gcc49, then reinstall it, but not able to use --force.