rust in SLE15 SP2 does not links to rust.10459 even though rust.10459 has newer version... however this is also happened on old leaper - different sources from GA and Update :)

SLE is a funny man, having newer sources in the oldest version in family while older sources in newest version of family. Due to the inheritance used by SLE project setup, the only way to tell what direction something is going is to layer the revisions from inherited projects. This is doubly needed since the first revision in an :Update project loses the entire revision history that was previously exposed (OBS VCS ftw).

From the output using CLI:

$ osc origin -p openSUSE:Leap:15.2 package --debug rust
[D] origin_find: openSUSE:Leap:15.2/rust with source ee80bc9 (True, True, True)
[D] source_contain: SUSE:SLE-15-SP2:GA                       d24738d == ee80bc9
[D] source_contain: SUSE:SLE-15-SP2:GA                       294e547 == ee80bc9
[D] source_contain: SUSE:SLE-15-SP2:GA                       ee80bc9 == ee80bc9 (match)
SUSE:SLE-15-SP2:GA

One can see it thinks it is matching the third revision and submitting the first (which it is).

Adding some extra debugging since we are working with a super fun case:

from SUSE:SLE-15-SP2:GA/rust (True)
[D] source_contain: SUSE:SLE-15-SP2:GA                       d24738d == ee80bc9
from SUSE:SLE-15-SP2:GA/rust (True)
[D] source_contain: SUSE:SLE-15-SP2:GA                       294e547 == ee80bc9
from SUSE:SLE-15-SP1:Update/rust (True)
from SUSE:SLE-15-SP1:Update/rust (True)
from SUSE:SLE-15-SP1:GA/rust (True)
from SUSE:SLE-15-SP1:GA/rust (True)
from SUSE:SLE-15:Update/rust (True)
[D] source_contain: SUSE:SLE-15-SP2:GA                       ee80bc9 == ee80bc9 (match)

The projects in the middle with no source_contain line because there are no unique revisions and searching for last 5 revisions. Interestingly, this scenario came to be since origin-manager submitted Leap:15.1:Update version of rust as it was tracking that origin previously. In the process it matched SLE due to their maintenance update (which behaves as is expected).

The next time origin-manager goes to update it sees that it is behind latest SLE and submits this. Using rdiff one can verify this is the latest SLE revision as the diff matches this request.

osc rdiff openSUSE:Leap:15.2 rust SUSE:SLE-15-SP2:GA

While rdiff to SUSE:SLE-15:Update shows no diff

osc rdiff openSUSE:Leap:15.2 rust SUSE:SLE-15:Update

You can see SUSE:SLE-15:Update/rust was updated recently. This all fits the expected behavior and is part of the very screwy VCS/workflow model used. I would also suggest this is a bug on SLE side to update rust in latest service packs.