[Pkg-javascript-devel] Bug#725363: Bug#725363: present but uninstallable on architectures lacking nodejs
On Sat, Oct 05, 2013 at 02:53:33PM +0200, Jonas Smedegaard wrote: Feels to me that it would be better to fix this at its core instead of covering over it by use of bogus build-dependency. I am sure you've already considered that option, and would appreciate your elaborating more (I saw and tried to follow your conversation on irc, but failed to understand it there). I don't think artificial build-dependencies are a particularly inappropriate fix. Any change to britney to try to have it promote only architectures that worked would amount to accepting permanent technical debt in unstable, which I think is very poor design. Package maintainers should generally be trying to avoid dependency breakage in unstable where they can as well as in testing (or, to put it another way, accepting permanent dependency breakage in unstable makes it harder to see the wood for the trees), and by far the simplest way to do this is to fix the packages rather than blaming the infrastructure for pointing out a real problem. Is there perhaps already a bugreport tracking this flaw of only considering i386 for arcch-compatibility? No idea, sorry. -- Colin Watson [cjwat...@debian.org] ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#725363: Bug#725363: Bug#725363: present but uninstallable on architectures lacking nodejs
On 06/10/2013 11:28, Colin Watson wrote: On Sat, Oct 05, 2013 at 02:53:33PM +0200, Jonas Smedegaard wrote: Feels to me that it would be better to fix this at its core instead of covering over it by use of bogus build-dependency. I am sure you've already considered that option, and would appreciate your elaborating more (I saw and tried to follow your conversation on irc, but failed to understand it there). I don't think artificial build-dependencies are a particularly inappropriate fix. Any change to britney to try to have it promote only architectures that worked would amount to accepting permanent technical debt in unstable, which I think is very poor design. Package maintainers should generally be trying to avoid dependency breakage in unstable where they can as well as in testing (or, to put it another way, accepting permanent dependency breakage in unstable makes it harder to see the wood for the trees), and by far the simplest way to do this is to fix the packages rather than blaming the infrastructure for pointing out a real problem. (I have nothing to say about the general case) for the particular case of node-* packages, it is true that when test suites are or will be run, they will have to build-depend on nodejs. So adding a build-dependency on nodejs for each arch:all module doesn't seem so bad to me today. Jérémy. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#725604: mapnik-reference: FTBFS: /bin/sh: 1: node: not found
Source: mapnik-reference Version: 5.0.5-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20131006 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): debian/rules build dh build dh_testdir dh_auto_configure dh_auto_build make[1]: Entering directory `/«PKGBUILDDIR»' node util/make-datasource-ref.js latest/datasources.template latest/datasources.json /bin/sh: 1: node: not found make[1]: *** [latest/datasources.json] Error 127 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/10/06/mapnik-reference_5.0.5-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
