Bug#578047: no reproducible build
Package: squid3 Version: 3.1.3-1 Sorry Luigi, this is not quite done. A packaging change adding --enable-ipv6 to the rules file is also required to prevent a future relapse. The fix I was able to make upstream just makes --enable-ipv6 behave properly when specified. Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#578047: no reproducible build
Luigi Gangitano wrote: Hi Bastian, Adam, you are saying that squid3's configure should fail if optional features cannot be built when requested via --enable- switches. Actually I've seen squid3 behavior in many different projects, so was not expecting it to do anything different. Yes Squid upstream believe in that behaviour as well. A fix is underway to correct this bug. Unfortunately it's deep in the autoconf code, so a simple patch won't be able to be passed down. 3.1.2 will have the correct build pass/fail you require when --enable-ipv6 is specified. Might be 10-15 days for 3.1.2 release though. The upstream fix will not enable Squid-3.1 to build on the failing buildd, only an update to make it support v6 in the kernel will do that. But this will at least make the broken builds finish in FTBS. Il giorno 20/apr/2010, alle ore 19.04, Bastian Blank ha scritto: The build of Debian packages needs to be stable. It must not use state into count that depends on the environment except for build-depends and build-conflicts. squid3 uses a test to detect if ipv6 is supported on the current system, which may return false. Also it must support both split-stack and unified-stack on Linux. I'm not sure what Bastian is talking about requiring split-stack for. The test which fails is the one which determines if v6 is able to build at all and is the pre-dependency test for detecting which stack type to build. spit-stack in Squid currently fails hard under upstream bug 2753. Setting to RC because the behaviour is not sufficient fixed. Ack, and agreed. Amos Jeffries Squid Proxy Project -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#578047: no reproducible build
Hi Bastian, Adam, you are saying that squid3's configure should fail if optional features cannot be built when requested via --enable- switches. Actually I've seen squid3 behavior in many different projects, so was not expecting it to do anything different. I will forward this request upstream and try to develop a patch against configure. Regards, L Il giorno 20/apr/2010, alle ore 19.04, Bastian Blank ha scritto: > The build of Debian packages needs to be stable. It must not use state > into count that depends on the environment except for build-depends and > build-conflicts. > > squid3 uses a test to detect if ipv6 is supported on the current system, > which may return false. Also it must support both split-stack and > unified-stack on Linux. > > Setting to RC because the behaviour is not sufficient fixed. -- Luigi Gangitano -- -- GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#578047: no reproducible build
severity 578047 serious thanks The build of Debian packages needs to be stable. It must not use state into count that depends on the environment except for build-depends and build-conflicts. squid3 uses a test to detect if ipv6 is supported on the current system, which may return false. Also it must support both split-stack and unified-stack on Linux. Setting to RC because the behaviour is not sufficient fixed. Bastian -- Either one of us, by himself, is expendable. Both of us are not. -- Kirk, "The Devil in the Dark", stardate 3196.1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
