Hi,
via this bug I learned (the hard way) that a
Depends: ${js:Depends}
will be resolved into
libjs-jquery (<< 1.11.3+dfsg.0~), libjs-jquery (>= 1.11.3+dfsg)
(for instance) in the final package. I have no reason to assume that
the actual version that was available at package build time is the only
valid dependency for my package. So it seems unadvisable to use
${js:Depends} depends at all to avoid continuous uploading of the
package (depending from 9 different libjs-* packages) if any of its
libjs-* was uploaded with a new version.
I wonder what the idea behind this resulution of the ${js:Depends}
would be since I have the feeling that this is not sensible in the
most practical cases.
Am I missing something?
Kind regards
Andreas.
On Wed, Apr 13, 2016 at 12:33:41PM +0200, Andreas Beckmann wrote:
> Package: r-cran-shiny
> Version: 0.13.1+dfsg-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package is no longer
> installable in sid:
>
> 1m45.1s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpmbw__d',
> 'apt-get', '-y', 'install', 'r-cran-shiny']
> 1m45.6s DUMP:
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
> r-cran-shiny : Depends: libjs-jquery (< 1.11.3+dfsg.0~) but 1.12.3-1 is to
> be installed
> E: Unable to correct problems, you have held broken packages.
>
>
> Cheers,
>
> Andreas
>
> _______________________________________________
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>
--
http://fam-tille.de
