12.11.2014 22:45, Aurelien Jarno wrote: > On Wed, Nov 12, 2014 at 09:17:20PM +0400, Michael Tokarev wrote: >> Should I list them all in the build-deps? If yes, what's the complete list?
> It should be libc6-dev[linux-any !alpha !ia64] | libc6.1-dev [alpha ia64] | > libc0.1-dev (>> 2.19-12~) [kfreebsd-any] | libc0.3 (2.19-12~) [hurd-any] Please double-check: Build-Depends: # glibc static-nss #754813, 2.19..2.19-11, -12 is ok libc6-dev (>> 2.19-12~) [linux-any !alpha !ia64] | libc6-dev (<< 2.19) [linux-any !alpha !ia64] | libc6.1-dev (>> 2.19-12~) [alpha ia64] | libc6.1-dev (<< 2.19) [alpha ia64] | libc0.1-dev (>> 2.19-12~) [kfreebsd-any] | libc0.1-dev (<< 2.19) [kfreebsd-any] | libc0.3-dev (>> 2.19-12~) [hurd-any] | libc0.3-dev (<< 2.19) [hurd-any], Since this is all alternatives, is it really necessary to list the [arch] names? I mean, just list of pkgs with versions should be enough I think, each arch will pick the right name, no? Thanks, /mjt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5463cb2b.9050...@msgid.tls.msk.ru
