Hi,
I recently got a few failed build alerts with suspicious errors about missing commands/libs in the buildroot, despite the builddep step had succeeded. The root.log always contains "Skipping packages with conflicts" listing packages that weren't installed. So DNF now silently skips installation of some packages in koji. That's a problem - there are packages (usually using autoconf) that enable/disable features based on what they see in the environment, so silently skipping package installations may result in sucessful build of package that is missing functionality.
IMO this should be fixed, but I don't know whether it's a regression/feature of DNF or just misconfiguration in koji/mock. Where should I report it?
Michael
On Thu, Sep 22, 2016 at 11:01:56AM +0200, Michael Šimáček wrote:
Hi,
I recently got a few failed build alerts with suspicious errors about missing commands/libs in the buildroot, despite the builddep step had succeeded. The root.log always contains "Skipping packages with conflicts" listing packages that weren't installed. So DNF now silently skips installation of some packages in koji. That's a problem - there are packages (usually using autoconf) that enable/disable features based on what they see in the environment, so silently skipping package installations may result in sucessful build of package that is missing functionality.
IMHO best practice is to *always* pass all the --enable-XXX feature flags to 'configure' that you expect the package to be building with, and not rely on auto-detection. There's plenty of ways that auto-detection can get broken, beyond DNF not installing some pre-reqs, so you want to have a robust build that always fails upfront.
Regards, Daniel
Daniel P. Berrange wrote:
IMHO best practice is to *always* pass all the --enable-XXX feature flags to 'configure' that you expect the package to be building with, and not rely on auto-detection.
But some build setups will still happily ignore the dependency if it is unavailable, even if you explicitly asked for it.
Kevin Kofler
On Thu, 22 Sep 2016 11:01:56 +0200 Michael Šimáček msimacek@redhat.com wrote:
Hi,
I recently got a few failed build alerts with suspicious errors about missing commands/libs in the buildroot, despite the builddep step had succeeded. The root.log always contains "Skipping packages with conflicts" listing packages that weren't installed. So DNF now silently skips installation of some packages in koji. That's a problem - there are packages (usually using autoconf) that enable/disable features based on what they see in the environment, so silently skipping package installations may result in sucessful build of package that is missing functionality.
IMO this should be fixed, but I don't know whether it's a regression/feature of DNF or just misconfiguration in koji/mock. Where should I report it?
AFAIK the "conflicts" are result of weak deps being disabled for builds in koji
Dan
On 2016-09-22 11:12, Dan Horák wrote:
On Thu, 22 Sep 2016 11:01:56 +0200 Michael Šimáček msimacek@redhat.com wrote:
Hi,
I recently got a few failed build alerts with suspicious errors about missing commands/libs in the buildroot, despite the builddep step had succeeded. The root.log always contains "Skipping packages with conflicts" listing packages that weren't installed. So DNF now silently skips installation of some packages in koji. That's a problem - there are packages (usually using autoconf) that enable/disable features based on what they see in the environment, so silently skipping package installations may result in sucessful build of package that is missing functionality.
IMO this should be fixed, but I don't know whether it's a regression/feature of DNF or just misconfiguration in koji/mock. Where should I report it?
AFAIK the "conflicts" are result of weak deps being disabled for builds in koji
Ah, ok. If that's the case, I'll fill a bugreport on DNF to report them correctly (not as conflicts).
Thanks, Michael
If this causes the autoconf not to work as expect, sure we need resolve this issue. But could you give
an example that we can check it in detail.
On 09/22/2016 05:01 PM, Michael Šimáček wrote:
Hi, package https://fedoraproject.org/wiki/Packaging:Guidelines#Modifying_an_existing_package
I recently got a few failed build alerts with suspicious errors about missing commands/libs in the buildroot, despite the builddep step had succeeded. The root.log always contains "Skipping packages with conflicts" listing packages that weren't installed. So DNF now silently skips installation of some packages in koji. That's a problem
- there are packages (usually using autoconf) that enable/disable
features based on what they see in the environment, so silently skipping package installations may result in sucessful build of package that is missing functionality.
IMO this should be fixed, but I don't know whether it's a regression/feature of DNF or just misconfiguration in koji/mock. Where should I report it?
Michael _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org