Re: nodejs-dev: broken/uninstallable backports
On 5 May 2017, at 16:42, Andreas Tille <tille@debian.org> wrote:
> On Mon, May 01, 2017 at 05:44:48PM +0100, James Clarke wrote:
>>> On Mon, May 01, 2017 at 12:39:58PM +0000, Holger Levsen wrote:
>>>>
>>>> according to https://piuparts.debian.org/jessie2bpo/state-dependency-does-not-exist.html
>>>> there are 8 packages in jessie-backports with depends which cannot be
>>>> satisfied.
>>>
>>> nodejs-dev (0, 0) (Debian Javascript Maintainers <pkg-javascript-devel@lists.alioth.debian.org>)
>>> dependency libssl1.0-dev is does-not-exist
>>>
>>> persists on your list and I'd be happy about any hint how to fix this.
>>
>> I believe that would be [1], which should instead be libssl-dev. The version
>> restriction should (presumably) stay; 1.0.2 is available in backports.
>
> Unfortunately my fix do not helped and nodejs-dev remains on the page
> linked by Holger. I keep on thinking that this is a false positive.
The version in jessie-bpo hasn't changed.
I notice from coccia's logs that someone (you?) attempted an upload:
> May 1 19:21:50 processing /nodejs_6.9.1~dfsg-1~bpo8+1_amd64.changes
> May 1 19:21:50 nodejs_6.9.1~dfsg-1~bpo8+1_amd64.changes: does not start with a clearsigned message
> May 1 19:21:50 /nodejs_6.9.1~dfsg-1~bpo8+1_amd64.changes has bad PGP/GnuPG signature!
> May 1 19:21:50 Removing /nodejs_6.9.1~dfsg-1~bpo8+1_amd64.changes, but keeping its associated files for now.
As well as not being signed properly, this is the wrong version; you should be
uploading a backport of 4.8.2~dfsg-1, since that's the current version in
stretch.
Regards,
James
Reply to: