Created attachment 243854 [details]
zypper.log

This is what caused removal of the product, as far as the solver is concerned:

[zypp] Product.cc(referencePackage):90 (5430)product:openSUSE-11.1-0.noarch(@System): no reference package found: product(openSUSE) == 11.1-0
[zypp] Product.cc(referencePackage):90 (5429)product:openSUSE-11.1-0.noarch(@System): no reference package found: product(openSUSE) == 11.1-0
[zypp++] PoolItem.cc(setBuddy):148 U__s_(2)product:openSUSE-11.1.x86_64(openSUSE-11.1-Beta2) has buddy U__s_(2583)openSUSE-release-11.1-1.14.x86_64(openSUSE-11.1-Beta2)

Regarding the actual commit, i have no idea why it did not remove the product. Michael, can you look at it?

'no reference package found' indicates that the product is not able to detect the associated reference package. This happens if the product metadata or the release packages provides are faulty.

The package providing the /etc/products.d entry must also provide 
  product(%{prodname}) = %{prodversion}


I could handle this in commit and forcefully remove buddyless /etc/products.d entries. 

(In reply to comment #3 from Michael Andres)
> 'no reference package found' indicates that the product is not able to detect
> the associated reference package. This happens if the product metadata or the
> release packages provides are faulty.
> 
> The package providing the /etc/products.d entry must also provide 
>   product(%{prodname}) = %{prodversion}
> 
> 
> I could handle this in commit and forcefully remove buddyless /etc/products.d
> entries. 
> 

Yes, I would support this.
Entries below /etc/products.d 'belong' to our tools and should be according to the standard. 

*** Bug 436800 has been marked as a duplicate of this bug. ***

Fixed in libzypp-5.18.0 (openSUSE 11.1)

*** Bug 438792 has been marked as a duplicate of this bug. ***