RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?
I dont have kinternet installed. This is what doesnt seem to work: <software> <patterns config:type="list"> <pattern>default</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> <packages config:type="list"> <packages>perl-libwww-perl</packages> <packages>net-snmp</packages> <packages>kernel-source</packages> </packages> <remove-packages config:type="list"> <packages>pptp</packages> <packages>smpppd</packages> <packages>ppp</packages> <packages>wvdial</packages> <packages>mutt</packages> </remove-packages> </software> In y2log it mentions that those packages should be removed, but it goes ahead and installs them anyway. I can do it manually on the command line: # rpm -e pptp smpppd ppp wvdial mutt and that works fine so I know I have no dependency problems. matt
-----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Friday, 30 June 2006 12:50 AM To: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section?
On Thursday 29 June 2006 16:45, Manfred Hollstein wrote:
If that fails, you have kinternet installed; add that to the list and it should work.
good point. <remove-packages> can not break dependencies and so it's very likely that there is still a package that needs those packages. I did a very small installation with no X - so it worked for me.
-- ciao, Uwe Gansert
Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug now playing Covenant - Wasteland
-- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.
On Friday 30 June 2006 00:16, Matt Gillard wrote:
This is what doesnt seem to work:
<software> <patterns config:type="list"> <pattern>default</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> <packages config:type="list"> <packages>perl-libwww-perl</packages> <packages>net-snmp</packages> <packages>kernel-source</packages> </packages> <remove-packages config:type="list"> <packages>pptp</packages> <packages>smpppd</packages> <packages>ppp</packages> <packages>wvdial</packages> <packages>mutt</packages> </remove-packages> </software>
yes, I can reproduce that. Seems to be a resolver issue. I'll talk to the zypp guys about this. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug now playing :Wumpscut: - Opening The Gates Of Hell
Uwe Gansert wrote:
On Friday 30 June 2006 00:16, Matt Gillard wrote:
This is what doesnt seem to work:
<software> <patterns config:type="list"> <pattern>default</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> <packages config:type="list"> <packages>perl-libwww-perl</packages> <packages>net-snmp</packages> <packages>kernel-source</packages> </packages> <remove-packages config:type="list"> <packages>pptp</packages> <packages>smpppd</packages> <packages>ppp</packages> <packages>wvdial</packages> <packages>mutt</packages> </remove-packages> </software>
yes, I can reproduce that. Seems to be a resolver issue. I'll talk to the zypp guys about this.
Was this issue solved in the final SLES10 or SLES10-SP1? The posting above was the last one in this thread and I couldn't find any newer on that topic. Sorry for digging in the past, but testing SLES10-SP1 and SLED10-SP1 and some "combination" with openSuSE 10.1. I have similar problems with <remove-packages> which have been solved for openSuSE 10.1 in 2006 by the fix for the root image. But what about SLES? And to answer an obvious question: Yes, I only want to remove packages, that are not required by others and which I can remove with yast, but not automatically (as described above). And not beeing removed, they even cause some dependency conflicts, so later removal with rpm -e... is no solution here. As far as I understand, the problem still seems to occur in some newer distributions again as e.g. openSUSE 10.3 (see posting from 26.2. and 27.2.2008)!? Is that right? Best regards, -- Guenther Haas, Uni Ulm, Abteilung TAIT, guenther.haas@gmx.de -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Wednesday 27 February 2008, Guenther Haas wrote:
Was this issue solved in the final SLES10 or SLES10-SP1?
it's definitely fixed in SP1 but IIRC SLES10 was not affected too.
Sorry for digging in the past, but testing SLES10-SP1 and SLED10-SP1 and some "combination" with openSuSE 10.1. I have similar problems with <remove-packages> which have been solved for openSuSE 10.1 in 2006 by the fix for the root image. But what about SLES?
the problem that autoyast can not remove packages that are required by a pattern still exists. There was a bug that no package could be removed at all and that bug is fixed but that does not guarantee that you can remove each and every package now.
And to answer an obvious question: Yes, I only want to remove packages, that are not required by others and which I can remove with yast, but not automatically (as described above).
RPM dependency is one thing but there are also patterns that require packages.
As far as I understand, the problem still seems to occur in some newer distributions again as e.g. openSUSE 10.3 (see posting from 26.2. and 27.2.2008)!? Is that right?
you can remove packages but not all. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: Breathe by Seabound -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Uwe Gansert wrote:
On Wednesday 27 February 2008, Guenther Haas wrote:
Was this issue solved in the final SLES10 or SLES10-SP1?
it's definitely fixed in SP1 but IIRC SLES10 was not affected too.
OK, thank you for that information.
RPM dependency is one thing but there are also patterns that require packages.
Do you see a possibility to remove the package novfs-kmp-...? In openSuSE 10.1 I can not find it in any selection file. But anyway an appropriate entry in the remove-packaegs section is ignored although other entries are not. Removing this package manually is possible without any problems anwithout any dependency warning. But, why do I want to remove this package? Actually my problem is a different one: I tried to include an add-on repository during my installation, containing some (not all) rpms from ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586 . Especially all kernel... packages for some reason connected to our hardware. Doing so, everything works well except the fact, that I get the following error messages: Cannot solve dependencies automatically. Manual intervention ist required. And entering the sofware section (details) manually: novfs-kmp-smp-1.2.0_2.6.16.13_4-10.i586[SUSE-Linux-10.1-FTP-10.1-0-20080228- 142043] cannot be installed due to missing... There are no installable providers of kernel(fs_proc) == fb66c0190774e82 for novfs-kmp-smp...[...] I tried to solve this problem by also adding all current novfs-kmp- rpms to my "update add-on" repository. But without effect. I can see the new rpm version in yast/autoyast but it is ignored by the system, that automatically still wants to install the old version 1.2.0_... and therefore I get the same error messages and the installation doesn't start. Now I have three questions: Is there a way to do, what I want to do. Directly install the newest kernel with autoyast? Why does autoyast want to install the 1.2.0 version of novfs-kmp-... althout there is a newer and better fitting version availabe? Is the version hard coded somewhere? In the /var/log/YaST/y2log I can find the information, that this rpm is chosen "Explicit !". What does this mean? Why is it not possible to remove the package novfs-kmp-... automatically with the remove-packages method? Many thank in advance and Best regards, -- Guenther Haas, Uni Ulm, Abteilung TAIT, guenther.haas@gmx.de -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Guenther Haas wrote:
Now I have three questions:
I think, I have found some answers myself. Just for the case, someone else should be interested...:
Is there a way to do, what I want to do. Directly install the newest kernel with autoyast?
Use the original source rpm novfs-1.2.0-10.src.rpm to build the rpms novfs-kmp-bigsmp-1.2.0_2.6.16.54_0.2.5-10.i586.rpm novfs-kmp-debug-1.2.0_2.6.16.54_0.2.5-10.i586.rpm novfs-kmp-default-1.2.0_2.6.16.54_0.2.5-10.i586.rpm novfs-kmp-smp-1.2.0_2.6.16.54_0.2.5-10.i586.rpm novfs-kmp-xen-1.2.0_2.6.16.54_0.2.5-10.i586.rpm novfs-kmp-xenpae-1.2.0_2.6.16.54_0.2.5-10.i586.rpm for the current kernel and add them to some add-on repository as you already did with the kernel-*-2.6.16.54-0.2.5.i586.rpm packages. Also put all current apparmor-* and yast2-apparmor-* rpms there. That way at least it works. I hope there is nothing missing.
Why does autoyast want to install the 1.2.0 version of novfs-kmp-... althout there is a newer and better fitting version availabe?
Not interested in the answer any more. The novfs-*-1.2.0* rpms will be updated during the first(?) update process.
Is the version hard coded somewhere? In the /var/log/YaST/y2log I can find the information, that this rpm is chosen "Explicit !". What does this mean?
Has somebody else an answer to that question? Or could explain?
Why is it not possible to remove the package novfs-kmp-... automatically with the remove-packages method?
Doesn't matter any more... Regards, -- Guenther Haas, Ulm University, Institute TAIT, guenther.haas@gmx.de -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Does somebody has as graphic configuration which gives me as a graphic card vesa-bios ? I ask because after installation it seems to be impossibly to change the graphic card. Sax gives only the an option button but no change button for the graphic card. tia Hajo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (4)
-
Guenther Haas -
Hans-Joachim Ehlers -
Matt Gillard -
Uwe Gansert