[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

nodejs backport unbuildable



Hi!

The nodejs backport that was recently uploaded cannot actually be built. The 
backport looks to have been built in an unclean environment where a newer 
version of the "gyp" package than is present in wheezy+wheezy-backports was 
installed.

https://buildd.debian.org/status/package.php?p=nodejs&suite=wheezy-backports

Trying to understand this problem raised a number of issues:

(a) Should we develop automated mechanisms to check dependencies and build-
dependencies prior to accepting packages into backports (either through NEW 
or directly). Can't backport's dak do that for us? This appears to be a 
recurring problem.

(b) Can we get the backporters list fixed? the list is still not being 
updated (and hasn't been for some months now)

    http://backports.debian.org/changes/wheezy-backports.html

(c) The PTS (new or old) doesn't include backports uploads in the News 
section -- is this intentional or just because no-one has added it yet?

(d) The package search function is still listing lenny+squeeze as options 
and not wheezy

   http://backports.debian.org/Packages/


Finally and not entirely related... 

(e) As has been raised numerous times before, the sources.list parts of the 
instructions page are somewhere between misleading and wrong.


I've raised these issues in the past and others have too but even offers of 
help seem to be met with silence. How can we make some progress at sorting 
out these things?

cheers
Stuart


-- 
Stuart Prescott    http://www.nanonanonano.net/   stuart@nanonanonano.net
Debian Developer   http://www.debian.org/         stuart@debian.org
GPG fingerprint    BE65 FD1E F4EA 08F3 23D4 3C6D 9FE8 B8CD 71C5 D1A8




Reply to: