[opensuse-buildservice] autoreconf missing in build
Hi, while at it, I find it a little surprising (again), that a package like python3 cannot be built in a new project due to a missing autoconf package. https://build.opensuse.org/project/monitor/home:frispete:python3 https://build.opensuse.org/package/live_build_log/home:frispete:python3/pyth... Is that to be expected? IOW, do I really need to adjust projects with something like Preinstall: autoconf in prjconf? Cheers, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hans-Peter Jansen <hpj@urpla.net> writes:
while at it, I find it a little surprising (again), that a package like python3 cannot be built in a new project due to a missing autoconf package.
autoconf hasn't been part of the default build environment since 12.2. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Dienstag, 26. November 2013 13:28:29 Andreas Schwab wrote:
Hans-Peter Jansen <hpj@urpla.net> writes:
while at it, I find it a little surprising (again), that a package like python3 cannot be built in a new project due to a missing autoconf package.
autoconf hasn't been part of the default build environment since 12.2.
Okay, I see. Doesn't that mean, that about 90% of all packages using it are broken in this regard, then? BTW, I branched python3 from openSUSE:Factory. Why did the build not fail there? autoconf is not mentioned in factory's prjconf, hence it must be pulled by an side effect of some other preinstalled package. Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hans-Peter Jansen <hpj@urpla.net> writes:
BTW, I branched python3 from openSUSE:Factory. Why did the build not fail there?
autoconf is required by automake. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday 2013-11-26 13:49, Hans-Peter Jansen wrote:
On Dienstag, 26. November 2013 13:28:29 Andreas Schwab wrote:
Hans-Peter Jansen <hpj@urpla.net> writes:
while at it, I find it a little surprising (again), that a package like python3 cannot be built in a new project due to a missing autoconf package.
autoconf hasn't been part of the default build environment since 12.2.
Okay, I see. Doesn't that mean, that about 90% of all packages using it are broken in this regard, then?
Nope, because "all™" packages have it explicitly BuildRequires, because, turned out (in the 12.2/12.3 release cycle) that not so many packages need autotools installed all the time. And for those who do, it was addressed as far as openSUSE releases went. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Dienstag, 26. November 2013 13:59:48 Jan Engelhardt wrote:
On Tuesday 2013-11-26 13:49, Hans-Peter Jansen wrote:
On Dienstag, 26. November 2013 13:28:29 Andreas Schwab wrote:
Hans-Peter Jansen <hpj@urpla.net> writes:
while at it, I find it a little surprising (again), that a package like python3 cannot be built in a new project due to a missing autoconf package.
autoconf hasn't been part of the default build environment since 12.2.
Okay, I see. Doesn't that mean, that about 90% of all packages using it are broken in this regard, then?
Nope, because "all™" packages have it explicitly BuildRequires, because, turned out (in the 12.2/12.3 release cycle) that not so many packages need autotools installed all the time. And for those who do, it was addressed as far as openSUSE releases went.
Sorry, I was bitten by the fact of reusing an project with old versions lying around, and just osc linkpac -f'ing them with the current packages. This does keep the local changes, which is a good thing, but not in this case. I'm sorry for the churn, beg my pardon, Andreas and Jan. Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 26.11.2013 12:36, Hans-Peter Jansen wrote:
Hi,
while at it, I find it a little surprising (again), that a package like python3 cannot be built in a new project due to a missing autoconf package.
https://build.opensuse.org/project/monitor/home:frispete:python3 https://build.opensuse.org/package/live_build_log/home:frispete:python3/pyth...
Is that to be expected?
IOW, do I really need to adjust projects with something like
Preinstall: autoconf
in prjconf?
No, your package needs to buildrequire it - and your pacakge removes the buildrequire: http://s.kulow.org/python-rdiff Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (4)
-
Andreas Schwab -
Hans-Peter Jansen -
Jan Engelhardt -
Stephan Kulow