Bug 469940

Summary: samba 3.2.7 packages from openSUSE Build Service don't get installed
Product: [openSUSE] openSUSE 11.1 Reporter: Lars Müller <lmuelle>
Component: libzyppAssignee: E-mail List <zypp-maintainers>
Status: RESOLVED INVALID QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: mls, samba-maintainers
Version: Final   
Target Milestone: Final   
Hardware: All   
OS: All   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: tar ball of the solver test case

Description Lars Müller 2009-01-27 21:04:55 UTC 
While using http://download.opensuse.org/repositories/network:/samba:/STABLE/openSUSE_11.1/ in adition to the openSUSE 11.1 oss and update repo Samba packages don't get upgraded to the current 3.2.7 release.

The packages are available neither a zypper dup nor zypper up upgrades from 3.2.6 to 3.2.7.

We have seen one public report on this.  And I'm seeing this currently on x86_64 and i586.

giles:~ # rpm -qa | grep ^samba
samba-winbind-3.2.6-0.3.1
samba-winbind-32bit-3.2.6-0.3.1
samba-3.2.6-0.3.1
samba-vscan-0.3.6b-5.3.1
samba-client-3.2.6-0.3.1
samba-doc-3.2.7-7.1
giles:~ # zypper dup
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Nothing to do.
giles:~ # zypper lr
#  | Alias                     | Name                      | Enabled | Refresh
---+---------------------------+---------------------------+---------+--------
1  | Libdvdcss repository      | Libdvdcss repository      | No      | Yes    
2  | Packman Repository        | Packman Repository        | No      | Yes    
3  | Virtualization_Qemu       | Virtualization_Qemu       | Yes     | Yes    
4  | Virtualization_VirtualBox | Virtualization_VirtualBox | Yes     | Yes    
5  | mozilla                   | Mozilla based projects    | Yes     | Yes    
6  | network_samba_STABLE      | network_samba_STABLE      | Yes     | Yes    
7  | nvidia                    | NVIDIA Repository         | Yes     | Yes    
8  | repo-debug                | repo-debug                | No      | No     
9  | repo-non-oss              | repo-non-oss              | Yes     | Yes    
10 | repo-oss                  | repo-oss                  | Yes     | Yes    
11 | repo-source               | repo-source               | No      | Yes    
12 | repo-update               | openSUSE-11.1-Update      | Yes     | Yes    
giles:~ # zypper locks
# | Name             | Type    | Repository
--+------------------+---------+-----------
1 | compat           | package | (any)     
2 | beagle           | package | (any)     
3 | beagle-gui       | package | (any)     
4 | beagle-index     | package | (any)     
5 | kdebase3-beagle  | package | (any)     
6 | beagle-firefox   | package | (any)     
7 | beagle-evolution | package | (any)
Comment 1 Lars Müller 2009-01-28 10:11:04 UTC 
This looks more like a generic zypper issue.

After I called zypper in samba samba-winbind I got informed about a vendor change.

I'm not able to follow why a configured install source - in this case the openSUSE Build Service samba STABLE repository - isn't used to update software components if the system trusts the signed packages.
Comment 2 Michael Schröder 2009-01-28 10:26:24 UTC 
trusted doesn't mean that a repository change is allowed. That's what vendor equivalence is for, i.e. /etc/zypp/vendors.d.

zypper dup doesn't look at the vendor, though. So I guess there's something else wrong with the 3.2.7 packages. Hard to tell without a solver testcase (hint)...
Comment 3 Lars Müller 2009-01-28 12:29:38 UTC 
Created attachment 268265 [details]
tar ball of the solver test case
Comment 4 Michael Schröder 2009-01-28 16:26:30 UTC 
It's because the "repo-update" repository has priority 20, while "network_samba_STABLE" only has priority 99. Thus, samba is taken from repo-update. Not a bug.
Comment 5 Lars Müller 2009-01-28 17:21:48 UTC 
Modified the repository priority to 19 and it works as expected.