On 09/30/2011 09:32 AM, Cristian Morales Vega wrote:

...

Hi,

After some more digging and lots of clicking ;) I end up with the following entries in the whitelist that do not appear to match anything.

"libartskde1" : "no package found", "libevolutionglue" : "no package found", "libgladesharpglue-2" : "no package found", "libglibsharpglue-2" : "no package found", "libgnomesharpglue-2" : "no package found", "libgsfglue" : "no package found", "libICE6" : "no package found", "libind_helper0" : "no package found", "libmdbodbc0" : "no package found", "libQtSql4" : "no package found", "libSM6" : "no package found", "libz1" : "no package found",

If anyone recognizes one of these names and can confirm that it really no longer exists I would appreciate it. On the contrary, if you do recognize a name and the package still exists in the project please point me to the project and spec that produces the library in question.

I'll rip these out within the next couple of days if I do not hear anything back. How does that list exactly work? libz1 is obviously how the zlib

On 30 September 2011 14:22, Robert Schweikert wrote: package *should* be named, and libICE6 is the name xorg-x11-libICE should have.

Thanks.

So I suppose it's not that they "no longer exists" but that they will never exists until those entries are ripped from the list? What we agreed on at osc was that entries in the list will get version numbers, for example the exception for zlib will look like this:

"libz1" : ('1.2.3','1.2.5','1.2.5_git201105272030'), This encodes the versions of zlib in the project today, the idea being that we break as few of these as possible. When we check the exception to the rule we will also check the version. If the version no longer matches the encoded version the "policy error" is triggered. Whomever is the lucky person touching the package at the time will have to fix the naming ;) This way over time we should be able to get rid off the naming exceptions without having to fix everything at once. That of course implies that the guardians of the exception list remain steadfast and do not add new versions or entries. ;) Later, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei@suse.com rschweik@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

From openSUSE 11.4, not verified in Factory:

On 30 September 2011 14:22, Robert Schweikert wrote:

Hi,

After some more digging and lots of clicking ;) I end up with the following entries in the whitelist that do not appear to match anything.

"libartskde1" : "no package found",

Using the command: zypper wp "libartskde.so.1()(64bit)" kdelibs3-arts

"libevolutionglue" : "no package found",

Using the command: zypper wp "libevolutionglue.so()(64bit)" evolution-sharp

"libgladesharpglue-2" : "no package found",

Using the command: zypper wp "libgladesharpglue-2.so()(64bit)" glade-sharp2

"libglibsharpglue-2" : "no package found",

Using the command... you see ;-) glib-sharp2

"libgnomesharpglue-2" : "no package found",

gnome-sharp2

"libgsfglue" : "no package found",

gsf-sharp

"libICE6" : "no package found",

xorg-x11-libICE

"libind_helper0" : "no package found",

sblim-indication_helper

"libmdbodbc0" : "no package found",

mdbtools-odbc

"libQtSql4" : "no package found",

libqt4-sql

"libSM6" : "no package found",

xorg-x11-libSM

"libz1" : "no package found",

zlib -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org