View Single Post
Posts: 1,463 | Thanked: 1,916 times | Joined on Feb 2008 @ Edmonton, AB
#3
i can try hard coding the dependencies, but i have to remove the
Code:
Depends: ${shlibs:Depends}, ${misc:Depends}
from the original and then put that list instead. Not the end of the world, but it's really not supposed to be done like that...
I already tried adding a
Code:
Recommends: liblua5.1-0
and it made no difference. As far as I can tell, after reading an official debain guide to packaging, that *should* also prompt apt to grab it.
I also simplified the control file as a test, removing the "fake package to ease transition to the new packaging format" or whatever that dummy package said, but that didn't work.
I asked on IRC if it could be confused that liblua is in extras-testing too, maybe blacklisting stuff from there, but MohammadAG said nope.
I think this is level 1 of dependency hell, level 2 - 9 is when it conflicts and you break everything else...

Last edited by Creamy Goodness; 2010-10-28 at 21:43.