Latest upstream release: 3.1.3-beta-1 Current version/release in rawhide: 3.0.2-5.fc36 URL: https://www.audacityteam.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/139/
Skipping the scratch build because an SRPM could not be built: ['fedpkg', '--user', 'hotness', 'sources'] returned 1: b''
This is a beta, but I have been working on preparing an update to 3.1.2. It is actually a somewhat involved change, and I have it building but it currently segfaults when I try to open a previously saved project. I need to diagnose that before I can finish the upgrade.
Turns out it was firing an assert on project load. Upstream issue I opened was https://github.com/audacity/audacity/issues/2216, which has a fix merged in and will be released with 3.1.3.
Latest upstream release: 3.1.3 Current version/release in rawhide: 3.0.2-5.fc36 URL: https://www.audacityteam.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/139/
Scratch build failed. Details bellow: GenericError: File upload failed: cli-build/1640345359.6442113.aCMaFtpn/audacity-3.1.3-1.fc34.src.rpm 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 198, in build output["build_id"] = self._scratch_build(session, package.name, srpm) File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 451, in _scratch_build session.uploadWrapper(source, serverdir) File "/usr/lib/python3.9/site-packages/koji/__init__.py", line 3000, in uploadWrapper self.fastUpload(localfile, path, name, callback, blocksize, overwrite, volume=volume) File "/usr/lib/python3.9/site-packages/koji/__init__.py", line 2935, in fastUpload raise GenericError("File upload failed: %s/%s" % (path, name)) 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
Looks like this needs conan, not in Fedora yet.
It doesn't actually need conan. I worked with upstream during the 3.1 release to allow for building using local system libraries and to disable networking support more fully. All of this is controlled by CMake flags we pass to it. I have an update to the spec file already in progress (I did it for the 3.1.2 release), but hadn't pushed it due to the assert failing on my compiled RPM (making the built Audacity package unusable). I am travelling now, but should be able to be back at the computer with the updated spec in about 2 weeks.
The version of audacity currently in f34 / f35 is really buggy. Not possible to save a project to the new audacity format, the audio tracks are not correctly reoopened. So, I really vote for an update of audacity on f34 / f35 ...
I am happy to do some testing if there is a new build. Would be awesome if 3.1.3 is packaged.
FEDORA-2022-d435c74328 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d435c74328
FEDORA-2022-857f49ff15 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-857f49ff15
FEDORA-2022-857f49ff15 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-857f49ff15` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-857f49ff15 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-d435c74328 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-d435c74328` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d435c74328 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-d435c74328 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-857f49ff15 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.