On 9/19/2005 9:14 AM Pascal Bleser wrote:
houghi wrote:
On Mon, Sep 19, 2005 at 12:01:30AM +0200, Eberhard Moenkeberg wrote: ... Great. As you know something that is installed via a non-official repo will become locked. This causes it to be excluded from newer versions, wich might be importand in case of security patches. Would this also be handled?
That needs to be adressed by the YaST2 developers. If you use apt or redcarpet, those packages are not "locked", and they may not be. It's a broken approach.
I think some susers take care of this by adding a build-Number with 0.xyz cause every "official" package that suse releases has a 0 there, so it is overwritten by the suse package. Just a workaround as far as I see. OJ -- "Have you ever noticed that the Klingons are all speaking unix? 'Grep ls awk chmod.'' 'Mknod ksh tar imap.' 'Wall fsck yacc!' (that last is obviously a curse of some sort)." Gandalf Parker