On Dec 14, 12 15:45:29 +0000, Cristian Morales Vega wrote:

- libcdio-paranoia separated from libcdio due to license issues see bnc#756564

I want to read the bug report to know how to do a proper update. But I can't access to it.

Added christian.morales.vega@gmail.com to see bnc#756564 Please try again.

Now that I have shown that making legal related bugs private causes problems, there is any good reason to do that?

We don't want to invite law-trolls to browse really critical issues. With all legal issues closed, they cannot even tell *if* we currently have somthing critical. That is a reason. Maybe not a good one.

And if it's actually needed, what's the recommended workaround?

We run a need-to-know-policy here. The workaround is to ping someone from the legal team and ask to be added. Susanne (on CC) you can handle such requests? Right? cheers, JW- -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de back to ascii! __/ _---|____________\/ \ | 0911 74053-508 say #263A!__/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Jeff Hawn, J.Guild, F.Imendoerffer, HRB 16746 (AG Nuernberg), Maxfeldstrasse 5, 90409 Nuernberg, Germany SuSE. Supporting Linux since 1992. ☺ -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org