Good question, I always add source packages from the command line. So, I had not run into that problem, hopefully Anas or somebody "more in the know" will respond -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Wednesday, March 09, 2005 3:04 PM To: suse-autoinstall@suse.com Subject: RE: [suse-autoinstall] YaST2 Doesn't Search for Source Packages In my example, yes, both of the k3b packages are listed in the packages file, Todd. For the binary package, there's: =Pkg: k3b 0.11.7 23.1 i586 < ... stuff ... > =Src: k3b 0.11.7 23.1 src =Tim: 1088641834 =Loc: 1 k3b-0.11.7-23.1.i586.rpm < ... stuff ... > And then for the source package, there's: =Pkg: k3b 0.11.7 23.1 src =Loc: 3 k3b-0.11.7-23.1.src.rpm src < ... stuff ... > =Shr: k3b 0.11.7 23.1 i586 These two descriptions clearly relate the packages to each other. Does the "src" token in the "=Pkg:" statement inform YaST2 not to show it in a search?? -- Charlie -----Original Message----- From: Ness, Todd [mailto:todd.ness@eds.com] Sent: Wednesday, March 09, 2005 4:43 PM To: suse-autoinstall@suse.com Subject: RE: [suse-autoinstall] YaST2 Doesn't Search for Source Packages Try to grep src out of the CD1/suse/setup/descr/packages if it is in there I think the yast sw_single module should be able to see it. You can create packages files with /usr/lib/YaST2/bin/create_package_descr -----Original Message----- From: Suffin, Charles [mailto:Charles.Suffin@stratus.com] Sent: Wednesday, March 09, 2005 1:27 PM To: suse-autoinstall@suse.com Subject: [suse-autoinstall] YaST2 Doesn't Search for Source Packages Hi guys, This isn't an autoyast question, but it involves an installation server, and I'll bet someone here will know the answer... More to the point, I'm adding packages for my company's software, and I want to do it right! :) With YaST2 pointing at an SLES9 installation server, I find that "Install and Remove Software" does not find the source packages for a given name when you do a search on it (with the filter in search mode). The sources are part of the distro though, and sometimes someone in my dept. wants to study them... For example, the k3b binary package is found if you search for it, but not the source package. The two packages are in the CD1 and CD3 directories, respectively, on the server: ./SUSE-CORE-Version-9/CD1/suse/i586/k3b-0.11.7-23.1.i586.rpm ./SUSE-CORE-Version-9/CD3/suse/src/k3b-0.11.7-23.1.src.rpm The package database on the server (./SUSE-CORE-Version-9/CD1/suse/setup/descr/packages) is standard SLES9, and I see that both the binary and source packages for k3b are listed there. Why doesn't YaST2 find it? Is there something in the syntax of the packages file that indicates whether it should be found by the YaST2 search? Thanks. -- Charlie ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. (http://www.stratus.com) 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com