Comment # 11 on bug 1180626 from Max Lin

(In reply to Neil Rickert from comment #10)
> Responding to c#9
> 
> # zypper se -s librepository
> Loading repository data...
> Warning: Repository 'Main Update Repository' appears to be outdated.
> Consider using a different mirror or server.
> Reading installed packages...
> 
> S | Name                  | Type    | Version         | Arch   | Repository
> --+-----------------------+---------+-----------------+--------+-------------
> -----
> i | librepository         | package | 1.1.3-2.84      | noarch | (System
> Packages)
> v | librepository         | package | 1.1.3-bp153.1.1 | noarch | Main
> Repository
>   | librepository-javadoc | package | 1.1.3-bp153.1.1 | noarch | Main
> Repository
> 
> Looking at that output, the discrepancy does not seem very important.

All these downgrading package is noarch package, I believe product builder just
picks one of that from any build_arch. Have a closer look,

* librepository-1.1.3-2.84 is from SLE, a x86_64 build
* librepository-1.1.3-bp153.1.1 is from Backports, a non-x86_64 build

librepository in SLE only have x86_64 build, we rebuild librepository in
Backports in order to have non-x86_64 build, ie. x86_64 build is disabled but
other archs are enabled, so we have librepository-1.1.3-bp153.1.1 noarch RPM
from any non-x86_64 build in Backports. product buidler picks
librepository-1.1.3-bp153.1.1 instead of librepository-1.1.3-2.84 to ftp-tree
perhaps it's a fall out with multiple-layering repos.

Although librepository-1.1.3-2.84 and librepository-1.1.3-bp153.1.1 is from the
identical source, but librepository-1.1.3-2.84 is greater than
librepository-1.1.3-bp153.1.1 that's why downgrade happened. I'll file another
bug to track this issue.