> is package doesn't exist.
>  >
>  > (Btw, how did this happen?)
>
>  Wrong entry in Depends. Anyway, this is fixed in SVN since February 15.  I
>  do not know why 2.1+parpack96-2 is not yet released.
easy
the package -1 entered NEW and I waited for it to appear in Debian/unstable
then I forgot about this fix to the deps



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

Reply via email to