Bug 1939969

Summary: boost-1.81.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: boostAssignee: Jonathan Wakely <jwakely>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: code, dakingun, denis.arnaud_fedora, jwakely, kkeithle, laurent.rineau__fedora, romulasry, trodgers
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: boost-1.81.0-0.fc39 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-27 23:50:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
[patch] Update to 1.78.0 (#1939969)
none
Update to 1.79.0 (#1939969)
none
Update to 1.80.0 (#1939969)
none
Update to 1.81.0 (#1939969) none

Description Upstream Release Monitoring 2021-03-17 11:11:23 UTC
Latest upstream release: 1.76.0.beta1
Current version/release in rawhide: 1.75.0-3.fc34
URL: http://www.boost.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/6845/

Comment 1 Upstream Release Monitoring 2021-03-17 11:11:43 UTC
An HTTP error occurred downloading the package's new Source URLs: Getting https://dl.bintray.com/boostorg/release/1.76.0.beta1/source/boost_%{version_enc}.tar.bz2 to ./boost_%{version_enc}.tar.bz2

Comment 2 Upstream Release Monitoring 2021-04-17 02:11:49 UTC
Latest upstream release: 1.76.0
Current version/release in rawhide: 1.75.0-4.fc35
URL: http://www.boost.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/6845/

Comment 3 Upstream Release Monitoring 2021-04-17 02:11:54 UTC
An HTTP error occurred downloading the package's new Source URLs: Getting https://dl.bintray.com/boostorg/release/1.76.0/source/boost_%{version_enc}.tar.bz2 to ./boost_%{version_enc}.tar.bz2

Comment 4 Upstream Release Monitoring 2021-07-14 09:13:41 UTC
Latest upstream release: 1.77.0.beta1
Current version/release in rawhide: 1.75.0-8.fc35
URL: http://www.boost.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/6845/

Comment 5 Upstream Release Monitoring 2021-07-14 09:13:50 UTC
An HTTP error occurred downloading the package's new Source URLs: Getting https://dl.bintray.com/boostorg/release/1.77.0.beta1/source/boost_%{version_enc}.tar.bz2 to ./boost_%{version_enc}.tar.bz2

Comment 6 Upstream Release Monitoring 2021-08-11 16:09:00 UTC
Latest upstream release: 1.77.0
Current version/release in rawhide: 1.76.0-4.fc35
URL: http://www.boost.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/6845/

Comment 7 Upstream Release Monitoring 2021-08-11 16:09:07 UTC
An HTTP error occurred downloading the package's new Source URLs: Getting https://boostorg.jfrog.io/artifactory/main/release/1.77.0/source/boost_%{version_enc}.tar.bz2 to ./boost_%{version_enc}.tar.bz2

Comment 8 romulasry 2021-11-06 18:53:07 UTC
This should be an easy fix:
Change it from %{version_enc} to %{version}

https://boostorg.jfrog.io/artifactory/main/release/1.77.0/source/boost_%{version}.tar.bz2
./boost_%{version}.tar.bz2

That should fix it.

Comment 10 Jonathan Wakely 2021-11-08 11:26:40 UTC
No, it needs to be boost_%{version_enc}.tar.bz2 so that the 1.77.0 is turned into 1_77_0
The problem was that it was using %%{version_enc} instead, and that has already been fixed:
https://src.fedoraproject.org/rpms/boost/c/3824fb19034c59a1dd5377abdb0719535931f51d

Comment 11 Upstream Release Monitoring 2021-11-11 21:39:55 UTC
Latest upstream release: 1.78.0.beta1
Current version/release in rawhide: 1.76.0-6.fc36
URL: http://www.boost.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/6845/

Comment 12 Upstream Release Monitoring 2021-11-11 21:40:00 UTC
Skipping the scratch build because an SRPM could not be built: ['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-b7qv4mad/boost.spec'] returned 1: b'warning: line 357: Possible unexpanded macro in: Requires: python(abi) = %{python3_version}\nerror: Bad source: ./boost_1_78_0_beta1.tar.bz2: No such file or directory\n'

Comment 13 Upstream Release Monitoring 2021-12-08 20:44:06 UTC
Latest upstream release: 1.78.0
Current version/release in rawhide: 1.76.0-6.fc36
URL: http://www.boost.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from anitya: https://release-monitoring.org/project/6845/

Comment 14 Upstream Release Monitoring 2021-12-08 20:44:30 UTC
Created attachment 1845330 [details]
[patch] Update to 1.78.0 (#1939969)

Comment 15 Upstream Release Monitoring 2021-12-08 21:12:24 UTC
the-new-hotness/release-monitoring.org's scratch build of boost-1.78.0-1.fc34.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=79733176

Comment 16 Upstream Release Monitoring 2022-03-16 18:16:48 UTC
Latest upstream release: 1.79.0.beta1
Current version/release in rawhide: 1.76.0-9.fc36
URL: http://www.boost.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/6845/

Comment 17 Upstream Release Monitoring 2022-03-16 18:16:53 UTC
Scratch build failed. Details bellow:

BuilderException: Build started, but failure happened during post build operations:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-5q67a6iu/boost.spec']' returned non-zero exit status 1.

StdOut:
warning: line 366: Possible unexpanded macro in: Requires: python(abi) = %{python3_version}
error: Bad source: ./boost_1_79_0_beta1.tar.bz2: No such file or directory


Traceback:
  File "/usr/local/lib/python3.9/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 188, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Comment 18 Upstream Release Monitoring 2022-04-14 13:40:26 UTC
Latest upstream release: 1.79.0
Current version/release in rawhide: 1.76.0-10.fc37
URL: http://www.boost.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/6845/

Comment 19 Upstream Release Monitoring 2022-04-14 13:40:54 UTC
Created attachment 1872511 [details]
Update to 1.79.0 (#1939969)

Comment 20 Upstream Release Monitoring 2022-04-14 13:46:22 UTC
the-new-hotness/release-monitoring.org's scratch build of boost-1.79.0-1.fc34.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=85667662

Comment 21 Upstream Release Monitoring 2022-07-14 09:43:42 UTC
Releases retrieved: 1.80.0.beta1
Upstream release that is considered latest: 1.80.0.beta1
Current version/release in rawhide: 1.78.0-6.fc37
URL: http://www.boost.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/6845/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/boost

Comment 22 Upstream Release Monitoring 2022-07-14 09:43:47 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-tpz8clw2/boost.spec']' returned non-zero exit status 1.

StdOut:
warning: line 366: Possible unexpanded macro in: Requires: python(abi) = %{python3_version}
error: Bad source: ./boost_1_80_0_beta1.tar.bz2: No such file or directory


Traceback:
  File "/usr/local/lib/python3.10/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line 188, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Comment 23 Upstream Release Monitoring 2022-08-11 18:26:02 UTC
Releases retrieved: 1.80.0
Upstream release that is considered latest: 1.80.0
Current version/release in rawhide: 1.78.0-9.fc37
URL: http://www.boost.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/6845/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/boost

Comment 24 Upstream Release Monitoring 2022-08-11 18:26:52 UTC
Created attachment 1905033 [details]
Update to 1.80.0 (#1939969)

Comment 25 Upstream Release Monitoring 2022-08-11 18:36:31 UTC
the-new-hotness/release-monitoring.org's scratch build of boost-1.80.0-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=90707488

Comment 26 Jonathan Wakely 2022-08-22 13:19:14 UTC
(In reply to Upstream Release Monitoring from comment #25)
> the-new-hotness/release-monitoring.org's scratch build of
> boost-1.80.0-1.fc36.src.rpm for rawhide failed
> http://koji.fedoraproject.org/koji/taskinfo?taskID=90707488

Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.kLjO1g
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/BUILD
+ rm -rf boost_1_80_0
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/boost_1_80_0.tar.bz2
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd boost_1_80_0
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ find ./boost -name '*.hpp' -perm /111
+ xargs chmod a-x
chmod: missing operand after 'a-x'
Try 'chmod --help' for more information.
error: Bad exit status from /var/tmp/rpm-tmp.kLjO1g (%prep)

Something is very wrong if there are no .hpp files in the release tarball!

Comment 27 Ben Beasley 2022-08-22 13:29:49 UTC
(In reply to Jonathan Wakely from comment #26)
> Something is very wrong if there are no .hpp files in the release tarball!

There are no *executable* .hpp files in the release tarball.

Comment 28 Jonathan Wakely 2022-08-22 13:34:58 UTC
Ha yes, of course. Maybe Boost finally fixed this longstanding isue ... or maybe it's just a blip for this release.

We should use xargs -r there.

Comment 29 Thomas Rodgers 2022-08-29 00:51:42 UTC
I have applied this change to the current boost.spec, no apparent issues, so I am going to push the change, but I am not quite ready to commit to the rest of the work to move to 1.80.0.

Comment 30 Laurent Rineau 2022-09-15 13:42:49 UTC
(In reply to Thomas Rodgers from comment #29)
> I have applied this change to the current boost.spec, no apparent issues, so
> I am going to push the change, but I am not quite ready to commit to the
> rest of the work to move to 1.80.0.

What would be the work to update to 1.80.0?

Side note: I am the maintainer of the CGAL package of Fedora, and for next release of CGAL (5.6, planned in November-December 2022), Boost-1.80 or later would be a nice bonus (it will not be required, but with Boost-1.80, CGAL-5.6 will become fully header-only without required binary dependencies).

Comment 31 Thomas Rodgers 2022-09-15 16:02:27 UTC
It requires a system-wide change proposal. There are about 180 dependent packages that need to be assessed for impact with each release we decide to ship. Usually there are a handful of patches that need to be adjusted/dropped/picked up in each release. All of this needs to be done in a side-tag, and you need a proven packager to bump the rpm specs of the various dependent packages, such as yours during the build process.

It's a solid commitment of 2-3 weeks worth of time, every time.

Comment 32 Laurent Rineau 2022-09-16 13:55:06 UTC
(In reply to Thomas Rodgers from comment #31)
> It requires a system-wide change proposal. There are about 180 dependent
> packages that need to be assessed for impact with each release we decide to
> ship. Usually there are a handful of patches that need to be
> adjusted/dropped/picked up in each release. All of this needs to be done in
> a side-tag, and you need a proven packager to bump the rpm specs of the
> various dependent packages, such as yours during the build process.
> 
> It's a solid commitment of 2-3 weeks worth of time, every time.

I thank you for that message. That is easy for users like me to complain, and we usually do not see what work such a change could trigger.

...Now I know I will not talk about the similar bug #2036372. ;-)

Comment 33 Upstream Release Monitoring 2022-11-17 23:20:23 UTC
Releases retrieved: 1.81.0.beta1
Upstream release that is considered latest: 1.81.0.beta1
Current version/release in rawhide: 1.78.0-9.fc37
URL: http://www.boost.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/6845/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/boost

Comment 34 Upstream Release Monitoring 2022-11-17 23:20:28 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-5zdekzn1/boost.spec']' returned non-zero exit status 1.

StdOut:
warning: line 367: Possible unexpanded macro in: Requires: python(abi) = %{python3_version}
error: Bad source: ./boost_1_81_0_beta1.tar.bz2: No such file or directory


Traceback:
  File "/usr/local/lib/python3.10/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line 188, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Comment 35 Upstream Release Monitoring 2022-12-14 15:52:41 UTC
Releases retrieved: 1.81.0
Upstream release that is considered latest: 1.81.0
Current version/release in rawhide: 1.78.0-9.fc37
URL: http://www.boost.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/6845/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/boost

Comment 36 Upstream Release Monitoring 2022-12-14 15:53:14 UTC
Created attachment 1932649 [details]
Update to 1.81.0 (#1939969)

Comment 37 Upstream Release Monitoring 2022-12-14 16:13:58 UTC
the-new-hotness/release-monitoring.org's scratch build of boost-1.81.0-1.fc36.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=95358477

Comment 38 Jonathan Wakely 2022-12-14 17:49:49 UTC
(In reply to Jonathan Wakely from comment #28)
> We should use xargs -r there.

Done now on rawhide.