<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><div style="direction: inherit;">Hi Holger</div><div style="direction: inherit;"><br></div><div style="direction: inherit;">Thanks for the answer, but I already knew that sid does not have those packages, I was asking what to do about that.</div><div style="direction: inherit;"><br></div><div style="direction: inherit;">The concrete packages libssl1.0.0 and libhiredis010 are determined by the build package procedures. The dependencies in the control file are more generic. Does that mean that I cannot build a package for sid in my jessie system ? Because, when I build it on jessie it injects those dependencies ?</div><div style="direction: inherit;"><br></div><div style="direction: inherit;">Thanks !</div><div style="direction: inherit;">Oleg</div></div><div><br>On Aug 23, 2016, at 4:01 AM, Holger Levsen <<a href="mailto:holger@layer-acht.org">holger@layer-acht.org</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Hi Oleg,</span><br><span></span><br><span>On Tue, Aug 23, 2016 at 12:41:10AM -0700, Oleg Moskalenko wrote:</span><br><blockquote type="cite"><span>the problems that I am having are only with SID. When I run it with</span><br></blockquote><blockquote type="cite"><span>jessie, everything is fine.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>So, what is special about sid, how I can set those dependencies so</span><br></blockquote><blockquote type="cite"><span>that they work both for sid and jessie ?</span><br></blockquote><span></span><br><span><a href="https://tracker.debian.org/coturn">https://tracker.debian.org/coturn</a> gives you two hints:</span><br><span></span><br><span>----begin-quote----</span><br><span>This package will soon be part of the auto-openssl transition. You</span><br><span>might want to ensure that your package is ready for it. You can probably</span><br><span>find supplementary information in the debian-release archives or in the</span><br><span>corresponding <a href="http://release.debian.org">release.debian.org</a> bug.</span><br><span></span><br><span>This package will soon be part of the auto-libevent transition. You</span><br><span>might want to ensure that your package is ready for it. You can probably</span><br><span>find supplementary information in the debian-release archives or in the</span><br><span>corresponding <a href="http://release.debian.org">release.debian.org</a> bug. </span><br><span>----end-quote----</span><br><span></span><br><span>it also says "piuparts found (un)installation error(s) " and links to</span><br><span><a href="https://piuparts.debian.org/sid/source/c/coturn.html">https://piuparts.debian.org/sid/source/c/coturn.html</a> which links to</span><br><span><a href="https://piuparts.debian.org/sid/state-dependency-does-not-exist.html#coturn">https://piuparts.debian.org/sid/state-dependency-does-not-exist.html#coturn</a></span><br><span>which tells you </span><br><span></span><br><span>    coturn (0, 0) (Debian VoIP Team <<a href="mailto:pkg-voip-maintainers@lists.alioth.debian.org">pkg-voip-maintainers@lists.alioth.debian.org</a>>)</span><br><span>        dependency libhiredis0.10 is does-not-exist</span><br><span>        dependency libssl1.0.0 is does-not-exist</span><br><span></span><br><span>which pretty much explains why.</span><br><span></span><br><span>Your package depends on packages which don't exist in sid anymore.</span><br><span></span><br><span></span><br><span>-- </span><br><span>cheers,</span><br><span>    Holger</span><br></div></blockquote></body></html>