Releases retrieved: 1.15.3 Upstream release that is considered latest: 1.15.3 Current version/release in rawhide: 1.15.2-1.fc38 URL: https://github.com/gopasspw/gopass-jsonapi 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/243357/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gopass-jsonapi
Releases retrieved: 1.15.4 Upstream release that is considered latest: 1.15.4 Current version/release in rawhide: 1.15.2-2.fc38 URL: https://github.com/gopasspw/gopass-jsonapi 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/243357/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gopass-jsonapi
Releases retrieved: 1.15.5 Upstream release that is considered latest: 1.15.5 Current version/release in rawhide: 1.15.2-2.fc38 URL: https://github.com/gopasspw/gopass-jsonapi 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/243357/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gopass-jsonapi
Ohai Fale! Would you mind updating gopass-jsonapi please? The following trivial bump worked for me locally: From ec0847843e1227c5f5cc15b523e0254b024702ef Mon Sep 17 00:00:00 2001 From: Evgeni Golov <evgeni> Date: Sat, 24 Jun 2023 16:59:44 +0200 Subject: [PATCH] 1.5.5 --- .gitignore | 1 + gopass-jsonapi.spec | 2 +- sources | 2 +- 3 files changed, 3 insertions(+), 2 deletions(-) diff --git .gitignore .gitignore index a621992..1f790cb 100644 --- .gitignore +++ .gitignore @@ -3,3 +3,4 @@ /gopass-jsonapi-1.15.0.tar.gz /gopass-jsonapi-1.15.1.tar.gz /gopass-jsonapi-1.15.2.tar.gz +/gopass-jsonapi-1.15.5.tar.gz diff --git gopass-jsonapi.spec gopass-jsonapi.spec index 39591a3..4b228ea 100644 --- gopass-jsonapi.spec +++ gopass-jsonapi.spec @@ -3,7 +3,7 @@ # https://github.com/gopasspw/gopass-jsonapi %global goipath github.com/gopasspw/gopass-jsonapi -Version: 1.15.2 +Version: 1.15.5 %gometa %global goname gopass-jsonapi diff --git sources sources index 7cdc805..656e35d 100644 --- sources +++ sources @@ -1 +1 @@ -SHA512 (gopass-jsonapi-1.15.2.tar.gz) = 88d83445b1b3a32fb9046392a27cedd11d4c25ede6899e5fbb28f90ace4d19bd25f92ceb392dc54e65c3623bad8724d08162921b36ef08d3c90bb80c687c3f26 +SHA512 (gopass-jsonapi-1.15.5.tar.gz) = dbc8de9cf16f1c20af1e94bc1c0a7c168b76db28a889f0f51d04f8a922f6ec70fd6b921ef5413708bd6832f79e82521f48feef3f9eb9742062d1e2c806ff3067 -- 2.40.1 Nice benefit, now the version reporting seems to work again, so that gopassbridge does not tell us to use a newer version than 1.8.5…
Releases retrieved: 1.15.6 Upstream release that is considered latest: 1.15.6 Current version/release in rawhide: 1.15.2-3.fc39 URL: https://github.com/gopasspw/gopass-jsonapi 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/243357/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gopass-jsonapi
Releases retrieved: 1.15.7 Upstream release that is considered latest: 1.15.7 Current version/release in rawhide: 1.15.2-3.fc39 URL: https://github.com/gopasspw/gopass-jsonapi 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/243357/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gopass-jsonapi
FEDORA-2023-8900da74ab has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-8900da74ab
FEDORA-2023-8a543758e4 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-8a543758e4
FEDORA-2023-b6804153b4 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b6804153b4
FEDORA-2023-45a3486b53 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-45a3486b53
FEDORA-2023-b6804153b4 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-b6804153b4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b6804153b4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-45a3486b53 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-45a3486b53` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-45a3486b53 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-b6804153b4 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-45a3486b53 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.