On 06/05/2015 03:21 AM, Fabrizio Regalli wrote: > Package: java-package > Version: 0.59 > Severity: wishlist > Tags: patch > > Hi, > > during the creation of java package provided by java-package software on > a pretty new Debian 8 box, I encountered the following error: > > dpkg-buildpackage: source changed by Debian Java Maintainers > <pkg-java-maintain...@lists.alioth.debian.org> > sh: 1: gcc: not found > dpkg-architecture: warning: couldn't determine gcc system type, falling > back to default (native compilation) > > solved with 'apt-get install gcc' and > > ... > dpkg-checkbuilddeps: Unmet build dependencies: build-essential:native > ... > > solved with 'apt-get install build-essential' > What I'd like to suggest is to add those packages as dependencies > Attached you can find a patch - feel free to add at your convenience.
Hello Fabrizio, Thank you for the patch. I didn't catch this in the last round of dependency updates because pbuilder chroots always have build-essential installed, and build-essential already depends on gcc. Note that gcc is already in the Recommends for java-package, and that the first warning you are referencing is just a warning. You can refer to these bug reports for prior discussion of the gcc issue [1], [2]. Regarding the issue with dpkg-checkbuilddeps, again, that package already recommends build-essential - perhaps recommends isn't strong enough. However, for java-package, I don't really agree that requiring gcc is overly heavy-weight in the overall scheme of things. It's not as if users will want to run make-jpkg on every system in a cluster, and so requiring gcc seems nominal. I'll give it some more thought, but suspect it's best to depend on build-essential and be done with it. Cheers, tony [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=281766 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=405814
signature.asc
Description: OpenPGP digital signature
