Janne Karhunen a écrit :
G'd day,
Hi,
Y2 package manager (qt+curses) is giving me some unnecessary headache. First, it started to hang on initialization after adding sunet as installation source. Having removed it, it still hangs. Hmm; some installation source not responding and y2pm is just not able report it?
That's why I mirrored the mostly used sources : inst-source, inst-source-java, inst-source-extra, supplementary/KDE ...
Anyhoo, i tried removing all sources + adding a set of new ones. While doing that i noticed that if I add any of the extra repositories (such as Packman) it does indeed add it, but same entry is shown dozen times in installation sources menu. Hrmh. So, how do I make y2pm to start from a clean table again?
I've never had this but I think that removing all the IS_CACHE_0x0000000? directories in var/adm/YaST/InstSrcManager/ will do the trick. You have to add your clean sources then. I've noticed that refresh source doesn't seem to work very well :-( Also that sources are not always up to date : it's not always YaST fault ;-) For exemple, packman do provide libvorbis-1.1.1-0.pm.0 but the corresponding entry aren't in the packages, packages.DU and packages.en files used for the yast repository so you won't get a chance to upgrade suse version to packman's even if packman is the first source as Yast doesn't even know it exists. It seems quite complex to maintain a yast repository so be cool as everybody's doing his best for all this to work. Regards MaNU
--