stable

boost-1.81.0-9.fc40

FEDORA-2023-fc189d7673 created by spot a year ago for Fedora 40

Automatic update for boost-1.81.0-9.fc40.

Changelog
* Tue Aug 29 2023 Tom Callaway <spot@fedoraproject.org> - 1.81.0-9
- apply upstream fixes for failing random tests
* Sun Aug 20 2023 Kefu Chai <tchaikov@fedoraproject.org> - 1.81.0-8
- Add patch for Boost.Accumulators bug
  See https://github.com/boostorg/accumulators/pull/54
* Wed Aug  2 2023 Tom Callaway <spot@fedoraproject.org> - 1.81.0-7
- add symlink for b2 files


Automatic update for boost-1.81.0-8.fc40.

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2023-fc189d7673

This update was automatically created

a year ago

This update has obsoleted boost-1.81.0-8.fc40, and has inherited its bugs and notes.

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'failed'.

a year ago

Looks like the tests failed here:

:: [ 21:19:46 ] :: [  BEGIN   ] :: Running 'cd /home/boost.HaBUzVqRpH/BUILD/boost*'
/usr/share/beakerlib/testing.sh: line 896: cd: too many arguments
:: [ 21:19:47 ] :: [   FAIL   ] :: Command 'cd /home/boost.HaBUzVqRpH/BUILD/boost*' (Expected 0, got 1)
:: [ 21:19:47 ] :: [  BEGIN   ] :: Running 'su -c './bootstrap.sh &>/home/boost.HaBUzVqRpH/bootstrap.log' bstbld'
:: [ 21:19:47 ] :: [   FAIL   ] :: Command 'su -c './bootstrap.sh &>/home/boost.HaBUzVqRpH/bootstrap.log' bstbld' (Expected 0, got 127)

/me throws his hands up in the air, just can't win

User Icon mkolar commented & provided feedback a year ago
karma

It's a false positive, manually passed. I can confirm that the failing tests have been fixed.

The issue is caused by a new rpm build behavior. The rpmbuild -bp SPECS/*.spec command for some reason generates two BUILD/boost* directories (boost_1_81_0 and boost_1_81_0_SPECPART). The testcase only expects one directory and that's why command cd /home/boost.HaBUzVqRpH/BUILD/boost* failed with cd: too many arguments.

So the testcase needs to be adapted to the new behavior. Does anyone know where boost_1_81_0_SPECPART came from?

rpm-4.18.92.tar.bz2 tarball of rpm package contain the guilty code. Older rpm-4.18.91.tar.bz2 doesn't generate mentioned directory:

--- rpm-4.18.91/macros.in   2023-06-09 13:32:52.000000000 +0200
+++ rpm-4.18.92/macros.in    2023-08-01 14:37:23.000000000 +0200
@@ -262,6 +267,9 @@
 #  Build root path, where %install installs the package during build.
 %buildroot   %{_buildrootdir}/%{NAME}-%{VERSION}-%{RELEASE}.%{_arch}

+#  Path for spec file snippets generated during build
+%specpartsdir %{_builddir}/%{buildsubdir}-SPECPARTS
+
 #  Directory where temporaray files can be created.
 %_tmppath    %{_var}/tmp

@@ -752,11 +760,12 @@
   RPM_SOURCE_DIR=\"%{_sourcedir}\"\
   RPM_BUILD_DIR=\"%{_builddir}\"\
   RPM_OPT_FLAGS=\"%{optflags}\"\
+  RPM_LD_FLAGS=\"%{?build_ldflags}\"\
   RPM_ARCH=\"%{_arch}\"\
   RPM_OS=\"%{_os}\"\
   RPM_BUILD_NCPUS=\"%{_smp_build_ncpus}\"\
   RPM_SPECPARTS_DIR=\"%{specpartsdir}\"\
-  export RPM_SOURCE_DIR RPM_BUILD_DIR RPM_OPT_FLAGS RPM_ARCH RPM_OS RPM_BUILD_NCPUS RPM_SPECPARTS_DIR\
+  export RPM_SOURCE_DIR RPM_BUILD_DIR RPM_OPT_FLAGS RPM_ARCH RPM_OS RPM_BUILD_NCPUS RPM_SPECPARTS_DIR RPM_LD_FLAGS\
   RPM_DOC_DIR=\"%{_docdir}\"\
   export RPM_DOC_DIR\
   RPM_PACKAGE_NAME=\"%{NAME}\"\

The issue fixed in PR#18.

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'passed'.

a year ago

This update has been submitted for stable by bodhi

a year ago

Please login to add feedback.

Metadata
Type
unspecified
Karma
1
Signed
Content Type
RPM
Test Gating
Autopush Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
0 days
Dates
submitted
a year ago
in testing
a year ago
in stable
a year ago
approved
a year ago

Automated Test Results