tags 338638 -sarge
stop
Bill Allombert [EMAIL PROTECTED] wrote:
tags 338638 sarge
quit
Why do you believe so? As far as I remember the problem, it will be
triggered when the sarge package is removed (instead of upgraded).
Since this will be the case when upgrading to etch (I think the
# correcting myself
found 338638 3.0-20
thanks
Frank Küster [EMAIL PROTECTED] wrote:
I haven't had time to think about this and do any coding. But I believe
it can only be solved by a upload *to*sarge*, because during etch
upgrade there won't be a fallback maintainer script from a new
tags 338638 sarge
quit
Cheers
--
Bill. [EMAIL PROTECTED]
Imagine a large red swirl here.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
3 matches
Mail list logo
