Bug 1989667

Summary:	restic-0.12.1 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	restic	Assignee:	Steve Miller <code>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	andersonkw2, cglombek, code, pzeppegno, quirin.maier
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	restic-0.12.1-1.fc35	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-29 06:38:30 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:

Description Upstream Release Monitoring 2021-08-03 17:12:33 UTC

Latest upstream release: 0.12.1
Current version/release in rawhide: 0.12.0-1.fc35
URL: https://github.com/restic/restic

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

Comment 1 K. Anderson 2021-08-09 23:42:17 UTC

I believe this will require a bump of golang-github-spf13-cobra to 1.1.3. Cobra related ticket is bug 1927115.

Comment 2 Christian Glombek 2021-12-06 20:52:00 UTC

The version of golang-github-spf13-cobra in Fedora is now 1.2.1.

Any chance this could be looked at soon? I'm happy to help with the packaging work.

Comment 3 pzeppegno 2021-12-12 23:39:51 UTC

Same here. Is there a way I can be of help? I can for sure test the new package.

Comment 4 Steve Miller 2021-12-13 03:45:55 UTC

I will try to build in two weeks.

Comment 5 Christian Glombek 2021-12-20 13:03:34 UTC

It only requires bumping the version, there are no changes in any relevant dependencies.
See https://github.com/LorbusChris/restic-rpm/commit/cc5ba430182b786ed43026ca1505a32a7d7959dc for the commit I used to build on COPR.

I'd be willing to co-maintain the package too if you don't have the cycles for it.

Comment 6 pzeppegno 2022-01-17 00:42:00 UTC

One more month has passed. Any chance to push this thru?

Comment 7 Fedora Update System 2022-01-21 02:21:33 UTC

FEDORA-2022-68bd2fc96b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-68bd2fc96b

Comment 8 Steve Miller 2022-01-21 02:23:07 UTC

Please note that building in rawhide is not working at the moment, investigating. However, f35 works.

Comment 9 Fedora Update System 2022-01-21 18:53:22 UTC

FEDORA-2022-68bd2fc96b 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-68bd2fc96b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-68bd2fc96b

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

Comment 10 pzeppegno 2022-01-27 17:07:37 UTC

I tested the update on my personal server backup. More than 7Tb scanned with 96GiB added, backed-up to a remote minio S3 server. It worked without a hitch. Of course I did not try a restore just yet :-), but I swear I will do a full check tonight.

Thumb up for now.

Comment 11 Fedora Update System 2022-01-29 06:38:30 UTC

FEDORA-2022-68bd2fc96b has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.