Preliminary Injunction against SuSE
According to this article on Slashdot [http://slashdot.org/article.pl?sid=02/01/08/1322202&mode=thread], a preliminary injunction has been granted to an anonymous client, barring SuSE from selling their distribution until they change the name of some allegedly trademark infringing program. Any of you SuSE people want to give us the skinny on this? Thanks, -Steven
"Steven R. Hatfield" schrieb:
According to this article on Slashdot [http://slashdot.org/article.pl?sid=02/01/08/1322202&mode=thread], a preliminary injunction has been granted to an anonymous client, barring SuSE from selling their distribution until they change the name of some allegedly trademark infringing program.
Yep. This is the "German Trademarks" thread... ;-) Juergen -- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\
Hello SuSE folkz, Once I've got a broken rpm package. It has been installed with some minor errors,though it worked. When I wasn't need in this package anymore I executed 'rpm -e PACKAGE' and got this error: 'execution of PACKAGE script failed, exit status 126'. Well, then I removed all components of this package manually verifying their locations with 'rpm -ql PACKAGE'. I did 'rpm --rebuilddb' to rebuild rpm database. However, RPM still keeps the records about already removed package in its database. When I do 'rpm -q PACKAGE' it shows me that it exists as PACKAGE-xx-xx. My question is how to remove this package entry from RPM database? Many thanks in advance. Alex
On Tuesday 08 January 2002 19.15, Alex Daniloff wrote:
My question is how to remove this package entry from RPM database?
rpm -e --justdb packagename should do it. In future, if you get errors like "script failed", you may want to look at options like "--force" or "--noscripts" instead of manually deleting the files. You can then do "rpm -q --scripts packagename" to see what the scripts actually tried to do, and if it's important, do it manually. regards Anders
participants (4)
-
Alex Daniloff -
Anders Johansson -
Juergen Braukmann -
Steven R. Hatfield