Bug 2074716

Summary: lapack-3.10.1 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: lapackAssignee: Tom "spot" Callaway <spotrh>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: frantisek.kluknavsky, spotrh
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: lapack-3.10.1-1.fc35 lapack-3.10.1-1.fc36 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-02 07:08:24 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
Update to 3.10.1 (#2074716) none

Description Upstream Release Monitoring 2022-04-12 21:39:06 UTC
Latest upstream release: 3.10.01
Current version/release in rawhide: 3.10.0-5.fc36
URL: http://www.netlib.org/lapack/

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/1534/

Comment 1 Upstream Release Monitoring 2022-04-12 21:39:10 UTC
Scratch build failed. Details below:

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

StdOut:
error: Bad source: ./v3.10.01.tar.gz: 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 2 Upstream Release Monitoring 2022-04-12 23:02:57 UTC
Latest upstream release: 3.10.1
Current version/release in rawhide: 3.10.0-5.fc36
URL: http://www.netlib.org/lapack/

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/1534/

Comment 3 Upstream Release Monitoring 2022-04-12 23:03:03 UTC
Created attachment 1872042 [details]
Update to 3.10.1 (#2074716)

Comment 4 Upstream Release Monitoring 2022-04-12 23:08:00 UTC
the-new-hotness/release-monitoring.org's scratch build of lapack-3.10.1-1.fc34.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=85582713

Comment 5 Fedora Update System 2022-04-24 17:20:00 UTC
FEDORA-2022-081b6f017d has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-081b6f017d

Comment 6 Fedora Update System 2022-04-24 18:44:24 UTC
FEDORA-2022-c1063ab2a6 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-c1063ab2a6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c1063ab2a6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-04-24 20:43:30 UTC
FEDORA-2022-081b6f017d has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-081b6f017d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-081b6f017d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-05-02 07:08:24 UTC
FEDORA-2022-081b6f017d has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2022-05-07 04:30:59 UTC
FEDORA-2022-c1063ab2a6 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.