Bug#725362: node-bones: present but uninstallable on architectures lacking nodejs
Followup-For: Bug #725362 Control: severity -1 serious regardless which solution you take (arch:all or B-D:nodejs), right now the armel binary package is uninstallable, blocking migration to testing (besides the freeze). Andreas
Bug#725362: [Pkg-javascript-devel] Bug#725362: node-bones: present but uninstallable on architectures lacking nodejs
Quoting Colin Watson (2013-10-04 17:34:19) node-bones is present but uninstallable on a number of Debian architectures that lack nodejs. There is no point shipping it on these architectures, and it introduces noise for anything trying to do dependency consistency checks. While it would be possible to fix this by explicitly limiting node-bones' architecture list, this would require keeping that in sync with nodejs over time; so it's better to add an artificial build-dependency on nodejs to ensure that the package will harmlessly enter a dependency-wait state when it isn't available. You'll probably need to get an ftpmaster to manually remove the old binaries after uploading this. * Artificially build-depend on nodejs, to ensure that this package only builds on architectures where nodejs is available. Are you sure the package is really shipped on archs that do not include the interpreter that the _binary_ package depends on, even though _source_ package does not? As also commented in the related bug#725363, I believe it is filtered off by the transition rule for testing, and therefore only is noisy in unstable. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#725362: [Pkg-javascript-devel] Bug#725362: node-bones: present but uninstallable on architectures lacking nodejs
On Sat, Oct 05, 2013 at 01:59:18PM +0200, Jonas Smedegaard wrote: Are you sure the package is really shipped on archs that do not include the interpreter that the _binary_ package depends on, even though _source_ package does not? I'm sure. As also commented in the related bug#725363, I believe it is filtered off by the transition rule for testing, and therefore only is noisy in unstable. Unstable-to-testing migration does not magically filter out some binaries; entire source packages plus all their binaries migrate at once. If there is a problem on one architecture then it blocks the whole migration, so that would still not be an excuse for disregarding this bug; problems that prevent migration to testing need to be addressed. At present, the two cases of Architecture: any packages shipping binaries that depend on nodejs are indeed held out of testing *as a whole source+binaries unit* because of this (and in the case of node-bones, because of other problems too). However, a simple look at http://ftp-master.debian.org/testing/testing_uninst_full.txt demonstrates that many nodejs-dependent packages are indeed in testing in an uninstallable state for architectures that do not include the interpreter in question, due to the IMO misguided decision to make them Architecture: all despite the interpreter having rather limited architecture support. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725362: node-bones: present but uninstallable on architectures lacking nodejs
Package: node-bones Version: 2.0.1+ds1-4 Severity: important Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch saucy node-bones is present but uninstallable on a number of Debian architectures that lack nodejs. There is no point shipping it on these architectures, and it introduces noise for anything trying to do dependency consistency checks. While it would be possible to fix this by explicitly limiting node-bones' architecture list, this would require keeping that in sync with nodejs over time; so it's better to add an artificial build-dependency on nodejs to ensure that the package will harmlessly enter a dependency-wait state when it isn't available. You'll probably need to get an ftpmaster to manually remove the old binaries after uploading this. * Artificially build-depend on nodejs, to ensure that this package only builds on architectures where nodejs is available. diff -Nru node-bones-2.0.1+ds1/debian/control node-bones-2.0.1+ds1/debian/control --- node-bones-2.0.1+ds1/debian/control 2012-09-20 10:00:20.0 +0100 +++ node-bones-2.0.1+ds1/debian/control 2013-10-04 16:26:06.0 +0100 @@ -6,6 +6,7 @@ Build-Depends: debhelper (= 8~) , dh-buildinfo + , nodejs Standards-Version: 3.9.4 Homepage: https://github.com/developmentseed/bones Vcs-Git: git://git.debian.org/collab-maint/node-bones.git Thanks, -- Colin Watson [cjwat...@ubuntu.com] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
