Gordon, Well, its difficult to find out what went wrong without looking at the selection files. You can take a look at what those tags in /usr/share/doc/packages/yast2-packagemanager/selection-descr.html which is part of yast2-packagemanager-devel Just adding some packages to the list is sometimes not enough, you also have to see of the selections dependencies are OK. When you say "many packages seem to be missing", where are they missing from? the selection? The package manager? When debugging such issues, it is advised to install the package y2pmsh which is an interactive interface to the packagemanager. It can also be used as a full replacement for the GUI package manager: For example, # y2pmsh Welcome to the YaST2 Package Manager! This tool is meant for debugging purpose only. initializing installation sources ... initializing target ... reading RPM database .......................................................................................................... ok type help for help, ^D to exit [0] y2pm > help allconflicts display all conflicting packages commit commit changes. actually performs installation depends search for depending packages depstats dependency statistics deselect deselect packages marked for installation/removal df display disk space forecast help this screen init initialize packagemanager (happens automatically if needed) install select packages for installation isc install, solve and commit newer show packages with newer candiate available products show installed products remove select package for removal search search for packages selinstall mark selection for installation, need to call solvesel selremove mark selection for removal, need to call solvesel selshow show selection info selsolve solve selection dependencies and apply state to packages selstate show state of selection set set or show variable show show package info solve solve dependencies source manage installation sources sourceorder set installation order for sources state show state of package(s) summary display summary about what would be done on commit unset unset variable upgrade compute upgrade whatconflictswith search for conflicting packages whatdependson search for depending packages whatprovides search for package provides whatrequires search for package requirement why print solve results for arguments [0] y2pm > I hope this will help you find out what is going wrong... Anas Schumacher, Gordon wrote:

I'm trying to make myself a custom package set, by using the command:

create_package_descr -o setup/descr/ -x setup/descr/EXTRA_PROV

as suggested by Ole Streicher, and as contained in section 4.5.3. I do get the "not a directory" warning, and it continues, and seems to complete just fine, claiming to have processed 7233 packages. If I look in the file "packages", I can see my new packages in it. (This repository is a duplicate of the standard SuSE 9.2 Professional one, with one extra .sel file and three new packages added, as a test to start out.)

But when I start YaST afterwards, pointed at this repository, many, many packages seem to be missing! I'm not quite sure what I should be looking for here.

All I did was, I added a file "Maxtor-9.2-i586.sel", which has =Ord: 150 (I'm not at all sure what that is for!) and three packages in the +Ins: section, and is otherwise pretty much identical to the other .sel files. I also added Maxtor-9.2-i586.sel alphabetically in the list in both "selections" and "directory.yast".

Did I miss something? I noticed that the file MD5SUMS is not updated; do I need to regenerate this?