On Tue, 16 May 2006 19:31:02 +0200, Gémes wrote in message 
<[EMAIL PROTECTED]>:

> Bastian Blank írta:
> 
> >severity 367370 normal
> >tags 367370 moreinfo
> >thanks
> >
> >On Mon, May 15, 2006 at 02:32:42PM +0200, Arnt Karlsen wrote:
> >  
> >
> >>Justification: breaks unrelated software
> >>    
> >>
> >
> >You did not show anything which breaks unrelated software.
> >
> >  
> >
> >>...output of: dpkg --abort-after 666 -D 4000 --log=/tmp/ccs.drivel \
> >>--force-all,depends-version,depends,confnew,confmiss,conflicts,remo
> >ve-reinstreq,remove-essential \ >--purge ccs
> >>2006-05-14 20:48:02 status half-configured ccs 1.02.00-4
> >>2006-05-14 20:48:46 remove ccs 1.02.00-4 1.02.00-5
> >>2006-05-14 20:48:46 status half-configured ccs 1.02.00-4
> >>    
> >>
> >
> >This is the log output, not the output of dpkg.
> >
> >Bastian
> >
> >  
> >
> This bug is related with the fact, that the prerm script of ccs tries
> to stop ccs which fails if ccs has problems (magma plugins etc,
> unfortunately there are too many possibilities :-( ).

..yes, ccs either runs, or it doesn't.  Regardless of whether it runs
or not, the script should be able to remove it and update it.  So, if
it runs and needs to be stopped, ccs is ok, in my case it didn't run 
so the script failed, and blocked dpkg, apt etc from updating other
programs too.

> Instead of modifying the init script I would suggest to correct prerm
> scripts to return 0 regardless of the fact of has it succeeded or not
> to stop ccs.

..this is precisely how I got it working, I removed _everything_ 
and put in "exit 0".  ;o)

..hyperestraier has the same prerm script blunder and 
my wee trick works there too.

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to